Use only the data needed to produce and retain proof.

This notice covers the Certus marketing site, product account, API, repository connections, verification runs, and support interactions. It does not govern a third party service you choose to connect to Certus.

Certus processes account and tenant identifiers, business contact information, repository and installation identifiers, the repository inputs selected for a run, configuration and policy, execution telemetry, support correspondence, and the evidence and verdicts a run produces.

Billing records include the plan, metered usage, credits, and payment-provider references needed to administer the account. Certus does not need the full payment-card number to run the product.

We use this data to authenticate users, authorize tenant-scoped operations, connect the repositories a customer selects, execute and replay verification, account for usage, secure and operate the service, respond to requests, and meet contractual obligations.

Credentials are accepted through write-only flows, sealed, and leased through brokered capabilities. They are excluded from prompts, logs, and evidence artifacts. Tenant API credentials remain on the server side of the browser boundary.

Certus uses infrastructure, identity, payment, repository-host, and model providers to deliver selected product functions. Each receives the data needed for its role. A deployment that uses customer-managed model keys does not charge that model use against Certus-managed AI credits.

Evidence retention follows the selected plan or customer agreement. Account, billing, security, and audit records may follow different periods where they are needed to operate the service, resolve disputes, or meet legal obligations. Requests to close an account do not erase records that must be retained for those purposes.

Tenant identity is carried with run-owned records and checked before tenant data is returned. Global content-addressed artifacts become readable to a tenant only through an authorized reference belonging to that tenant’s run.

Contact privacy@certus.dev to ask about access, correction, deletion, portability, or another privacy matter. Identify the organization and account concerned, but do not send passwords, access tokens, or repository source in the request.