Cookies & browser storage

What the beta currently uses

Wadmin uses browser storage and cookies needed to provide the signed-in service. The current application dependencies do not include a marketing analytics SDK, advertising pixel or behavioural-tracking SDK.

Authentication and security

Supabase authentication uses session information to sign users in, maintain an authenticated session and protect access to club workspaces. This storage is used for the service and security functions requested by a signed-in user rather than for advertising.

Signing out clears or invalidates the current authenticated session as supported by the authentication service. The exact cookie/storage names, expiry periods and refresh behaviour will be recorded from the production build before wider launch rather than guessed in this notice.

Preferences

Parts of the workspace may use browser storage to remember functional choices such as a selected season or view. Clearing site data may reset those choices and can also sign you out.

External competition pages

Some areas can link to or embed official competition/provider pages. Those services may set their own cookies or use their own browser storage under their own policies. Where an embedded third party would set non-essential storage before a user chooses it, that integration needs a separate consent review before wider production use.

Non-essential tracking

The beta does not intentionally add advertising or marketing analytics tracking. If non-essential analytics, advertising or behavioural tracking is introduced later, it must be reviewed before activation and an appropriate consent mechanism and updated information must be provided where required.

Your browser controls

You can delete or block cookies and site storage using your browser settings. Blocking storage that is required for authentication or security may prevent the signed-in service from working correctly.