Back to Home

Privacy Policy

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 short version

  • There are no accounts. There is nothing to sign up for and no password to give.
  • The site never asks for your Fantasy Premier League login, and could not use it.
  • This site sets no cookies of its own.
  • There is no Google Analytics, no advertising network, and no third-party tracking script.
  • Your browser only ever talks to fplanaly.st. No page loads images, fonts, or scripts from another company.

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.

Your FPL Team ID

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:

  1. Your browser sends the Team ID to this site's own API routes on fplanaly.st.
  2. The server uses it to request public endpoints on fantasy.premierleague.com — the team entry, gameweek history, transfer history, and gameweek picks.
  3. The server sends the result back to your browser and displays it.

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.

What the server logs

Two of the API routes — the xPoints route and the team optimiser — write the Team ID they are 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.

What is stored in your browser

The site writes two values to your browser's local storage. Local storage is not a cookie: it stays on your device and is never attached automatically to requests.

  • fplTeamIdThe last Team ID you entered, so you do not have to retype it on every page.
  • fplSettingsTwo display preferences: which analysis tab opens by default, and whether bench points appear in charts.

That is the whole list. Neither value is sent anywhere except as described above, and neither identifies you personally.

Cookies and tracking

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.

Services the server talks to

Your browser talks only to fplanaly.st. To assemble a page, the server then makes its own requests to:

  • fantasy.premierleague.com — the official public FPL API. This is the only one that ever receives a Team ID.
  • raw.githubusercontent.com and api.github.com — the xPoints prediction dataset, which is a public file. No information about you is sent.
  • fpldbt-production.up.railway.app — the analytics service behind features such as differentials, form momentum, and fixture difficulty. It receives no Team ID and nothing that identifies you.

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 form

The contact page asks for a name, an email address, and a message, and posts them to an endpoint on this site.

TODO: describe what actually happens to contact submissions before relying on this section. At the time of writing, the endpoint the form posts to is not implemented in this codebase, so submissions are not delivered or stored anywhere. Either implement it and say where messages go and who reads them, or remove the form.

Removing your data

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 Cached 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

Questions about anything on this page can go to: TODO: add the contact email address that should receive privacy questions.

If this site starts collecting anything it does not collect today, this page will be updated to say so before that change ships.

This is an unofficial site

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.