Every document is encrypted with AES-256-GCM under a key of its own, those keys are protected under AWS KMS, passwords are kept as Argon2 hashes, every fingerprint is SHA-256, the record's daily anchors sit under S3 Object Lock, and everything is hosted on AWS in Mumbai.
Documents
We encrypt every document with AES-256-GCM as it arrives, before it is stored. Each document has a key of its own. That key is protected by your firm's key, and your firm's key is protected under AWS KMS. Data is encrypted in transit. When a document is deleted, its key is destroyed, so the file cannot be read again. See who can see your documents.
An upload link can add and replace files, and it never returns a document to whoever opens it. We store your client's upload link encrypted under your firm's key so that you can send it again. We store the rights link only as a SHA-256 fingerprint, so no screen can show it again.
Access
Only people signed in to your firm can open your documents, and only through a role that allows it. Each firm's records are walled off from every other firm's inside the database. See admins, members and other roles.
We keep passwords only as Argon2 hashes. Repeated wrong passwords pause sign-in for 15 minutes. Each person can turn on two-factor authentication for their own account.
Every view and every download of a document is entered on the proof record with the person who did it and the document's fingerprint.
Fingerprints and the record
Every fingerprint we compute is SHA-256. That covers each document, each notice, each entry on the proof record and each link in the chain between them. Once a day we publish the fingerprint of your latest entry to S3 Object Lock in compliance mode, which nobody can rewrite. See the daily anchors.
Where it is
We host the documents, the keys, the database and the record on AWS in Mumbai. The database holds written answers and contact details. Its disks and its backups are encrypted. For the other services we use, see whether we share your data with third parties.