Privacy policy: Auto Delete Cookies on Tab Close
Effective 2026-10-12.
This extension does not collect your data and does not send it anywhere. It has no server, no analytics and no account system. It reads your cookies and open tabs on your computer so that it can delete cookies, and that is all it does with them. Below is what it stores and the one outside service it talks to.
What it stores on your computer
In Chrome's extension storage (chrome.storage.local):
- your settings and your keep lists (each rule's domain or pattern, which list it is on, its match type and, on Pro, your note);
- the sites waiting for their cleanup delay to pass, with the time each is due;
- the activity log: the last 300 cleanups, each with a time, the site names and how many cookies were removed (you can switch the log off in Settings);
- lifetime counters (cookies removed, cleanups run) and whether your Chrome supports partitioned cookies;
- your Pro status: whether you have paid, the email ExtensionPay reports for the purchase, and when it was last checked.
In session storage (chrome.storage.session), which lives in memory and is wiped when Chrome closes: the host name of each open tab, the sites each tab has navigated away from, and up to 20 host names seen per site (used for the optional site data cleanup).
Chrome sync
A copy of your settings and keep lists is also written to chrome.storage.sync. If you use Chrome sync, Google stores that copy with your Google account and brings it to your other computers, as it does for any extension's synced settings. If you do not use Chrome sync, it stays on this computer. Sync has a 100 KB limit; very large lists stop syncing and the local copy carries on. The activity log, pending cleanups and Pro status are never synced. The ExtensionPay library keeps its own small records in sync storage too: an install date and, once you have opened the purchase page, a random key and your payment status (with the email you paid with, after a purchase).
ExtensionPay
Pro is sold through ExtensionPay (extensionpay.com), which takes payment with Stripe. Nothing is sent to ExtensionPay until you click Upgrade or Restore purchase. At that point the extension asks ExtensionPay for a random key and opens its payment or login page. After that it checks your payment status using that key when Chrome starts (at most every six hours) and when you open the settings page. These requests contain the key and nothing about your browsing, cookies or lists. A small script from the ExtensionPay library runs on extensionpay.com pages only, to tell the extension that a payment went through. What you enter on the payment page is covered by ExtensionPay's privacy policy: https://extensionpay.com/privacy
No other network requests are made.
Permissions
| Permission | Why |
|---|---|
| cookies, and access to all sites | To list and delete cookies. Chrome only allows this for sites the extension has access to, and cookies can belong to any site. No script runs on the sites you visit. |
| tabs | To know which sites are open, so a site is cleaned only after its last tab closes. |
| browsingData | For the optional Pro cleanup of localStorage, IndexedDB, caches and service workers. |
| storage | To save the items listed above. |
| alarms | To run a cleanup on time even if Chrome has paused the extension in the background. |
| notifications (optional) | Only if you turn on cleanup notifications. |
Removing your data
The Clear log button on the Activity tab of the settings page deletes the log. Uninstalling the extension deletes everything it stored on this computer.
Children
The extension is not aimed at children and collects nothing from anyone.
Changes
If this policy changes, the new version will be published here with a new date.
Contact
Jonathon Wager. Open an issue at https://github.com/JonathonWager/auto-delete-cookies/issues or use the support email on the Chrome Web Store listing.