Cookie Policy

This policy covers cookies and similar browser storage used on www.fpl-analyzer.com. A cookie is a small value stored by the browser and sent with matching web requests. localStorage and sessionStorage stay in the browser and are treated here as similar storage technologies.

Your choice. Essential browser storage supports requested app features and records your privacy choice. Optional analytics — Google Analytics and PostHog, including PostHog session replay — remain off unless you select Allow all. “Reject all” is equally prominent and does not prevent sign-in or core features. Session replay has its own switch in Cookie Settings, so you can allow analytics while refusing to be recorded.

Open Cookie Settings

1. First-party cookies

Name	Category and purpose	Set when	Duration
`fpl_analyzer_consent`	Essential. Stores either `essential` or `analytics` so the site can remember and enforce your choice.	When you make or update the choice.	365 days, unless you delete it or replace the choice sooner.
`_ga`	Optional analytics. Google Analytics uses a random client identifier to distinguish visitors.	Only after “Allow all.”	Google's default is up to 2 years, subject to browser limits and earlier deletion.
`_ga_<measurement-id>`	Optional analytics. Persists Google Analytics session state.	Only after “Allow all.”	Google's default is up to 2 years, subject to browser limits and earlier deletion.
`ph_phc_<project-token>_posthog`	Optional analytics. PostHog stores a random visitor and session identifier, used for product analytics and to tie a session replay recording to a session.	Only after “Allow all.”	PostHog's default is up to 1 year, subject to browser limits and earlier deletion.
`fpl_analyzer_replay`	Essential. Stores either `on` or `off` so the site can remember and enforce whether you allow session replay.	Always, once you make a choice.	1 year.

Older FPL Analyzer releases created fpl_total_visits, fpl_user_timezone, fpl_last_active, fpl_pref_formation, fpl_squad_count, and fpl_star_player. The current release no longer creates them and attempts to delete existing copies when the app loads.

2. Google Sign-In storage

Session replay

If you select “Allow all”, PostHog records a replay of your visit: the pages you open, clicks, scrolling, mouse movement, and the content of the page as it was rendered to you. It is a reconstruction assembled from those events, not a video or camera recording, and it does not capture your screen outside this site. We use it to see where the app is confusing or broken.

Text you type into inputs, and password fields, are masked by PostHog's default recording settings and are not collected. Recording never starts unless you have accepted analytics.

Turning it off. Open Cookie Settings and switch off PostHog product analytics & session replay. Recording stops immediately in the page you are on, and no recording is started on later visits. Your choice is stored in the essential fpl_analyzer_replay cookie. Choosing “Reject all” also switches it off, along with all other optional analytics.

The Google Identity Services library is available to support the optional “Sign in with Google” flow. Google may access or set authentication, fraud-prevention, preference, or security storage in connection with that library and the sign-in flow. Names and durations are controlled by Google and can change independently of FPL Analyzer. This storage supports the sign-in you request; it is not FPL Analyzer analytics consent.

3. localStorage and sessionStorage

The app uses browser-local storage rather than cookies for much of its functionality. Depending on which features you use, it can include:

This feature storage is not used to start Google Analytics. Some locally stored information is sent only when needed for a feature—for example, an FPL ID used to fetch a team, chat context sent to the AI endpoint, or a local sign-in token sent to authenticate a community request.

4. What optional analytics collects

After opt-in, the Google tag for measurement ID G-CJY927LHXT can collect page views, interactions, session statistics, approximate location, and browser/device information. The implementation grants analytics storage but explicitly denies ad storage, ad user data, and ad personalisation; it also disables Google signals and advertising-personalisation signals and requests ad-data redaction. FPL Analyzer does not intentionally send names, email addresses, prompts, or FPL manager IDs to Google Analytics.

5. Change or withdraw your choice