Trust
Security and trust
What is in place today, described precisely — including what is not.
Dutyrex is a multi-tenant platform, and separation between organisations is the property we treat as non-negotiable. Every record carries its organisation and every query is scoped by it in the database layer.
Access is role-based and checked server-side on every request. Six roles map to the permissions an operation actually needs, and a permission is evaluated before a handler runs rather than by hiding a link.
Backups are taken daily, encrypted on the server before upload using a public key, and stored off-platform. The private key is held by the owner and is not present on any server, which means a compromise of our infrastructure does not expose a backup. Automated checks confirm a recent backup exists, is a plausible size, and carries valid integrity metadata.
Documents are scanned for national identity and payment card numbers before any AI processing, and a flagged document is refused rather than partially redacted.
Error messages shown to a user are written for that user. Database identifiers, stack traces and server paths are logged privately under a request reference and are never rendered to a browser.
What we are not claiming
We hold no SOC 2 or ISO 27001 certification and we do not claim HIPAA or GDPR compliance certification. We have no customer logos to show you and we are not going to invent any. If a formal certification is a requirement for you, tell us on the demo call and we will be straight about where that sits on our roadmap.
Your data is separated by organisation
Every record carries its organisation, and every query is scoped to it. Separation is enforced in the database layer, not by filtering results afterwards.
Permissions are checked on every request
Six roles, with each permission evaluated server-side. Hiding a button is not access control, so we do not rely on it.
Encrypted backups, held off-platform
Daily backups are encrypted before they leave the server, using a key we cannot read. Automated checks verify that a recent backup exists and is well-formed.
A real audit trail
Consequential actions are recorded with who did them and when. Audit history is never deleted as part of normal operation.
Personal identifiers are detected and blocked
Documents are scanned for national ID and card numbers before any AI processing. A flagged document is refused, not quietly redacted.
Errors do not leak internals
Messages shown to users are written for users. Database details, stack traces and file paths are logged privately and never rendered.