Privacy Policy — thefinal

Who we are

The controller of your personal data is True Growth OÜ, a company registered in Estonia under registry code 16504010, at Pae tn 25-47, 11414 Tallinn, Harju maakond, Estonia. Full details are on the legal notice page.

For anything in this policy — questions, requests, complaints — write to [email protected]. That single address reaches us for every kind of request; there is no separate queue to find.

We have not appointed a Data Protection Officer, and are not required to: we do not carry out large-scale systematic monitoring, and we process no special categories of data. We also need no EU representative under Article 27 — the controller is itself established in the EU.

What we collect, and why we may

Ten groups, nothing else. Each is listed with the legal ground we rely on under Article 6 of the GDPR, because a purpose without a ground is just a preference.

What	Why	Legal ground
Account Email address, password, display name, your age declaration, which revision of the Terms you accepted, when and in which language, and the language you chose for the game. If you sign in with Google instead of a password, we receive from your Google account its email address, name, profile-photo address and Google account identifier — the game itself uses only the email address, but Firebase Authentication stores them all. If you play inside Telegram, there is no email address or password — see the Telegram row below.	To create and hold your account, to show your display name on leaderboards, where other registered players with a confirmed account can see it (and on public pages, unless you switch that off — below), and to prove you were told the terms you agreed to.	Performance of a contract — Art. 6(1)(b). Without it there is no account.
Game Your Predictions and Live Moment answers, your Score and Rating, your Followed Club, the national team you support if you pick one, which of the two you show on leaderboards, whether you show colour stripes beside your name and whose colours they are (your club's or your national team's), your leaderboard positions.	To run the game: to resolve Predictions against real match events and rank you. The short code of the club you follow is shown next to your display name on leaderboards, so other registered players can see which club you follow — or, if you choose to show it instead, the code of the national team you support. Picking a national team is optional and changes nothing in the game; we never ask for your nationality and do not infer it. If you are among the top players of a fixture, or in the top 100 of a season, month or week, or in the top 10 of a season on one competition's matches, your rank and Score can also appear on public pages — your name on public pages, below. Everything else here is shown only to you. A ranking row names you to the other players’ apps by a code made from your account identifier that cannot be turned back into it, never by the identifier itself.	Performance of a contract — Art. 6(1)(b). This is the service.
Technical IP address, browser and device type, the pages and API paths you requested, timestamps, and error reports when something crashes (which include your account identifier so we can tell one player's broken session from a site-wide outage, and the address of a failed request with any identifier of yours in it replaced by a placeholder).	To keep the service up, find and fix faults, and detect abuse such as automated play or multiple accounts.	Legitimate interests — Art. 6(1)(f): operating and securing a service you asked to use. You can object; see your rights.
Analytics Google Analytics 4 events — which pages and screens you open on this site and in the game alike, and in the game also which steps you take: signing up (and whether by password, Google or Telegram), verifying your email, choosing a club (which club, and whether it is your first or a change), submitting a Prediction Card (which fixture, how many of its questions you answered, whether all of them, how many carry Bold, whether it replaces an earlier card, and whether the fixture was still to come or already live) and making a Live Moment (which fixture, which question, and whether it is Bold); plus two one-off milestones, your first Prediction Card (which fixture, and whether it was still to come or already live) and the first card you make on a later day (which fixture). What you actually predicted — the scoreline, the scorer, the minute — is never sent. To state the two milestones only once, we keep the time of each on your player record in our own database, written only if you have allowed measurement. In the game every event also carries the language the game is shown in, so we can see whether a translation works as well as the original, and whether the game was opened in a browser tab, as an app installed on your home screen or inside Telegram, and on which kind of device (iPhone, iPad or iPod touch, Android, computer, or other) — a choice from a short fixed list, never a device identifier. Firebase Performance Monitoring, which times how fast things load, runs in the game only. In the game both are tied to your account identifier; this site has no account to tie anything to.	To understand which parts of the site and the game are used and where they are slow.	Your consent — Art. 6(1)(a), the same switch as the next row. Nothing here runs until you say yes, and you may withdraw at any time.
Ad measurement (since September 2026) If you arrived from a Google advert we bought for thefinal, the identifier of that click is kept in a cookie on whichever of our two sites you are on. If you allow measurement only once you reach the game, the click identifier and campaign tags we noted when you arrived on thefinal.io (see the next row) go to Google Analytics with your first page in the game — only if that arrival was less than 30 minutes earlier — so the visit still counts as the advert's. When you then sign up, make your first Prediction Card or come back for another, we pass that milestone to Google Ads together with the click identifier. Google Ads receives the milestone and the click — never your name, email or predictions. We have told Google not to use any of this to personalise adverts, and we show no adverts ourselves.	To see which of the adverts we buy for thefinal bring players who actually play.	Your consent — Art. 6(1)(a), the same switch as the row above: "analytics and ad measurement" is one yes or one no.
Where you came from (since 28 September 2026) On your first visit we note, in two cookies of our own, when you arrived, on which page, the name of the website that linked to you (never the full address), and any campaign tags and advert click identifiers in that link — from any advertising network — plus the same for your latest visit from a campaign, an advert or another site. When you create an account we keep that record with it, together with whether you had allowed measurement at the time, and delete the cookies. It is sent to no one else — except that, only if you allow measurement, the campaign tags and advert click identifier of an arrival less than 30 minutes old go to Google Analytics, as the row above describes.	To learn which links, searches and adverts bring people who sign up, so we know where to spend on promoting thefinal. We read it in totals, not to target you.	Legitimate interests — Art. 6(1)(f), for everyone, without asking for consent. This is a deliberate decision: the cookies are not strictly necessary, and the law on device storage normally requires consent for them — see the Cookie Policy. You can object, and we will delete the record; see your rights.
Your name on public pages (fixture pages since 10 October 2026, the Ranks page and the league and cup pages since 26 October 2026) thefinal.io has public pages for the meetings of two clubs: one page per pair of clubs, and one for each of their past fixtures. Each shows the ten players with the highest Score on that fixture, and on all the meetings of those two clubs, this season and all-time: their display name, the short code of the club they follow (or of the national team they chose to show), their rank and their Score. The Ranks page shows the same for the top 100 players of each season, month and week — the rankings of the game — together with the badge of that club or national team and, if you turned them on, the colour stripes beside your name. Each league and cup page shows the same for the ten players with the highest Score on that competition's matches this season. Anyone can read these pages without an account, and search engines can index them. Nothing else about you appears there. A display name we would not publish anyway — one containing an at sign, for example — is never shown.	To show who predicts best — on a fixture, and over a season, month and week — on pages anyone can find, which is how thefinal becomes known.	Legitimate interests — Art. 6(1)(f): it is a public game ranking, it shows only the name you chose and how well you played, and you can switch it off at any time. The switch is "Hide my name" on your profile page in the game: you then appear on these pages as "Hidden Player", without your club's code, badge or stripes, and your ranking inside the game is unchanged. Writing to us works too. Hiding your name keeps it off the public pages only: inside the game, other registered players still see your name on the same rankings, so one of them could tell who holds a "Hidden Player" place.
Telegram (since 25 October 2026, only if you play at tg.thefinal.io) Inside Telegram the game signs you in with the launch data Telegram gives it: your Telegram user id, name, username, language and a few other details, signed by Telegram. Our server checks the signature and keeps only your Telegram user id, linked to your account, so the same account opens on every launch. Your name, username, photo and phone number are never stored, and the launch data is never written to our logs. Analytics, if you allow it, learns only that you signed up through Telegram, never your Telegram id.	To give you an account inside Telegram, where there is no email address to sign in with.	Performance of a contract — Art. 6(1)(b). Without it there is no account in Telegram.
Notifications (since 19 October 2026, only if you turn them on) For each browser you turn notifications on in: the identifier Firebase gives that installation of the game, your account identifier, your two choices — the reminder before your club's fixture, and the message when a card is scored — and when the game last confirmed them. For each notification sent, a note that it went out, so you never get the same one twice. A notification itself carries the two clubs' names, and either the kick-off time with which of the two is your club, or your card's Score and whether the Club-Boost applied; and the fixture's number in our system — never your name or email.	To remind you before a fixture of the club you follow while you have no card for it yet, and to tell you when a card has been scored.	Your consent — Art. 6(1)(a): nothing is registered until you tap to turn notifications on and allow them when your browser asks (or have already allowed them for this site). Turn either kind off with its switch on your profile page in the game, block notifications in your browser's settings, or sign out on that browser; you may withdraw at any time.
Email and Telegram messages (since 2 November 2026, only if you turn them on) Four switches, all off until you turn one on: a match reminder about two hours before your club plays while you have no card for it yet, and a weekly digest on Monday, each by email or — if you play inside Telegram — from our bot @thefinalgame_bot. We keep your four choices, your device's time zone (to send the digest at 09:00 your time — a little later east of about UTC+6, once the week's results are in, and at 09:00 UTC if we do not know your time zone), and a record of every time you turned one on or off: which one, where (your profile, a link in an email, your mail app's unsubscribe button, the bot's Stop button, or a spam report), which version of this policy you were shown, and when. For email we also keep whether our email provider reported your address as undeliverable; for Telegram, your chat with our bot — which is your Telegram user id — and whether the bot can still write to you. Your email address is not copied: we read it from your account each time we send. For each message sent, a note that it went out, so you never get the same one twice. A reminder carries the two clubs' names, the kick-off time and a link to the fixture; a digest carries last week's Score, your place among the players ranked that week, how it moved since the week before and how many of your card answers were correct, with a link to that week's ranking. Never anyone else's data. Our email provider's open and click tracking is switched off. The links carry campaign tags saying they came from one of these emails, so if you allowed measurement, analytics records that you arrived from one — as it would for any other link.	To remind you before your club plays and to tell you how your week went, where you asked for it.	Your consent — Art. 6(1)(a): each of the four is off until you tap it on, on your profile page in the game; inside Telegram the bot also needs your permission to write to you, which Telegram asks for. Withdraw at any time: with the same switch, with the link at the bottom of every email or your mail app's unsubscribe button, or with the Stop button under every reminder and digest from the bot. Blocking the bot stops its messages too. You are shown this policy, with a link to it, beside the switches before you turn one on.

