RACERZ

Consumer Health Data Privacy Policy

Version 1.2 — Effective 2 September 2026

1. Scope

This policy applies to residents of Washington, Nevada, and other US states with consumer-health-data laws, and supplements our Privacy Policy. It describes how RACERZ (Bred Applications, CVR 45915905, Denmark) handles consumer health data.

2. Consumer Health Data We Collect

3. Sources

Directly from you; from your device's sensors during runs you start; and derived by our servers from the above.

4. Why We Collect It

Solely to provide the service you request: run tracking, opponent simulation, fair matchmaking, anti-cheat validation, display of the resulting race simulations to other users, and your own statistics. We collect no consumer health data beyond what these features need.

5. Sharing

Consumer health data is shared only with processors under contract: Supabase (storage, in the European Union) and Google/Firebase (push delivery). RevenueCat (subscriptions) and GitHub (static content) receive no health data. When you race in ranked mode, a derived fitness summary (VDOT score, fatigue profile, recent maximum distance) is shared with your opponent's device solely to simulate your performance — never your health inputs or identity beyond username.

We do not sell consumer health data, and we do not share it for advertising. Product analytics (TelemetryDeck, anonymised, EU-hosted) never receives health data, run data or anything that could be linked to you — see the Privacy Policy.

6. Your Rights

Requests and questions: contact@bredapplications.com. If we refuse a request, you may appeal by replying to our decision; if the appeal fails, you may contact your state Attorney General.

7. Changes and Contact

Material changes are announced with 30 days notice via in-app notification. Contact: contact@bredapplications.com.