Fresh Reload
Privacy policy
Last updated: August 28, 2026
The short version
Fresh Reload has no server, account, analytics, advertising, or telemetry. After your toolbar click, it handles the active tab's URL in memory only to clear HTTP cache for that exact origin and reload the tab. It does not retain or transmit the URL.
What it handles
After you click, the extension reads the active URL and reduces it to scheme, hostname, and port. It passes that origin to Chrome's browsing-data API with only the HTTP-cache data type selected. It does not read page content, other tabs, cookies, login values, or site-storage contents.
What it changes
It removes HTTP browser cache associated with the active origin, then asks Chrome to reload the active tab while bypassing local HTTP cache. The website receives a normal reload request. No request is made to us.
It does not remove cookies, local storage, IndexedDB, Cache Storage, service workers, history, downloads, passwords, or form data.
Chrome Web Store Limited Use
Information received from Chrome APIs is used only for Fresh Reload's prominently described single purpose. This use follows the Chrome Web Store User Data Policy, including its Limited Use requirements. URL data is not transferred to us or others, used for advertising, or made available for humans to read.
Website link
The Options page can show one ordinary maker-website link. It is disabled until a real public URL is configured and opens only when you choose it.
Permissions
activeTab reads the clicked tab's URL for that invocation. browsingData removes only HTTP cache for the derived origin.
What we never do
- No analytics, telemetry, tracking pixels, or fingerprinting
- No account, login, or email collection
- No sale, sharing, or transfer of user data
- No advertising, affiliate-link injection, page scraping, or remote code
Children
This utility is not directed at children.
Changes
Material changes will be published here with a new date and reflected in release notes.