We never ask for and never store payment details, because there is nothing to pay for. We show no adverts inside thefinal and never build an advertising profile of you. We do buy adverts for thefinal elsewhere: we record which advert, link or search brought each player (the row above), and, only with your consent, tell Google Ads whether its adverts worked — that is the whole of our advertising. We do not sell or rent personal data to anyone.

Match data — fixtures, line-ups, goals, cards — comes from a sports data provider and is about football, not about you. Nothing about you is ever sent to them. The public fixture pages also show how all players predicted a fixture, as totals and percentages, never with a name — and the split only once at least 20 players have made a Prediction Card for it; below that, only how many have. Each club’s public page shows how many players follow that club — one number, never who, and for a club few players follow it can be 1 or 2. When you change club or your account is erased, the number is normally lower within about two hours.

Cookies & device storage

We store a small amount of data on your device. Some of it is unavoidable — your sign-in token, your saved profile, the offline cache that lets the game work on a weak connection — and it is there whatever you choose. Analytics storage is not, and it only appears if you allow it. Two cookies sit in between: the ones that remember where you came from are not necessary, and we set them without asking. And if you turn notifications on, the game keeps what it needs to deliver them — nothing of it exists until you do.

The full list, item by item, is on the Cookie Policy page, along with the control to change your mind.

