docs: the SOC 2 row said Compliant with nothing behind it

The ISO 27001 and HIPAA rows on this page say Planned, which is true. The
SOC 2 row said Compliant and the section callout linked that word to the
trust page, so a reader took it as a report that exists. It does not — no
auditor, no attestation, no Type II period. The row and the callout now say
what a buyer can act on, and the section states the controls actually in
place and where formal certification gets decided.
This commit is contained in:
2026-08-14 20:00:26 -07:00
parent ecb5146422
commit 6fcaf801bc
@@ -7,12 +7,12 @@ import { Callout } from 'fumadocs-ui/components/callout';
### Compliance Status Overview
| Certification | Status |
| -------------- | ---------------------- |
| 21 CFR Part 11 | Compliant (Enterprise) |
| SOC 2 | Compliant |
| ISO 27001 | Planned |
| HIPAA | Planned |
| Certification | Status |
| -------------- | ----------------------------------- |
| 21 CFR Part 11 | Compliant (Enterprise) |
| SOC 2 | Certification scoped per engagement |
| ISO 27001 | Planned |
| HIPAA | Planned |
## 21 CFR Part 11
@@ -31,10 +31,14 @@ Read more about [21 CFR Part 11 with Hanzo eSign](https://esign.hanzo.ai/21-CFR-
## SOC 2
<Callout type="info">Status: [Compliant](https://esign.hanzo.ai/trust)</Callout>
<Callout type="info">Status: [Certification scoped per engagement](https://esign.hanzo.ai/trust)</Callout>
SOC 2 is a framework for managing and auditing the security, availability, processing integrity, confidentiality, and data privacy in cloud and IT service organizations, established by the American Institute of Certified Public Accountants (AICPA).
Controls aligned to the SOC 2 Type II control set — encryption in transit and at rest, role-based access control, and audit logging.
Formal certification — SOC 2 Type II, ISO 27001, HIPAA with a BAA — is scoped per enterprise engagement. Tell us what your procurement needs.
## ISO 27001
<Callout type="warn">Status: [Planned](https://github.com/hanzo-sign/backlog/issues/26)</Callout>