Chomp
Menu

Privacy Policy

Last updated: October 20, 2026

The Short Version

Your tabs, browsing history and Belly archive stay on your device. The Chomp extension has no accounts, advertising or cross-site tracking. Optional extension usage data and website analytics are separate choices, both off unless you opt in.

Website Analytics and Cookies

If you choose Accept in our cookie banner, this website loads Google Analytics (G-4HB8XBLLG6) to help us understand visits and how the site is used. Google receives information about your visit, including pages viewed, browser and device information, and the network request needed to deliver analytics. This does not give the website access to your extension's tabs or Belly archive.

We use first-party _ga and _ga_* cookies to distinguish visits, with an expiry of 180 days. Google Signals and advertising personalisation are disabled in our tag configuration. Google may process data outside your country; see how Google uses information from partner sites.

Choosing No thanks leaves Google Analytics unloaded. Continuing to browse does not count as acceptance. We remember your choice in this browser's local storage for 180 days. You can change it at any time using Cookies in the bottom corner. Withdrawing consent disables further analytics collection and removes this site's analytics cookies; it does not erase data already sent to Google. Private article review pages do not load analytics.

Data Chomp Stores Locally

When Chomp "eats" a tab, it stores the following in your browser's local IndexedDB database:

Chomp also stores your settings, appearance, reduced-motion choice, permanent Bond, Care Set category counters and calm-browser minutes in Chrome's local storage. These companion records contain built-in enums and numbers, not browsing content.

To recognise a thoughtful return, Chomp may keep the normalised URL of a tab you rescued for up to 30 days, locally on your device. The record is removed when that return earns care. Duplicate tidying compares URLs among tabs that are currently open and does not create a separate browsing-history record.

Where Your Tab Data Is Stored

Your tab, archive and companion data is stored locally in your browser using IndexedDB and Chrome's storage.local API. URLs, titles, domains, favicons, page excerpts, archive searches, rescued-page memory and duplicate-tab details are never included in product-usage analytics. There is no cloud sync or remote backup for your Belly or Bond.

Optional Product-Usage Analytics

Nothing is sent until you choose Share usage data in Chomp. If you opt in, Chomp may send these product events:

Each event may also contain the Chomp version, operating system, distribution channel and a random installation identifier. The identifier is generated only after opt-in and does not contain or derive from your identity.

Events are sent over HTTPS to Chomp's endpoint at chomptabs.com and stored in Cloudflare Workers Analytics Engine for three months. Cloudflare necessarily processes the request IP to deliver the HTTPS request, but Chomp does not write IP addresses into its analytics dataset.

You can turn usage sharing off immediately in Settings. Opting out clears the unsent event queue and deletes the local installation identifier. Events already accepted by Analytics Engine remain until they expire under its three-month retention period.

What the Extension Never Sends in Analytics

Permissions Explained

Chomp requires the following Chrome permissions:

Data Retention

Archived tabs are stored indefinitely in your local IndexedDB until you manually delete them. Companion progress remains until you use Reset Bond and appearance or uninstall Chomp. Rescued-page memory expires within 30 days or is removed after a qualifying return. Uninstalling the extension removes all locally stored data. Opted-in product-usage events expire from Cloudflare Workers Analytics Engine after three months.

Children's Privacy

Chomp is not directed at children under 13 and does not knowingly collect personal information from children.

Changes to This Policy

If Chomp's data practices change, the extension will prominently explain the change before collecting any newly introduced data, and this page will be updated at the same time.

Chrome Web Store Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

Questions about this privacy policy? Reach us at hello@chomptabs.com