Who processes it besides us

We run on Google Cloud and Firebase. That means Google processes your data on our instructions, under Google's data processing terms — it does not get to use it for its own purposes. There is one exception, and it is named as such in the table: the ad-measurement signals we pass to Google Ads, which Google handles as a controller in its own right. Your browser's push service, if you turn notifications on, is not ours to choose either: your browser comes with it. And if you play inside Telegram, Telegram is a controller in its own right, also listed below.

Processor or recipient	What it handles
Google Cloud / Firebase Google Ireland Limited & Google Cloud EMEA Limited	Firebase Authentication (your email and password, your Google sign-in, or — if you play inside Telegram — your Telegram user id, kept on your account), Cloud Firestore (your account and game data), Cloud Run (serving the site and API), Cloud Logging (technical logs), Error Reporting (crash reports).
Google Analytics 4 & Firebase Performance Google Ireland Limited	Analytics events — only with your consent.
Google Ads Google Ireland Limited	The advertising milestones — that a click on one of our adverts led to a sign-up, a first Prediction Card or a return — with the click identifier, only with your consent. Google Ads is the one recipient that is not a mere processor: for these signals Google acts as an independent controller under its Google Ads data protection terms, which is why it is listed on its own line and why the switch that covers it is yours.
Firebase Cloud Messaging Google Ireland Limited	Delivers notifications, only if you turned them on: it receives each notification's content, described above, with the identifier of your browser's installation of the game — not your account identifier, name or email.
Your browser's push service run by the company that makes your browser — for example Google for Chrome, Microsoft for Edge (Windows Push Notification Services), Mozilla for Firefox, Apple for Safari	Carries a notification the last step to your device. Every browser does this through its own maker's service, so we do not choose it. It receives the notification encrypted, so that only your browser can read it; it does see that a message arrived for your browser, and when. If your device is offline, it holds the message for at most an hour.
Telegram Telegram Messenger Inc.	Only at tg.thefinal.io. That site loads Telegram's own script from telegram.org on every visit, even outside Telegram, so your device sends Telegram your IP address and browser details; inside Telegram, the app around the game is Telegram's. Telegram is not our processor: it runs the Mini App platform as an independent controller, and its own privacy policy governs what it does. From Telegram we receive the signed launch data and keep only your Telegram user id. Our bot @thefinalgame_bot also receives what you do in your chat with it — a message you send it (with the name, username and language Telegram attaches), blocking or unblocking it, pressing its Stop button — and we keep only whether it can still write to you and the switch a Stop press turns off. If you write /start, it answers once with a link to the game. Otherwise it writes to you only if you turn on its messages (above): each one goes through Telegram to your chat, addressed by your Telegram user id, and Telegram keeps it there under its own policy until you delete it.
Resend Plus Five Five, Inc.	Sends our emails, only if you turned an email switch on: it receives your email address, the message described above and two labels on it — your account identifier and which kind of message it is — so it can tell us if the address bounces or you mark a message as spam. It keeps a log of each message for 30 days. Open and click tracking are switched off.
Cloudflare Cloudflare, Inc.	Delivers and protects both sites. Every request passes through Cloudflare before it reaches us, so it handles your IP address, the page you asked for and your browser's user agent — this is how the site is served to you and it is not optional. Separately, only with your consent, Cloudflare Web Analytics measures page performance; it sets nothing on your device and does not profile you across sites. Cloudflare also keeps copies of some public data the site is built from — match and club pages, public rankings — for at most a few minutes, so it can be served again without reaching us.
Google reCAPTCHA Enterprise Google Ireland Limited	Checks that requests to the game come from the real app rather than an automated script, so that nobody can run up our costs or scrape other players' scores. It runs on every visit and is not covered by the measurement switch, because switching it off would leave the service undefended — see necessary cookies.

