Purge does not collect, store, or transmit any personal data. There are no cookies, tracking pixels, or telemetry of any kind used to monitor what you do.
Clearing browsing data uses Chrome's own browsingData API directly — Purge
never sees the data itself. The security check runs by injecting a short-lived script into
the active tab with Chrome's scripting API; the scan happens entirely in your
browser and its findings never leave the page.
Your settings — which data types to clear, automation schedule, behavior toggles — are
stored using chrome.storage.local by default. If you turn on "Sync across
devices," they move to chrome.storage.sync instead, which is synced by your
own Google account the same way Chrome syncs bookmarks — Purge has no server of its own
to send this data to.
Purge also keeps a simple purge counter in local storage, and remembers the last web tab
you had open in chrome.storage.session (cleared when Chrome closes) so the
popup knows which site you mean. No browsing history, page content, or cookie values are
ever stored.
We do not track installs, uninstalls, or usage patterns. We have no way of knowing who is using Purge, how often, or which sites it has been used on.
Each permission Purge requests is used for exactly one purpose:
browsingData — to clear the data types you've selected.storage — to save your settings locally (or in sync storage, if enabled).activeTab / tabs — to identify the current site for "this site only" clears and the security check, reload the tab after clearing or close other windows (only if you enable those options), and open Chrome's keyboard-shortcuts page from settings.scripting — to run the local, in-page security scan.alarms / idle — to run automatic clears on a schedule or when the system goes idle.notifications — to tell you when an automatic clear was held back by the security check.cookies (optional) — only used for the "cookies missing Secure or SameSite" check. Only those flags are checked; cookie values are never read. Purge works fully without granting it.Purge does not use remote code. All of its code ships inside the extension package; it
loads no external scripts and does not use eval.
Purge is open source. The code is public so anyone can audit it and confirm it does exactly what this policy describes — nothing more.
Source code and issue tracking live on GitHub. Visit the Purge repository to audit the code, report a bug, or contribute.
Because Purge collects no user data, there is nothing to sell, share with third parties, use for advertising, or use to determine creditworthiness. The use of any information Purge handles complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
If this policy changes, the "Last updated" date above will change with it. For questions, open an issue on the GitHub issue tracker.