How we protect the record

We are an early-stage company and we would rather tell you exactly where we stand than imply a maturity we have not reached. Where something is a design commitment rather than an independently audited fact, we say so. If your firm has a security questionnaire, send it. We will complete it, and we will sign a data-processing and confidentiality agreement before a pilot begins. For vendor review there is also a condensed security due-diligence brief covering the controls, the evidence behind each one, and what we do not have yet.

Encryption

• In transit. The website and product are served only over HTTPS/TLS, with HSTS enabled, so traffic between you and us is encrypted.
• At rest. Stored data and documents are envelope-encrypted with AES-256-GCM. Each File has its own data key, wrapped by a customer-managed AWS KMS key, and in production the platform refuses to start if encrypted storage is not configured. We will not run a pilot on client data that is not encrypted at rest.

Keeping one firm's file away from another

Tenant isolation is enforced in the database with row-level security, so a File belonging to one firm is not reachable by another account. Within a File, access is scoped by role, and privileged material sits in separate lanes visible only to the parties entitled to see it.

Access control

• Multi-factor authentication is available, by authenticator app (TOTP). Passkeys are on the roadmap.
• Every party's identity is recorded on the File when they join, and access is role-based rather than all-or-nothing.
• Actions are attributed to the party who took them and written to the record.

Integrity and tamper-evidence

This is the heart of the product. Every entry on a File is content-hashed (SHA-256) and chained to the entry before it, so the record is append-only: nothing can be quietly changed or removed after the fact. At closing the File is sealed into a Certified Archive with a Merkle root, and that archive can be verified offline, on any machine, with no account and no call to us. Edit a single byte and verification fails.

In the spirit of not overclaiming: today the timestamps in the chain are ours by default, and the product labels them that way. Anchoring those checkpoints to an independent RFC-3161 timestamp authority is implemented and test-verified, but it is not yet switched on as the production default; making it the default is on our near-term roadmap. The demo says the same thing where it matters. And, as we say throughout the site, none of this decides admissibility. A court does; we make the record cheap to verify and expensive to fake.

Logging, backups, and continuity

• Access and activity are logged as part of the record itself.
• Database backups are live today: daily snapshots with thirty-day point-in-time recovery, run across two availability zones with deletion protection. The full retention schedule is in the due-diligence brief; we have not yet run our first restore drill, and we say so there too.
• If we ever disappear, your sealed records do not. Because a Certified Archive verifies offline without us, the files you have already sealed stay independently verifiable regardless of the company's status, a continuity property most cloud tools cannot offer.

Where your data lives

Data is hosted in the United States on Amazon Web Services (US East region). We do not sell or rent data, and we do not use advertising trackers. See our Privacy Policy for what the website itself collects (in short: cookieless, no persistent identifier, and we do not store your IP address).

Responding to legal process

If we receive a subpoena or other demand for a firm's data, our commitment is to require valid legal process, to notify the affected firm promptly where we are lawfully able to, and to give you a reasonable opportunity to object or move to quash before we produce anything, so that decisions about privilege and scope stay with you and your client, not with us. The specifics are set out in the pilot agreement.

What we do not have yet

We are not SOC 2 or ISO 27001 certified today, and we will not pretend otherwise. For a five-firm founding cohort, our answer is concrete practice plus a signed agreement rather than a certificate on the wall, and a roadmap to formal attestation as we grow. We are glad to talk this through directly.

Questions, or a security questionnaire to send? Email jesse@jeskelgroup.com. This page describes our practices in good faith and is not a warranty; the binding commitments for a pilot live in the written agreement.