If we ever add a processor we will list it here before it starts processing anything, and if it involves a new category of data or a new purpose we will tell you directly rather than quietly editing this table.

Where your data is held

In the European Union. Our servers run in Google's Belgium region (europe-west1) and the database is in Google's multi-region European location (eur3). We did not pick those by accident and we do not move them casually — the database location, in particular, is permanent once chosen.

One exception, and only if you consent to analytics: Google Analytics may transfer some data to the United States. Google relies on the EU–US Data Privacy Framework and on the European Commission's standard contractual clauses for those transfers. Decline analytics and this does not apply to you at all.

The same applies to notifications, and only if you turn them on: Firebase Cloud Messaging is a global Google service that may handle a notification outside the EU, under the same Data Privacy Framework and standard contractual clauses. Your browser's push service is wherever its maker runs it, and it sees only the encrypted message.

Emails, if you turn them on: Resend sends them from its European region (Ireland), but keeps its log of each message — your address and the message — in the United States for 30 days. Resend relies on the EU–US Data Privacy Framework and on the European Commission's standard contractual clauses. Messages from our bot travel through Telegram, which operates as an independent controller under its own policy.

A second qualification, and this one applies to everybody: since 4 August 2026 both sites are served through Cloudflare, whose network is global. Your request is handled by whichever Cloudflare location is nearest you, which may be outside the EU, and Cloudflare is a US company. Cloudflare relies on the EU–US Data Privacy Framework and on standard contractual clauses. What reaches Cloudflare is the request itself — your IP address, the address you asked for, your user agent — not your account or game data, which stay in the European locations named above.

