Security & trust
Law firms hand us their clients' most sensitive documents. This page says plainly what happens to them.
Client documents never travel by email
Originals, drafts, and signed translations are never attached to or sent by email. FirmCert's notification emails — an invitation, a document ready for review, a deliverable ready to download — contain only a link to sign in. The documents stay in your workspace.
That matters long after a job is done. An inbox is an archive: every attachment ever sent to it stays in sent folders, backups, and synced phones and laptops. Because FirmCert keeps files out of email entirely, a compromised email account — yours, a colleague's, or an outside translator's — doesn't hold a library of your clients' identity documents.
Outside translators, on your terms
Invite outside or contract translators with their own email address, assign them a specific document as its designated reviewer, and they sign in to review and sign it — no files emailed back and forth. Deactivate them when the engagement ends and their workspace access stops immediately, while their name stays on the certifications they signed.
Encryption, everywhere it matters
Documents are encrypted in transit (TLS) and at rest. Object-storage keys are themselves encrypted per record with AES-GCM and unique IVs, and contact details (emails, phone numbers) are encrypted at rest as well.
Uploads are scanned before they're processed
Every uploaded file passes malware scanning before translation. Files that fail scanning never reach a deliverable; inconclusive scans hold the document for human review rather than shipping it into your firm.
Signer integrity is enforced, not assumed
A certification is a legal attestation attributed to a person. In FirmCert, only the designated signer's own authenticated session can sign a document — a firm admin can't sign for a colleague, our operators can't sign for anyone, and our own support tooling is hard-blocked from signing. Uploads can be delegated; signatures cannot.
Departed members are deactivated, never deleted: the identity attached to every signed certification and audit entry survives staff changes.
An attributable record of every document
Every page credit is logged — when, who uploaded, which document, how many pages, and which signer path — and the log is visible to your firm admins, not just to us. Support actions taken by our team on your workspace are recorded with both identities.
How the engine processes documents
Translations are produced by our proprietary pipeline, which combines commercial language-processing technology with our own formatting and quality systems. Document content is transmitted to the technology providers under API agreements that do not permit training on submitted content. The full subprocessor list is published at /subprocessors.
Text the engine cannot read is marked illegible rather than guessed — an invented name in a legal filing is a far bigger risk than an honest marker, and your reviewers see exactly what the engine saw.
Data handling and deletion
Client documents belong to your firm. Deletion requests are honored on demand, and certain records (billing, audit entries) are retained in de-identified or minimal form where law requires. A data-processing agreement (DPA) for firms is available as part of onboarding.
