Privacy Policy · BatchName

Scope

This policy covers the following products developed by 5KM Tech, LLC (collectively, “the product”), and this website batchname.5km.tech:

BatchName, the macOS app, together with the Safari browser extension it contains
BatchName for Chrome, a browser extension distributed through the Chrome Web Store, which works in Chrome and other Chromium-based browsers

Both extensions have the same features, so everything this policy says about the extension applies to both. Where something applies to only one of them, we say so.

What we do not collect

The product has no backend server, no account system, and no analytics or tracking code. We do not collect:

Your name, email address, phone number, or any personally identifying information
Your cloud drive credentials, passwords, cookies, or session tokens
Your filenames, file contents, or folder structure
Your browsing history, visit records, or usage patterns
Your IP address, device identifiers, or location

The product sends no telemetry to us or to any third party. No registration or sign-in is required to use every feature.

Data stored locally

To function, the product saves a small amount of configuration in your browser’s local storage. This data stays in the browser you are using and never leaves your device:

What	Why
Rename rule settings	Remembers the rule and parameters you last used, so you need not retype them
Last rename batch	Powers the “undo last batch” feature. Overwritten when a new batch runs. The Chrome version keeps it only in the current page’s memory, so it is discarded when you reload or close the page
State of an unfinished batch	If a batch rename is interrupted (for example, the page is reloaded or closed), lets the product offer to resume it within 30 minutes. Cleared as soon as the batch completes or you choose not to resume, and cleared once it is older than 30 minutes
Cumulative success / failure counts	The counter shown in the extension popup; resettable at any time
Floating button position and visibility	Remembers where you dragged the button, and whether it is shown
Interface language and appearance preference	Remembers your language and light / dark choice
Diagnostic logs	Up to the 300 most recent runtime log entries (the oldest are deleted automatically beyond that), plus a snapshot of the most recent batch that had failures: the original and target names of the failed files, and the error messages. The snapshot is cleared the next time a batch completes with no failures. Used only when you choose to export diagnostics or send feedback — see “Diagnostics and feedback” below

You can clear this data at any time:

Safari version: remove the product’s website data in Safari, or uninstall BatchName
Chrome version: remove BatchName from your browser’s extensions page (chrome://extensions in Chrome); its local data is deleted along with it

Permissions

Storage

Used to save the local settings listed above. Limited to browser local storage; the data never leaves your device.

Tabs (Safari version only)

Used to read the current tab’s URL, to determine whether you are on a supported cloud drive and therefore whether the floating button should appear. We do not read tab contents, and we keep no record of which pages you visit. The Chrome version does not request this permission.

Scripting

Some drives only allow their APIs to be called from within the web page itself. So the product places a page script into supported drive pages, which calls that drive’s own API as the account you are signed in to. The product first loads this script the ordinary way, and uses this permission to inject it only if the ordinary way fails.

The injected script is a file bundled inside the extension package and ships with the extension. The product never downloads or runs remote code, and never injects scripts into pages other than the supported drives.

Website access

The product requests access to the following websites. Hosts containing api and the like are the drives’ API endpoints:

Quark Drive: pan.quark.cn
Alibaba Cloud Drive: www.alipan.com, www.aliyundrive.com, api.aliyundrive.com
Baidu Netdisk: pan.baidu.com
Xunlei Drive: pan.xunlei.com
115 Drive: 115.com
UC Drive: drive.uc.cn, pc-api.uc.cn
123 Pan: yun.123pan.cn
China Mobile Cloud: yun.139.com, personal-kd-njs.yun.139.com
Tianyi Cloud: cloud.189.cn

These permissions are used to:

Display the rename panel and floating button on those sites
Read the file list of the current folder for you to select from
Call those sites’ own APIs to perform the rename

Rename requests go straight to the drive, never through us. When you click Rename, the product calls that drive’s own API from within your browser, as the account you are already signed in to — equivalent to renaming each file by hand, only automated. No data is sent to us at any point in that process.

Diagnostics and feedback

When some renames in a batch fail, the extension panel offers diagnostic options. Each of these happens only when you click it:

Export Diagnostic: creates a JSON file on your device, saved by the browser to your downloads location. It contains the diagnostic logs and failure snapshot described in the table above. The file is not uploaded anywhere.
Copy details: copies a text version of the same information to your clipboard.
Email: opens a draft to [email protected] in your own email client, through a mailto: link. The draft includes the original and target names of the failed files, the error messages, recent warning and error log entries, and your browser’s user agent string.
Report Issues (the link in the extension popup): likewise only opens an email draft, prefilled with the extension version, the current drive and your browser’s user agent string.

Whether to send it, and what to edit or remove first, is entirely up to you. The extension itself sends nothing; an email reaches us only if you press Send in your email client. Emails you send us, including your email address, are used only to reply to you and investigate the issue you reported. We do not use them for anything else or share them with third parties.

During the TestFlight beta (macOS app only)

The macOS app is currently distributed through Apple TestFlight. That data is handled by Apple and falls outside this policy, but you are entitled to know:

Crash and performance data: if you have enabled sharing analytics with developers in system settings, Apple provides us with crash logs and performance metrics. These contain none of your filenames or drive contents.
TestFlight feedback: feedback you choose to submit through TestFlight includes the text you write, an optional screenshot, and your device model and OS version. A screenshot may contain filenames visible on your screen — please check before sending.
Your Apple account email: Apple shows us aggregate figures such as tester counts. For testers who joined via the public link, we cannot see individual email addresses.

That data is governed by the Apple Privacy Policy.

This website

This site is entirely static. It sets no cookies and runs no analytics or advertising code. Your appearance preference (light / dark) is kept in browser local storage and is never transmitted anywhere.

Our hosting provider may keep ordinary server access logs for operational purposes, as is standard for web hosting.

Third parties

We do not share, sell or exchange user data with any third party — because we hold no such data to begin with.

The product has no affiliation, partnership or endorsement relationship with any of the cloud drive providers. Your data on those platforms is governed by their own privacy policies.

Children’s privacy

The product is not directed at children under 13, and we do not knowingly collect any information from children.

Changes to this policy

If this policy changes, we will update the date at the top of this page. Material changes to how data is handled will also be announced in the app.

Contact us

Questions about this policy, or want to know what data we hold about you (spoiler: nothing beyond the emails you choose to send us)? Email [email protected].