Privacy Policy

Last updated: September 1, 2026

The Short Version

Your tabs, browsing history and Belly archive stay on your device. Chomp has no accounts, advertising or cross-site tracking. Optional product-usage analytics are disabled unless you explicitly opt in.

Data Chomp Stores Locally

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

• The tab's URL and page title
• The website's domain name and favicon
• A text excerpt from the page content (for archive search)
• Metadata: when the tab was opened, when it was eaten, how many times you visited it
• A staleness score (used to decide which tabs to eat first)

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:

• Chomp opened (at most once per day)
• A countdown started
• A tab was eaten, rescued, undone or reopened
• A daily configuration snapshot: threshold, countdown length, aggression, schedule and rescue limit
• Broad tab-count and Belly-size ranges, rather than exact counts

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 Chomp Never Sends in Analytics

• No names, email addresses, usernames or account information
• No URLs, tab titles, domains, browsing history or page excerpts
• No archive searches, form data or anything you type
• No cookies, advertising identifiers or tracking pixels
• No request IP stored as an analytics field

Permissions Explained

Chomp requires the following Chrome permissions:

• tabs - Monitor your open tab count and track tab staleness to decide which tabs to eat
• activeTab - Let user-invoked Chomp actions apply to the current webpage
• storage - Save your settings, companion state, local archive, telemetry choice and any unsent opted-in events locally
• sidePanel - Display the companion panel with Belly, Care, stats, settings and mascot
• alarms - Periodically check if Chomp should wake up
• notifications - Show a summary after eating tabs ("Chomp ate 5 tabs")
• scripting - Inject the countdown or user-invoked Chomp World, and extract page text from a tab being eaten for the local archive
• Access to websites you visit (host permission) - Required so the countdown can appear on the tab Chomp is about to eat, and so Chomp World can appear when you explicitly summon it on the current webpage. Page text is read only from a tab being eaten for its local archive; World does not inspect the underlying page. Page data is never sent in analytics.

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