Trust & Security · Data Handling
Built for case data that can't leak.
TrustAI holds the most sensitive files in the building — protected health information, financial records, and matters involving vulnerable people. This page is the plain-language account of how that data is protected, what is true by construction, and what is still being built. Bonis Systems would rather state exactly where the platform stands than imply more than it delivers.
Three things that are true by construction
A per-user encrypted vault — with an isolation wall
Case documents are encrypted with AES-256-GCM under a key derived per user (HKDF-SHA256, with the user's identity bound into the encryption so a record cannot be decrypted under anyone else's account). On top of that, a structural ownership wall gates every read and write: one user — one accredited rep, one attorney — cannot see another's matter. A missing check denies rather than leaks. It is enforced by construction and proven by test, not by policy alone.
Cryptographic tamper-evidence
Each case's findings ledger is append-only and hash-chained, and is verified on every read — change one byte and it refuses to load rather than serve altered history. Audit records are signed with post-quantum ML-DSA-87 (FIPS 204) keys held in a managed secrets vault, and anchored to the Bitcoin blockchain via OpenTimestamps. The audit trail is content-free by construction — no case text ever enters it.
Encrypted, durable, access-controlled hosting
Traffic is served over TLS 1.3 with HSTS preload and a strict content-security policy behind an edge security layer. Case data persists to durable Google Cloud Storage with Google-managed AES-256 encryption at rest. Passwords are bcrypt-hashed; sign-in and registration are rate-limited; and application secrets — signing keys, the encryption key, API keys — are held in Google Secret Manager, never in code.
How your clients' data is handled
- It stays yours, and isolated. Each organization's and each user's case data is walled off by the ownership check on every operation — there is no shared, cross-tenant view.
- It is durable and encrypted at rest. Sealed case records live on Google Cloud Storage, encrypted at rest, and survive restarts and deploys — nothing is held on a disposable scratch disk.
- The AI sees the case, the audit log never does. When the analysis engine reviews a matter, the content is transmitted under TrustAI's own enterprise API keys over encrypted channels. The tamper-evident audit ledger records only the action taken — method, path, status — and never the case content itself.
- PII detection is built in. A scrubber recognizes key HIPAA Safe-Harbor identifiers — Social Security and bank-account numbers, medical record numbers, dates of birth, phone/email/IP, driver-license and card numbers — for flagging sensitive fields.
- The free tools upload nothing. The filing-window and Visa Bulletin checks run entirely in your browser — no date, no case fact, leaves the device.
The honest status, stated plainly
Security claims are only worth the parts that are true. Here is the current status.
SOC 2 Type IIIn progress — not yet attested. The page will say so until an independent auditor says otherwise; Bonis Systems does not claim a certification it does not hold.
Independent reviewA third-party security review is planned. Until it completes, treat this page as Bonis Systems' own honest account, not an external attestation.
Start on syntheticA new organization can evaluate the full workflow on a synthetic matter — invented parties, dates, and documents — before any real client file is ever uploaded.
Deeper reviewIf a security team needs architecture detail, data-flow diagrams, or a questionnaire completed, Bonis Systems will work through it directly under NDA.