Privacy Policy

Effective date: October 24, 2026 (last updated October 24, 2026)

RenameBee (“we”, “us”) is a Chrome extension that renames files in Google Drive. This policy explains exactly what data RenameBee accesses, why, where it is kept, and your choices. The operator of RenameBee is Autopilot Digital LLC (an Illinois LLC in formation), Champaign, Illinois. Contact: support@renamebee.com.

1. The short version

• RenameBee can only access the specific Google Drive files you choose in Google’s file picker.
• It reads file names and basic metadata and changes file names. It never uploads your files, and it does not open what is inside them, except if you ask for AI name suggestions and tick “Also read the first 500 characters of Google Docs and Sheets, on this computer”: then RenameBee asks Google Drive for the text of those Google Docs and Sheets and keeps only the first 500 characters, on your computer (section 3).
• Renaming happens inside your browser. Your files, file names and file details never reach our servers. The one exception is the optional online AI suggestions, which are switched off today and always ask you first (section 3).
• AI name suggestions run on your own computer with Chrome’s built-in AI. The file details and any text it uses are not sent to RenameBee’s servers or anyone else for that; only the number of names you asked for is counted.
• Our small license server stores only your Google account ID (a number), your plan, and usage counts (renames and AI names), so your plan and limits follow your Google account. No name, no email, no file data.
• We do not sell your data, use it for advertising, or use it to train AI models.

2. Google user data we access

RenameBee requests two Google permissions (OAuth scopes): https://www.googleapis.com/auth/drive.file – “See, edit, create, and delete only the specific Google Drive files you use with this app” – and openid, which only tells RenameBee your Google account ID (a number that identifies your account, without your name or email). With drive.file, RenameBee accesses, for the files you select only:

• File ID, file name, file type (MIME type), parent folder ID, created and modified dates, and whether you are allowed to rename it.
• Only if you tick “Also read the first 500 characters of Google Docs and Sheets, on this computer” when asking for AI name suggestions: the text of the Google Docs and Google Sheets you chose. RenameBee asks Google Drive for it with Google’s export function (still limited to those files), keeps only the first 500 characters on your computer, and stops reading the rest. That text is never sent to RenameBee’s servers. Other file types are never opened.

RenameBee does not request access to your whole Drive, your Gmail, contacts or any other Google service. It may also see the email address of the Google account you sign in with only to the extent Chrome’s sign-in shows it; RenameBee does not store or transmit it.

With openid, RenameBee’s license server receives your Google account ID. See section 4.

3. How we use Google user data

We use the file data above only to provide RenameBee’s single, user-facing feature: showing you a preview of new file names (including AI name suggestions when you ask for them), renaming the files you chose, and undoing a rename when you ask. We use your Google account ID only to link your plan and usage limits to your account. We do not use Google user data for any other purpose.

AI name suggestions

When you click “Suggest names”, RenameBee uses each chosen file’s name, file type and created/modified dates (and, only if you ticked the box, the first 500 characters of text of Google Docs and Sheets, kept on your computer) to suggest new names. Suggestions only appear in the preview. You can edit or undo them, and nothing is renamed until you click Rename.

• On your computer (the normal way): RenameBee uses Chrome’s built-in AI (Gemini Nano), which runs on your device. Google says no data is sent to Google or anyone else for this, and RenameBee does not send the file details or text anywhere either. RenameBee only tells its license server how many names you asked for (a number), to count them against your plan’s monthly AI names. Monthly AI names reset on the 1st of each month (UTC). This is separate from the free plan’s daily rename limit, which resets at midnight in your own time zone. Chrome’s built-in AI needs a computer that meets Google’s requirements (Chrome 138 or newer on Windows 10 or 11, macOS 13 or newer, Linux, or a Chromebook Plus with ChromeOS 16389.0.0 or newer; 22 GB of free disk space; and a graphics card with more than 4 GB of memory, or 16 GB of RAM and 4 or more CPU cores) and downloads its model once over a connection without a data limit. Suggestions are in English.
• Online AI (optional, switched off today): if Chrome’s built-in AI can’t run on your computer, a future version may offer online AI instead. RenameBee will ask you before using it. If you agree, the details listed above for the chosen files (never file IDs, real folder IDs or your email) are sent to RenameBee’s license server, which sends them to our AI provider to get name ideas and passes the ideas back. We will name the provider here before turning this on. Neither we nor the provider store this text: we ask the provider not to store it, and it is not used to train AI models. Our server keeps only how many AI names you used this month.

4. Where data is stored and for how long

