Trust Center
Built for procurement review
What we protect, how, and the contracts your legal team needs. Our controls are mapped to the SOC 2 Trust Services Criteria. Ordinal has not yet completed an independent SOC 2 audit — we say so plainly rather than display a badge we haven't earned.
Your data never trains models
Briefs, files and Knowledge Vault entries are used only for your orders.
Isolated per client
Row-level security means no other client can read your work.
Pay only on acceptance
Funds are held until you approve the deliverable.
Controls matrix
The criteria references describe intended control alignment, not an auditor's finding that the criteria have been met.
| Area | Control | SOC 2 criteria |
|---|---|---|
| Tenant isolation | Row-level security on every client table; each client can read only its own orders, files and Knowledge Vault. | CC6.1, CC6.3 |
| Encryption | TLS in transit; data and files encrypted at rest by the hosting provider (AES-256). | CC6.7 |
| Access control | Role-based access stored server-side; privileged actions re-check the caller's role on every request. | CC6.1, CC6.2 |
| AI compute & model isolation | Customer briefs, uploaded files and deliverable outputs are not used by Ordinal to train or fine-tune foundation AI models. Enterprise AI processing is governed by commercial no-training terms. Processing may involve project-isolated transient caching and safety or abuse monitoring; this is not a zero-retention guarantee. | CC6.1, CC6.7, C1.1, C1.2, PI1.2 |
| Third-party credentials | Tokens you enter for live pushes (GitHub, webhooks) are used for that one request and never stored. | CC6.1 |
| Signed delivery | Webhook pushes can carry an HMAC SHA-256 signature so your systems can reject forged requests. | CC6.6 |
| Output integrity | Deterministic checks on figures, citations and dates before any deliverable reaches you; failed drafts are reworked, not shipped. | PI1.2, PI1.3 |
| Change & cost control | Bounded retries and per-order compute ceilings stop runaway processing. | CC7.2, A1.1 |
| Payment safety | Card data handled entirely by Stripe; funds held until you accept the work. | CC9.2 |
Contracts for your legal team
Ready-to-review templates. Contact us for a signed copy.
Live integrations
Deliverables can be pushed straight into GitHub as issues, or to any HTTPS endpoint — HubSpot, Salesforce, Zapier, Make or n8n — with an optional signed payload. Access keys are used for the single push and are not kept.