Privacy Boundary

Public-safe browser fingerprint education, local fingerprint inspection, component explanation, privacy-resistance analysis, headless/browser automation indicator analysis, local non-sensitive comparison snapshots, read-only MCP introspection, RSS/feed consumption, trusted-domain discovery, standard route compliance, Vercel metadata capture, backend model scaffolding, and trace-linked Fingerprint operations are intentionally supported for public educational and defensive use. Fingerprint does not provide covert tracking, does not silently collect fingerprints, and does not expose raw fingerprint records publicly. PLATPHORM_API_KEY support is scaffolded for future protected backend services, protected persistence, Atlas correlation, webhook operations, sync, test-triggering, reporting, administrative actions, and sensitive operations.

Local by default

Dashboard inspection and comparison snapshots stay in the browser unless you explicitly submit a redacted summary.

No raw public records

Fingerprint list/detail routes return public-safe metadata without a valid future protected context.

Clear local data

The dashboard and compare view include controls to clear browser-only snapshots.

No key exposure

PLATPHORM_API_KEY is never stored in browser storage, fingerprints, public docs examples, RSS, sitemap, llms, or traces.