DownloadRenamer Privacy policy Back to site

Public policy

DownloadRenamer privacy policy

DownloadRenamer is designed to rename downloaded files locally inside Chrome. It does not use analytics, remote processing, or third-party tracking services.

Last updated: April 7, 2026 Extension ID: haopfpoimcploggpianaioljkglpdnpj

1. Summary

DownloadRenamer does not collect, transmit, sell, or share personal data. Filename generation happens locally in the browser, and settings are stored in Chrome storage.

2. Data collection and transmission

DownloadRenamer does not send user data to external servers.

  • No analytics or telemetry
  • No advertising identifiers
  • No account system or sign-in
  • No remote logging of downloads, filenames, titles, or URLs
  • No sale or transfer of data to third parties

3. Data stored locally in Chrome

To provide its features, the extension stores a small amount of information inside Chrome's own storage areas:

  • Settings in chrome.storage.sync, such as template choices, date format, filters, domain rules, and folder settings
  • Recent rename history in local extension storage so users can review recent filename changes
  • Session values such as badge counters used to show lightweight status information during a browser session
  • Local UI flags such as whether a review prompt has already been dismissed

This information is stored by Chrome for the user's own extension usage. It is not transmitted to the developer.

4. Permissions used by the extension

  • downloads — required to detect download events and suggest a renamed filename before Chrome saves the file
  • storage — required to save settings, local history, and lightweight state inside Chrome storage
  • scripting — required to inject local user-interface scripts, such as rename toasts and review prompts, on supported pages after a rename
  • tabs (optional) — requested only if the user wants filenames to include the current tab title; the extension works without it

The extension does not read page content, does not capture form input, and does not fetch remote scripts.

5. How processing works

When a file is downloaded, DownloadRenamer evaluates the filename locally using the user's current settings. Depending on the available context, it may use the date, the current tab title, the download hostname, the original filename, and the file extension. The resulting suggested filename is then handed back to Chrome locally on the device.

6. Third-party services

DownloadRenamer does not rely on third-party analytics, ads, cloud APIs, or remote backend infrastructure. The public website and Chrome Web Store listing may link to external pages, but the extension itself performs no external requests as part of its core operation.

7. Changes to this policy

If this policy changes, the updated version will be published on this page with a revised effective date.

8. Contact

Questions about this policy or the extension can be sent to [email protected].