Cookie Policy for WebRenamer

01 What “cookies” and browser storage mean here

A cookie is a small value a website can ask a browser to store and send with later web requests. Browsers also provide related storage technologies, including localStorage, session storage, IndexedDB, caches, and temporary object URLs. These technologies behave differently, but privacy rules and browser controls may discuss them together because each can store or access information on a device.

This policy uses “browser storage” as the broader term. It describes both traditional cookies and the local preference storage used by WebRenamer. The UK Information Commissioner’s Office similarly treats cookies, pixels, fingerprinting, and comparable storage or access methods as a wider family of technologies in its storage and access technologies guidance.

02 WebRenamer’s current cookie use

WebRenamer does not set cookies for advertising, personalization, login, or a shopping cart. It does not include advertising pixels or use selected files for behavioral profiling. The site does load Google Analytics 4 when a valid measurement ID is configured so we can understand aggregate visits and product usage.

GA4 may set first-party analytics cookies on webrenamer.com. These cookies distinguish browsers and sessions; they do not contain selected file contents or filenames. Browser settings and privacy tools can block or delete them.

03 The localStorage entry WebRenamer uses

WebRenamer uses one browser localStorage entry named batch-file-renamer. The persisted state is deliberately limited. It includes:

• customPresets: custom preset names, descriptions, icon selections, and rename-rule configurations that you choose to save;
• showAdvanced: a true-or-false preference recording whether advanced mode is enabled.

The persisted entry does not intentionally include selected file objects, file contents, original filenames, proposed filenames, the current file list, or undo history. Files and active rename work remain in the running page rather than being written into the persisted preference store.

04 Google Analytics cookies

Google documents _ga as a cookie used to distinguish users and _ga_<container-id> as a cookie used to persist session state. Their documented default expiration is up to two years, although browsers may impose shorter limits and users can delete them sooner.

Analytics may receive page views, session statistics, approximate location, browser and device information, referring pages, and enabled interaction events. WebRenamer does not intentionally send selected files, file contents, original or proposed filenames, preset names, or ZIP contents to Google Analytics. See Google’s Privacy Policy for its handling of Analytics data.

05 Temporary in-browser processing

When you select files, the browser exposes them to the page for the current session. WebRenamer calculates new names and builds the export locally. This active session data is not the same as a cookie and is not intentionally persisted in localStorage.

For browsers without the supported save-file interface, WebRenamer can create a temporary object URL for the generated ZIP. The URL refers to data held by the browser, is used to begin the download, and is revoked by the application afterward. It is not an advertising identifier and is not sent back with later page requests.

06 Hosting and security infrastructure

The website is delivered through hosting and network infrastructure. Providers may use necessary technical measures to route traffic, protect against abuse, balance load, or maintain security. They may also generate request logs containing an IP address, user agent, requested URL, time, and response details.

Those provider-level mechanisms are separate from WebRenamer’s rename workspace and may change when hosting configuration changes. This policy does not claim that every network intermediary is incapable of using a short-lived security cookie. It describes the application code controlled by WebRenamer and will be revised if a known provider mechanism materially changes the site’s storage practices.

07 Google Analytics and third-party websites

Google receives website-measurement data through the GA4 tag and processes it under Google’s policies and Analytics terms. Separately, blog articles may link to Microsoft, Apple, software publishers, regulators, or other external websites. Following one of those links leaves WebRenamer. The destination may set its own cookies or use analytics under its own policies.

08 How to control or delete stored data

You can avoid the persistent entry by not saving a custom preset. To remove a particular preset, use the delete action in the preset interface. To remove all WebRenamer browser data, open your browser’s privacy or site-data settings, find webrenamer.com, and clear its stored data.

Clearing site data removes custom presets, the advanced-mode preference, and first-party Analytics cookies from that browser profile. It does not delete ZIP files already downloaded to your device. You can also use the Google Analytics opt-out browser add-on. Browser menus vary, so consult the current support page for your browser if the site-data control is difficult to find.

09 Changes to this Cookie Policy

This policy may be updated when browser-storage behavior, hosting infrastructure, analytics, advertising, or legal requirements change. A material update will be reflected in the effective date shown above. New non-essential storage should not be introduced silently.

10 Contact

Questions about cookies or browser storage can be sent to [email protected]. Do not send or attach files selected in the renaming tool.