# Security and data handling

- Tenant isolation: every document, ticket and usage event is scoped to a workspace, and access is checked on every request.
- Private by default: uploads start as drafts, viewer URLs are gated until a document is deliberately published, and published documents are excluded from search indexes.
- Encrypted transport: TLS is required in production with HSTS; cookies are HttpOnly, SameSite and Secure; sessions are revocable.
- Encryption at rest: the database and object storage encrypt data at rest; originals and transcripts are private objects served 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: the database is exported daily, encrypted to an offline key, checksum-verified, with a documented restore procedure that is exercised against those artifacts. Document files are not currently mirrored to a second location.
- AI processing: document enrichment uses a third-party provider and can be turned off for a workspace; translation and question answering run only on request. Providers: https://remediatepdf.com/legal/subprocessors
- Accessibility: the viewer is keyboard operable with semantic tables, landmarks and announcements.

Security reports: https://remediatepdf.com/security — disclosure policy: https://remediatepdf.com/.well-known/security.txt

Canonical: https://remediatepdf.com/security
