Security
Enterprise Security
Published 2026-07-04 · Living document
These policies are published for transparency and are maintained as living documents. They receive ongoing internal review and will receive formal legal counsel review before enterprise deployments. Questions: [email protected].
Beyond the baseline
Our standard security practices are described in Security. For enterprise deployments, the platform's security architecture adds controls designed for organizations with their own compliance obligations.
Enterprise controls (implemented in the platform)
- Per-tenant envelope encryption (AES-256-GCM): each tenant's knowledge is encrypted with its own data key.
- Customer-managed keys (CMK): in CMK mode the platform cannot decrypt your knowledge vault — you hold the key.
- Cryptographic shredding: deletion destroys the key first, making residual data unreadable, then purges and tombstones.
- Hash-chained audit log: tamper-evident, verifiable event chain per tenant, with anomaly detection for suspicious patterns (denied-action bursts, export-then-delete sequences, mass reads).
- Dual-consent transfers: moving an employee between organizations requires both sides' explicit consent and re-encryption under the receiver's key.
- Default-deny access policies with full authorization auditing.
Honest boundaries
During education, knowledge is transiently processed in memory in plaintext — we document this rather than hide it. Compliance posture is computed honestly per configuration: some regimes are only satisfied in CMK mode, and some (e.g. government workloads) we do not currently claim at all.
Talk to engineering
Enterprise security review, questionnaires, or architecture walkthroughs: [email protected] with subject "ENTERPRISE".