DIRTY RIDE / PRIVACY
Your ride.
Your information.
What this beta records
The application can store your account identifier, Google profile details if you sign in, playback progress, session timestamps, optional reports that you rode along, and emails submitted to a ride’s interest list. Playback does not verify physical exercise.
Using the site without an account
You can explore public content without signing in. Playing a video may create an anonymous session cookie and save progress in this browser’s local storage. Device records may disappear when you clear browser data. If account services are unavailable, progress may remain only on this device.
Language preference
When you explicitly choose a language in the site’s selector, a functional cookie named dirtyride-locale remembers your choice for one year. You can remove it through your browser’s site-data settings.
Optional site analytics
Only after you allow analytics, we measure visits to the landing page and ride pages, campaign codes, external referrer hostname, language, broad screen-size category, section views, scroll depth, CTA clicks, form steps and active viewing time. Random browser identifiers last up to 30 days; sessions expire after 30 minutes of inactivity or 24 hours. Your analytics choice is remembered for one year. We do not record typed values, email addresses, full referring URLs, IP addresses or session replay in analytics events, and do not use fingerprinting. Hosting providers may keep separate operational logs.
Analytics controls and retention
Use Analytics preferences in the footer to decline or withdraw optional measurement. Global Privacy Control and Do Not Track signals disable it. Withdrawal clears local analytics identifiers and stops future collection; requests already dispatched and previous server records are not automatically deleted. Analytics records are retained for approximately 90 days. Older analytics records become eligible for cleanup during new ingestion, with a separate maintenance command available; immediate deletion on day 90 is not guaranteed. If you allow analytics and submit an interest form, the server associates that new interest with the visit to measure conversion. Interest-list consent remains separate.
Optional Google sign-in
When enabled, Google sign-in uses basic identity information to create your account. It does not request access to your Gmail, contacts or Drive. The current anonymous server session can be linked to your account after sign-in. Offline device records are not automatically uploaded.
Interest lists
Submitting an email with the consent box checked records your interest in that specific ride. This beta does not promise a release date or an automated email notification.
Service providers
The deployed service requires hosting and database providers. Google participates only when you choose its sign-in option. Video hosting may receive playback requests. The final operator must identify the actual production providers and their retention practices before launch.
Controls and contact
You can stop local playback tracking by leaving the player and remove device records through your browser’s site-data settings. This does not delete server records. A verified contact and process for account access, deletion and consent withdrawal must be published before the public beta accepts users.