Drive File RenamerDrive File Renamer
FeaturesPricingGuideGetting startedFAQAboutAlternativesChangelog
FeaturesPricingGuideGetting startedFAQAboutAlternativesChangelog

On this page

What this app accessesWhat is stored, and whereThird partiesRetention & deletionContact
Privacy Policy

Privacy Policy

Last updated: August 2, 2026

What this app accesses

Drive File Renamer requests exactly one sensitive OAuth scope: drive.file. Under that scope, the app can only see or modify files and folders you explicitly select through the Google Picker dialog inside the app. It cannot browse, list, or access any other file in your Google Drive — including files you own but never selected, and files in Shared Drives you haven't picked.

The app also requests:

  • script.external_request — used to call the Paddle API, to check whether your account has an active paid plan, and — if you send feedback through the app — to deliver that feedback to a Google Form. Never used to send your file contents anywhere.
  • userinfo.email — used only to identify your account for plan/billing status and to attach your email to a Paddle Checkout session if you choose to upgrade.

What is stored, and where

  • Rename history (old name → new name per batch, for undo) is stored in your own per-user Apps Script Properties, scoped to your account, never sent to a third party. Capped at the most recent 20 batches — older batches are deleted automatically.
  • Saved rename presets are stored the same way — per-user, private to your account.
  • Billing status (your email address, plan status, Paddle customer ID) is stored in the app owner's Script Properties so the app can check your plan on each visit. Not shared beyond what's needed to query Paddle for subscription status.
  • Feedback you submit (rating, written comments, and — if signed in — your email) is sent to a Google Form/Sheet controlled by the app owner, used only to improve the app. Optional.
  • File contents are never read or stored. The app only reads file names and, if you enable metadata-based renaming, file metadata (created/modified date, size, image EXIF fields) for files you've selected — never file contents.

Third parties

  • Google Drive API — to read and rename the files you select.
  • Paddle — to process payment for paid plans and verify subscription status, acting as merchant of record. Paddle's own privacy policy governs data entered directly into Paddle Checkout (e.g. card details); this app never sees your card details.
  • Google Forms — only if you submit feedback through the app, to deliver it to the app owner.

Data retention and deletion

You can delete your rename history and presets at any time from within the app — undo removes a history batch, and the preset delete button removes a preset. To request deletion of your billing record, contact [email protected].

Contact

Questions about this policy: [email protected].

Drive File RenamerDrive File Renamer

Bulk-rename Google Drive files without handing over your whole Drive.

Product

FeaturesPricingGetting startedAlternatives

Resources

GuideFAQAboutChangelogTesting log

Legal

Privacy policyTerms of service

Connect

GitHub[email protected]
© 2026 Drive File Renamer. Built by codebyjosephdaniel.