AES-256 Encryption
Documents are encrypted with AES-256-GCM before storage.
Each file uses a unique IV and authentication tag. Encryption keys are never stored beside ciphertext.
SeraCase Trust Center
Plain-language explanations of the controls that protect confidential case materials.
Documents are encrypted with AES-256-GCM before storage.
Each file uses a unique IV and authentication tag. Encryption keys are never stored beside ciphertext.
Traffic between your browser and SeraCase uses HTTPS/TLS.
Sessions and API calls travel over encrypted connections to protect credentials and case materials in transit.
Uploads live in private cloud buckets — not public links.
Objects are not publicly listable. Access uses short-lived signed URLs or authenticated decrypt proxies.
Database policies restrict each account to its own records.
Supabase RLS and ownership checks help ensure users cannot read another user’s cases, files, or chats.
Uploads are scanned before processing continues.
Heuristic checks and optional remote scanning run before OCR/AI. Suspicious files are quarantined.
Executable payloads and known test signatures are blocked.
Dangerous extensions, magic-byte executables, and EICAR-style signatures are rejected with clear user messages.
Platform backups rely on provider encryption at rest.
Infrastructure-level encryption complements application-layer file encryption for stored materials.
Preview and export links expire quickly.
Document previews and case export downloads use short TTLs to reduce risk if a link is shared accidentally.
Security-relevant actions are recorded for accountability.
Login, upload, download, delete, export, and related events can be reviewed in your activity history.
Admin tools are allowlist-gated; users own their cases.
Ordinary accounts cannot access admin diagnostics. Cross-user browsing of workspaces is not permitted.
Authenticator-app MFA can be required after password sign-in.
When MFA is enrolled, protected areas require a second factor (AAL2) before the workspace opens.
Idle sessions expire; activity cookies are integrity-checked.
Signed last-activity cookies and trusted-device options reduce risk on shared machines.
Reset flows use email recovery links and session controls.
Password changes are audited. Prefer a strong unique password and MFA for mediator and firm accounts.
Browser protections help reduce common web attacks.
CSP, HSTS, X-Frame-Options, and related headers harden the application surface.
Sensitive routes throttle abusive traffic.
Login, uploads, downloads, and AI routes apply request limits to slow credential stuffing and cost abuse.
Signed-in users can open Security Center and Settings → Security to enable MFA, review trusted devices, and download audit activity. Admins can run the internal security diagnostics scorecard.