Written to be read, not to be got past. If anything here is unclear, ask and we'll fix the wording.
Last updated 26 October 2026 ยท The English version is the operative one.
This policy covers two situations, and they are not the same in law.
That distinction matters if you are a member of a club. Questions about your own record (seeing it, correcting it, deleting it) go to your club's committee first, because it is their data and their decision. We will always help them action it.
This policy is the first of those two: what we do as controller of this website. The second is a contract, not a policy: the terms on which we act as a club's processor are in the data processing agreement, which forms part of every club's terms. If you are on a committee, that is the document you want.
Two things, and only one of them without asking:
Two other companies are involved in showing you this page, and neither of them is optional in the way a cookie is, so they are named here rather than on the cookie page. The enquiry form is carried to our inbox by EmailJS: what you type in it, and the address you give, pass through them. Their script is fetched only when you open the form, not on every page. And the typeface these pages are set in is served by Google Fonts, which means your browser asks Google for the font file and Google sees that request and your IP address. Neither sets a cookie on this site.
We keep the email, because that is what an inbox is. We use it to answer you and to keep track of a club we're talking to, and we don't add you to a mailing list you didn't ask for. If you'd like the correspondence deleted, say so and it will be.
Registering happens at clubs.foxface.io. The form asks for the club's name and your name, email and (if you give it) phone number. We keep those, in our database in Frankfurt, Germany (EU), to set the club up, send you its welcome email and first logins, and look after the subscription; we don't use them for anything else. The welcome email is sent through our own mail provider, IONOS.
Payment is taken by Stripe, on Stripe's own pages. Card details are never entered on this site and never reach us: we see the club's name, the billing email, and whether the subscription is paid. Stripe is the controller of its own payment records and processes the payment on our behalf; its privacy notice covers what it does with card data.
Every club's records are held in one database in Frankfurt, Germany (EU), run by Neon through Netlify. Each club's records are kept apart from every other club's by rules enforced in the database itself, not only in the pages. Registering a club and signing in happen at clubs.foxface.io.
Whatever the club puts there, which is normally:
If the club uses them, a member can also fill in their own details for the club: an emergency contact and next of kin (name, relationship and phone number), their training agency and certification number, their kit sizes, and whether they agree to photos and the club's rules.
Emergency contacts and next of kin are kept to the committee posts the club has chosen, and to whoever is running a dive, who can open an emergency sheet for the people booked on it. That sheet opens the day before the dive and closes five days after it, and every opening is recorded for the committee to see.
It deliberately does not hold medical forms, dates of birth, home addresses or payment details. Those belong in the club's own records. If your committee asks us to add a field like that, we will ask them why before we do.
Technically, the club's data sits on hosting we administer, so we can reach it in order to run the service: restoring a backup, fixing a fault, answering a question the committee has asked us. We do not look at a club's records for any other reason, and we never use them to build anything of our own.
My kit (a member's own record of the gear they personally own) is filtered out on the server before the page is sent. Another member cannot see it. The Equipment Officer cannot see it. The Chair cannot see it. It is not hidden in the page with styling; it is never transmitted at all. The only exceptions are the names of people a member books for, because a dive list has to say who was in the water.
Anything the committee marks as committee-only is likewise removed before the page leaves the server, so it is not discoverable by a member who goes looking.
The app for iPhone, iPad and Android shows your club's own site, so everything above about a club's site applies to it too. On top of that:
| Who | What for | Where |
|---|---|---|
| Netlify | Hosting these pages and the clubs.foxface.io app | EU / US, under standard clauses |
| Neon | The database that holds every club's records, run through Netlify | Frankfurt, Germany (EU) |
| Stripe | Taking subscription payments | EU / US, under standard clauses |
| IONOS | Sending our emails, including a new club's welcome email | EU |
| Counting visits to these marketing pages, if you allowed it | see the cookie page | |
| EmailJS | Carrying the enquiry form to our inbox. It sees what you typed and your email address. Loaded only when you open the form. | US, under standard clauses |
| Apple | Delivering notifications to iPhones and iPads that allowed them. Apple sees the phone's notification address and the line of text being sent. | US, under standard clauses |
| Google Firebase | Delivering notifications to Android phones that allowed them. Google sees the phone's notification address and the line of text being sent. | EU / US, under standard clauses |
| Google Fonts | Serving the typeface these pages are set in. Your browser asks Google for the font file, so Google sees the request and your IP address. | EU / US |
Nobody else, and there is no analytics of any kind inside a club's own site.
We do not sell data. On advertising we have to be more precise than "we don't": if, and only if, you agree to advertising on the cookie banner, by pressing Accept all or by ticking the advertising box under Choose what to allow, this marketing site loads Meta's pixel, which tells Meta that this browser visited these pages so that we can advertise FoxFace Diving to people who looked at it. That is sharing with an advertising platform, and calling it anything else would be dishonest. Press Reject all, or ignore the banner, and the pixel never loads. It is never on a club's own site, and it is never on the demo.
Under UK GDPR you can ask for a copy of your data, ask for it to be corrected or deleted, object to how it's used, or ask for it in a portable form. If your data is on a club's site, ask the club: they decide, and we act on their instruction. If it's ours, ask us.
Write to hello@foxface.io. We answer within a month, usually within a few days.
If you think we've got it wrong you can complain to the Information Commissioner's Office, which regulates data protection in the UK.
If this policy changes in a way that matters, the date at the top changes and clubs are told by email. We don't quietly rewrite it.