CrumbSweep Privacy Policy

Effective date: July 28, 2026

The short version

CrumbSweep collects no data whatsoever. It has no analytics, no telemetry, no accounts, no servers, and makes no network requests. Its job is to delete data, not gather it.

What CrumbSweep stores, and where

Your settings, whitelist/greylist, cleanup counters, and internal bookkeeping (which sites have open tabs, which cleanups are pending) are stored in your browser's extension storage on your device. If you are signed into Chrome with extension sync enabled, Chrome may sync your settings and lists between your own devices through your Google account — that sync is performed by Chrome, not by CrumbSweep, and the data never reaches us. We couldn't read it if we wanted to: we operate no servers.

What CrumbSweep accesses, and why

• Cookies and site data on all sites: Chrome's cookie API requires host access in order to delete a site's cookies. This access is used only to enumerate and delete cookies (and, if you opt in, localStorage/IndexedDB/cache/service workers) for sites you close. Nothing is read for any other purpose and nothing is transmitted.
• Tabs: used only to know which sites currently have open tabs, so cleaning happens when a site's last tab closes. Browsing history is not recorded.
• Notifications (optional): requested only if you enable "notify when a site is cleaned", and used only for that.

Data sharing

None. There is nothing to share and no one to share it with.

Changes to this policy

If this policy ever changes, the new version will be published at this URL with an updated effective date. Since the extension makes no network requests, any future change could never apply retroactively to data — there is none.

Contact

Questions, bug reports, or privacy concerns? Open an issue at github.com/dookofcards/crumbsweep/issues. Issues are public, so please don't include anything sensitive.