Security
How we protect your organisation's data. If you think you've found a security problem, please email [email protected] — we'll respond quickly and won't take action against good-faith research.
Separation between organisations
Every record belongs to one organisation, and every query in the app is limited to the organisation you're signed in to. Automated tests check that one organisation can never open another's records.
Accounts
- Passwords are stored hashed, never in plain text, with minimum-strength rules.
- Two-factor sign-in (authenticator app) is required for owners and admins.
- Sign-in attempts are rate-limited. Password reset links work once and expire in an hour.
- Roles limit what people see — a fire marshal login sees only the evacuation list.
Kiosks
A kiosk holds no password: it's a long, unguessable link that can be revoked or replaced in one click. A kiosk only shows who is signed in at its own site.
Data
- All traffic is encrypted (HTTPS with HSTS). A strict Content Security Policy blocks third-party scripts; fonts and assets are self-hosted.
- Stored secrets (such as your mail server password) are encrypted by the application.
- Photos are only served to signed-in staff of the same organisation, never from public links.
- Uploaded logos are re-encoded to strip hidden metadata.
- Records are deleted automatically after your retention period.
- Payments are taken on Stripe's PCI DSS Level 1 certified pages; card numbers never reach our servers.
- Traffic passes through Cloudflare for protection against denial-of-service attacks; the original hosting address is not exposed.
Accountability
An audit log records exports, deletions, subject access exports, settings, role and plan changes. Your admins can read and download it. Our own platform tools show account-level information only, never visitor records.