DiveHQSecurity and data protection
How DiveHQ keeps each centre’s records apart, who can see guest medical answers, and what a signed form proves.
Liability release
Blue Reef Divers
- Typed name
- Sara Mahir
- Time
- 21 Sep 2026, 08:14 GMT+5
- IP address
- 203.0.113.24
- Device
- Safari on iPhone
- SHA-256
- 9f2c 41d8 b07e … 5e71
Keeping centres apart
DiveHQ serves many dive centres from one system. The separation between them is enforced by the database, not only by the screens.
Row-level security on every centre's records
Each record carries its centre, and the database refuses to return a row that belongs to another. The rule is forced on, so it applies to every query the app makes.
A restricted database account
The app connects to the database as an account without administrator rights, and every request is scoped to one centre before it reads or writes anything.
Files kept under each centre's own folder
Invoices, logos and uploaded documents are stored in Cloudflare R2, which encrypts them at rest. A file opens only for a signed-in member of the centre it belongs to, through a link that expires after five minutes.
Signing in and staff access
Who can get in, and what each person can do once they are in.
No passwords
Staff sign in with Google or with a one-time link sent to their email address, which expires after 15 minutes. There is no password to reuse, guess or leak.
Limits on sign-in attempts
Repeated sign-in attempts from the same address are refused for a short time.
Seven staff roles
Owner, admin, front desk, dive staff, equipment, HR and read-only. Only the owner can change billing, and front desk staff cannot void or credit an invoice.
Encrypted staff records
Salary, bank and identity details are encrypted with a key for your centre and shown only to the roles allowed to see them.
An audit log
Changes to bookings, guests, invoices, cash, staff records, roles and invitations are recorded with who made them, when, from which IP address, and what changed. It is kept under Settings.
Guest medical answers and signed forms
Medical answers are health data, and a signed release may one day need to be produced as evidence.
A full record of every signature
Each signed form is stored with the typed name, the time, the IP address, the device, and a SHA-256 hash of the exact text that was signed. A form completed on the desk tablet also records which member of staff opened it.
Medical answers visible to booking staff only
A guest's answers can be opened by staff who can view bookings. The boat manifest shows only the guest's medical status.
Your data
What DiveHQ does not hold, and how to get data out.
No guest card details
DiveHQ records payments taken on your own terminal, in cash or by transfer. It never receives or stores a guest's card number.
Guest data export and erasure
Export a guest's personal data from their profile, or erase it. Erasing is limited to owners and admins.
Encrypted connections
The app and this website are served over HTTPS, and the sign-in cookie cannot be read by scripts on the page.
Report a security issue
If you think you have found a vulnerability, email us with the details and how to reproduce it. Please give us a chance to fix it before telling anyone else.
[email protected]
Who else handles your data
The services DiveHQ uses for email, file storage and sign-in, what each one receives, and where. How personal data is handled is set out in the privacy policy.