Privacy
Search queries are private to the person or workspace that submits them. CertificateScan does not publish a user's query history automatically.
Data processed
This build processes account name and email, password credentials through Better Auth, database-backed sessions, short-lived verification and recovery records, saved hunts, API-key metadata, an API usage ledger, and Stripe customer/subscription identifiers and status. Cleartext passwords, personal API keys, and payment-card details are not stored by the application; payment details stay on Stripe-hosted surfaces.
Optional public-site analytics
With your explicit permission, CertificateScan uses Google Analytics on a fixed set of public marketing, documentation, status, and legal pages. Page locations are sent without query strings or referrers. CertificateScan does not send user IDs, email addresses, search queries, investigated domains, certificate fingerprints, API locations, authentication pages, or workspace activity to Google Analytics. The Google tag is blocked until permission is granted, and your choice is stored only in this browser. You can change it through “Analytics choices” in the footer.
Email and payment providers
In the production profile, the account email address and verification or recovery message are sent to the configured transactional email provider. When billing is enabled, Stripe processes checkout and subscription management and sends signed status events to CertificateScan. Auth links expire after one hour. Provider retention, transfer terms, and the final subprocessor list must be published before a paid public launch.
Public intelligence
Certificate records and public endpoint observations originate from public internet infrastructure. Public source data is kept separate from customer account data.
Retention and controls
Production retention periods, webhook-event audit retention, subprocessors, export and deletion controls, and regional rights must be finalized before a paid public launch.