GEO & AI SEO Inspector Privacy Policy

1. Data we process

The extension processes data only when you actively start an analysis.

• Website content: the current page title, URL, metadata, readable text, headings, links, image and Schema signals, and page structure.
• Public discovery files: robots.txt, sitemap.xml, llms.txt and similar files published by the site itself.
• Credentials (bring-your-own-key mode only): the API URL, key and model you enter. Used only against the endpoint you configure.

2. How the data is used

The data above is used only to produce the report you asked for:

• Score AI citation readiness and show the weakest chunks
• Check AI crawler access, llms.txt, Schema and E-E-A-T coverage
• Extract named entities and simulate retrieval questions
• Run the 14 classic SEO checks and export the report

3. Data storage

In Local Analysis mode, page content is processed inside your browser and is not uploaded.

In bring-your-own-key mode, the selected page content needed for the requested AI report is sent to the API endpoint you configure. The extension does not send it to a developer-owned default AI service.

Settings and temporary per-tab analysis state are stored in Chrome storage. Results are cached per page and language for up to 24 hours. Your API key stays in Chrome storage and is sent only to the endpoint you entered. The publisher does not keep a server-side copy of your page content or report.

4. Data sharing

We do not sell, rent or disclose your data for advertising, tracking, profiling, marketing or unrelated analytics. The extension contains no advertising or third-party analytics SDK.

When you enable bring-your-own-key mode, the necessary page content is transmitted only to the API provider and endpoint you selected, solely to generate the report you requested. That provider may process the data under its own terms and privacy policy, which you should review.

5. Browser history and background activity

The extension does not access your full Chrome browsing history and does not use the Chrome history API. It reads the current page only after you explicitly start an analysis.

It does not run scheduled or background analysis. The current page URL, title and temporary per-tab state may be retained in Chrome storage only as needed for the report and its short-lived cache.

6. Remote code

The extension does not execute remote code. All extension code ships inside the package. AI provider responses are parsed as JSON text and rendered as report content only.

7. Your control

• Nothing runs in the background — analysis starts only when you click Analyze.
• You can clear the cached report, remove your API key or reset settings at any time in the options page.
• Uninstalling the extension lets Chrome remove the stored settings and cache.

8. Contact us

• Developer: Jing
• Email: aja2@qq.com
• Chrome Web Store developer contact is also available for privacy questions.