Exhibit · Privacy

Privacy.

Effective 21 May 2026

The one-paragraph version
Read this first

We store a Clerk session for you, an audit log of the wallet addresses you queried, and short-lived IP-derived rate-limit counters. We do not sell anything to anyone, run advertising pixels, or fingerprint visitors. Everything below is the long version of that sentence.

What we collect
By category, with reason
  • Account identity. Email and any identity-provider profile fields you authorise through Clerk (Google sign-in, etc.). Required to keep your audit history attached to you and to enforce invite-only access.
  • Audit history. The Solana addresses you submit, the timestamp, and the verdict we returned. Persisted so you can re-open prior audits without re-running them.
  • Rate-limit counters. A short-lived, per-IP-prefix counter in Upstash Redis. Used to prevent abuse. Not joined to your account, expires within minutes.
  • Server logs. Vercel records request-level metadata (URL, status, region, IP) for operational reasons. Retained per Vercel's policy.
Sub-processors
Where the data physically lives
  • Vercel — hosting, build, edge delivery.
  • Clerk — authentication, session management.
  • Helius — Solana RPC for the on-chain reads we perform on your behalf. We send public addresses; we never send Auditor account data.
  • Upstash — Redis for rate limiting.
  • Postgres (provisioned via Vercel Marketplace) — audit history.
No tracking, no resale
What we don't do
  • No advertising pixels, analytics SDKs, fingerprinting libraries, or session-replay scripts.
  • No sale or sharing of personal data with third parties, ever. The sub-processors above are operational dependencies, not data buyers.
  • No cross-site tracking. We do not embed third-party iframes that read your other browsing context.
Your rights
If you want it gone

Email 0xpushrax@gmail.com from the address on your account and ask for a copy of your data, a correction, or a full deletion. We act within 30 days. Deletion removes your account, audit history, and any cached lookups attributable to you; it does not retroactively expunge anonymised aggregate counters or server-side logs that Vercel rotates on its own schedule.

Versioning
Changes

Material changes get a new effective date at the top of this page and a note in the changelog when we have one. Continued use after the new effective date is acceptance.