PaddockTracker
Legal

Cookie Policy

Last updated: 2026-05-21

This Cookie Policy explains what cookies and similar local-storage technologies Paddock Tracker uses, why they are used, and how you can control them.

For a broader explanation of how we handle your personal data, see the Privacy Policy.

What are cookies?

Cookies are small text files placed on your device when you visit a website. Similar technologies — such as localStorage and sessionStorage — store data in your browser without sending it back automatically. We treat both under the same consent framework.

Categories we use

Category Consent required Description
Strictly necessary No Required for the Site to work: authentication, security, your preferences.
Functional Implicit (essential to features you turn on) Things you opt into, like push notifications.
Analytics Yes Aggregate usage measurement (Google Analytics). Disabled by default.
Marketing Yes Advertising via Google AdSense. Disabled by default.

Cookies and storage we set or allow

Strictly necessary

Name Owner Purpose Duration
__cf_bm, _cfuvid Cloudflare (via Clerk) Bot mitigation on auth requests Session / 1 year
__client, __client_uat, __session_*, __refresh_*, __clerk_db_jwt_*, clerk_active_context Clerk Authentication session Up to 1 year
paddock:consent (localStorage) Paddock Tracker Your cookie-consent choice Until you clear it
paddock:followed-series, paddock:theme, and similar (localStorage) Paddock Tracker Your in-app preferences Until you clear them

Functional

Name Owner Purpose Duration
Push subscription record (Vercel KV) Paddock Tracker Sending race notifications when you've enabled them Until you disable notifications

Analytics (only after you grant consent)

Name Owner Purpose Duration
_ga, _ga_DDMJ2NMBWC Google Analytics Pseudonymous usage measurement Up to 24 months

Marketing (only after you grant consent)

Name Owner Purpose Duration
__gads, __gpi, IDE (and others set by Google ad servers) Google AdSense Ad delivery and frequency capping Up to 24 months

Third-party cookies set by Clerk on .clerk.com

Clerk uses its own product analytics (Segment, PostHog) and an ad-conversion identifier when you sign in. These cookies (ajs_anonymous_id, ajs_user_id, _gcl_au, ph_phc_*) are set on clerk.com, not on paddock-tracker.com, and are governed by Clerk's own privacy policy. We mention them here for transparency.

How to control them

The consent modal

On your first visit, Paddock Tracker shows a consent modal with four categories: Necessary, Analytics, Advertising, and Functional. Necessary is always on (the site can't work without it). The other three are off by default — nothing non-essential runs until you opt in.

Three options are presented with equal prominence: Accept all, Reject all, or Customize (per-category toggles). Whatever you choose is applied immediately via Google Consent Mode v2: the analytics and advertising scripts still load on the page, but they suppress cookies and fall back to cookieless pings unless you have granted consent. Rejecting leaves the site fully usable.

Changing your mind later

The Manage cookies link in the footer re-opens the consent modal at any time. Your update is applied immediately site-wide. We also re-prompt automatically after 12 months so your decision stays current.

Browser controls

You can also block or delete cookies from your browser settings. This may break authentication and stop us from remembering your preferences.

Consent record

Your consent decision is stored locally in your browser under the paddock:consent key (in localStorage) along with the date you made it. We do not maintain a server-side log of consent — clearing your browser storage will simply prompt you again on your next visit.

Changes to this policy

The list above will change as we add or remove services. The "Last updated" date reflects the most recent change. Material changes are noted in the release notes.

Contact

pparaskevas.dev@gmail.com