Privacy Policy

This site is a static blog hosted on Cloudflare Pages. It can be used fully anonymously — accounts are optional and exist only to enable features like favoriting teams. Visitors who don’t sign in are not tracked.

Last updated: 7 May 2026.

What’s collected from anonymous visitors

Nothing site-side. No analytics, no cookies, no JavaScript tracking. No personal information is collected, stored, or processed by this site for visitors who don’t sign in.

Standard web server information (such as IP addresses) appears in Cloudflare’s infrastructure logs as part of normal request processing. I do not have access to individual visitor data. See Cloudflare’s privacy policy.

jsDelivr (cdn.jsdelivr.net) serves one client-side library (hyparquet) used to read data files in your browser. They receive standard request metadata (IP, user-agent) like any CDN.

What’s collected if you sign in (optional)

Signing in is only useful if you want to favorite teams, comment, or otherwise persist preferences across visits. If you sign in, the following is stored:

By Clerk, our authentication provider:

  • Your email address (provided by Google or GitHub via OAuth)
  • Your name and profile picture (provided by Google or GitHub)
  • A Clerk-issued user ID linking your account
  • Session cookies needed to keep you signed in (strictly necessary; no consent banner under GDPR)
  • Sign-in event metadata (timestamps, IP, user-agent) for security purposes

Clerk is a US-based service. Their privacy policy: clerk.com/legal/privacy.

By this site, in a Cloudflare D1 database stored in the Oceania region:

  • Your Clerk user ID (linking identifier — not your email)
  • A copy of your email and display name, synced from Clerk on sign-up so the site can address you by name
  • Your account creation date
  • Your favorited teams (sport + team identifier)

Nothing else.

Sign-in providers

Clicking “Sign in with Google” or “Sign in with GitHub” triggers a standard OAuth flow. Google or GitHub will share your email address and basic profile info (name, picture) with Clerk. Neither provider is told anything about which pages of inthegame.blog you’ve visited. The only signal they receive is that you authenticated.

If you’d rather not sign in with Google or GitHub, simply don’t — every page of the site works without an account.

Cookies

  • Anonymous browsing: zero cookies set by this site.
  • Signed in: Clerk sets a session cookie. This is strictly necessary for authentication. No advertising, analytics, or tracking cookies are set.

Your rights and controls

  • View your data: the My Teams page shows your favorites; your name and email are visible in your profile menu.
  • Delete your account: profile menu → Delete account removes your data from this site (favorites, profile copy) and triggers Clerk to delete the underlying account. If the in-app option is unavailable, email me and I’ll process the deletion within 7 days.
  • Export your data: email me; I’ll send a JSON export of everything stored about you. (A self-service export endpoint is planned but not yet built.)
  • GDPR / Australian Privacy Principles: these rights are honored regardless of where you live.

Third-party data

Sports data displayed on the site is fetched from third-party APIs at page load time (AFL, Squiggle, football-data.org, Opta). These requests go through a Cloudflare Worker proxy, not directly from your browser to the data providers. Anonymous request metadata reaches them; nothing about your account does.

Social meta tags

The site includes Open Graph and Twitter Card meta tags so that links display nicely when shared. These tags do not track visitors.

Changes

If anything material about data collection changes, I’ll update this page and bump the date at the top. Account holders may also receive a one-off email if a change affects them.

Contact

Questions or data requests? Find me on GitHub or email the address linked from my GitHub profile.