Personal data is hashed by default.

The API is built to decide on weak signals, not to collect personal data. What we receive is hashed unless a plan explicitly opts into raw PII.

Agent Attribution

When a workspace enrolls an account, Chitmark stores its issuer and account reference. If the account holder chooses document verification, Stripe collects the documents and selfie. Chitmark keeps a verification reference, status, and timestamps. A verified email is retained only with explicit consent and disclosed only to an authorized recipient with a current agent proof. The workspace owner can revoke links and remove retained email in the dashboard.

A participating website can resolve an enrolled agent when the agent sends a fresh signed proof for that recipient. Each workspace and site receives a separate identifier. Principal details require separate recipient authorization. The proof includes the agent's public key, which the agent uses across participating websites. Chitmark records attribution outcomes to operate the API. That processing is separate from visitor analytics on Chitmark's own website.

What we receive

By default, subject fields (email, IP, user agent) are sent as SHA-256 hashes and the API returns verdicts, not profiles. Raw PII is accepted only on the Pro plan and up, and never stored beyond the retention window of the plan.

Retention

Trust Decisions events are retained for 30 days on Free and 90 days on Pro to connect verdicts with their outcomes.

Agent Attribution enrollment records are retained for up to 120 days after account authentication. Consented verified email is removed after 90 days or sooner if the workspace owner removes it. Attribution observations are retained for 30 days.

Site visitors

We do not track, analyze, or advertise on site visitors: no visitor analytics, no ad scripts, no third-party trackers. The footer promise is the policy.

Usage data

Metering counts verify events per account for billing and the usage dashboard. It is product usage, not visitor tracking, and it is never shared.

Auth and billing

Sign-in is handled by Clerk, which stores your account credentials under its own privacy policy. Payments run through Stripe; we never see or store card numbers.

Questions: [email protected].