Security & privacy
Built for the most sensitive material you hold.
Case information is treated as highly sensitive by default. The architecture is defensive in depth; nothing here depends on trust in the interface alone.
Tenant isolation
Every case lives inside an organization with row-level security at the database — not just checks in application code. Cross-tenant reads and writes are denied by the database itself, and an automated suite proves it for every resource class.
Access & identity
Passwords are hashed with Argon2id; sessions are 256-bit, stored hashed, and rotated. Optional TOTP two-factor authentication, per-account rate limiting, and lockout are standard. Roles combine at the organization and case level, and the most restrictive rule wins.
Evidence integrity
Uploaded originals are immutable and content-addressed (SHA-256). Every transformation stays linked to its original. Audit events are append-only — the database rejects updates and deletes. Version history is preserved for claims, notes, entities, and timeline events.
Privacy
No training on case material. AI processing sends only explicitly scoped, case-authorized content to the configured provider — local by default. No case content appears in operational logs. Backups are encrypted, and restoration is tested.
Alignment, not certification
Controls are documented against common frameworks (e.g., NIST 800-53 control families). Second Trace does not claim formal compliance or certification — those require independent audit.