How long we keep it

Concrete periods, not "as long as necessary":

Account and game data — for as long as your account exists. When you ask us to delete it, we do so within 30 days. One record is the exception, and it is the next line.
Record of a deletion — when we erase an account we keep a single record of it: your account identifier and the date you asked. We keep it for as long as the service runs, because it is what stops the deletion being undone — signing in again would otherwise re-create the account we had just erased. It holds nothing else about you, no name, no address, no game history, and nothing reads it except the check that refuses to bring the account back.
Dormant accounts — deleted after 24 months with no sign-in. We will email you before that happens.
Technical logs and error reports — 30 days, then discarded automatically.
Analytics and ad measurement — 14 months in Google Analytics, then deleted by Google; the click cookie lasts 90 days on your device; conversion signals passed to Google Ads are kept by Google under its own terms. The two milestone timestamps on your player record stay as long as your account does, and we delete them earlier on request if you withdraw consent.
Where you came from — kept with your account for as long as it exists, click identifiers included, and deleted with it; deleted earlier if you object. The two cookies last 90 days at most and are deleted as soon as you sign up.
Your name on public pages — the pages keep no lasting copy of it: they are built from your account, and a page built for a finished match is kept in our servers' memory for up to 12 hours so it can be served again without being rebuilt; Cloudflare, which delivers the site, keeps a copy a little longer — a few minutes for the data behind our pages, up to an hour for a match or club page. When you switch "Hide my name" on, or when we delete your account, your name, club code, badge and stripes are gone from our pages within 24 hours, often much sooner — if our service is having an outage, a page saved earlier can show them a little longer. Copies that search engines or web archives already made are outside our control; we cannot delete them, but they refresh from our pages, and we will help you ask for their removal — write to [email protected].
Notifications — the registration of a browser is kept while notifications are on there. It is deleted when you sign out on that browser, when its push service tells us it can no longer receive them, and with your account; if the game has not been opened on that browser for 60 days, it is deleted the next time a notification would go to you. Turning both switches off stops every notification at once. We keep at most ten browsers per account. The note that a notification went out is deleted after 30 days.
Email and Telegram messages — your four choices, your time zone and the record of every time you turned one on or off are kept for as long as your account exists and deleted with it; turning a switch off keeps the record, because it is the proof of what you chose. The note that a message went out is deleted after 30 days. Resend keeps its log of an email for 30 days; a message from our bot stays in your Telegram chat until you delete it.
Telegram user id — for as long as your account exists, and deleted with it.
Consent record — 12 months on your device, then we ask again.

Your rights

Under the GDPR you may ask us to:

Show you what we hold about you, and a copy of it (Art. 15).
Correct anything wrong (Art. 16).
Delete your account and data (Art. 17).
Export your data in a machine-readable form (Art. 20).
Restrict what we do with it while a dispute is resolved (Art. 18).
Object to processing we base on legitimate interests (Art. 21) — for the record of where you came from, an email is enough: we delete it, no reason needed; for your name on public pages, the "Hide my name" switch on your profile page is the objection: it works at once, no reason needed, and your name is gone from our pages within 24 hours.
Withdraw consent to analytics and ad measurement, at any time — from the Cookie Policy page or from the switch on your profile page in the game; either one turns measurement off on both sites. Withdrawing does not undo what was lawfully collected before.
Withdraw consent to notifications, at any time — with the switches on your profile page in the game, by blocking notifications for play.thefinal.io in your browser, or by signing out on that browser.
Withdraw consent to emails and messages from our bot, at any time — with the switches on your profile page in the game, the link at the bottom of every email, your mail app's unsubscribe button, or the Stop button under every reminder and digest from the bot.

Email [email protected] from the address on your account; if you play only inside Telegram, there is no address on your account, so tell us your display name and we will agree with you how to confirm the account is yours. We reply within one month, as Article 12(3) requires; if a request is genuinely complex we may take longer and will tell you why within that first month. We do not charge for this.

