Cookie Monster Raccoon автор DcOpen

Cookie extensions ask you to list what to erase. That is the wrong list: the sites you visit once are endless, the ones you care about are a dozen.

Cookie Monster inverts the default. Nothing survives, except what you save.

WHAT IT DOES

Close the last tab of a site and, after a short grace period, its cookies, localStorage, sessionStorage, IndexedDB and Service Workers are erased. No trace, no list to maintain.

Need the session? One click on "Save this site" in the popup and that site is never touched again. On a subdomain you choose the scope: the whole site, or that one host.

OBSERVATION MODE, ON BY DEFAULT

On first run nothing is erased. The extension only records what it would have erased, so you can browse for a day, read the journal, and decide. Purging becomes real when you switch observation off yourself.

SESSION COPIES

Saving a site and saving its session are different things. A session copy is a snapshot of a site's cookies you can restore from if access is lost anyway. Be aware the copy holds cookie values in the clear in local extension storage: keep only the ones you need.

PRIVACY IS THE WHOLE POINT

No network calls at all. Not for telemetry, not for statistics, not for crash reports, not for update checks. No server, no account, no identifier, no paid tier.

No content scripts: the extension never injects code into the pages you visit. It does not see their contents, does not read the forms you fill in, does not intercept requests. It only needs the tab's address.

All state lives in local extension storage, inside your profile. Uninstalling erases it.

None of this asks to be taken on trust. The source is public under the MIT licence, and a test in the repository fails the build if anyone adds a network call, an extra permission, a remote script or font, or a new dependency.

WHAT IT DOES NOT DO

It cannot wait less than 30 seconds before purging: that is the minimum the browser imposes on the only timer that survives an extension being suspended. It does not clear the HTTP cache, which is shared and holds no session. On Firefox, Cache API entries also survive a purge: Firefox has no way to remove them for a single site, and removing them for all sites would be a wider erasure than the one you asked for.

Source and full privacy policy: https://github.com/DomenicoCentrone/cookie-monster