What we store, and what we do not

Children and young players

A manager builds a squad list so that people have someone to vote for. Each player is stored as a display name and nothing else.

That display name is a first name only. An initial is added on the end only when two players in the same squad share a first name, so that voters can tell them apart. If there is one Noah in the squad, the entry reads Noah. If there are two, they become Noah H and Noah T.

We do not ask for and there is nowhere to store a surname, a date of birth, an age, a school, a shirt number tied to an identity, a photo, an address, a phone number or an email address for any child. The squad list is a list of first names.

The manager types those names in. Please keep them short. A first name plus an initial is all the system needs and all it is designed to hold.

People who vote

Voters are parents, players and coaching staff. We store nothing that identifies them.

• No name is asked for.
• No email address is asked for.
• There is no account and no sign-in. A voting link opens straight onto the voting form.
• No IP address is recorded against a vote. The votes table has no column for one.

There is one small exception, and it is worth explaining properly. When a vote is submitted, the page can generate a short random marker in the voter's own browser and send it along with the vote. It exists for a single purpose, which is to stop a double tap or an impatient second press recording the same vote twice. It is a random string created on the device. It is not a name, an account, an IP address, a device ID or anything supplied by a third party, and it cannot be traced back to a person. If it is cleared from the browser, nothing is lost.

Managers

A manager needs an account, because a manager is the only person who can see results. Sign-in is by magic link, so there is no password to store.

That means we hold a manager's email address, because sending the sign-in link is impossible without one. A manager can optionally add a display name for themselves. Alongside that sits the manager's own content: team names, season labels, the squad and staff lists they type in, and the short explainer they write for the top of their voting page.

A manager's email address is never shown on a voting page and is never returned to a voter's browser.

What a single vote actually records

A vote is a small, fixed record. This is the whole of it.

Who the vote is on behalf of

Which child or staff member the vote is cast for, so that a manager can see who has voted and who has not. For a parents vote that is the child, so one family votes once. For a managers vote it is the staff member.

The match date

The date of the game being voted on.

The three players chosen

First, second and third place. First is worth three points, second two, third one.

Housekeeping

Which team and which voting link the vote came through, which of the three vote types it is, the season label at the time, the time it was submitted, and the anti double tap marker described above.

That is the entire record. There is no free text box, no comment field, no rating, no message to the manager and nowhere for anyone to write anything about a child.

Voting links

Each team gets its own voting links, one for each vote type it turns on. A link carries a long random token, so the address is not something anyone can guess or work their way to by trying numbers.

Voting pages are marked so that search engines do not index them, and they are not listed anywhere on this site. They load no third-party scripts, no third-party fonts, no advertising and no analytics. Everything a voting page needs comes from terracetrivia.com.

A link is only as private as the sharing of it, so a manager should send it to their own team's group rather than post it publicly. If a link does get out, the manager can rotate it, which issues a new token and makes the old address stop working immediately. Votes already recorded are kept.

Who can see the results

Only the manager who owns the team. Results, tables, the vote log and who has yet to vote are visible on that manager's dashboard after they sign in, and nowhere else.

• There are no public leaderboards.
• Voters cannot see the running totals, only their own confirmation that a vote was recorded.
• One manager cannot see another manager's teams, players or votes. The database enforces that, rather than the page simply hiding it.
• A voting page returns only what it needs to draw itself: the team name, the vote type, the manager's explainer text and the list of first names. It never returns vote data or the manager's email address.

We do not sell data, share it with advertisers, or hand it to anyone else for their own purposes. There is no advertising on this site.

Cookies and tracking

There are no analytics cookies, no advertising cookies and no tracking pixels on any page of this site.

A signed-in manager's browser stores a session so that they stay signed in between pages. Signing out clears it. On a voting page, the only thing that may be stored locally is the short anti double tap marker described above.

Deleting data

Deletion here means the record is gone from the database, not hidden or flagged. Nothing is soft-deleted and nothing is kept in an archive afterwards.

Deleting a player

A manager can remove a player from their squad at any time from the dashboard.

Deleting a team

Deleting a team hard-deletes that team's players, staff, voting links and every vote recorded for it.

Deleting an account

A manager can delete their account from the dashboard. That hard-deletes everything belonging to them: their teams, players, staff, links, votes and the account itself. It cannot be undone, so a manager who wants to keep a season's tables should note them down first.

If you are a parent

Your child's first name was added by your team's manager, so the quickest route is to ask them to remove it, which takes seconds. If you would rather not, or you are not sure who to ask, email us at [email protected] and we will deal with it.

Where the data is held

The site itself is served by Cloudflare Pages. The database is Supabase, which is hosted Postgres, running in the London region, eu-west-2. Both are used as suppliers to run the service, not to do anything of their own with the data.

Anything else, just ask

This page deliberately does not put a number on how long data is kept, because it is kept until a manager deletes it or asks us to. If you want to know what is held about a particular team or child, want a copy of it, want it corrected, or want it gone, email us and say so. You do not need to use any special wording.

If something on this page is unclear or looks wrong, we would rather hear about it than have you guess.