If you think we have handled your data badly, you can complain to the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee) or to the supervisory authority where you live. We would rather you told us first, but that is your choice, not a precondition.

US state privacy rights

If you live in California or another US state with a comprehensive privacy law, you have rights to know what we collect, to delete it, to correct it, and not to be treated worse for exercising them. Use the same address: [email protected].

We do not sell personal information. With your consent we pass the advertising milestones described above to Google Ads so that we can measure our own adverts; we do not target you with adverts and we do not disclose your information for cross-context behavioural advertising as the CCPA/CPRA defines it. Declining or withdrawing the measurement switch — on the Cookie Policy page or on your profile page in the game, one answer for both sites — stops any further passing; what Google already received is held under its own terms and we cannot recall it. That switch is the opt-out. We do not process sensitive personal information for inferring characteristics.

Children

thefinal is for people aged 16 and over. You confirm your age when you register. We do not knowingly collect data from anyone younger, and if we find out we have, we delete the account and its data.

If you are a parent or guardian and believe your child has registered, write to [email protected] and we will remove it.

Images of footballers

This policy is about your data. One kind of personal data on thefinal is not yours, and it is fairer to say so here than to leave it out: the site shows photographs of professional footballers, alongside their names and shirt numbers, on squad lists and prediction screens, and on the leaders lists of each competition (top scorers, assists, cards) in the game and on our public league and cup pages. Our public fixture pages also list the events of past fixtures — who scored, who was booked, who came on — by the footballer's name, and we keep that record permanently, as the history of the fixture.

The photographs come through our football data provider, SportMonks. We import them, re-encode them — which discards any camera or location information the original file carried — and serve them from our own domain, so your browser never contacts the provider and the provider learns nothing about you. We show a player's name, shirt number and picture and nothing else about them. We do not analyse faces, match people between images, or infer anything from a photograph.

We do not import photographs of players our provider reports as under 18. Where no date of birth is given we cannot make that check, which is one of the reasons the channel below exists.

Any player, or anyone acting for them, can have their photograph removed — without giving a reason and without proving anything. So can any club or competition whose crest or logo we show. Write to [email protected]; the full procedure, including how quickly we act, is on the image rights & takedown page.

Security

Traffic is encrypted in transit (HTTPS everywhere) and data is encrypted at rest by Google Cloud. Passwords are handled by Firebase Authentication and stored hashed — we never see your password and cannot recover it for you; we can only help you reset it.

Access to production data is limited to what the services themselves need. No system is perfect, and we will not pretend otherwise: if a breach occurs that is likely to put your rights at risk, we will notify the Estonian Data Protection Inspectorate within 72 hours and tell you directly when the law requires it.

Changes to this policy

When we change this page we bump the version at the top and record what changed in the changelog below. Small changes — clearer wording, a new processor doing something we already disclosed — move the minor number and take effect when published.

Substantive changes — a new category of data, a new purpose, a new legal ground, a transfer somewhere new, or anything that reduces your rights — move the major number, and we tell you before they take effect rather than after.

Changelog

