This document describes how the SeoBrowser Chrome extension (the "Extension"; available on the Chrome Web Store) handles user data. Read together with the SeoBrowser website terms of use.
Plain-language summary
SeoBrowser does not collect, transmit, sell, or share your personal data or the contents of the pages you audit. All analysis happens locally inside your browser. The Extension never sends page contents or any user-identifying information to any server — neither ours nor a third party's. The one time a page URL leaves your browser is when you yourself click a Quick Tools link, which opens the SEO service you picked with that URL in the query string.
What the Extension does
When you click the SeoBrowser toolbar icon or open its side panel, the Extension audits the currently active tab for SEO, GEO (Generative Engine Optimisation) and AEO (Answer Engine Optimisation) signals. The audit runs in three stages, all on your device:
- DOM extraction. A content script reads page metadata (title, meta tags, headings, links, images, JSON-LD/Microdata schema, hreflang, etc.) and the visible text of the active tab.
- Same-origin probes. The Extension fetches a small set of well-known files from the same origin as the active tab:
/robots.txt,/llms.txt,/llms-full.txt,/ai.txt,/sitemap.xml,/.well-known/*(agent-skills, api-catalog, mcp-server-card, oauth-authorization-server, openid-configuration), and re-fetches the page itself once withAccept: text/markdownto detect content negotiation. These requests are made withcredentials: 'omit'andreferrerPolicy: 'no-referrer'so they carry no cookies or referrers. - Local analysis & report rendering. Twelve analyzers and 33 AIO/GEO/AEO criteria run inside the Extension's service worker. The resulting report is rendered in the popup and side panel.
What data the Extension stores
All data is stored locally on your device using Chrome's standard extension storage APIs. Nothing is ever uploaded.
Every key the Extension writes is listed below. There are no others.
| Storage key | Purpose | Data | Lifetime |
|---|---|---|---|
chrome.storage.local → theme-preference |
Light / dark / system appearance | Single string | Until you uninstall the Extension or clear extension data |
chrome.storage.local → seobrowser-settings |
Your choices on the Options page: robots.txt User-Agent preset and custom token, which tabs are hidden, auto-audit on/off, which tab opens first, audit-history on/off and its per-URL cap, badge on/off, which crawlers the simulator uses, review-prompt suppression, and the AIO/GEO/AEO focus discipline | Settings object, no page content | Until you uninstall or press "Reset all" on the Options page |
chrome.storage.local → ai-bots-registry-v1 |
Cached AI-bot registry | List of public AI crawler User-Agents and access categories. Currently sourced only from the Extension package itself; no remote registry is fetched. | Refreshed when a new Extension version is installed |
chrome.storage.local → onboarding-seen |
Suppresses the first-run overlay after you dismiss it | Single boolean | Until you uninstall or clear extension data |
chrome.storage.local → review-prompt-state |
Decides whether to ever show the "rate this extension" prompt, and stops showing it once dismissed | Counter and a boolean | Until you uninstall or clear extension data |
chrome.storage.local → last-tab |
Reopens the Extension on the tab you last used | Single string | Until you uninstall or clear extension data |
chrome.storage.local → pending-update-version |
Remembers that Chrome has staged a newer Store version, so the footer can tell you to reload | Version string | Cleared once you are running that version |
IndexedDB (seobrowser-history database) |
Audit history | Per audit: page URL, audit timestamp, full audit report. Powers the "History" tab and per-URL diffs between consecutive scans. | Entirely optional — history can be switched off on the Options page, in which case nothing is written at all. When on, at most 100 audits are kept globally and at most 20 per URL by default (configurable 1–200); older entries are pruned automatically. "Clear all" in the History tab deletes everything immediately. |
You may inspect or remove all stored data at any time via Chrome's extension management page: click "Details" → "Site settings" / "Extension storage", or simply uninstall the Extension.
What data the Extension transmits
None to any server we operate. The Extension makes the following network requests, all of which target the same origin as the page you are currently auditing (i.e. the same website you are already viewing):
GET /robots.txtGET /llms.txt,GET /llms-full.txtGET /ai.txtGET /sitemap.xmlGET /.well-known/agent-skills,/api-catalog,/mcp-server-card,HEAD <current page URL>(for theLink:HTTP header)GET <current page URL>withAccept: text/markdownGET <current page URL>(no-JS re-fetch to capture initial HTML)
/oauth-authorization-server, /openid-configuration
These are publicly addressable resources that any web client could request. We do not include any cookies, authentication tokens, or referrer information. Each request is bounded by a 2.5 — 5 second timeout to keep audits fast.
No page content is ever transmitted anywhere. Nothing the Extension reads from the page you are auditing leaves your browser. There are no analytics, error-reporting, A/B-testing, ad, or telemetry SDKs anywhere in the Extension's code base, and the Extension sends no request to any server we operate.
Three narrow cases exist where a request does reach a host other than the audited site. We list them rather than round the claim off, because a privacy policy that overstates is worth less than one you can check:
- Update checks. The Extension calls
chrome.runtime.requestUpdateCheck()so the footer can tell you a newer version is available. The resulting request is made by Chrome itself, to Google's extension-update endpoint — the same one Chrome already uses for every installed extension. The Extension originates no request of its own and sends no data about you or the page. - Quick Tools, only when you click one. The Quick Tools tab and the right-click menu open a new tab at a third-party SEO service (such as Ahrefs, Semrush, PageSpeed Insights or the Wayback Machine), passing the audited URL or its hostname in the query string. This is ordinary navigation that you initiate; nothing happens until you click. Be aware that if the audited URL itself contains something private — a session token, an internal hostname — that URL is what gets handed to the service you chose.
- Image thumbnails in the drill-down. Expanding the Images list renders the page's own images, which means your browser requests them from whatever host serves them. Those requests carry no cookies and no referrer, and the host in question already saw you when you loaded the page being audited.
Permissions the Extension requests
| Permission | Why we need it |
|---|---|
activeTab |
Read the currently active tab's DOM and run the in-page extraction script when you explicitly invoke the Extension. The Extension never reads any tab you have not explicitly chosen. |
storage |
Save the seven local keys listed in the storage table above — your appearance choice, your Options-page settings, the bundled AI-bot registry cache, and four small UI-state flags — plus the optional audit history. |
scripting |
Inject the in-page extraction script into the active tab when you trigger an audit. |
contextMenus |
Add a right-click menu entry that opens the Extension on the current page. |
sidePanel |
Render the audit report as a Chrome side panel in addition to the popup. |
alarms |
Schedule a daily check for the AI-bot registry refresh (currently dormant — the registry is bundled with the Extension and not fetched from the network). |
The Extension does not request host_permissions, <all_urls>, tabs, webRequest, declarativeNetRequest, webNavigation, or any other broad-access permission.
Cookies, tracking, and advertising
The Extension does not set any cookies, does not use any browser fingerprinting techniques, does not participate in any advertising network, and does not track your browsing activity across sites. The audit history described above is the only record the Extension keeps, and it never leaves your device.
Third-party services
The Extension does not integrate any third-party services, SDKs, analytics platforms, or APIs. Its outbound requests are the same-origin probes listed above, plus the three user-initiated or browser-initiated cases described in that section.
The website is a separate matter, and we would rather be explicit than vague about it. The companion site seobrowser.ru — including the page you may be reading this policy on — runs Yandex.Metrika, which records page views, clicks, scrolling and, through its Webvisor feature, a replay of your session on the site. That is analytics on the *website*, entirely separate from the Extension, and it observes only what you do on seobrowser.ru. It never sees anything from the pages you audit with the Extension. If you would rather not be recorded, you can block mc.yandex.ru or use the site with JavaScript disabled; the Extension is unaffected either way.
Children's privacy
The Extension is a developer/SEO tool intended for adults. It is not directed at children under 13 and does not knowingly process any personal information of children.
Changes to this policy
When this policy is updated, the "Last updated" date at the top of the page will change. Material changes are announced on the seobrowser.ru homepage at least 30 days before they take effect, and the announcement stays up for at least 30 days afterwards. Non-material corrections — fixing a typo, clarifying wording that already described existing behaviour — take effect immediately.
Contact
Questions or concerns?
- Web: <https://seobrowser.ru>
- Email: privacy@seobrowser.ru
Compliance attestations
- Chrome Web Store Developer Program Policies — the Extension
- GDPR — the Extension does not "process personal data" within the
- CCPA / CPRA — the Extension does not "sell" or "share" personal
declares only the minimum permissions it needs and uses them solely for the single declared purpose stated in the Chrome Web Store listing.
meaning of Regulation (EU) 2016/679, because no data ever leaves the user's device.
information within the meaning of California Civil Code §§ 1798.140 and 1798.100 et seq.
