Account privacy

Clairevue stores your verified email, account role and usage caps to run sign-in and API access. The dashboard shows an API key only when you create it; we store its SHA-256 hash and a short identifying prefix, not the key itself.

Resend handles sign-in email delivery. Links expire after 15 minutes and work once, while sign-in cookies expire after seven days. Expired sessions and day-old login intents leave the database during routine account activity. We keep API operation names, transport, status and timestamps for up to 30 days during active service operation, not raw API queries or key values. Expired quota records also leave during activity; there is no scheduled cleanup job for accounts yet.

The shared public-search backend stores a hashed query key and caches results for ten minutes (30 seconds for partial results), plus short-lived leases. It does not persist raw search queries in the cache payload. Model-backed searches send your query and public candidate text to the configured Jev provider (Typesafe.ai). Its retention policy also applies; do not send confidential information in a search.

Account and key metadata remain until account deletion. Email interests use the existing subscriber store and retention rules, separate from account creation. Signing in never grants newsletter consent, and unsubscribing does not delete your account.

We disable page analytics on sign-in, verification and account pages. Hosting and email providers may still keep their own operational records. To request account deletion, contact karim@clairevue.ai. Revoke a key from your account if you think someone else has it.