Privacy Policy · Fairtime

Fairtime is built around the weekly job of a grassroots football manager. Because that work involves children's names, availability, and minutes played, we keep what we collect to the minimum needed for the product to work, and we keep it inside your club: the team members you invite, and — if your team belongs to a club — your club's administrators, can see it. We don't share it outside your club.

What we collect

Manager account: email address, name (from your Google account if you sign in with Google).
Squad: player names and squad numbers. Optional: position, availability status, parent link, coaching notes (development plan, position preferences, rotation intent).
Fixtures: opposition, date, kick-off time, venue, scores, your own match notes.
Match data: minutes played per period, goals, assists, cards, substitutions.
Parent-link availability: when a parent uses a per-player parent link to set availability, we record their response and the timestamp. We do not store the parent's name or email — only that the response came via the parent link.

What we don't collect

Player dates of birth or ages.
Home addresses.
Medical or safeguarding information unless you choose to put it in a notes field — and we ask you not to (see the in-product notice on Match Notes).
Player photos.
Public player rankings of any kind.
Any data from anyone outside your squad without their participation (the parent-link flow is explicit consent — the parent receives the link from you and chooses to respond).

Where it's stored

All squad, fixture, and match data lives in a Supabase Postgres database (EU region) accessed via row-level security policies that ensure only your authenticated account (and any team members you have explicitly invited) can read or write your team's data. The parent-link route accepts a hashed bearer token instead of a Supabase session, scoped to one player.

Club administration

If your team belongs to a club, the club's administrator can see the players registered across all the club's teams, and can: merge two records that are the same child (for example, a player a second coach re-added), and move a player from one team to another within the club. A club admin can see and tidy up player records but cannot run your team's matches or change your lineups. These actions stay within your club, are recorded, and a merge can be undone if it was a mistake.

Club fair-play oversight

If your club's committee turns on fair-play oversight, the committee can see fair-playing-time records across its teams, to check every child is getting a fair go. Fairtime never ranks or grades children by ability or performance, and your child's record is never shown to other parents. Oversight is off by default and is turned on deliberately by the club owner; it lets the committee spot a child being under-served, never to rank or grade children. Each time the committee views a child's record it is recorded. It does not give the committee any control over a team's matches or lineups.

Continuity across reorganisation (merge/split)

Sometimes teams in a club are reorganised — for example two age-group teams merge, or one team splits. When a child moves into the new team, that team's manager can see the minutes and appearances the child played for their previous team(s) in the same club, and which team and season those came from — so a child who moves teams keeps the fair playing-time history they've built up, rather than starting from scratch. This is limited to minutes and appearances. It deliberately does not expose the child's coaching or development information (rotation intent, development notes, or playing-load settings). It is read-only context to help the manager share playing time fairly across the changed squad — it is not used for any automated decision about the child, and it does not change how the new season's fair playing-time totals are worked out. Only coaches of the new team can see it, and only within a single club. Our basis for this is our legitimate interest in keeping a child's fair playing-time record connected as they move between teams in the same club, balanced against their interests as a child; it surfaces no new category of data — the same sporting record the child already had.

Third-party processors

Supabase — database, authentication, storage. EU region.
Google — only if you sign in with Google. Google receives your sign-in event; we receive your email and basic profile.
FA Full-Time — only if you choose to import your league fixtures. We fetch the public Full-Time pages on your behalf; no Fairtime data is sent back.

Your rights

You can:

Export your data — request a JSON dump of everything Fairtime holds about your team. Email the address below.
Delete your account — the "Delete Account" button on your profile page removes your team and every player, fixture, and match record under it. This action cannot be undone.
Edit or remove individual records — players can be marked "out for season" from the squad page. Fixtures can be deleted from the fixture detail page.

Contact

For data questions, exports, or anything else: privacy@fairtime.football

This is a plain-English statement of how Fairtime handles data. Before formal public launch this policy will be reviewed by a data-protection lawyer; if you spot anything that doesn't match the actual product behaviour, please flag it via the contact above.