Subprocessors

The services DiveHQ uses to run the app, what each one does, and what it receives. Each one handles only what it needs for its part.

Last updated 26 September 2026

Service	Used for	What it receives
Cloudflare R2	File storage	Invoice PDFs, logos, and documents uploaded to guest, staff and asset records. Encrypted at rest.
Resend	Email delivery	Names, email addresses and message content: sign-in links and invitations to staff, duty emails, and form links, estimates and reminders to guests.
Google	Sign-in, if you choose itOnly for people who sign in with Google	The sign-in request. Google returns the person's name, email address and profile picture to DiveHQ.

Cloudflare R2
File storage
Invoice PDFs, logos, and documents uploaded to guest, staff and asset records. Encrypted at rest.
Resend
Email delivery
Names, email addresses and message content: sign-in links and invitations to staff, duty emails, and form links, estimates and reminders to guests.
Google
Sign-in, if you choose it
Only for people who sign in with Google
The sign-in request. Google returns the person's name, email address and profile picture to DiveHQ.

DiveHQ does not process card payments for guests, so no payment provider receives guest data. Guest payments are recorded in DiveHQ after they are taken on your own terminal, in cash or by transfer.

Data processing agreement

Your centre decides what guest data is collected and why, and PixelYard LLC, which operates DiveHQ, processes it on your behalf. If you need a signed data processing agreement for your records, email us and we will send one.

Ask for the agreement

Changes to this list

We update this page before a new service starts receiving your data, and the date at the top changes when we do. Product update emails mention it too.

How your data is protected