Privacy Policy
Version 1.6 · 26 September 2026
This policy explains the categories of personal data we process, why we process them and for how long. It describes what the service actually does today, not what it might do later. When that changes, this document changes with it and gets a new version number.
1. Who is responsible
The controller of your data is Pavlo Ozhehov, an individual entrepreneur (ФОП) registered in Ukraine under registration number 2793508359. For anything in this policy — including a request to see, correct or delete your data — write to support@worldbestclub.love. That address reaches us directly and is the contact point for data protection matters. Our full registration details, including our registered address, are provided on request.
2. What we collect
2.1 Your account
- Email address — so you can sign in and so we can confirm the address is yours. We also store whether and when it was confirmed.
- How you sign in. There are two ways: a code sent to your email, or your Google account. If you sign in with Google, Google sends us your email address and whether it is verified, the identifier of your Google account, and — because Google includes them whether we ask or not — your name and a link to your profile picture. We use only the email address. Your name and picture are never shown, never used and never passed on; they sit in the sign-in record that our sign-in provider keeps for your account and are removed with it. Both ways lead to the same account when the email address is the same.
- Fan number — a number given to your account, shown next to unnamed supporters in club lists.
- Nickname, if you choose one, and when it was set or changed. Your nickname is public.
- The club you support, when you chose it, and whether you have changed it.
- Your balances and daily limit — the points you hold, free and purchased.
- Who invited you — if you opened the site through another supporter’s link, we keep that supporter’s fan number next to your account, and we count how many people came through your own link. Nothing else about either of you is stored for this, and no reward is attached to it today.
We ask for no name, no phone number, no address and no date of birth. The only name we ever receive is the one Google attaches when you choose to sign in with it, and we do not use it. We never see your card details.
2.2 What you do in the game
- Votes — which club, how much, when, and which balance the points came from.
- Your statement — a line for every movement of points, so you can check what happened to your balance.
- Titles and records, if and when the service starts awarding them. Nothing is awarded today.
Club standings, supporter counts and the average contribution per supporter are public. Your nickname appears in them if you set one; if you have not, you appear as an unnamed supporter with your fan number.
2.3 Technical error reports
When something breaks in your browser, we record the error so we can fix it: the error text and stack, which screen you were on, the interface language, the build of the app and a random identifier for the browser tab. We do not store your IP address with it, and the identifier is not linked to your account. Before an error is saved, both your browser and our server apply filters designed to remove email addresses and access tokens from the text. Access to the reports that remain is restricted to fixing faults.
2.4 Protection against email abuse
To stop one person burning through everyone’s confirmation emails, we count how many emails were requested for an address and from a network. That counter table holds no raw email addresses and no raw IP addresses: it stores a SHA-256 hash of each, salted with a secret key that is not in our source code. We use those hashes only to recognise repeated requests. The same kind of counter, hashed the same way, also records how many wrong confirmation codes were entered for an address, so that a code cannot be found by guessing.
To be accurate about what that protects: these are pseudonymous identifiers, not a guarantee of anonymity. Whoever holds the secret key can hash a known address or IP and check whether it matches — for IP addresses the set of candidates is small. The hashing keeps the counter table itself from being a list of addresses; it is not a promise that a record can never be linked back to a person. Note also that this paragraph is about the counter table only: your account and the other records described in this policy do hold your email address or IP address, as set out here.
2.5 Fair-play signals
Standings only mean something if one person is one supporter. To notice coordinated voting — many accounts driven by one script — we record, with each vote, a small set of signals: the IP address the vote came from and its network prefix, a hash of your browser’s identification string, your time zone, and timing (how long after opening the page the vote was given, and how long the tab had been open). These signals are looked at by a person, in aggregate, to spot patterns such as many accounts voting for one club from one network within the same minute. No decision about your account is made automatically from them, and they are shared with nobody. They are kept for 90 days and then deleted. Our rules for what happens when coordinated voting is found are in the Terms: free daily credit can be withheld from the accounts involved and the affected votes removed from the club’s total; accounts are not closed for this.
2.6 Consent records
When you accept these documents at registration, we record which version you accepted, a hash of the text you were shown, the date and time, and the IP address and browser you accepted from. We keep that record to be able to show which terms you accepted.
2.7 Captcha
The registration form is protected by Cloudflare Turnstile, which checks that you are a person rather than a script. Cloudflare receives your IP address and signals from your browser in order to make that check. We receive only the verdict.
2.8 Sign in with Google
If you press “Continue with Google”, you leave for Google’s own sign-in page and come back with a one-time code that our sign-in provider exchanges for your session. Google learns that you are signing in to World Best Club and when; what Google does with that is governed by Google’s privacy policy, not by this one. We receive from Google the items listed in 2.1 and nothing else: no contacts, no calendar, no files. You can remove World Best Club from your Google account at any time in Google’s security settings; your account here keeps working with the email code.
2.9 Server logs and sign-in sessions
Our hosting and database providers keep standard technical logs of requests, which include IP addresses, for a short period, to keep the service running and to investigate abuse and faults. We do not use these logs to build a profile of you.
For each sign-in that is still active, our sign-in provider keeps the IP address and the browser the session started from, until you sign out or the session expires after 30 days without activity. It also records the date and time of your last sign-in. We look at these only to answer a question about your account or to investigate abuse.
2.10 Storage in your browser, and visit statistics
We keep your current state — the club you picked, your points, whether your email is confirmed — in your browser’s local storage, so that reloading the page does not throw your session away. It stays on your device.
That storage is what the functions you asked for need in order to work — keeping you signed in and remembering your club — which is why we do not ask you for consent to it.
We count visits. The site loads a small script from Vercel, our hosting provider, which reports each page load to Vercel: the page path (any query string is removed before it is sent), the page you came from, your country, region and city as derived from your IP address at that moment, and your browser, operating system and device type. The IP address itself is not stored, the script sets no cookies and stores nothing on your device, and one visitor is told apart from another by a hash that is discarded after 24 hours — so visits cannot be tied to your account or followed from one day to the next. What we see is aggregated: how many people, from which countries, on which devices, looking at which pages. We use it to understand where the site is reaching. There is no advertising and there are no tracking cookies. If we ever introduce optional storage that does need your consent, this policy changes first and you will be asked before it is used.
2.11 Notifications about your club
If you switch on notifications in My record, your browser gives us a delivery address — a URL at the push service run by your browser’s maker (Google, Apple or Mozilla) — and two encryption keys for that address. We store those with the language of your interface, which of the three kinds of message you have switched on, and when we last sent you one. That is all: no device model, no location, no IP. We send at most three kinds of message, each about your club only: a reminder in the evening if you have not given a voice that day, a change of your club’s place, and the Monday result. Every message is encrypted for your browser alone; the push service sees that a message went to your browser and cannot read it. You switch notifications off in My record or in your browser’s site settings; either way the address is deleted, and an address the push service reports as gone is deleted automatically.
3. Why we are allowed to hold it
- To perform our agreement with you — your account, the way you sign in (including what Google sends when you choose it), your balances, your votes, your statement, who invited you. Without these there is no service as it is described in the Terms.
- Our legitimate interest in keeping the game honest and the service up, and in knowing where it is being used — the email and code counters, the captcha, server logs and sign-in sessions, error reports, and the visit statistics in 2.10. These are kept minimal deliberately: hashes instead of addresses, no IP with error reports, no cookies and no identity behind a visit.
- Legal obligation — once purchases are available, records of payments have to be kept for tax and accounting purposes.
- Your consent — notifications about your club (2.11). You give it by switching them on and take it back by switching them off; nothing else about your account changes either way.
Accepting the Terms and acknowledging this policy is not, by itself, consent to optional processing. The processing above rests on the bases named above — our agreement with you, our legitimate interests, and the law — not on a consent you could later withdraw. The one optional thing today is notifications (2.11): it rests on your consent, is asked for separately when you switch it on, and stops the moment you switch it off. Withdrawing a consent does not stop processing that lawfully rests on one of the other bases.
4. How long we keep it
Closing an account is handled by a person, on a request from the address on the account, sent to the address in section 1. There is no button for this inside the app yet, and there is no 30-day grace period in which a closed account can be restored — we would rather say that than describe a procedure that does not exist. When we act on such a request we close the account and erase the personal data in it: your email address, nickname, notification addresses, the sign-in record (including anything Google sent), the IP addresses and browser details kept with your votes and consents, and your balances — unspent purchased points are refunded first, as the Terms describe. Your votes stay in the club totals under a fan number with no name attached, so the season’s record does not change and nothing in it points back to you.
- Account data, votes and statement lines — while your account exists, and until a deletion request has been carried out. The sign-in record from Google (section 2.1) goes with the account. Club totals themselves are part of the public record of a season and stay, but they carry no personal data once your account is gone.
- Error reports — 14 days, then deleted automatically.
- Email-counter and wrong-code hashes (section 2.4) — 7 days, then deleted automatically.
- Sign-in sessions (section 2.9) — until you sign out, or 30 days without activity.
- Visit statistics (section 2.10) — the per-visit hash lives 24 hours; the aggregated reports are kept by Vercel for the reporting window of our plan, at present one month.
- Fair-play signals (section 2.5) — 90 days, then deleted automatically.
- Notification addresses (section 2.11) — until you switch notifications off, or until the push service reports the address gone; the log of what was sent, 30 days.
- Consent records — at present these are removed together with the account they belong to.
- Payment records — as required by tax law, once purchases are available.
We may keep a limited record beyond these periods where the law requires it, or where it is needed to bring or defend a legal claim, with access restricted to that purpose.
Backups. Our database provider keeps a daily backup of the database for seven days. We also take our own copy every day and keep it for 14 days: it is encrypted before it leaves the database, with a key that only we hold, and stored on a server in Amsterdam (EU) and in a private repository at GitHub — neither host can read it. Backups and our providers’ own technical logs roll over on their own schedules, so a deletion is not instantaneous everywhere at once; it is gone from every copy within 14 days.
5. Who else sees it
We do not sell data and we do not share it for advertising. We use these providers to run the service:
- Supabase — database and sign-in. Your account and game data live here, in the EU (eu-west-1, Ireland).
- Vercel — hosting of the site and the visit statistics described in 2.10. Sees requests and technical logs. Based in the United States.
- DigitalOcean — the server in Amsterdam (EU) that runs our tools and holds our encrypted database copy (section 4).
- GitHub — holds our source code and a second, encrypted copy of the database, which GitHub cannot read.
- Retool — the console our team uses to look after accounts: to find an account by its email address, answer a request, block an account that breaks the rules, or carry out a deletion. It runs in the United States and, while we use it, passes our queries and their results — email address, fan number, club, sign-in dates, interface language — between us and the database. It keeps no copy of your data, works through accounts that can read only what the console needs and can change nothing directly, and every action taken in it is logged with who did it and why.
- Assistants built on language models — we run part of our day-to-day work (checks on the database, reports, drafts of replies) with software assistants built on large language models, provided by Anthropic and, for some tasks, through OpenRouter; both are based in the United States. They act only on our instructions and only on what we put in front of them, and we keep personal data out of what they see wherever a count or a hash will do instead.
- Resend — sends our confirmation emails, EU region (eu-west-1). Receives your email address and the content of those emails.
- Cloudflare — the captcha on the registration form, as described in 2.7.
- Google — only if you choose to sign in with Google, as described in 2.8. Google is not a provider we send your data to; it is the source of the sign-in data listed in 2.1, and it sees that you signed in.
- Push services — Google, Apple or Mozilla, whichever runs your browser — only if you switch notifications on, as described in 2.11. They carry encrypted messages to your browser and see the delivery address, not the content.
- Porkbun — our domain and the forwarding of mail sent to our support address, which means they handle messages you send us.
- A payment provider — none is connected today, because purchases are not available. When one is, it will take payments as merchant of record and handle your card details, which we will still never see. We will name it here before any paid checkout is switched on.
Some of these providers are based outside the European Union, and the region where a provider delivers one service is not necessarily where all of its logs, support and sub-processors sit. Where data leaves the EU or Brazil, it is transferred under the safeguard that provider’s agreement with us puts in place for that service. Write to us at the address in section 1 and we will tell you which safeguard applies to a given provider, and how to obtain a copy where one can be provided.
6. Your rights
You can ask us to:
- show you what we hold about you;
- correct anything wrong;
- delete your account and your data;
- give you your data in a portable file;
- restrict or object to a particular use;
- withdraw a consent you gave.
Write to support@worldbestclub.love. There is no button for this in the app yet — the request is handled by a person, and we would rather say so than pretend otherwise.
Writing from the address on your account is the simplest way for us to know the request is yours. If you have lost access to that address, say so and we will agree another proportionate way to check — we will not demand identity documents we do not need.
We respond without undue delay, and within the deadline set by the law that applies to your request. Under the GDPR that is normally one month, extended only where the law allows and only with an explanation sent inside the first month. For requests under Brazil’s LGPD the deadlines of that law apply, including its shorter deadline for access requests. Where the rules on distance selling in your country require an earlier acknowledgement of a complaint, we send it within that time.
If you think we have handled your data badly, you can complain to the data protection authority where you live. In Brazil that is the ANPD; in the EU, the authority of your country.
7. Children
The service is for people aged 18 and over. It is not designed for children and we do not knowingly collect data from anyone under 18. If you believe a child has registered, write to us and we will delete the account.
8. Security
Connections to the site and to the database are encrypted. Direct network access to the database is closed, except for our own console (section 5), which reaches it from fixed addresses through accounts of its own with the narrowest rights that will do. Error reports are stripped of anything resembling an email address or an access token before they are stored, on your side and on ours. Email-counter records hold only salted hashes. Our own database copies are encrypted with a key held by us alone. Sign-in codes are eight characters long and expire in ten minutes.
No system is perfect. If a breach affects your data, we will tell you and the relevant authority as the law requires.
9. Changes to this policy
Each version carries a number and a date, shown under the title. We keep a record of which version you acknowledged. If a change materially affects you, we will tell you before it applies.
These documents are currently available in English only. If we publish translations, they will be for convenience: where a translation and the English text disagree, the English text applies, without taking away any right your own data-protection or consumer law gives you.