Browser extension privacy policy

Effective date: 14 October 2026. Updated 15 October 2026 for extension version 0.3 (network requests, storage and your controls).

This policy covers the Chompr.io browser extension (“AI Search Readiness”) for Chrome, Edge and Firefox. The extension is published by Chompr.io, operated by Imbertech. In this policy, “we” means that operator.

The short version: the extension reads the pages you visit so it can score them, and it does that work inside your browser. It does not send page content, your browsing history or anything about you to us or to anyone else. We have no server that receives data from the extension, no analytics, no advertising and no account system.

What the extension reads

When a web page (http or https) finishes loading, the extension’s content script measures it. It reads the page’s text, headings, links, structured data (JSON-LD), meta tags and similar markup, and turns that into a set of counts and short samples: word counts, the heading outline, link counts, which schema.org types are present, a handful of named entities, and an excerpt of up to 2,000 characters of the main content. Before the excerpt is kept, email addresses, phone numbers, card numbers, IBANs, US Social Security numbers and IPv4 addresses are replaced with placeholders. Names and postal addresses are not removed, so the excerpt can still contain them if the page does.

This happens on every page you load, not only when you open the extension, so the score badge is ready when you look at it. It runs in the top-level page only, not in embedded frames, and it measures again when a single-page app changes the address without a full reload. The measurements are passed to the extension’s background process, scored there, and held in memory for that tab. They are discarded when you close the tab, and the browser may discard them sooner when it unloads the background process. They are never written to disk and never leave your computer.

Network requests the extension makes

The extension makes these requests, all directly from your browser:

1. robots.txt. For each website you visit, the extension requests that site’s /robots.txt file to see which AI crawlers the site blocks. The request is sent without your cookies, and the result is cached in memory for an hour. The site will see this as a normal request from your browser. In pre-publish mode the request goes instead to the production address you entered, because that is the site whose crawler policy matters. That is the only case where the extension contacts a site other than the one in your tab, apart from the comparisons below.
2. Site files, when you open the popup. When you open the extension on a page, it requests that site’s /llms.txt, /llms-full.txt, /robots.txt and sitemap (plus at most three sitemaps listed in a sitemap index) to show whether they exist and whether this page is listed. These requests go only to the site you are on, include your cookies for that site, and their results are held in memory until the popup closes.
3. Page downloads, when you ask for them. Only when you press the button, the extension downloads raw HTML for these features:
   • In pre-publish mode, comparing a draft against its live page, or the page as rendered against the raw HTML a crawler would get: the page you are on and, if you supplied one, the live URL you typed.
   • “What a fetcher sees”: the page you are on.
   • “Compare with another page”: the page you are on and the address you typed.
   These requests include your cookies for those sites, because draft pages usually sit behind a login. The downloaded HTML is parsed and scored inside the extension popup, never run, and thrown away when the popup closes.
4. Fonts. The extension’s popup loads the Inter and JetBrains Mono typefaces from Google Fonts (fonts.googleapis.com and fonts.gstatic.com) each time you open it. As with any web font, Google receives your IP address and browser details with that request. No page content or URL is included. Google’s handling of that request is covered by its own privacy policy at policies.google.com/privacy.

The extension does not contact any Chompr.io server.

What the extension stores

These are saved in your browser’s local extension storage. They stay on your device, are not synced to other devices, and are never sent to us or anyone else.

• Staging-to-production pairs. If you use pre-publish mode and enter the production address for a staging site (for example, that staging.example.com goes live as example.com), the extension remembers that pair so you do not have to type it again. It is saved when you turn pre-publish mode on with a production address filled in.
• Scan history. Each time the popup shows a score, the extension saves the page address, its score and checklist result, and the time, so it can show how a page has changed. It keeps the last 20 scans per website and at most 50 websites, dropping the oldest. This is a record of pages you scored, so treat it like browser history.
• Fix checklist. When you tick a fix as done or ignored, the extension saves the page address (without its query string) and which fixes you marked, for at most 200 pages.
• Last comparison. The last address you compared each website against, so the field is filled in next time.

Copying a report, fix or prompt puts it on your clipboard, and “Download JSON” saves a file where you choose. Both happen only when you click them.

Scores, page measurements, robots.txt files and which tabs are in pre-publish mode are held in memory only. Pre-publish mode for a tab is switched off when you close the tab or move it to a different website.

What we collect

Nothing. We do not receive, collect, sell or share any data from the extension. Because no data reaches us, there is nothing for us to retain, hand over or delete.

Sharing

We do not share data from the extension with anyone, because we do not have it. The only third party the extension talks to is Google Fonts, as described above, and the only other requests go to the websites you visit, the production address you enter in pre-publish mode, or the pages you ask it to compare.

Limited Use

Chompr.io’s use of information received from browser APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Page data is used only to show you the readiness score and checklist for the page you are looking at. It is not transferred to us or to anyone else, not used for advertising, not used to decide credit-worthiness or for lending, and not read by any person.

Your controls

• Turn the extension off or remove it at any time from your browser’s extensions page. Removing it deletes everything it stored.
• In Chrome and Edge you can limit the extension to sites you choose under “Site access” on its details page. In Firefox, use the extension’s permissions in Add-ons Manager. Pages it cannot access will not be scored.
• To clear one website’s scan history, open the History panel on that site and choose “Clear history for this site”.
• To clear everything else it stored without uninstalling, remove and reinstall the extension, or clear its storage from the browser’s developer tools.

Children

The extension is a tool for people who build and publish websites. It is not aimed at children and collects no data from anyone, children included.

Other Chompr.io products

The Chompr.io command-line tool, API and this website (including the waitlist) are separate from the extension and are not covered by this policy. The extension does not use them.

Changes

If the extension’s handling of data changes, for example if a future version sends anything to a Chompr.io server, or if the extension moves to a different operator, we will update this policy and its effective date before that version is released, and describe the change on this page. A change that sends page data off your device will be opt-in.

Contact

Questions about this policy or the extension: admin@chompr.io.