Legal
Privacy
Every kind of personal data this product stores, where it lives, how long it stays and how to take it back.
Last edited 11 August 2026
Draft — not reviewed by a lawyer
This is a draft. It was written by the people building this product, and it has not been reviewed by a lawyer. It must be before anything is sold. The decisions still open are listed at the foot of this page.
The short version
This product stores your e-mail address, the public Fantasy Premier League team id you connect, the squads and plans you build, your preferences, and what the payment provider reports about your subscription. It never stores a password for anything, it never sees your card details, and nothing about you is sold to anybody.
The table below is the whole list, table by table, exactly as the database is built. It is checked against the database by an automated test, so it cannot quietly fall out of date.
What is stored, and why
Every table in this product’s database.
Where
users
What is in it
Your e-mail address, whether you have confirmed it, and — for the small number of accounts the owner has personally marked complimentary — the date that access was granted and a short note the owner wrote for their own records about who the account belongs to and why. That note is never shown to the account holder inside the product.
Why
It is how you sign in and how a payment is attached to somebody. There is no password column.
How long
Until you delete your account, and then removed with everything linked to it.
Where
sessions
What is in it
One row per signed-in browser, holding a one-way hash of the session token, when it was created, when it expires and when it was last seen.
Why
It is what keeps you signed in, and what lets you end a session. The token itself is never stored, so a copy of the database cannot be used to sign in as you.
How long
Until the session expires, is signed out, or the account is deleted.
Where
login_tokens
What is in it
One row per sign-in link that has been sent and not yet used, holding a one-way hash of the link, when it was created, when it stops working, and when it was used.
Why
It is what makes a sign-in link work exactly once and stop working after fifteen minutes. The link itself is never stored, so a copy of the database cannot be used to sign in as you.
How long
Removed once it expires or shortly after it is used.
Where
teams
What is in it
The public Fantasy Premier League team id you connected, plus the team name and manager name FPL publishes for it, and when they were last read.
Why
It is the only thing that links this product to FPL. It is public information, and no password is involved at any point.
How long
Until you disconnect the team or delete your account.
Where
drafts
What is in it
The squads you build: their names, the players in them, and which one is active.
Why
Before the season starts this is the only squad the product can have, so it is kept on your account rather than on one device.
How long
Until you delete the draft or the account.
Where
plans
What is in it
Multi-gameweek plans: their names, the gameweeks they cover and their contents.
Why
So a plan you made on a laptop is there on a phone.
How long
Until you delete the plan or the account.
Where
journal_entries
What is in it
Decisions you chose to record: the gameweek, a headline, any detail you added, when the decision was made, and, for a decision frozen from a decision room, which room it came from.
Why
So the product can show you what you decided and what happened, rather than asking you to remember.
How long
Until you delete the entry or the account.
Where
settings
What is in it
Your preferences: risk appetite, a rank goal if you set one, the pitch overlay you last chose and your light or dark theme.
Why
So the product opens the way you left it, on any device.
How long
Until you delete your account.
Where
subscriptions
What is in it
What the payment provider reports about your subscription: its status, which plan, when the current period ends and whether it is set to cancel. Also the identifiers the provider uses for you and for the subscription.
Why
It is how the product knows what you have paid for. No card number, no expiry date and no name on a card is ever stored here or anywhere else in this product.
How long
Kept while the subscription exists, and afterwards for as long as tax and accounting law requires the record of a sale to be kept.
Where
entitlements
What is in it
What your account is allowed to use, when it was granted, when it expires and whether it has been withdrawn.
Why
It is the record the server checks before doing paid work, so that what you bought is what you get on every device.
How long
Until you delete your account, subject to the accounting record above.
Where
billing_events
What is in it
The messages the payment provider sends about payments, stored with the provider’s own identifier so the same message is never acted on twice.
Why
A payment message that is processed twice charges or credits somebody twice. Keeping the record is how that is prevented and how a disputed payment can be traced.
How long
For as long as tax and accounting law requires the record of a payment to be kept.
Where
adoption_receipts
What is in it
A record that this product asked whether to move the drafts on your device onto your account, and what you answered — including when you said no.
Why
So that "did anything happen to my drafts when I signed in" has an answer that is not somebody’s recollection.
How long
Until you delete your account.
Where
decision_rooms
What is in it
The name and question for one Fantasy Premier League decision you are weighing, the gameweeks it covers, any note you added, and a small record of where you started it from — a draft, a connected team or neither — holding only ids and the time it was read, never a name.
Why
It is the workspace one decision lives in while you weigh it, so the branches, assumptions and conversation below all belong to something.
How long
Archiving a room only puts it away — the title, question, notes and everything hung off it stay exactly where they are. What ends the storage is deleting the room itself, or deleting your account.
Where
room_branches
What is in it
The alternative versions of your squad you are comparing inside a decision room: a short label for each one, where it came from — typed by you, proposed by the companion, produced by the solver, or imported — and which one you are currently looking at.
Why
A decision room lets you hold several versions of a squad against each other, and this is the tree that holds them.
How long
Until you delete the branch, the room, or your account.
Where
room_branch_versions
What is in it
A full snapshot of one branch’s squad at one point in its history — who is in it, what was paid for each player and the money left over — plus a short note if you left one.
Why
Undo inside a decision room works by moving a pointer over these snapshots rather than recomputing anything, so each change to a branch is kept.
How long
Until the branch, the room, or your account is deleted.
Where
assumption_sets
What is in it
A name and a description for a group of assumptions you have saved, so it can be reused.
Why
So a set of assumptions built once can be applied again without retyping it.
How long
Until you delete the set or your account.
Where
room_assumptions
What is in it
A place where you have told the product a figure is wrong — a player’s expected minutes, a team’s attacking strength, and the like — what you think it should be instead of the model’s own reading, and, for the ones that apply to one decision only, which room that is. When no room is named, an assumption applies to every decision on your account instead of just one.
Why
The model’s reading is a projection, not a fact, and this is how you can hold a different view of one and see decisions worked out against it.
How long
Until you delete the assumption, the room it belongs to, or your account — and if it is saved inside a named set, deleting that set deletes it too.
Where
live_readings
What is in it
One snapshot per gameweek of what FPL published about every player — minutes, goals, cards, bonus and points — with the time it was read. It holds nothing about you or your team.
Why
FPL says what a player has done and never when he did it, so telling you a goal has just gone in means comparing the newest reading with the one before it. Something has to hold the earlier one.
How long
Each gameweek keeps one row, overwritten every time the gameweek is read again.
Where
live_events
What is in it
The changes found between two of those readings: which player, what changed, and the time it was read. Shared by everyone — a goal is one entry, not one per manager — and it names no account.
Why
It is the running list of what has happened in a gameweek, which is what makes a live screen worth opening twice.
How long
Kept for the season, then removed with the gameweek it describes.
Where
room_messages
What is in it
What you typed to the decision companion and what it replied, kept in the order the conversation happened.
Why
It is the conversation that built the branches and assumptions beside it, kept so you can read back why a branch exists rather than only that it does.
How long
Until you delete the room or your account.
Where
room_analyses
What is in it
A stored result from asking the decision companion to compare branches or look more closely at one: what kind of look it was, whether it finished, and what it found.
Why
Some of what the companion produces takes real time and cost to work out, and keeping the result is what lets it be shown again without asking for it twice.
How long
Until the room, or the branch it looked at, is deleted, or your account is.
Where
ai_usage
What is in it
A record that a request was made to the model behind the decision companion: which model answered it, roughly how big the request and the reply were, how many further lookups it made, how long it took, whether it succeeded, and its estimated cost.
Why
It is what a usage allowance is measured from, and it is kept even after a decision room is deleted because the record of what was spent has to outlive the workspace it was spent inside.
How long
Until you delete your account.
What is kept in your browser
This product sets no advertising cookies and no third-party tracking cookies. What it keeps in your browser is listed here by its real name, so you can find it and delete it yourself. The table is the whole list — it is compared against a real browser, not written from memory.
Reading this site leaves nothing behind. Every page here can be visited from a clean browser without a single cookie or stored value being written; the first entry below appears when you connect a team, and the rest when you build a squad, sign in or subscribe. Nothing is written before you do something.
Everything is either a cookie or ordinary browser storage. This product uses no IndexedDB database, nothing in session storage, no offline cache and no service worker, so there is nowhere else on your device for it to have left anything.
Cookies and browser storage this product uses.
Name
overnil-session
What it is
A cookie holding the token that says this browser is signed in as you. Only the server can read it — no script on the page can, including this product’s own.
Why
It is what keeps you signed in from one page to the next. What the server keeps is a one-way hash of it, so a copy of the database cannot be turned back into this cookie.
How long
Thirty days, renewed while you keep using the product. Signing out, deleting your account, or clearing site data removes it immediately.
Name
overnil-team
What it is
A cookie holding the public FPL team id you connected.
Why
The server needs it to draw your screens on the first request, before any script runs.
How long
Until it expires or you disconnect the team. Clearing site data removes it.
Name
overnil-draft
What it is
A cookie holding the player ids in your current draft.
Why
Same reason: so the first paint of a page already knows your squad instead of flashing an empty one.
How long
Until it expires or the draft is cleared.
Name
overnil:manager:v1
What it is
Browser storage holding your team id and your preferences — risk appetite, rank goal, the overlay you last chose — so the product works on a device before you have an account.
Why
You can use this product without signing up. That only works if the device can remember.
How long
Until you clear it, or clear the site’s data in your browser.
Name
overnil:squad:v1
What it is
Browser storage holding the squads you build on this device: their names, the players in each one, who has the armband, and which squad is the one you are working on.
Why
A squad you build before signing up has nowhere else to live. After you sign in it is still written here, so the product keeps working when the network does not.
How long
Until you delete the squads, clear the site’s data, or your browser clears it. Deleting your account does not reach this device; clearing site data is what removes it here.
Name
overnil:squad-sync:v1
What it is
Browser storage holding what this device and your account last agreed on: which squad here matches which squad there, and when each was last changed. Kept per account, so two people sharing a browser do not inherit each other’s.
Why
It is how the product can tell "you changed this here" from "you changed it on your phone", instead of guessing and overwriting one of them.
How long
Until you clear the site’s data.
Name
overnil:adoption:v1
What it is
Browser storage holding your answer to "move what is on this device onto your account?" — including when the answer was no.
Why
So you are asked once rather than on every visit, and so declining is a decision the product remembers rather than one it keeps reopening.
How long
Until you clear the site’s data.
Name
overnil.theme
What it is
Browser storage holding whether you chose light, dark or your system setting.
Why
So the page does not flash the wrong theme before it can ask a server.
How long
Until you clear it.
Of these, only overnil-session is kept out of reach of scripts on the page — it is the one that would let somebody act as you, so nothing running in the page can read it. Clearing this site’s data in your browser removes every one of them, and signing out removes the session on the server as well as here.
What is never collected
- Your Fantasy Premier League password. This product has never asked for one and has nowhere to store one.
- A password of any other kind. Signing in here uses a one-time link to your e-mail address.
- Your card number, its expiry date, its security code or the name on it. Those are entered on the payment provider’s own page and never reach this product.
- Anything about you from anywhere other than you and the public Fantasy Premier League data you point this product at.
Why this data may be held
- To give you what you asked for — your account, your squads, your plans, your subscription. That is the contract you entered into.
- To keep the product working and safe: session records, rate limiting, the record of payment messages. That is a legitimate interest, and it is limited to what the job needs.
- To meet the law: records of a sale have to be kept for tax purposes whether anybody wants them kept or not.
If this product ever needs to do something with your data that is none of the above, you will be asked first, and you will be able to say no without losing anything you paid for.
Who else sees it
Only the companies that run parts of this product: whoever hosts it, whoever runs the database, the payment provider, and whoever sends the sign-in e-mails. Each of them sees only the part it needs and is bound by a written agreement to use it for nothing else. Their names are one of the open questions below, and this draft does not guess at them.
Personal data is not sold, not traded, and not handed to anybody for advertising. If a court or a law compels a disclosure, it will be made, and you will be told unless telling you is forbidden.
What this product sends to Fantasy Premier League
The requests this product makes to Fantasy Premier League are made by this product’s own server, not by your browser, and they contain the public team id you connected and nothing about you. Your e-mail address, your subscription and everything you build here are never sent to them.
Your rights, and how to use them
- Get a copy of everything held about you, in a form you can read and move elsewhere.
- Correct anything that is wrong.
- Delete your account and everything attached to it, except records the law requires to be kept.
- Object to a use of your data that rests on a legitimate interest, and have that considered rather than dismissed.
- Ask for processing to stop while a dispute about accuracy is worked out.
- Complain to the data protection authority where you live. Doing that costs nothing and does not require any contact here first.
Deleting your account is the one you can do yourself, now: it is a control on the "Your account" screen in the product. It lists exactly what will be removed, asks you to type the address you sign in with, and then does it — the account and everything linked to it go in one operation. What survives is the record of a payment, because tax law requires it, and it holds no more than the fact and the amount of the sale.
The other five are answered by a person, at the address in "How to reach a person" below, within one month of asking. If that section says no address is published yet, then it is not published yet and this page will not pretend otherwise — nothing here is sold until it is. Complaining to the data protection authority where you live needs nothing from this product at all.
How it is kept
- There is no password column anywhere in this product’s database, for anything.
- A session is stored as a one-way hash of its token, so a copy of the database cannot be used to sign in as anybody.
- Deleting an account deletes everything linked to it in the same operation, rather than leaving orphaned rows behind.
- Card details never enter this product at any point.
No system is perfectly safe, and anybody who tells you otherwise is selling something. If personal data here is ever exposed in a way that puts you at risk, you and the relevant authority will be told within the time the law sets.
Children
This product is not aimed at children and accounts are for people old enough to enter a contract where they live. If you believe a child has an account here, say so at the address in "How to reach a person" below and it will be removed.
Changes to this policy
When what is stored changes, this page changes with it — the table above is generated from the same record the database is built from. Where a change affects your rights you will be told rather than the page merely being edited.
How to reach a person
Write to Murkelvägen 4 Mjölby 59553. A person reads it; there is no ticket queue and no form to fill in.
Everything on this page that names this address is answered from it, and nothing on this page sends you anywhere else. If the paragraph above says no address is published yet, that is the true state of it rather than a page you have failed to find.
Before this can be published
What a lawyer and the owner still have to decide
Written down rather than guessed at. Every item here is a place where inventing an answer would have made this document read as finished while being wrong.
- The legal name and address of the controller — the business that decides what happens to this data — which must be named here.
- Whether a data protection officer is required, and if so who it is and how to reach them.
- The country or countries the database and backups actually run in, and what covers any transfer outside the United Kingdom and the European Economic Area.
- Each processor’s name: the hosting provider, the database provider, the payment provider and the e-mail provider, with a written agreement in place for each before launch.
- The exact retention period for payment records, which is set by tax law in the country of establishment rather than chosen here.
- The exact retention period for server logs, which is not yet set.
- Which supervisory authority a complaint should be made to, which follows from where the controller is established.
- Whether a control for exporting a copy of everything held about you will exist at launch, or whether that one right is answered by writing to the contact address. Deleting an account is already a button on the account screen; getting a copy is not, and today that means it has to be asked for.
- The contact address itself, which has to be published here before anything is sold. Every right above except deleting the account is exercised through it, and until one is published this page says so rather than pointing at a page that does not exist.