2-week trial Try Remediate free for two weeks on your own PDFs. Contact team

Trust

Security built for public documents.

Remediate is designed for publicly published records, with a private review workspace before anything goes live.

Tenant isolation

Every document, ticket and usage event is scoped to a workspace. Access is checked on every request.

Private by default

Uploads start as drafts. The viewer URL is gated until a document is deliberately published, and published documents are kept out of search indexes.

Encrypted transport

TLS is required in production with HTTP Strict Transport Security. Cookies are HttpOnly, SameSite and Secure. Sessions are revocable.

Encryption at rest

The database and object storage encrypt data at rest. Originals and derived transcripts are private objects, served only through an access-checked route.

Least privilege

Owner, admin and member roles. Platform administration is separate from customer workspaces and protected by two-factor authentication.

Auditability

Sign-ins, password and two-factor changes, uploads, publishes, deletes, team changes, billing changes and support actions write to an audit log.

Backups and recovery

The database is exported daily, encrypted to a public key, checksum-verified, with a documented restore procedure that is exercised against those artifacts. Document files are not currently mirrored to a second location, so a deleted document is removed at once and cannot be recovered from a backup.

AI processing

Document enrichment uses a third-party AI provider. Automatic enrichment can be turned off for a workspace; translation and question answering run only when a reader asks for them. Providers are listed at /legal/subprocessors.

Accessibility

The viewer is keyboard operable with semantic tables, landmarks and announcements. Our target and known limitations are published in the accessibility statement.

Report a vulnerability

Use the contact page and select the security topic. Our disclosure policy is published at /.well-known/security.txt. We aim to acknowledge a security report within two business days and to tell you within five whether we are treating it as a vulnerability.

This page describes the current build. The DPA and subprocessor list are published, the accessibility statement says where our conformance report stands, and other security-review material is available on request.