Last updated 19 September 2026
There is no account to create, no password to choose and no cookie set. Type a league id, get a dashboard. Nothing you type is stored against you, because there is no you here to store it against.
A league id, and optionally a team id. They are sent to the official Fantasy Premier League API to fetch that league, and they sit in the address bar, which means they appear in ordinary web-server request logs kept by the hosting platform. They are not attached to a name, an account or a profile, because there is none to attach them to.
None. The pages of this dashboard set no cookies and read none — not for sessions, not for preferences, not for analytics.
One thing is written to your browser, and it is not a cookie: a random string in session storage, used to tell one visit apart from another while the measurement below is taken. Session storage is never sent as a header, cannot be read by any other site, and is thrown away by the browser when you close the tab — so it starts again from nothing next time and cannot follow you between visits.
Page visits are counted by the hosting platform's own analytics. That script is served from this domain rather than a third party, it sets no cookie, and it produces aggregate counts — how many people opened a page — not a trail of who went where.
How long each screen was open is also measured, because a page everyone opens and leaves in three seconds and a page they read for two minutes otherwise look identical. When a screen goes away your browser sends one short message: the random per-tab string above, which screen it was, the team id if one was in the address bar, and a number of seconds. That is the whole message.
What that message does not carry, and what is not stored anywhere alongside it: no IP address, no cookie, no browser or device fingerprint, no referrer, and no text you typed. The screen is recorded as one of this site's own page names, matched on the server — an address that is not one of them is discarded rather than written down. Time only counts while the page is actually in front of you; a tab left open in the background stops the clock.
Separately, a private endpoint reports how many leagues and teams have been opened, and how many of them were new. Those numbers are read out of the cache described below rather than out of any log of visitors: they count leagues and team ids, not people, and one visitor opening three leagues is indistinguishable from three visitors opening one each.
Responses from the Fantasy Premier League API are cached so that fifty people opening the same league do not cost fifty fan-outs. What is stored is the game's own public data — standings, squads, fixtures — keyed by league id, with the time it was fetched. Rows are deleted about a week after they expire.
The cache holds no visitor identity: not an IP address, not a browser fingerprint, nothing that distinguishes one reader of a league from another. Nor does the timing measurement described above, which is kept in a separate table with the same four fields it was sent and nothing added to them.
There is no advertising or third-party tracking script on this site. The code can carry one conversion pixel, for measuring ads, but it stays off unless it is deliberately switched on — and this page says so plainly on the day that changes, because it reads the switch when you load it rather than repeating a sentence written months ago.
Every name on these pages — managers, teams, mini-leagues — comes from the Fantasy Premier League API, which publishes it for any public league. This site is a different way of reading data the game already makes public; it is not a new place your details have been collected. Changing what appears here means changing it in Fantasy Premier League itself, and the cached copy follows within a week.
Where the bot is enabled it is pinned to a single group chat, named in configuration, and it answers in that group only. It reads messages to see whether one is a command it knows; messages that are not are ignored and not stored. The identifier of a message it did answer is kept briefly, for long enough to avoid replying twice to the same question when the gateway retries a delivery.