SHA-512 file fingerprinting
Every file is hashed with SHA-512 at the moment of upload. The fingerprint is re-computed and compared on access, so any alteration — however small — is detected and surfaced immediately, with the full verification history retained.
Chain-of-custody records
Custody events are recorded automatically for online and offline exhibits: who collected the item, the collection environment, every access, and every transfer — compiled into authenticity certificates suitable for service.
Per-firm isolation, per-case permissions
Each firm's data is isolated from every other firm's. Within a firm, access is granted case by case — a team member sees only the matters they are assigned to, with roles controlling what they can do there.
Activity audit logs
Sign-ins, views, downloads, shares, and administrative changes are logged. When a question arises about who did what and when, the answer is in the record — not in anyone's recollection.
Encrypted transport
Connections to the platform are made over TLS, so evidence and credentials are encrypted in transit between your browser and our servers.
Controlled third-party ingestion
Evidence from clients and witnesses arrives through expiring, tokenized upload sessions — never open inboxes. Material is fingerprinted on receipt and held for solicitor review before it joins the case file.
We only publish what we can demonstrate
Marketing copy on a legal-technology product is read as a representation, and we treat it that way. The measures above describe how the platform actually behaves. We do not use phrases like “bank-grade encryption” or “zero-knowledge”, and where a capability is on our roadmap rather than in production, we will say so rather than imply otherwise.
If your firm requires detail beyond this page — architecture, data residency, retention, or incident handling — ask us. Security questionnaires are answered by the people who run the platform.