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.
Public policy
DownloadRenamer is designed to rename downloaded files locally inside Chrome. It does not use analytics, remote processing, or third-party tracking services.
DownloadRenamer does not collect, transmit, sell, or share personal data. Filename generation happens locally in the browser, and settings are stored in Chrome storage.
DownloadRenamer does not send user data to external servers.
To provide its features, the extension stores a small amount of information inside Chrome's own storage areas:
chrome.storage.sync, such as template choices, date format, filters, domain rules, and folder settingsThis information is stored by Chrome for the user's own extension usage. It is not transmitted to the developer.
downloads — required to detect download events and suggest a renamed filename before Chrome saves the filestorage — required to save settings, local history, and lightweight state inside Chrome storagescripting — required to inject local user-interface scripts, such as rename toasts and review prompts, on supported pages after a renametabs (optional) — requested only if the user wants filenames to include the current tab title; the extension works without itThe extension does not read page content, does not capture form input, and does not fetch remote scripts.
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.
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.
If this policy changes, the updated version will be published on this page with a revised effective date.
Questions about this policy or the extension can be sent to [email protected].