Privacy and retention

Who provides Heretic

Heretic is operated by HYPR PTE. LTD., a Singapore company with UEN 202520273N, at 408B FERNVALE ROAD, SINGAPORE 792408. Our terms of service cover accounts, subscriptions, and use of the service.

Data used for an assessment

The collector does not read application cookies or create advertising identifiers. It can test browser storage and cache a configured service address in session storage. The public site key associates the result with your site. Signing in to Heretic uses security cookies for the account session and registration flow.

Ordinary collection

A successful collection returns a request ID. Your server can use a secret key to read the verdict, observed address, connection details, and browser claims. The site operator is the controller of that record. The dashboard shows session evidence for seven days.

Results can include browser instance, machine, and rendering identifiers. Each is scoped to the site key and its version. Matching values mean matching normalized inputs; distinct devices can share them.

Phone verification and passkeys

A phone verification ceremony collects motion and orientation readings, timestamps, interaction records, and browser and connection assessments. A desktop hand-off can link the phone and desktop assessments. The requesting site can supply an account reference and action information.

Passkey verification provides a credential identifier, public key, verification response, and authenticator metadata. Local device verification happens through the authenticator; this protocol does not send Heretic a fingerprint image, face image, device PIN, or private key.

Ceremony history is available for seven days from creation. Credentials remain until explicit erasure because later account-exclusion checks can use them. Erasing one site's history does not revoke named-account credentials shared across that customer's sites.

Zero data retention

Set zdr: true when the collection must leave no stored record. Success returns the same request-ID shape as ordinary collection.

• The result is held in memory for ten seconds and allows one authorized read.
• Heretic destroys the result during that read. Later reads return 404.
• The result does not appear in stored session history or the dashboard.

This setting applies to that collector request. It does not erase separate ceremonies, passkey credentials, customer accounts, billing, or support records.

Heretic website analytics

heretic.tech and the dashboard send page views, clicks, browser errors and session recordings to PostHog. Dashboard text and form inputs are masked in recordings. Signing in links these records to your account email and workspace.

PostHog does not run on the collector, the widget, the challenge or clearance pages, or the signup check. It receives nothing about your visitors.

Deletion

Revoking a key stops future use of that key. Retiring a site disables its active keys. Erasing a site's data hides its stored verdict history and queues physical deletion. It also removes that site's widget ceremonies and associated anonymous credentials.

The backend erasure API can remove a selected ceremony or the ceremonies and credentials associated with a customer's account reference. Deletion submissions are retried if storage is unavailable; a submitted receipt confirms acceptance of the deletion request, not that every physical copy has already been destroyed. Erasure receipts are retained for one year, or longer while a deletion remains pending.

Account and billing records are separate from measurement history. Contact hello@heretic.tech for questions about those records or a privacy request.

Stripe processes card payments and billing invoices. If you choose crypto checkout, MoonPay Commerce processes the wallet payment against your invoice. Transactions on public blockchains, including wallet addresses and amounts, are publicly visible.