Security.

HAVTO stores health and safety records that may be relied on in audits, investigations, and disputes. This page summarises the measures built into the product today. It is descriptive, not a certification or guarantee.

Tenant isolation

Every record belongs to exactly one organisation. Isolation is enforced at the data layer — queries are filtered by organisation by default, so one customer cannot read another's records. Organisation owners control who joins, and what each member can see and do, through roles and the permissions matrix.

Identity and access

Sign-in runs on industry-standard OpenID Connect. Passwords are stored only as salted hashes — we never store or email plaintext passwords. Two-factor authentication is available, sessions expire, and lockout applies after repeated failed attempts.

Transport and payment data

All traffic between your browser and HAVTO is encrypted in transit over TLS. Card details are entered directly into Stripe's hosted pages — they never touch HAVTO's servers, and we never see or store card numbers.

Audit trail and evidence integrity

Changes to significant records are written to an append-only audit trail with actor, timestamp, and before/after state. Evidence exports are hash-chained so tampering is detectable. This is the same trail that underpins the verification and statutory-claim features.

Monitoring and secrets

Errors and anomalies are captured in Sentry with correlation identifiers so a support report can be paired with the server trace. Application secrets live outside source control, and a documented rotation runbook covers keys, tokens, and webhook signing secrets.

Retention and deletion

Data follows the lifecycle described on the data retention page — active, grace, read-only, archive, and purge stages — so records are kept only as long as the documented schedule requires.

Reporting a vulnerability

If you believe you have found a security issue in HAVTO, please report it through the support page rather than disclosing it publicly. Include steps to reproduce; we will acknowledge and investigate.

This page describes current product behaviour and is not a security certification or audit report. Found a security issue? Please report it through the support page.

Privacy policy | Terms of service | Data retention | Contact support