Last updated: September 2026
This policy explains how Footy League uses cookies and similar browser technologies on footyleague.app. It supplements our Privacy Policy.
Your choice
Strictly necessary storage is always active. Analytics, advertising and conversion tracking, error reporting, and embedded media remain off until you allow the relevant category. You can reject optional technologies as easily as accepting them and change your choice at any time through Cookie settings in the footer.
When this policy version changes materially, we ask you again. Withdrawing advertising consent stops new browser and server advertising events, removes stored advertising attribution, and clears known first-party marketing cookies where the browser permits it.
Strictly necessary storage
Supabase Auth uses browser storage for secure account sessions. We also store your cookie choice, interface preferences, selected signup plan, and short-lived checkout state. Blocking essential storage can prevent login or cause the banner to reappear.
Optional analytics
If you allow analytics, Google Analytics measures page visits and acquisition interactions on approved Footy League apex pages. The Google tag is not requested before consent and does not run on tenant league subdomains.
Typical Google Analytics cookies include _ga and _gid. We configure single-page navigation explicitly and do not send form values, email addresses, passwords, or league names as event parameters.
Optional advertising and conversion tracking
If you allow advertising and conversion tracking, approved acquisition pages may load:
- Google Ads tags;
- Meta Pixel;
- TikTok Pixel; and
- LinkedIn Insight Tag.
These technologies measure page visits and actions such as selecting a plan, beginning or completing signup, creating a league, starting Checkout, and completing payment. They may set or read identifiers such as Google click IDs, _gcl_au, Meta _fbp/_fbc, TikTok _ttp, and LinkedIn first-party advertising identifiers.
For completed signup, league creation, Checkout, and successful subscription invoices, Footy League may also send the same consented conversion through the provider's server API. Browser and server copies share an event or transaction ID so providers can deduplicate them. Successful subscription renewals are server-only because no browser page is normally open.
Server events may include the action, time, plan, payment value/currency, Stripe invoice transaction ID, consented advertising click identifiers, and a normalized SHA-256 hash of the account email. We do not send the raw email, password, form contents, phone number, league name, IP address, or browser user agent in these server payloads.
Advertising attribution identifiers held by Footy League expire after 90 days. Provider retention is governed by the settings and terms of the respective advertising account.
Optional error reporting
If you allow error reporting, Sentry may receive crash and performance diagnostics needed to identify faults. Sentry remains unloaded when this category is off.
Optional embedded media
YouTube media loads only after embedded-media consent or an explicit Allow and load action.
Where tracking does not run
Footy League advertising tags do not run on tenant league subdomains, the platform-admin console, league admin/manager/referee areas, or ordinary account and billing-management pages. The minimal payment-confirmation page may deliver the consented purchase event without displaying billing details.
Managing browser storage
Use Cookie settings in the footer to change your choice. You can also remove site data through your browser settings. Removing all storage signs you out and resets your preferences.