Security

Where your data lives

DutyHub runs on Amazon Web Services. Each customer's records are held in a database with tenant scoping enforced in the query layer rather than by application convention — a read is constrained to your organisation before it reaches the database, and a write that names another organisation is refused rather than filtered.

Hosting region: to be confirmed

Encryption

• In transit: TLS, with HTTP redirected to HTTPS and strict transport security enabled.
• At rest: storage-level encryption, plus field-level encryption for designated sensitive fields.
• Uploaded files are scanned for malware before they are accepted.

Access control

• Permissions are per datastore and per record, with row-level rules where a record should be visible only to particular people.
• Two-factor authentication is available using an authenticator app, SMS or email.
• Single sign-on is supported, as are inbound SCIM provisioning and de-provisioning.
• Sessions have an idle timeout, and a countdown warns before it expires rather than discarding work silently.

No-login links

Several things — a contractor uploading a certificate, a casual worker acknowledging a procedure, a QR check in a plant room — deliberately work without an account. Those links are scoped to one purpose and one record, carry an expiry and a use limit, can be revoked, and are stored only as a hash, so the raw link exists in the message and nowhere else. Refusals are deliberately identical whether a link is expired, unknown, spent or wrong, so the endpoint cannot be used to discover which.

That is a trade and it is worth stating plainly: a link records that somebody holding it acted. It is not identity verification.

Audit trail

Changes to records are audited, and the audit trail is sealed into a tamper-evident chain — so the record of what you knew and when is not something that can be quietly tidied up later. That property is the whole point of a compliance record, and it is why decisions are written through the audit path rather than saved as documents.

Backups and continuity

Databases are backed up automatically with point-in-time recovery, and uploaded files are held in durable object storage. Restores are tested; a backup nobody has restored is a hypothesis.

Certifications

DutyHub does not currently hold a formal information security certification, and this page will say so until it does. A certification we have not been awarded is a misrepresentation rather than a marketing decision. If a certification is a procurement requirement for you, please ask us where we are with it.

Reporting a vulnerability

If you believe you have found a security problem, please tell us at to be confirmed. We will acknowledge your report, keep you updated, and will not pursue anybody who reports something in good faith and does not access or destroy other people's data while doing it.