Privacy Policy

JSON-LD & Agent Inspector (Safari, Chrome and Firefox extension) · Last updated: 20 July 2026

Privacy by design. The extension analyzes the current page locally on your device and sends nothing to us or to any third-party server. There are no analytics, no ads, and no tracking.

Who this applies to

This policy covers the browser extension “JSON-LD & Agent Inspector” (also published as “JSON-LD Tester”) for Safari, Google Chrome and Mozilla Firefox. The developer is Gerhard Kanzler.

Data we collect

None. The developer does not collect, receive, store, sell or share any personal data. No data ever leaves your device to us.

What the extension processes locally

All processing happens in memory, inside the extension, on your own device:

Data	When	Stored where	Removed when
Structured data on the current page (JSON-LD, canonical, robots, page meta)	When you open the extension on a page	In-memory only (not persisted)	When you close the extension window
Agent-tool list & schemas (WebMCP)	When you open the Agent Tools tab	In-memory only (not persisted)	When you close the extension window
Your settings (theme, language, default validator, header check, auto-update)	When you change a setting	Your browser’s local extension storage on your device	On uninstall or manual change

Data that is never transmitted

Visited URLs
Page content or the structured data found on a page
Agent-tool schemas or any inputs you type into the tool tester
Browsing history (the extension has no access to it)

Network requests the extension makes

The extension makes no requests to the developer and no third-party requests. The only network activity is optional and goes to the website you are currently viewing (same-origin), never to us:

Opening an external validator (Google Rich Results Test or the Schema.org Validator): opens a new tab with the current page’s URL — a normal navigation you click. Nothing is posted automatically.
Reading HTTP response headers: one same-origin request from the page to its own URL to show response headers and indexability. Can be turned off in Settings.
Checking agent/crawler files (only when you open the Readiness tab): same-origin requests to the site’s own /llms.txt, /robots.txt, /sitemap.xml, /ai.txt and similar. Every request goes to the site itself; nothing is uploaded.
Running an agent tool: only after your explicit, multi-step confirmation, and it calls the current website’s own code — not the developer.

Permissions

The extension requests only the minimum permissions it needs (activeTab, scripting, storage) and reads the active page only on demand — there is no background content script running on the pages you visit.

Children

The extension is a developer/SEO tool and is not directed at children. It collects no data from anyone.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new “Last updated” date.

Contact

Questions about privacy? Please open an issue at the project’s GitHub issue tracker.