CLUB MANAGER
Privacy notice
This notice describes Club Manager at breakpoint-tennis.app/club/. The match organiser, score and other Breakpoint apps have their own short notices inside those apps.
Who is responsible
The tennis club that creates the account is the controller for its members' data. The club decides who is invited, what is written down, and how long ordinary membership records are kept.
Breakpoint Tennis provides the software and the hosted database. For that club data, Breakpoint Tennis acts as processor. The split is described in GDPR.md in the project repository.
What is stored
- Your email address and a sign-in session, so the magic link can reach you.
- The name you choose to show in the club directory, your role, and an optional phone number.
- Court bookings, including a guest's first name if you add one.
- Membership category, season, and payments the treasurer types in (amount, date, method, optional note).
- Club-night rota sign-ups.
- If you are a junior: a guardian's name, email, and the fact they consented, with the time.
- The time you accepted this notice and the terms, and the version you accepted.
- A short audit log when an admin invites, removes, changes a role, records a payment, or runs a retention purge.
The directory shown to other members is the display name and role. Phone numbers and guardian details are not on that list. Admins can see them because they run the club. Member email addresses are on the shared club account list, which the match organiser also uses, so other people in the club can see them.
Why
The club uses the data to run bookings, collect membership fees by hand, and staff club nights. Sign-in and the acceptance record are needed to know who is allowed in and which notice you saw. The audit log is the club's record of admin actions on member data.
The legal bases the club is likely to rely on are contract (your membership) and legitimate interests (running the courts and the rota). Juniors are not signed up on the basis of a child's own consent: a guardian's consent is recorded. The club should confirm the basis that fits its own rules.
How long
The club sets a retention period in Club settings (the default is 6 years). An admin can run a purge of members who have not booked, paid, or opened the app in that time. Owners are not purged. Payment amounts, dates and methods are kept after a person leaves or erases their profile, because the club needs them for its accounts. The note and the name are removed.
Your choices
- Download a JSON file of your data from the Club tab.
- Edit your display name, phone and junior/guardian details yourself.
- Erase your club data from the Club tab. Future bookings are cancelled. The directory shows "Former member". Payment rows stay, without the note.
- Ask the club to correct something you cannot edit.
- Complain to the Data Protection Commission (Ireland) if you think the handling is wrong.
Erasing club data does not delete the email login by itself. The static site has no key that can delete Supabase Auth users. Email hello@breakpoint-tennis.app after you erase, and Breakpoint Tennis will delete the login.
Who else sees it
There are no advertising or analytics scripts on this site. Data is sent only to run the app:
- Supabase — database and sign-in, on the EU project the organiser already uses.
- Resend — sends the magic-link email. The club's Supabase project is configured with that SMTP.
- Codeberg Pages — hosts these HTML, CSS and JavaScript files. It does not receive the club database.
Other members of your club see the booking grid, the rota and the directory, because that is how the club runs. They do not see another club's data. A member of one club cannot read another club.
Where
The database is in the EU (the Supabase region chosen for this project). Codeberg Pages serves the files from their hosting. Keep the Supabase project in an EU region if you move it.