Security overview
HalvorAI operates in monitor-and-evidence mode. It does not sit in the payment authorization path and does not make payment decisions.
Tenant isolation
Section titled “Tenant isolation”Every organization’s data is isolated with PostgreSQL row-level security. The API sets the organization for every transaction from
the authenticated key or session, and a query without one is refused. Tests confirm that one organization’s key gets
404 for another organization’s ids on every route. Test and live environments are separate databases.
Keys and secrets
Section titled “Keys and secrets”- API keys are 32 random characters, stored only as a SHA-256 hash. The prefix is shown for identification. Revocation takes effect within 30 seconds.
- Source keys are Ed25519 keys generated on your machine. HalvorAI stores only the public key.
- Pack signing keys rotate by adding a new key id. Old public keys stay published forever so old packs keep verifying.
- Secrets, signatures and evidence values are redacted from logs.
Data protection
Section titled “Data protection”- TLS 1.2 or later in transit, and AES-256 encryption at rest.
- Card numbers are never accepted. Ingest rejects any field holding a card number, and the SDKs redact them first.
- Instruction text is never sent, only its hash and an optional redacted summary.
- Events, evidence, verification results, audit records and chain anchors are append-only. A correction is a new event that refers to the old one.
- Evidence packs live in US-region object storage with a seven-year retention lock.
Access control
Section titled “Access control”Dashboard roles are described in roles and access. Owners and admins use multi-factor authentication in production. Every write, and every view of evidence or a pack, is recorded in an audit log. Internal staff access to customer data needs a ticket and appears in the audit log your organization can see.
Integrity you can check
Section titled “Integrity you can check”You do not have to trust HalvorAI’s word that evidence is intact. Events are signed by their source, linked in a hash chain with signed daily anchors, and packs carry a signed manifest. See verify an evidence pack.
Residency and scope
Section titled “Residency and scope”All storage and compute run in US regions. The service does not accept personal data of EU or UK data subjects. See data handling.
Assurance status
Section titled “Assurance status”HalvorAI is preparing for a SOC 2 audit and does not yet hold a report. Do not describe it as certified. A security questionnaire (SIG Lite or CAIQ) is available on request.