Privacy

“fiq_device” holds a random identifier. The server generates it on your first visit — it is not derived from you, and carries no name, no email and nothing about your device. It is httpOnly, so page scripts cannot read it, and it lasts two years.

It does three jobs: enforcing rate limits (including one attempt per challenge), making sure only the device that finished a run can publish that run to the leaderboard or build a challenge on it, and, when you sign in, finding the runs this device finished as a guest so they can join your account.

“NEXT_LOCALE” holds nothing but a language code — en, es, pt, fr, de or it — so the site keeps showing the language you are reading. It is written whenever you pick a language from the language menu. Otherwise it is written only when the language you are reading differs from the one your browser asks for, or from the one the cookie already holds; when they agree it is never set at all. It lasts until you close the browser.

When you finish a test, the server keeps the result so the score can be re-checked and shared:

• your score, per-category points and archetype
• which option you picked for each situation, and how many milliseconds each answer took
• the language you played in, and when you played
• the random identifier from the “fiq_device” cookie, which is what ties a run to the device that played it
• your Clerk user id, if the run belongs to an account (see “If you sign in”)
• if you post the result to the leaderboard, the handle and country you type, and when you posted it
• a SHA-256 hash of your IP address — the address itself is not stored

The IP hash exists to count requests for rate limiting. It is a hash, not an anonymous token: it is stable for a given address, so treat it as a pseudonym rather than as anonymity.

Creating a challenge stores the challenger name you type, the device identifier that created it, and a SHA-256 hash of that device’s IP address.

Signing in is optional: the Test and Training work the same without it. An account keeps your results together, on any device.

Accounts are run by Clerk (clerk.com). Clerk holds your email address and the username you choose, plus the sign-in provider, such as Google or Apple, if you use one, and handles every sign-in step; Footy Eye never sees a password.

Footy Eye stores only your Clerk user id, on the runs you finish while signed in, and, if you set up your team, with your team (its format, your position, its shape and plan, and when it was first saved and last changed) so it’s remembered on any device you sign in on. Whenever you sign in on a device, the runs that device finished as a guest and that aren’t on an account yet join your account too, whoever played them. Signing out leaves them on the account. Your team is handled a little differently. One set up on this device before you sign in joins your account if the account has none; otherwise the account’s team replaces it here. After that, changes you make while signed in, “Remove my team” included, are saved to the account and reach your other devices the next time you open or return to Footy Eye there; if two devices change it, the change made last is kept. Signing out takes the team off this device, unless a change hasn’t reached the account yet (see “What stays on your device”); either way, the team stays on the account.

Clerk’s script loads from Clerk’s servers on every page, so Clerk receives the usual details of any web request, such as your IP address and browser. It sets cookies whose names begin “__client_uat”, “__session”, “__refresh” or “__clerk”, to keep you signed in and to protect sign-in. “__client_uat” is set for every visitor and holds only a timestamp (0 when you are signed out).

Nothing about your account, including your username, is shown publicly: the leaderboard still shows only the handle you type.

Nothing is published unless you ask for it. Three actions publish:

• Posting to the leaderboard adds the handle and country you type, next to your score. Pick any handle you like — it is not checked against a real identity.
• Sharing a result creates a link. Anyone with that link can see that result page, so treat it as public.
• Creating a challenge creates a link too, and the challenger name you type is shown to everyone who opens it.

Vercel Analytics and Vercel Speed Insights record page views, page performance, and a small set of product events: a test started or finished, a training session started or finished, and a score posted or shared.

The values sent with those events are your score, archetype, the training category, pattern, tactical problem, youth format or your team’s format and position and its correct-out-of-total, your leaderboard rank, and whether a share used the system share sheet or the clipboard. They are counted in aggregate and are not tied to a name.

If error monitoring is switched on for a deployment, Sentry receives diagnostics when something breaks — the error, and technical detail about the page or request where it happened. For about one page load or request in ten, it also receives performance measurements. Either can include the address of the page and of the page you came from, the addresses of what the page loads, your browser and operating system, your language and time zone, your connection type, and your device’s memory and processor count. Your cookies are never sent to Sentry.

Training practice keeps a short list of recently seen scenarios in your browser’s local storage, under “fiq_train_seen”, so practice does not repeat itself. It never leaves your browser and is never sent to the server. Clearing site data removes it. If you set up your team on the Training page, its format, position, shape and plan are kept there too, under “fiq_team”, to pick plays that fit. When you train for your team, its format and your position are sent with the Training analytics events (see “Analytics and errors”). While you’re signed in, the team is saved to your account too, and “fiq_team_sync” holds your Clerk user id, the team as this browser last saved or received it, when that change was made, and whether your account has it yet, so this browser can tell which copy is newer. Signing out removes both from this browser, unless a change hasn’t reached your account yet: then both stay, so the change is sent the next time you sign in here, as long as the team isn’t changed and no one else signs in here before then. Your Training results (per play, how often you found the best read and spotted the key cue) are kept there as well, under “fiq_train_results”, to show your progress by problem. After you post a score, your posted handle, score, rank and board tab are kept for the session in your browser’s session storage, under “fiq_last_post”, so the board can highlight your row; only its timestamp is added to your next leaderboard request, to skip a cached copy. The handle, score and rank are never retransmitted from this note, and it disappears when the tab closes. After you sign in, “fiq_adopted” in session storage holds your Clerk user id for that tab, so the runs this device played as a guest are added to your account only once. “fe_seen_intro” in session storage records only that the opening animation has played in this tab, so it isn’t shown again. If you pick a theme (dark, light or auto), “fiq_theme” in local storage keeps your choice, so every page opens in it. It never leaves your browser.

• no passwords or email addresses stored by Footy Eye — accounts are handled by Clerk
• no advertising and no ad networks
• no selling or sharing of data with data brokers
• no tracking you across other websites
• no payment details — nothing here costs money

Runs and challenges are kept indefinitely, because the leaderboard and share links depend on them. Streak records from the retired Daily Read are still stored, and are no longer read or updated; they will be deleted in a future cleanup. Clearing the “fiq_device” cookie gives your browser a new identifier: it will not remove what is already stored, but nothing new is connected to the old one. Deleting your account removes your email, username and sign-in details at Clerk; your runs stay, with the account’s id and what each run stores (see “What a run stores”), but nothing else from your account. Your saved team stays too, under that id. To remove it, choose “Remove my team” on the Training page while signed in, before you delete the account: the team itself is deleted, and only that id and when the team was first saved and removed are kept, so an older copy on another device can’t bring it back.

Footy Eye is a football quiz for a general audience and is not directed at children under 13. Playing never asks for your real name, an email or an age, and signing in is optional — but it does store the identifiers described above, so it is not accurate to call it data-free.

If what is collected changes, this page changes with it, and the date at the top moves.