DriveNest never changes anything automatically or silently. It shows you every action and carries it out only when you approve — on Google Drive as a script you run yourself, and now on OneDrive directly in the app. Full control, zero surprises.
DriveNest analyzes your storage with read-only access and never deletes files, revokes sharing, or changes anything automatically or silently. Every cleanup, unshare, or revision action is shown to you in full and happens only when you explicitly approve it. What differs is how an approved action is carried out, and that depends on the cloud — see below.
On Google Drive, DriveNest expresses each action as a script you run yourself. Choose the format that fits your workflow. Google Apps Script can be deployed directly to your Google account with one tap — DriveNest creates a new Apps Script project with the Drive API pre-configured. Bash scripts use the Google Drive CLI tools and run on macOS or Linux. PowerShell scripts work on Windows. All three do the same thing; the format is your choice.
Cleanup scripts move selected files to Google Drive trash. Trashed files remain recoverable for 30 days before permanent deletion. This gives you a generous safety window if you change your mind. Unshare scripts revoke specific sharing permissions — remove individual users, disable link sharing, or restrict access on shared folders. Revision cleanup scripts delete excess revision history for non-Workspace files using the Drive API v3 — including keep-forever revisions that accumulate silently against your quota. See the Revision Overhead page for how DriveNest detects and quantifies this waste. The same three action types — cleanup, unshare, and revision cleanup — are available on OneDrive too; there they run in-app rather than as an exported script (see below).
DriveNest v2 adds OneDrive alongside Google Drive, and the two clouds carry out an approved action differently:
Google Drive — unchanged. Drive keeps the established Google Apps Script model: DriveNest deploys the script to your own Google account with one tap (or you export Bash/PowerShell), and you open it and click Run yourself. Nothing about this changed in v2.
OneDrive — new in-app execution. Because OneDrive has no Apps Script equivalent, v2 adds in-app execution — a capability users requested repeatedly. DriveNest can carry out the same cleanup, unshare, and revision actions directly inside the app. You still review exactly what each action will touch and tap to run it; it is opt-in and never runs silently or in the background.
Whether an action runs in your Google account (Apps Script) or inside the app (OneDrive), the rule is identical: you see exactly what will happen and you trigger it. In-app execution is OneDrive-only — Google Drive continues to use Apps Script deployment exactly as before.
Ultimate subscribers can enable auto-cleanup. When combined with scheduled background scans, DriveNest automatically generates and deploys cleanup scripts for files that are confirmed safe to remove — verified duplicates with high confidence scores. The scripts are deployed to your Apps Script account automatically, but you still need to run them manually. This keeps your Drive clean with minimal effort while maintaining full control over what gets removed.
Scheduled background scans keep your scan data fresh without manual effort. Auto-cleanup takes it further by automatically preparing scripts for confirmed safe duplicates. You stay in control — scripts are deployed but never executed without your action.