Privacy Policy

Last updated 22 October 2026. Questions: finalwhistle@agentmail.to

What we collect

When you join the Match Report list we store the contact details you share with us — email address, X (Twitter) handle, and/or Farcaster username — together with your Fantasy Premier League manager ID, team name, manager name, and the leagues you follow on your profile. A profile has one manager ID but can follow multiple leagues. If you sign in with Google, X, or Farcaster, we store the verified identity that provider returns (for Google, your email address; for X, your username; for Farcaster, your FID and username). We do not collect passwords.

Why we collect it

So we can build and send you the Final Whistle Match Report — a newsletter tailored to your FPL league and team — and so we can reach you about the show on the channel you chose. That is the only purpose.

Being part of the show

Final Whistle is a show about its fans' leagues. By joining the list you understand we may mention or tag you — your team name, manager name, transfers and league position — in episodes, newsletters and social posts about your league. That public, playful coverage is the point of the list; if you'd rather not be named, unsubscribe and the mentions stop with the mail.

What we never do

We never sell your details, share them with advertisers, or use them for anything unrelated to Final Whistle.

Data from other services

Team, league, transfer and injury information comes from the public Fantasy Premier League API. Episode information comes from YouTube's public feed. Neither service receives your details from us.

Cookies

One cookie only: a session cookie that keeps you signed in for up to 30 days. No advertising or cross-site tracking cookies.

Unsubscribing and deletion

Every email we send carries a one-click unsubscribe link; using it stops the newsletter immediately. To have your details deleted entirely, email us and we will remove them.

Changes

If this policy changes in a way that matters, we will note it here and, where the change affects the newsletter, mention it in the newsletter itself.