This page describes what FPL Analyst actually does with data, written against the code that runs the site. It is deliberately short, because the site does very little.
Last updated: TODO: set the date this policy is published, and update it whenever the site starts handling data differently.
This policy has not been reviewed yet.
It was drafted from the behaviour of the code, not by a lawyer. Every highlighted TODO below is a fact that only the site owner can supply. Read it and resolve those before treating this page as a binding statement.
The one identifier the site handles is the FPL Team ID you type in, and it is a public number. The rest of this page explains exactly where it goes.
To analyse a team, the site asks for a Team ID. That is the number in the URL of a public FPL team page, for example the 1234567 in fantasy.premierleague.com/entry/1234567/history. Anyone who has the number can look up the same information, whether or not they use this site.
When you submit it, this happens:
The site holds no database of users or teams. Nothing about a team is written to storage on the server, so there is no profile building up over time.
The team optimiser route writes the Team ID it is processing into the server log, alongside the gameweek being calculated. These logs exist for debugging.
The site runs on Vercel. As with any web host, Vercel receives and records the ordinary details of each request in order to serve it: the IP address it came from, the browser user agent, the time, and the address requested. That processing is Vercel's, and it happens for every site they host.
How long those logs are kept: TODO: state the actual log retention. This depends on the Vercel plan and configuration in use, so it cannot be read from the code.
The site writes one value to your browser's local storage. Local storage is not a cookie: it stays on your device and is never attached automatically to requests.
That is the whole list. It is not sent anywhere except as described above, and it does not identify you personally. Older versions of the site also wrote a value namedfplSettings for two display preferences that no longer exist; the Settings page removes it when you save or clear.
This site sets no cookies. It loads no analytics SDK, no advertising tag, no session recorder, and no social media pixel. Nothing on any page reports your visit to a third party.
The web fonts are compiled into the site when it is built and served from fplanaly.st, so viewing a page does not send a request to Google Fonts either.
There is nothing to opt out of and no cookie banner, because there is nothing a banner would need to ask you about.
Your browser talks only to fplanaly.st. To assemble a page, the server then makes its own requests to:
Because these calls are made by the server and not by your browser, your IP address is not exposed to any of them.
The contact page has no form. It links to an X profile; anything you send there is handled by X under its own policies and never reaches this site's servers.
Since the site keeps nothing about you, the only thing to remove is what is stored on your own device. Open Settings and use Clear all site data, or clear site data for fplanaly.st in your browser. Either one removes the values described above immediately.
A Team ID that has already appeared in a server log cannot be pulled back out by this site; it ages out with the host's log retention.
Questions about anything on this page can go to @M_Bas1 on X.
If this site starts collecting anything it does not collect today, this page will be updated to say so before that change ships.
FPL Analyst is an independent project. It is not affiliated with, associated with, authorised by, or endorsed by the Premier League, Fantasy Premier League, or any of their affiliates. All Premier League and Fantasy Premier League names and marks belong to their respective owners. The site reads publicly available FPL data and adds its own analysis on top.
See also the Terms of Service.