Cookie Policy
What cookies this site uses, why each one exists and how to say no. The honest version: we run five functional cookies and nothing that follows you around the internet.
Applies to jetpackracinghub.com and all Jetpack Racing Hub services.
What Cookies Are
Cookies are small text files a site stores in your browser to remember things between visits. They can't run code, can't read other files and can't see what you do on other sites — despite their reputation, they're a fairly boring technology.
Local storage works the same way; where this policy says 'cookies' it covers both.
The Cookies We Set
The complete list — genuinely all of it:
- jr-cookies — remembers whether you accepted or declined this banner (functional, 12 months).
- session — keeps forms and preferences working during your visit (functional, session).
- region — remembers your league region so ladders load correctly (functional, 6 months).
- theme — your display preferences (functional, 12 months).
- analytics_id — anonymous aggregate visit counter, only if you accept (analytics, 12 months).
What We Deliberately Don't Use
No advertising cookies, no social-media pixels, no cross-site tracking, no fingerprinting. The portal is funded by services listed on the pricing page — not by an ad network.
Our quarterly audit verifies the list above is still complete; if a new cookie ever earns its place, this page updates before it ships.
Managing Cookies
The banner's Decline button blocks every non-essential cookie — the site works fully without them. You can also clear cookies any time through your browser settings; the banner will simply ask again on your next visit.
Browser-level controls (Chrome, Safari, Firefox, Edge) let you block all cookies, allow per-site, or auto-clear on exit — useful habits well beyond this site.
On This Page
- What Cookies Are
- The Cookies We Set
- What We Deliberately Don't Use
- Managing Cookies
- Anonymous Analytics
Anonymous Analytics
If you accept, a single anonymous analytics cookie counts visits and page popularity — no identifiers, no session replay, no individual tracking. It answers 'how many people read the pricing page', never 'what did this person do'.
Decline and nothing analytics-related loads at all — the code isn't even fetched.
A cookie should help your session, not harvest your biography.
Third-Party Content
Embedded maps (Google) on the contacts page may set their own cookies under Google's policy — we can't control those, and the embed only loads when you visit that page. App store buttons are plain links and set nothing.
Updates to This Policy
Changes post here with a fresh date. Because the list is five items long, we'll personally notice and care if it ever grows — that's the advantage of a small cookie jar.
Questions About This Policy?
Cookie questions, audit requests or concerns about anything on this list. Reach the desk at [email protected] or +61 7 3221 5500 (Mon–Fri, 9:00–18:00 AEST), or visit us at 175 Eagle St, Brisbane City QLD 4000. You can also use the contact form.