Privacy Policy for WebRenamer

01 Scope of this policy

This Privacy Policy applies to the WebRenamer website and its browser-based file-renaming tools. It covers information handled when you visit the site, select files, build rename rules, save a custom preset, or export renamed copies. It does not govern third-party websites linked from our blog or documentation; those sites publish their own privacy terms.

02 How file processing works

When you select files, the browser makes those files available to the renaming workspace on your device. WebRenamer reads the information needed to calculate the preview, including filenames, extensions, and file timestamps where the browser provides them. Rename rules and validation run in client-side code.

WebRenamer does not intentionally upload selected file contents or filenames to our servers. ZIP generation also happens locally. Depending on browser support, the finished archive is written through the browser’s save-file interface or downloaded from a temporary local object URL. Your original files are not overwritten by the website.

03 Browser storage and cookies

The current application uses browser localStorage under the key batch-file-renamer. It stores only custom presets you choose to save and whether advanced mode is enabled. A saved preset can contain its name, description, icon choice, and rename-rule configuration. The persisted store does not intentionally include selected files, file contents, filenames, or the in-progress file list.

This local data remains in that browser profile until you delete the presets or clear site data in browser settings. Separately, Google Analytics 4 may use first-party analytics cookies to distinguish browsers and sessions. Those analytics identifiers are not part of the batch-file-renamer preference store. For exact storage details and deletion options, read the Cookie Policy.

04 Website delivery and technical logs

Like most websites, WebRenamer must be delivered through a hosting and network provider. Those providers may process standard request information such as an IP address, browser and device details, requested URL, request time, response status, and security events. This information may be needed to deliver the site, prevent abuse, diagnose failures, and maintain network security.

Infrastructure logs are separate from the file-renaming workspace. We do not use them to reconstruct selected filenames or file contents. Retention and security controls for provider logs depend on the hosting service in use and its applicable terms.

05 Google Analytics 4

WebRenamer uses Google Analytics 4, provided by Google, to understand aggregate traffic and product usage. The default implementation may collect page views, session statistics, approximate location, browser and device information, referring pages, and interaction events enabled for the web data stream. GA4 may store a pseudonymous client identifier in first-party cookies named _ga and _ga_<container-id>.

The renaming workspace does not intentionally send selected files, file contents, original filenames, proposed filenames, preset names, or ZIP contents to Google Analytics. Analytics is used to evaluate how the public website is found and used, not to inspect a person’s files. Google processes Analytics data under its Privacy Policy and applicable Analytics terms.

06 Sharing, sale, and advertising

WebRenamer does not sell personal information or share it for cross-context behavioral advertising. Limited website-usage data is processed by Google as our analytics provider, and technical request data may be processed by infrastructure providers that deliver and protect the website. Information may also be disclosed when reasonably necessary to comply with law, protect users, investigate abuse, or defend legal rights.

If advertising, accounts, uploads, or another materially different data practice is introduced later, this policy will be updated before or alongside that change. Where consent or an opt-out is legally required, the site should provide the relevant control rather than relying on this policy alone.

07 Your choices and privacy rights

You can use the core renaming tool without creating an account. You can avoid persistent browser storage by not saving custom presets. To remove stored preferences, delete custom presets in the interface or clear WebRenamer’s site data through browser settings.

You can block or delete Analytics cookies through browser settings or compatible privacy tools. Google also provides a Google Analytics opt-out browser add-on. Blocking Analytics does not prevent access to the file-renaming tool.

Depending on where you live and whether a law applies to WebRenamer, you may have rights to request access, deletion, correction, restriction, or information about the use of personal data. California residents can review the California Attorney General’s CCPA overview; people in the European Economic Area can review the official text of the GDPR. We will not discriminate against a user for making a valid privacy request.

08 Children’s privacy

WebRenamer is a general-purpose file utility and is not directed to children under 13. We do not knowingly ask children to provide personal information. If you believe a child has sent personal information through a future contact feature or another part of the service, contact us so the situation can be reviewed.

09 Security and retention

Keeping file operations local reduces the amount of sensitive content transmitted to a service, but no browser, device, or network can be guaranteed completely secure. Keep your operating system and browser updated, avoid processing sensitive files on a shared device, and clear local presets when the device will be handed to someone else.

Browser-stored presets remain until you remove them or clear site data. Analytics cookies use the durations documented in the Cookie Policy, subject to browser limits and deletion by the user. Infrastructure and Analytics data are retained according to operational settings and provider controls. WebRenamer does not maintain a server-side account database for the current tool.

10 Changes to this policy

This policy may change when the product, hosting setup, or legal requirements change. Material updates will be reflected by a new effective date at the top of this page. The current version should describe the behavior of the current site rather than planned features.

11 Contact

For a privacy question or request, email [email protected]. Please do not attach sensitive files. We may need enough information to understand the request, but we will not ask you to send the files you renamed.