Privacy policy
Last updated: 21 October 2026
TourniTrak helps grassroots football clubs run tournaments. That means handling details about club volunteers, team managers and — on team sheets — children. This page explains what we collect, why, who can see it, how long we keep it, and your rights.
Who we are
TourniTrak is run by TourniTrak Ltd, a company registered in England and Wales (company number 17493698), whose registered office is 41 Southgate Street, Winchester, England, SO23 9EH.
We're registered with the Information Commissioner's Office, registration number ZC264800.
Questions about data protection, this policy or your details: hello@tournitrak.co.uk.
The club and us
When a club runs a tournament on TourniTrak, the club is responsible for the details collected for it — it decides what the tournament needs, and it's the club you entered with. We look after those details on the club's behalf and only use them to run the tournament. For organiser accounts, website enquiries and the running of the site itself, we are responsible.
What we collect
| Whose | What |
|---|---|
| Tournament organisers | Name, email address and club. Your password is held securely by our sign-in provider — we never see it. |
| Team managers and coaches | Team and club name, your name, mobile number and email address, kit colour, the club's FA Organisation ID and league, and your confirmation of the tournament's age groups and entry terms. |
| Players, on team sheets | Each player's first and last name, date of birth and shirt number, and whether they mustn't be photographed — plus the name of the person who sent the sheet. |
| Teams that add a badge | If a team's coach (through the team's private team sheet link) or the club's organiser adds one: a picture of the team's club badge or logo, whether a coach or the organiser added it (not their name), and when. It must be the club's badge only — no photos of people. |
| Pitch marshalls and desk volunteers | Your name, and the scores or check-ins you enter, recorded with your name. Your name is seen by the club running the tournament and its marshalls, never by parents or the public. |
| Players given a card in a match | The team and, if the pitch marshall records it, the shirt number of a player given a yellow card, sin bin or red card (never their name). Seen by the club running the tournament, its marshalls and its desk volunteers, never by parents or the public, who see only how many cards each team got. |
| People who enquire | Your answers on our enquiry form: name, role, club and its address, email, mobile, details of your tournament (including when you plan to open registration), and how you heard about us if you tell us. With it, the page notes what brought you to the site, such as a Google search or a link we shared. |
| People who message a club's organiser | Through the "Contact the organiser" form on a club's tournament page: your name, email address and message (see Messages to a club's organiser). |
| Phones where something goes wrong | If part of a screen breaks, or something you tried to save or open doesn't go through, the app sends us a short note: which screen, the kind of problem, the app's version and the tournament's code. It never includes what was on the screen, anything you typed, or who you are, and we use it only to find and fix the fault. |
| Everyone who visits | Records our providers keep to run the service securely, such as internet addresses and times of visits. |
| Website visitors who say yes to analytics | Through Google Analytics: the pages you visit, how you got to the site, your device and browser, and roughly where you are (town or region). Google doesn't get your name or email address. |
Why we use it
- To run the tournament — entries, fixtures, check-in, scores, tables and results. This is in the club's legitimate interests, and ours, in running a fair and well-organised event.
- To tell marshalls which players mustn't be photographed — the only reason we ask whether a player mustn't be photographed. Marshalls see it as a "No photos" note beside the player's name, so the team's wishes can be respected on the day. It's used for nothing else, and is deleted with the team sheet.
- To check players are in the right age group — the only reason we ask for dates of birth. This supports fair play and the club's safeguarding responsibilities, and is in the club's legitimate interests in running a fair competition. Whoever sends a team sheet confirms the players' parents or carers know their details are being shared with the club for this.
- To show a team's badge beside its name, if its coach or the organiser adds one, so everyone can see who's who at a glance. This is in the club's and the team's legitimate interests in running and following the tournament. Every picture is checked automatically before it's shown (see Anthropic, below), so that nothing unsuitable for children appears on the site: this is in our legitimate interests, and the club's, in keeping a site children use safe.
- To email you about your entry — your check-in code, your team sheet link, a place coming up from the waiting list, and a link to pay the entry fee where the club asks for one. These are part of the entry you asked the club for, and in the club's legitimate interests in running the tournament.
- To let you pay the entry fee by card, where the club takes payment that way. You pay on Stripe's own page, straight to the club. Your team's email address is passed to Stripe so it can send a card receipt. We record that your team has paid, how much, and the email address Stripe gives us — never your card details. This is needed for the entry you're paying for.
- To run organiser accounts — so a club's organiser can sign in and set up and run its tournament. This is needed for our agreement with the club.
- To reply to enquiries and set clubs up to use TourniTrak. This is a step you've asked us to take before any agreement, and in our legitimate interests in running TourniTrak.
- To tell clubs about TourniTrak. We may contact a club using contact details it publishes for club business, or that it gave us, only about TourniTrak and in our legitimate interests in offering it to clubs. Just say "no thanks" and we'll stop, and keep a note so we don't contact you again.
- To see how people use our website, so we can improve it — only if you say yes to analytics cookies. This is based on your consent, which you can take back at any time.
- To keep the service secure and working (our legitimate interests), and to meet our legal obligations, such as keeping financial records.
We don't sell anyone's details, and we don't use them for advertising.
Messages to a club's organiser
A club's tournament page can have a "Contact the organiser" form, so you can ask a question without the organiser's own email address being shown on the page.
- What and who: the name, email address and message you type go to that club's organiser by email, with your email address as the one their reply goes to. The club is responsible for your message once it has it, as for the rest of its tournament.
- Why: so you can ask the club about its tournament — in your interests and the club's legitimate interests in running it.
- How long: we don't keep your message on our systems: it's passed straight to the club. Our email provider, Resend, keeps a copy of each email it sends for up to 30 days. To stop the form being misused we keep a fingerprint of your email address and of your internet connection, scrambled with a secret key that only our server has, so neither the address nor the connection itself is stored. These fingerprints are deleted automatically, at most 3 days later.
Team badges
A team can show its club's badge beside its name instead of its colour square. Only the team's coach (through the team's private team sheet link) or the club's organiser can add, change or remove it; it can't be added from the public entry form.
- Your club's badge only — no photos of people. A picture of a person, anything explicit, violent, hateful or offensive, bad language, or anything that isn't a club badge or logo is turned away.
- How it's checked: before it's stored or shown, the picture is checked automatically by Anthropic's Claude, an AI model. It's sent the picture and nothing else — no names, email addresses, team or tournament details. If the check can't be done, the picture isn't used and the team keeps its colour. Nobody at TourniTrak or the club looks at the picture first, so if something unsuitable gets through, tell the club or us and it will be removed.
- What's kept: the picture is redrawn on your phone before it's sent, so details stored inside the file (such as the camera or where a photo was taken) are left behind. We keep the picture, and whether a coach or the organiser added it and when. To stop uploads being misused we also keep a fingerprint of the team and of your internet connection, scrambled with a secret key only our server has, deleted automatically at most 3 days later.
- Who sees it: anyone who can see the tournament's public page, like the team's name and colour.
Who can see what
- Anyone who opens the tournament's public page (the club shares its link, and it may appear in search results) — other teams, parents, spectators — sees team names, clubs, kit colours and team badges, fixtures, results, tables and winners. Never teams' or coaches' contact details, check-in codes or players' details, and never the names of the marshalls or organisers who enter the scores. The organiser's own contact name, email and phone are shown only if the club ticks "Show these contact details on our public page"; it's off unless they do. If the club unticks it, they come off the page straight away, though copies that phones have already loaded can take up to two days to clear. Because the page can appear in search results, search engines such as Google may also keep showing those details in their results for a while (sometimes weeks) after they're unticked, until they next look at the page.
- The organiser sees everything for their own tournament, including team sheets and dates of birth.
- The team that sent a team sheet — whoever has that team's private sheet link, usually the coach — can open that team's own sheet, including its players' dates of birth, until the sheet's deadline. After it locks they no longer see the dates. They never see another team's sheet.
- The registration desk (the club's volunteers with a desk code) sees what it needs to check teams in: each team's name, club, shirt colour and squad size, its coach's name and its check-in code, and whether it has paid and arrived. The desk never sees a team's phone number or email address, or its team sheet and players. Along with the results, it can see the shirt numbers of players given cards.
- Pitch marshalls see what they need to score their age group, including the shirt numbers of players given cards. For a spot check they see a player's name, shirt number and a "No photos" note if the team asked for one; they ask the player's date of birth and are told whether it matches — they aren't shown it.
- We can see the details on our systems, including players' dates of birth and teams' contact details, and only look when we need to — to support a club, or to fix something. Only our administrators can, and only when signed in with a second step (an authenticator code) as well as a password.
Who else handles it
We use a small number of trusted providers to run TourniTrak. They handle details only on our instructions:
- Supabase — our database and sign-in, with data stored in London.
- Netlify — hosts the website and app.
- Resend — sends our emails.
- Stripe — takes card payments for clubs that use it, into each club's own Stripe account. The club and Stripe handle that payment, under Stripe's own privacy policy; we never see or store card details, and the money never passes through us.
- Anthropic — checks every team badge picture before it's shown, using its Claude AI model, so nothing unsuitable for children reaches the site. It's sent the picture and nothing else, under its commercial terms, which don't allow it to use what it's sent to train its models. It deletes the picture and its answer within 30 days, unless its automatic safety checks flag them as possible misuse of its service, when it may keep them for up to 2 years.
- Cloudflare — runs a quick check that it's a person, not an automated program, sending our sign-in, account and contact forms and a team's entry (Cloudflare Turnstile). As one of those forms is sent, Cloudflare sees your internet address and details of your browser and device, and tells us only whether the check passed. It isn't used for advertising, and it isn't used anywhere else on the site or in the app.
- Google Workspace — our email inbox.
- Google Analytics — on our website only, and only if you say yes: counts visits and shows which pages people use. We've switched off its advertising features. It isn't used in the tournament app.
- Google Fonts — supplies the Saira font our pages and the app are drawn in. Your browser fetches it from Google, which sees your internet address and browser; no cookies are set.
Our database is in London, but Netlify, Resend, Stripe, Anthropic, Cloudflare and Google may handle details in the United States, and some of our providers' support teams work from other countries. Where details leave the UK, the transfer is protected by the safeguards UK law requires: the UK–US "data bridge" (the UK Extension to the EU–US Data Privacy Framework) where the provider is certified under it, or otherwise the standard contractual clauses with the UK's International Data Transfer Addendum, in each provider's data processing terms.
How long we keep it
- Team sheets, including players' dates of birth: deleted automatically 30 days after the tournament.
- Tournament details — teams, contact details, results, payment records, and anything the organiser uploaded such as logos: deleted automatically one month after the tournament's last day (sooner if the organiser asks us to delete it). The record of the emails we've sent for a tournament is deleted with it.
- Team badges: deleted with the tournament, one month after its last day. A badge that's removed or replaced is deleted at once (or, if that can't be done straight away, within two days), and so is the badge of a team taken out of the tournament.
- Earlier versions of a tournament (a private copy each time it's saved, so that if something goes wrong we can see what the tournament looked like before and put it right by hand): kept for 21 days, then deleted automatically. Nothing is ever switched back to an earlier version automatically. They're deleted straight away if the tournament is.
- Enquiries through our contact form: deleted automatically 6 months after you send one, and we delete the copy that reaches our email inbox within the same 6 months.
- Messages to a club's organiser through its tournament page: not kept by us — passed straight to the club by email. Our email provider keeps a copy for up to 30 days, and the scrambled fingerprints we use to limit how many can be sent are deleted automatically, at most 3 days later.
- Notes about problems: deleted automatically after 30 days. To stop one phone sending too many, we keep a scrambled fingerprint of the connection (never the address itself, and never with the note) for at most 2 days.
- Organiser accounts: until you ask us to close yours.
- Password-reset links we make by hand: if you're an organiser and we make you a password-reset link ourselves (for example because our emails aren't reaching you), we keep a record of which of us made it, for which email address and when — never the link itself — for 6 months, then delete it.
- What clubs pay us — invoices, receipts and payment records: 6 years, because tax law requires it.
- Backups: our database provider keeps a backup of each day for 7 days, so a copy of anything deleted can remain in a backup for up to 7 days more.
- Google Analytics: Google keeps the record of each visit for 2 months; after that only totals remain. Its cookies expire after 13 months at most.
Cookies and storage
We don't use advertising cookies. On our website — not in the tournament app — we ask whether you're happy for us to use Google Analytics. Only if you say yes does it set cookies (their names start with _ga), so we can count visits and see which pages people use. Say no and Google Analytics isn't loaded. (Every page, the app included, does load our lettering, the Saira font, from Google Fonts. That sets no cookies, but like any website it's fetched from, Google Fonts sees your device's internet address and browser.) You can change your mind at any time with Cookie settings at the bottom of each page; saying no later deletes those cookies.
Apart from that, TourniTrak only stores what it needs to work, on your device: keeping organisers signed in (and, until they sign out, age group settings they've changed but not saved yet), remembering the teams you've entered from that phone, remembering a marshall's code so they don't have to type it again, and keeping a pitch marshall's score that couldn't be sent (the match, the score and any cards with shirt numbers, never their code) until it has been sent, for up to 3 days or until they sign out. A marshall's code is kept only on that phone, for one marshall at a time, and is forgotten after 3 days or as soon as they sign out. It's taken out of the address bar (and the app's own Back and Forward steps) as soon as the page opens. Your browser's own history list may still keep the link a marshall's QR code opened, and signing out doesn't clear that, so a marshall's QR code or link should be treated like a key and not left on a shared phone. The same goes for the team sheet link we email a coach: it opens the players' names and, until the sheet's deadline, their dates of birth, and the browser's history list keeps it too, so open it on your own phone rather than a shared one. These are essential to how the site works.
Keeping it safe
- Everything travels over encrypted connections, and our database provider encrypts stored data.
- Only the organiser — and people they give a code to — can change a tournament.
- Each team's sheet has its own private link that can't be guessed.
Your rights
You can ask us for a copy of your details, to correct them, to delete them, to limit how they're used, to object to how they're used, or to have them sent to you or someone else in a usable format. Parents and carers can ask on behalf of their child.
Email hello@tournitrak.co.uk. If your request is about a club's tournament, we may pass it to the club, since they're responsible for those details, and we'll help them deal with it. We'll reply within a month.
If you're unhappy with how we've handled your details, please tell us first at hello@tournitrak.co.uk. We'll acknowledge your complaint within 30 days, look into it, and tell you what we've found and done. You can also complain to the Information Commissioner's Office at any time: ico.org.uk/make-a-complaint, or 0303 123 1113.
Changes
If we change this policy, we'll update this page and the date at the top.
