Privacy Policy
Last updated: September 28, 2026
1. Information We Collect
When you create an account, we collect your name and email address via our authentication provider (Clerk). When you use the API, we log the URLs you extract, usage counts, and performance metrics. Ordinary one-time extractions retain diagnostics, encrypted URL and prompt, but not the fetched page body. Monitors retain their last extraction, its evidence status and change history so they can detect and report changes. If you opt into page reuse with a positive maxAge, eligible fetched page bodies are stored privately for your account for up to 24 hours or a shorter origin expiry. Default zero skips those cache reads and writes; it does not disable diagnostic or monitor retention. Authenticated requests using an Idempotency-Key make the encrypted completed response available for replay for 24 hours. After replay expires, the response bytes are queued for scheduled deletion. When you use snapshot verification, we also retain encrypted copies of the HTML snapshots you submit, your field contracts, proposed values, verification results and review labels for your account.
2. How We Use Your Information
We use your information to provide and improve the Contrie service, track API usage against your plan limits, and communicate important service updates. We do not sell your personal information to third parties.
3. Data Security
API keys are hashed with SHA-256 before storage. Connections to Contrie use TLS. If you ask Contrie to fetch anhttp:// source, that source hop is not encrypted; use HTTPS source URLs when transport confidentiality matters. Your account is protected by Clerk's authentication infrastructure. We retain usage logs for billing and debugging purposes.
4. Third-Party Services
We use the following third-party services: Clerk (authentication), Neon (database), Vercel (hosting), OpenRouter and the selected downstream model providers (AI processing), TypeSafe (automated classification of monitor changes: it receives a monitor's request text and the changed values, never your account details), Upstash Redis (shared request limits), and Stripe (payments; through Stripe Managed Payments, Stripe's Link is the merchant of record and receives the billing details you enter at checkout). The rate-limit store receives pseudonymous key/account identifiers or a hash of the platform-observed network address for anonymous receipt verification. Model requests can include reduced page content, requested fields and, for eligible rendering, a screenshot. Each service has its own privacy policy governing how they handle data.
5. Data Retention
Extraction diagnostics expire after 90 days on the Free plan or 1 year on paid plans, based on the plan when the request began. Scheduled cleanup runs every 15 minutes to delete expired diagnostics and expired encrypted replay responses in bounded batches. Deletion can take longer during a backlog or service interruption; this schedule does not promise immediate removal. A completed response stops being available for replay after 24 hours even while its stored bytes await cleanup. Snapshot verification content stops being available after 7 days. Its content-free hashed request identities expire after 30 days so retries can be recognized without retaining the submitted page content. The same scheduled cleanup deletes expired verification content and identities in bounded batches, with the same possible backlog or service delays.
Never-billed accounts can delete Contrie product data from dashboard settings after pending work settles. Accounts with current or historical billing require support-led reconciliation first. Billing and deletion evidence, monthly usage totals, hashed request keys and outcomes, and a hashed sign-in identity linked to the account are retained to preserve accounting and prevent deletion from resetting allowances or repeating completed work. These retained records contain no extracted page content; the identity link is pseudonymous, not anonymous. The Clerk sign-in identity may also be retained. Successful product-data deletion removes saved snapshot verification content; its content-free hashed retry identities remain until their normal expiry and cleanup. The GET /api/v1/export endpoint exports the product-data families it names in its response; contact us for a broader privacy data request.
6. Your Rights
From dashboard settings you can delete your Contrie product data or download a copy of it (the same scoped export as the API). For anything broader, including your sign-in identity, contact us; we will respond to data requests within 30 days.
7. Contact
For privacy-related questions, contact us at privacy@contrie.com.