Version	Date	What changed
`12.0`	2026-11-02	Email and Telegram messages: a match reminder and a weekly digest, each by email or from our Telegram bot, only if you turn them on. New data (your choices, your time zone, a record of each time you turned one on or off), a new purpose, Resend as a new processor storing its email log in the United States, and Telegram now receiving the messages you asked for — so a major version. Nothing reaches you, and nothing about you reaches Resend or Telegram, unless you turn a switch on; the switches name this version of the policy and link to it, which is how you are told before anything starts — so you are not asked again.
`11.1`	2026-11-02	Cloudflare, which already delivers both sites, now also keeps copies of the public data behind match and club pages and the public rankings for a few minutes, and of the match and club pages themselves for up to an hour, so they are not rebuilt for every visit. The 24-hour limit for a hidden name is unchanged, and nothing new is collected, so a minor version.
`11.0`	2026-10-30	When you switch “Hide my name” on or your account is erased, your name now leaves the public pages within 24 hours instead of within a few minutes: a page built for a finished match is kept in memory for up to 12 hours, so the archive of past matches is not rebuilt on every visit. Nothing new is collected or published, but a hidden name can stay visible longer, which reduces a right, so a major version.
`10.4`	2026-10-29	The new public club pages show how many players follow each club, as one number with no names — for a small club, 1 or 2 — and how soon it moves after you change club or are erased. A number about a club, not about you, and nothing new is collected, so a minor version.
`10.3`	2026-10-28	Ranking rows no longer carry your account identifier: the other players’ apps now receive a code made from it that cannot be turned back into it, so the sentence 10.2 added about them is withdrawn. Narrower only, so a minor version.
`10.2`	2026-10-28	The rankings inside the game are now open only to registered players with a confirmed account, not to anyone signed in. We now say that other players’ apps receive your account identifier with your ranking row (never shown), and that an error report replaces any identifier of yours in a failed request’s address with a placeholder. The Cookie Policy moves to 7.1 for one new storage key that makes sure the game’s offline copy is deleted before anyone else signs in on the same device. Narrower or more precise only, so a minor version.
`10.1`	2026-10-26	Your name on public pages now also covers the league and cup pages: the ten players with the highest Score on one competition’s matches this season, shown as on the Ranks page. Same data, purpose, legal ground and “Hide my name” switch, and less detailed than the fixture pages already were, so a minor version. Images of footballers now also names the public league and cup pages, which show each competition’s leaders lists with the same photographs as the game.
`10.0`	2026-10-26	Your name on public pages now also covers the public Ranks page: the top 100 players of each season, month and week, with their display name, club or national-team code and badge, colour stripes if they show them, rank and Score. Same purpose, same legal ground and the same “Hide my name” switch; we also say plainly that hiding your name does not hide it from signed-in players inside the game. A wider publication of your name, so a major version, with the Terms (3.0).
`9.1`	2026-10-26	Clearer wording only: if you play inside Telegram, the Telegram user id we already keep with your account is also stored on your account in Firebase Authentication, Google's sign-in service we already list. Same data, same purpose, same recipient; nobody is asked again.
`9.0`	2026-10-25	thefinal can now be played inside Telegram, at tg.thefinal.io. There we keep your Telegram user id with your account, to sign you in, and nothing else from Telegram. That site loads Telegram's script from telegram.org, and Telegram is listed as an independent controller. New data and a new recipient, hence a major revision; the Cookie Policy moves to 7.0 for the storage Telegram's script uses. Nothing changes if you do not play inside Telegram, and nobody is asked again.
`8.1`	2026-10-22	If you allow measurement, the game's analytics events now also say whether the game was opened in a browser tab or as an app installed on your home screen, and on which kind of device — iPhone, iPad or iPod touch, Android, computer, or other. A choice from a short fixed list, for the same purpose and on the same basis; no device identifier is sent.
`8.0`	2026-10-19	The game can now send notifications: a reminder before a fixture of the club you follow while you have no card for it, and a message when a card is scored. They are off until you turn them on, and rest on your consent. We keep which browsers you turned them on in, and Google's Firebase Cloud Messaging and your browser's own push service deliver them. A new purpose and new recipients, hence a major revision. Nothing changes for you unless you turn notifications on.
`7.2`	2026-10-19	The colour stripes beside your name can now wear your club's or your national team's colours, whichever you choose, separately from the team shown beside your name. We keep that choice with your profile, like the stripes switch.
`7.1`	2026-10-14	You can now pick a national team you support and choose to show its code next to your name instead of your club's, on leaderboards and on the public fixture pages, and switch on colour stripes in its colours beside your name in the game. Both are optional and change nothing in the game, and we never ask for or infer your nationality.
`7.0`	2026-10-13	Your measurement choice is now one answer for both thefinal.io and the game, kept in a cookie of our own, so you are asked once and turning measurement off on either site turns it off on both. And if you allow measurement only once you reach the game, the campaign tags and advert click identifier we noted when you arrived on thefinal.io in the last 30 minutes now go to Google Analytics with your first page there. Passing a click identifier on is a major revision. Nothing is sent unless you allow measurement.
`6.0`	2026-10-10	thefinal.io now has public pages for fixtures between two clubs, and the top ten players by Score on each are shown there by display name and club code — pages anyone can read and search engines can index. A new purpose for your display name, on legitimate interests, hence a major revision. You can switch it off with "Hide my name" on your profile page; you then appear as "Hidden Player". The pages also show how players predicted a fixture, as totals only, from 20 players up, and the past events of fixtures by footballer's name.
`5.1`	2026-10-09	Your account now also keeps the language you chose for the game, so it opens in that language on any device, and the language of the Terms you accepted. Both are account details we already hold for the same purposes, on the same basis and for the same time. If you allow measurement, the game's analytics events also say which language the game is shown in.
`5.0`	2026-09-28	We now record where every player came from — the page, the linking website's name, campaign tags and advert click identifiers of any network — in two cookies of our own, set on your first visit without asking, and keep it with your account once you sign up. A new purpose, on legitimate interests rather than consent, hence a major revision. Nothing is sent to anyone else. The measurement choice is not asked again, because this does not depend on it; you can object by email and we will delete the record.
`4.1`	2026-09-19	The site started showing club crests, competition logos and photographs of footballers. Nothing about your data changed — no new collection, no new recipient, no new cookie, and the images are served from our own domain so no third party sees your browser. Added a section saying what we do with footballers' photographs, and a new image rights & takedown page with an address that reaches us quickly.
`4.0`	2026-09-10	We started buying adverts for thefinal and measuring whether they work — a new purpose and a new recipient, hence a major revision. The one measurement switch now covers ad measurement as well as analytics: with your yes, the identifier of the advert click that brought you here is kept in a cookie, and your sign-up, first Prediction Card and first return are passed to Google Ads with it. Google Ads is listed as a recipient in its own right. No adverts are shown inside thefinal, no advertising profile is built, and Google is told not to personalise. Everyone is asked again, because a "yes" to analytics alone did not cover this. The game gains a switch on the profile page, so an answer given there can be changed there.
`3.2`	2026-09-08	Added two one-off milestone events to the analytics list: your first Prediction Card, and the first card you make on a later day. To state each only once, your player record keeps the time of both — written only if you have allowed analytics, so nothing is kept for anyone who declined. Same processor, purpose and consent switch as every other analytics event; withdrawing consent stops the events, and the two timestamps stay only so that allowing analytics again does not count you twice.
`3.1`	2026-09-08	From this date the game's analytics events describe game steps as well as screens: sign-up and its method, email verification, choosing a club, submitting a Prediction Card and making a Live Moment — each with the fixture, club or question it concerns, as listed in full in the table above. What you predicted is never sent. Same processor, same purpose, same consent switch: nothing analytical runs until you allow it, and withdrawing stops it.
`3.0`	2026-09-06	Said plainly what happens after we delete an account: we keep one record of the deletion — your account identifier and the date you asked — for as long as the service runs, because without it signing in again would re-create the account we had just erased. This is not new behaviour being introduced, it is behaviour that the previous revision's flat "deleted within 30 days" did not qualify. Nothing new is collected, and the record holds nothing beyond those two fields.
`2.4`	2026-08-27	Leaderboards now show your display name and the short code of the club you follow instead of an anonymous handle, so other signed-in players can see both. Nothing new is collected, and leaderboards are not readable without signing in.
`2.3`	2026-08-07	Turned Google Analytics on for this marketing site, which until now measured nothing at all. It is the same measurement already used inside the game, so arriving here and then playing counts as one visit rather than two — and it still runs only if you allow analytics. Nothing new is collected in the game, and this site has no account to link anything to. Because any answer you gave here was given while nothing was running, answers recorded before today no longer count on either site and we will ask you once more.
`2.2`	2026-08-07	Removed the Prediction Point balance and spending history from the game data we hold: the currency was removed from the game itself, and the remaining historical balance records are being deleted. Nothing new is collected.
`2.1`	2026-08-05	Added sign-in with Google as an alternative to a password, and listed what it brings: the email address, name, profile-photo address and account identifier from your Google account. Same purpose, same legal ground, same retention as the rest of your account data.
`2.0`	2026-08-04	Added Cloudflare, which from this date serves and protects both sites — so it handles every request, including your IP address, and its network is global. Added Cloudflare Web Analytics, which runs only if you allow analytics. Added Google reCAPTCHA Enterprise, which checks that requests come from the real app. Recorded the transfer position for Cloudflare alongside the existing one for Google Analytics.
`1.0`	2026-07-29	First published.