Privacy & Cookies

Last updated: 2025-09-20 ← Back

Summary

We use only the minimum data and browser storage needed to run the Leaderboard and keep you signed in. We do not use advertising cookies and we do not run third-party analytics that track you across sites. If that ever changes, we’ll ask for your consent first.

What we store on our servers

When you create an account or enter scores, we store:

Passwords are stored using a strong one-way hash. Admins can reset a password to a temporary value but can’t view your existing password.

Cookies & Local Storage

We set only necessary cookies for login and security, plus a few local preferences saved in your browser (localStorage). These are listed below.

Name / Key Type Purpose Expiry
PHPSESSID Cookie (necessary) Keeps you signed in and ties your requests to a secure session. Session (deleted when you close the browser)
__cf_bm, _cfuvid Cookie (necessary, Cloudflare) Security/bot protection and performance. Set by Cloudflare to keep the site fast and reliable. Short-lived (managed by Cloudflare)
hh_hide_scored LocalStorage Remembers the “Hide filled holes” scorecard setting. Until you clear browser storage

LocalStorage isn’t a cookie, but it’s still browser storage on your device. We mention it here for transparency.

Why there’s no cookie banner

Under UK PECR and UK GDPR, consent is not required for strictly necessary cookies used to provide the service you request (e.g., logging in, security). Since we only use necessary cookies and local preferences, we don’t show a consent banner.

If we add optional analytics or marketing cookies in the future, we’ll display a consent banner and only enable those after you opt in.

Your choices & controls

Storage inspector (on this device)

This shows what your browser currently stores for this site. This view isn’t sent to the server.

Loading…

Contact

If you have any questions about privacy or cookies, please contact the site admin at admin@leaderboard-golf.co.uk.

Future analytics (optional, not enabled)

We don’t run analytics right now. If we enable privacy-friendly analytics later, we’ll add a consent prompt here and only load analytics after you opt in.