Cookie Policy
Last updated: October 9, 2026
Release pause: audience analytics cannot currently be enabled and new first-party audience events are not collected. Historical identifiers and records may remain until expiry or withdrawal. References below to analytics opt-in describe the retained feature, not an available choice during the pause. Affiliate permission remains separate; advertising remains disabled.
What this policy covers
This policy explains cookies, local storage, SDKs, pixels, and similar technologies used by RaceDayCountdown.com and its mobile app. It should be read with our Privacy Policy. It is a practical product disclosure, not a guarantee of legal compliance in every location.
Categories
| Category | Examples and purpose | Duration / provider |
|---|---|---|
| Essential | Authentication, security, routing, session and preference state needed to provide requested features. | Session or as documented in the browser/app storage; RaceDayCountdown, Clerk, hosting/API providers. |
| Preferences | Theme, calendar view, followed-series and similar choices. | Until removed or changed; browser local storage or account preferences. |
| Analytics | Optional first-party audience events, only after an explicit choice in Settings or the invitation. | Guest identifier/events up to 30 days; account raw events up to 90 days; RaceDayCountdown. |
| Advertising | Currently disabled. Google AdSense will not load through these controls. Any future ad mode requires a reviewed consent-management implementation. | No advertising activation in the current release. |
| Affiliate travel | Only after your separate travel permission, outbound Expedia links may pass through Partnerize with referral parameters. Partners can receive IP/browser information and use cookies or similar technologies after navigation. | Partner-controlled durations, not independently verified for our campaigns. We do not control or delete partner cookies. |
| Oedro/CJ accessories | A separate, default-off Oedro/CJ permission is required before opening these referral links. CJ and Oedro may receive referral, IP and browser/device data and use cookies after navigation. No CJ scripts, pixels, remote tracking images or preconnects load with our pages. Travel permission does not enable Oedro. | The essential device-local preference rcal_oedro_cj_consent_v1 lasts until changed or removed. Partner-cookie durations are not independently verified. Withdrawal prevents new openings here but cannot remove partner cookies or undo an earlier visit. |
Your choices
Optional analytics and affiliate links stay off worldwide until you enable each separately. A travel-card choice enables only travel links, not Oedro/CJ, analytics or ads, and declining does not block the calendar. Oedro/CJ has its own allow, reject and withdrawal controls in website Privacy settings and mobile Settings. Advertising is unavailable. When the browser exposes Global Privacy Control (GPC), affiliate activation and advertising remain blocked; first-party analytics remains a separate choice. Native apps cannot read an external browser’s GPC signal. This permission is not Apple tracking permission or confirmation of native-app promotional rights.
Privacy-choice storage remembers your decision; browser settings that block storage may prevent it being saved. Analytics withdrawal deletes raw analytics for that subject. Withdrawing affiliate permission prevents future activation here but cannot undo a completed outbound visit or remove a partner’s cookies. Browser controls can delete existing cookies and local storage, but may sign you out or reset preferences. We do not promise an untracked travel alternative, or that a link without a referral identifier is free of tracking.
Updates and contact
We may update this policy when technologies or requirements change. For access, deletion, correction, objection, portability, or a question about a technology, use our contact page and identify the account or device involved where safe to do so.