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: keeping the Daily Read to one attempt per device per day, enforcing rate limits, and making sure only the device that finished a run can publish that run to the leaderboard or build a challenge on it.

“NEXT_LOCALE” holds nothing but a language code — en, es or pt — so the site keeps showing the language you are reading. It is written only when that language 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
• 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.

Playing the Daily Read also keeps a streak record for your device identifier: your current streak, your best streak, and the date you last played.

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.

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, the Daily Read finished, a training session started or finished, and a score posted or shared.

The values sent with those events are your score, archetype, streak length, the training category 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 request that caused it.

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.

• no accounts, no passwords, no email addresses
• 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, streaks and challenges are kept indefinitely, because the leaderboard, streaks and share links depend on them. 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.

Footy Eye is a football quiz for a general audience and is not directed at children under 13. It never asks for a name, an email or an age — 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.