Your club decides what happens to your members' personal data. We only ever act on your instructions. This is the agreement that says so, and it is part of your terms. There is nothing separate to sign.
Last updated 26 October 2026 · The English version is the operative one.
In one paragraph. Your club is the data controller: they are your members and it is your decision what is held about them. We are your processor: we run the software that holds it, we do what you tell us, we do not use it for anything of our own, and when you leave you take it with you and we delete ours.
This agreement is between the club named in your subscription (the "club") and ("we", "us"). It forms part of the terms and applies for as long as the club's subscription runs.
Under UK GDPR and the Data Protection Act 2018, the club is the controller and we are the processor. Where a club has members in the EU, the EU GDPR applies in the same way and this agreement is intended to satisfy Article 28 of both.
Only what the club puts into its site, and only in order to run that site for the club. Nothing is processed for any purpose of our own.
| What | Detail |
|---|---|
| Subject matter | Running the club's membership and activity system: its membership records, dive calendar, equipment hire, boat records, noticeboard and committee papers. |
| Duration | For as long as the subscription runs, and then the period in section 8. |
| Nature and purpose | Storage, retrieval and display to people the club has given a login to. We do not analyse it, profile anybody, or use it to train anything. |
| Categories of person | The club's members, their dependants where the club records them, and guests taking a try dive. |
| Categories of data | Names; diving grades, instructor ranks and training records; committee posts; contact details the club chooses to hold; emergency contacts and next of kin a member gives; training agency, certification number and kit sizes; kit owned, hired and serviced; dives booked; the notification address of a phone using the app; and anything the club writes into a note, a minute or an attached document. |
| Special category data | None is asked for. Emergency contacts and next of kin are held where a member gives them, and are shown only to the committee posts the club chooses and to the person running a dive, for the people booked on it, from the day before the dive until five days after; every opening is recorded for the committee. A medical self-declaration may amount to health data if a club chooses to record it in a note or an attachment; the club decides whether to, and it is protected the same way as everything else. |
| Children | A club may record dependants, who may be under 18. Only a name, a relationship and what a parent books for them. |
We process personal data only on the club's documented instructions. Using the site is an instruction: what a committee types into it is what we hold, and what they delete is what we delete. Anything else (a request to export, correct or remove something) counts as an instruction when it comes by email from a committee member.
If we ever believe an instruction breaks data protection law, we will say so rather than carry it out quietly. If we are required by law to process something beyond the club's instructions, we will tell the club first unless the law forbids it.
Only people the club has issued a login to, and only what their role allows. Signed-out visitors see nothing about the club's members at all: not the roster, not the committee, not who is on a dive. Members' rosters are never in a file that can be fetched from the web.
On our side, access is limited to the one person who maintains the software, who is bound by the confidentiality in section 9 and looks only when asked to fix something.
We hold a small number of emergency logins for your site. They are not anybody's account: they carry no name and nobody's record is ever attributed to them. They exist for one situation: a committee that has lost every code and can no longer get into its own club. Rather than pretend this doesn't exist, here is exactly how it works.
A club that would rather we held no such login can ask, and we will remove it. The trade is honest: nobody can then let you back in if you lose every code, and the club's records go with it.
No system is perfect, and we will not pretend otherwise. What we promise is that the measures above are actually in place and that we will tell you quickly when something goes wrong.
We use these sub-processors. The club consents to them by accepting these terms, and we will give at least 30 days' notice before adding or changing one, long enough for a club that objects to end its subscription without penalty.
| Who | What for | Where |
|---|---|---|
| Netlify | Hosting the clubs.foxface.io app, which the club's area runs in | EU and USA |
| Neon | The database that holds the club's records, run through Netlify. One database holds every club, and each club's records are kept apart by rules enforced in the database itself | Frankfurt, Germany (EU) |
| EmailJS | Sending the club's enquiry and fault emails | USA |
| Apple | Delivering notifications to members' iPhones and iPads in the FoxFace Diving app: only the phone's notification address and the line of text sent | USA |
| Google Firebase | Delivering notifications to members' Android phones in the FoxFace Diving app: only the phone's notification address and the line of text sent | EU and USA |
Where data reaches the USA it is covered by the International Data Transfer Addendum to the European Commission's standard contractual clauses, or by the UK extension to the EU-US Data Privacy Framework where the supplier is certified under it.
Stripe takes the club's subscription payment. That is between Stripe, the club and us as separate controllers. It never touches your members' data, and no card detail reaches this site.
If personal data we hold for the club is lost, exposed or reached by somebody who should not have it, we will tell the club without undue delay and in any event within 48 hours of knowing. We will say what happened, whose data it involved, what we are doing about it and what we suggest the club does, enough for the club to meet its own 72-hour duty to the ICO.
We will also help the club, so far as we reasonably can, with data subject requests, with impact assessments, and with any question from a regulator.
The club can download everything it holds at any time, from the admin page, without asking us. That is on purpose: a club's records are not a hostage.
When a subscription ends we keep the club's data for 30 days, in case somebody changes their mind or a payment was missed by accident, and then delete it: the records, the attachments and the safety copies. We will confirm in writing when it is done. If the club would rather we deleted it immediately, say so and we will.
Everyone with access to the club's data is bound to keep it confidential. Today that is one person. Should anybody else ever be given access, they will be under a written confidentiality obligation before they are.
The club may ask us to demonstrate that we are doing what this agreement says, and we will answer questions and provide what we reasonably can. For a club that needs more than that, we will agree a proportionate inspection, with reasonable notice, no more than once a year, and not in a way that exposes another club's data.
Anything about this agreement, or about a member's data, goes to hello@foxface.io. We answer within a day or two.
This sits alongside the terms and the privacy policy, which covers what we do with the details of people who visit this site rather than the members of your club.