FPL Gaffer, run by FPL Gaffer, is built to know as little about you as it can. There are no accounts, no advertising trackers and no analytics vendors.
What stays in your browser
- The FPL team id you enter, in a cookie called
gaffer_team, so the app opens on your team. - Your theme, gaffer, watchlist and planner drafts, in your browser's local storage.
- If you buy Pro, a random pass in an httpOnly cookie called
gaffer_prothat switches Pro on for that device.
What we store on our server
- Page views: the page, a random visit id that lives in your browser, the site that sent you (its name only), your country (two letters), whether you are on a phone, tablet or computer, and your operating system in one word. No IP address, no browser fingerprint. If your browser sends Global Privacy Control or Do Not Track, nothing is recorded at all.
- Product events such as “a team was opened”, with the public FPL team id, the gameweek and your operating system.
- Pro: Paddle's ids for your subscription and customer record, the subscription's status and end date, and a one-way hash of each device pass. When you restore Pro on a device we ask Paddle for the email on your order to check it matches; we don't keep it.
Payments
Paddle.com sells Pro as Merchant of Record. Your name, email, address and card are given to Paddle and handled under Paddle's privacy policy; they never reach us, apart from the email check above.
The gaffer console
Questions you ask, and screenshots you attach, are sent to our AI model provider (Ollama) to write the answer, together with the public FPL data of the team you opened. They are not stored by us after the answer is sent.
Where it runs
The site is hosted on Vercel, with a Postgres database and a Redis cache for FPL data. FPL data comes from the public Fantasy Premier League game.
Your choices
Clear the cookies and local storage to remove everything kept in your browser. To have Pro records deleted, or for any question about your data: use the help link on your Paddle receipt, or paddle.net.