How we keep your data safe

Every page and API call is served over HTTPS, with HSTS so browsers never fall back to plain HTTP. The database is encrypted at rest (AES-256) by our database provider, and backup archives are encrypted before they leave our systems.

Owners, managers, staff and read-only viewers each see what their role allows. Every request is checked on the server against the properties that account may access, and automated tests check that one host can never read another host's data.

Repeated failed sign-ins lock the account for a short period. Resetting a password ends every other session. A sign-in from a new device sends an email alert. Two-factor authentication is available for every account.

Card details are entered on our payment processor's hosted payment pages, so we never receive or store card numbers. Payment notifications are verified with a shared secret before any booking or invoice is marked paid.

Sign-ins and sensitive changes are recorded with who, when and from which IP address. The audit log is append-only at the database level: entries cannot be edited or deleted through the application.

Errors are reported to our error tracker, health checks run around the clock and alert the team, and the database is snapshotted every day. Current service health is public on our status page.