Trust & safety

Security

For configured pre-call policies, the gateway decides before the model call. The response includes a signed record of Seal's outcome and applied policies. This page documents the controls we apply to our own infrastructure.

Last updated 1 October 2026

Checked before it acts. Offline check against a pinned key.

Seal leaves one signed file for each consequential AI decision that passes through it: a model call, or an agent's tool action. Same file for your team, counsel, and auditors.

A reviewer opens that file offline, on an air-gapped machine if needed, and checks it against our published key. The receipt stands without a network call. Change one signed field and the signature dies.

Open specification

ATTESTATION-v1

Open envelope · Apache-2.0

Published verifying key

9Y3Eiq6V8QjRDUM5nPqSwKIOPQaoEU4SbagfYFdvWa4

Ed25519 · 32-byte public key · in use since 2026-08-09

Receipts issued before then are signed by a previous key, listed at issuer-keys.txt. Retired keys are never withdrawn: a receipt must stay checkable for as long as the decision it records matters.

Engineers can run the open verifier

# Python

on PyPI ↗

pip install aqta-verify-receipt

# save as check.py; sample: curl -sO https://app.aqta.ai/samples/sample-receipt.json
import json
from aqta_verify_receipt import verify_receipt

receipt = json.load(open('sample-receipt.json'))
key = '9Y3Eiq6V8QjRDUM5nPqSwKIOPQaoEU4SbagfYFdvWa4'  # published key
print(verify_receipt(receipt, trusted_public_key=key).valid)  # True

# TypeScript / Node

on npm ↗

npm install aqta-verify-receipt

// save as check.mjs; sample: curl -sO https://app.aqta.ai/samples/sample-receipt.json
import { readFileSync } from 'node:fs'
import { verifyReceipt } from 'aqta-verify-receipt'

const receipt = JSON.parse(readFileSync('sample-receipt.json', 'utf8'))
const key = '9Y3Eiq6V8QjRDUM5nPqSwKIOPQaoEU4SbagfYFdvWa4' // published key
console.log(verifyReceipt(receipt, { trustedPublicKey: key }).valid) // true

Three properties a signed record can be asked to prove, worked through on a real production receipt. Authenticity is solved, correctness is partial, and completeness is open. Break each one yourself: What a signature cannot prove.

For regulated buyers

A vendor's own log is evidence written by the party being questioned, and that review is where deals stall. Since January 2025, DORA has made EU financial entities ask ICT third parties harder questions about what their models did, and those questions land on exactly that log. DORA does not ask for cryptographic evidence. Seal answers the question anyway.

Seal clears the model into that review with one signed file of what it decided, checkable offline against the published key. Attach it to a filing pack for counsel or audit, or refuse with a precise hole. Evidence for audit and regulatory review. Not a certification. Not a claim that a court must accept it.

When the record cannot be checked, someone pays. Horizon and the Dutch childcare-benefits cases both turned on automated systems whose operators could not produce an independent check of what the system decided.

Sources: Post Office Horizon Inquiry · Dutch childcare-benefits inquiry · Signed receipt

1. Data architecture

We do not store prompt content or model responses. The gateway inspects requests in transit to enforce configured policies (PHI detection, loop detection, spend limits) and immediately discards the content. Only metadata is retained.

Prompts and responses are processed in transit and not persisted; only one-way hashes and signed metadata are retained, per your retention tier
Metadata retained: timestamps, model names, token counts, policy outcomes, costs
Seal maintains an internal per-organisation hash chain that the authenticated dashboard checks during review
Optional advanced proving modes, when enabled for a workflow, are in preview and are not required for receipt verification

2. Encryption

TLS for all traffic in transit
AES-256 for data at rest
Receipts use an open signed format (ATTESTATION-v1), signed with Ed25519
SHA-256 internal hash chaining for dashboard sequence integrity
Optional advanced proving modes in preview; not required for receipt checks

3. Infrastructure

EU-hosted: gateway and database on Google Cloud in Belgium, website functions in Dublin; encryption at rest and in transit
Production signing keys are loaded only in the gateway environment
Rate-limit blocks lift within 24 hours, so a shared address is never locked out indefinitely
Rate limits are held in memory, per instance, when no shared cache is configured
Per-tenant isolation: all keys scoped to organisation ID

4. Authentication & access

OAuth 2.0 sign-in with provider ID verification
OTP via email, no passwords stored
Cross-tenant access is enforced with organisation-scoped queries
API keys hashed at rest
Enterprise SSO on request

5. Evidence coverage

EU AI Act: signed records support Article 12 and Article 14 evidence work; the export includes directional Articles 9-15 mapping
GDPR: EU-hosted option and data-minimisation controls; customers remain responsible for their own legal assessment
HIPAA: PHI detection and no prompt-or-response persistence in the Health pack; a Business Associate Agreement is subject to engagement
DORA, MiFID II, NIS2 and SR 26-2: FinServ policies and signed exports can support pilot evidence review
ISO/IEC 42001: design alignment only; Aqta is not certified

Framework references

Framework	Scope	Status
EU AI Act	All tiers	Evidence for Arts. 12 and 14; mapping supports review
GDPR	All tiers	Data-minimisation controls; customer obligations remain theirs
HIPAA	Health pack	PHI features; BAA subject to engagement
ISO/IEC 42001	All tiers	Roadmap
DORA · MiFID II · NIS2 · SR 26-2	FinServ pack	Evidence features for pilot review

6. Vulnerability disclosure

We welcome responsible disclosure of security vulnerabilities. If you believe you have found a security issue, please contact us before disclosing publicly so we can investigate and remediate.

Contact: security@aqta.ai with subject "Security disclosure".

7. Contact

For security enquiries: security@aqta.ai
Aqta, Dublin, Ireland

Now taking pilots.

A free 30-minute evidence review first, then up to five working days on one workflow: one review path, one evidence pack, judged against your reviewer’s own criteria.

Apply for a pilot Verify it yourself