• Sign-in token: Google issues a short-lived access token that Chrome keeps for RenameBee. It is sent to Google’s APIs (googleapis.com) and to RenameBee’s license server. The license server only asks Google which account the token belongs to, then forgets the token. It is never stored or used to access your Drive.
• Undo history: for your last 10 rename batches (25 on Business), RenameBee keeps each file’s ID, old name and new name in your browser’s extension storage (chrome.storage.local) so “Undo” works. It never leaves your computer. It is deleted when you uninstall the extension.
• License server (plan and usage counters): for each Google account ID: your plan (Free, a paid plan or a 7-Day Pass), subscription status and renewal date, your Stripe customer number if you bought something, when a 7-Day Pass ends, how many free renames you used today (a date and a number; the day ends at midnight in your time zone), whether you used your one free Pro try (yes/no), and how many AI names you used this month (a UTC month and two numbers: total, and how many were made online). For the online AI budget we also keep one running cost total per month for everyone together, not per person. We also keep a short log of Stripe payment event IDs so a payment is never counted twice. This contains no name, no email and no file names or file data. It runs on Cloudflare (Workers and D1). We keep it while you use RenameBee and delete it within 30 days of a request (section 10).
• Usage log and purchase records (for refunds): for each Google account ID, we log each rename (date, time and number of files) and each batch of AI names (date, time and number). It’s counts only: no file names, file IDs or file contents. We use it to check refund requests and answer payment disputes, and delete each entry after 180 days. For each purchase we also keep its Stripe reference numbers, amount, date and refund status, linked to your Google account ID. If you agreed to our Terms at checkout, we keep the exact wording you agreed to and when. We keep purchase records for at least 3 years, even after a deletion request, for tax, refund and payment-dispute reasons (section 10).
• Plan cache: a copy of your plan status and today’s free-plan usage is kept in your browser’s extension storage so RenameBee opens quickly and paid plans keep working offline.
• Selected files list: kept in temporary browser session storage and cleared when you close the browser.
• AI suggestions: kept only in the open RenameBee tab until you rename, undo or close it. The first 500 characters read from Google Docs and Sheets (if you ticked the box) are kept only in memory in that tab while the suggestions are made. Your choice to allow online AI (yes/no) is kept in your browser’s extension storage.
• Apart from your Google account ID, we do not keep any Google user data on our servers.

5. Sharing and transfer

We do not share, sell or transfer Google user data to anyone. The one exception: if you choose the optional online AI suggestions, the file details listed in section 3 go to our AI provider only to create name suggestions for you. File data goes only between your browser and Google (apart from that online option). Your Google account ID is passed to Stripe only as a reference on your own purchase, so your payment can unlock your plan. The file picker page on renamebee.com loads Google’s own Picker code, which talks directly to Google; that page does not record what you pick.

6. Payments (paid plans only)

If you buy one of our paid plans or the 7-Day Pass, RenameBee opens a Stripe checkout page. Payments are handled by Stripe (stripe.com) through Stripe Managed Payments: Stripe, with its Link service, sells the plan to you and handles payments, sales tax, receipts and subscription management under the Stripe Privacy Policy and Link’s terms. You type your email and payment details on Stripe’s page, not in RenameBee.

Stripe tells our license server which Google account ID made the purchase, the plan, and whether payment succeeded, renewed, failed or was canceled, so RenameBee can unlock and lock paid features. Our license server stores the plan details listed in section 4 and your Stripe customer number, but not your email or card details. We can see your email and payment status in our Stripe account to answer support and refund requests. We never see your full card number. Payment data is never combined with your Google Drive data.

7. Analytics, ads and tracking

The RenameBee extension contains no analytics, advertising or tracking code. Our website (renamebee.com) does not use cookies of its own. To count visits, the website uses Cloudflare Web Analytics, which does not use cookies or local storage and does not track you across sites. When you click a button such as “Get notified at launch” or “See pricing”, the website also records an anonymous count of that click (the button name, page and country only; no cookies, no IP address, no email). Neither runs on the file picker page. (Google’s Picker page may set Google cookies under Google’s Privacy Policy.)

7a. Website waitlist

If you join the waitlist on renamebee.com, we store your email address, the time you signed up and, if the link you arrived from had one, a short referral tag (such as “newsletter”). We use your email only to tell you when RenameBee is available in the Chrome Web Store. We do not sell or share it, and we do not add it to any other list. The list is stored in a Cloudflare D1 database that Cloudflare operates for us, separate from the license server. To limit spam, we also keep a one-way, salted hash of your IP address for up to 24 hours; we never store the IP address itself. We keep your email until you ask us to remove it or we stop using the waitlist. To be removed, email support@renamebee.com from that address. The waitlist never contains any Google Drive data.

8. Google API Services User Data Policy – Limited Use

RenameBee’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, we do not transfer Google user data to others except as needed to provide the feature you asked for, for security, to comply with law, or as part of a merger with your consent; we do not use it for advertising; we do not allow humans to read it unless you ask us to for support (and give permission), for security, or to comply with law; and we do not use it to develop, improve or train generalized AI or machine-learning models.

9. Security

All requests to Google, to our license server, to Stripe and to any AI provider use HTTPS. Stripe’s messages to our license server are signature-checked. RenameBee runs only code included in the extension package (no remotely loaded code), and asks for the minimum Chrome permissions: identity (Google sign-in), storage (undo history, settings, plan cache) and access to googleapis.com. Our license server accepts requests only from the RenameBee extension and only with a valid Google sign-in.

10. Your choices and deleting your data

• Remove RenameBee’s access to your Google account any time at myaccount.google.com/connections.
• Uninstalling the extension deletes its undo history, settings and plan cache from your browser.
• You don’t have to use AI suggestions. If you allowed online AI and change your mind, uninstalling and reinstalling RenameBee resets that choice.
• To be removed from the website waitlist, email us from the address you signed up with.
• Usage counts (including the usage log for refunds) are deleted automatically after 180 days.
• Purchase and consent records (Stripe reference numbers, amounts, dates, refund status, the Google account ID they belong to, and your agreement to our Terms) are kept for at least 3 years after the purchase, even if you ask us to delete your data, for tax, refund and payment-dispute reasons. Then they are deleted. Stripe may keep payment records it must keep by law.
• Everything else on our license server (your plan, subscription status and usage counts, including the usage log) is deleted within 30 days of your request. To ask, email us from the Google account you use with RenameBee. Deleting your data does not cancel an active subscription, so please cancel first.

11. Children

RenameBee is not directed to children under 13 and we do not knowingly collect their data.

12. Changes

If this policy changes we will update the date above, and for material changes we will notify users in the extension before the change takes effect.

13. Contact

Questions or requests: support@renamebee.com.