Defensive Pedal
Privacy Policy
Last updated: 6 May 2026
Who we are
Defensive Pedal is operated by Victor Rotariu, sole proprietor, based in Brașov, Romania. For privacy and data-subject requests, contact privacy@defensivepedal.com.
What we collect
- Account data: email address, display name, profile photo (optional).
- Ride data: planned routes, GPS breadcrumb trail, distance, duration, elevation gain, route mode, and derived metrics like CO₂ savings.
- Community content you create: hazard reports, ride shares, comments, reactions, and votes.
- Crash diagnostics (on by default; legitimate-interest basis under GDPR Art 6(1)(f) for service-stability — opt out anytime in Profile → Privacy & analytics): app version, device model, OS version, anonymised stack traces. No location, no personal data.
- Product analytics (on by default; opt out anytime in Profile → Privacy & analytics): anonymous usage events that help us prioritise the roadmap. No GPS tracking, no location data.
Why we collect it
Routing, navigation, and safety guidance are the core service. Trip history, badges, and the leaderboard depend on stored ride data. Crash reports help us fix defects faster. We do not sell your data and we do not use it for advertising.
How long we keep it
- Account and profile: while your account is active.
- Ride summaries (distance, duration, CO₂, route mode): while your account is active.
- Raw GPS breadcrumb trails: 90 days, then automatically truncated. You can opt to keep them longer in Profile → Account.
- Hazard reports: 45 days past their expiry, then deleted.
- Inactive accounts: deleted after 24 months without sign-in. We send a warning email at 23 months.
Automatic ride logging
With automatic ride logging on, Defensive Pedal can record a ride you did not start in the app. It is on by default, but your phone's operating system asks you to allow background location and motion access, and nothing is recorded until you have granted both.
What is collected
- Cycling detection: your phone's own activity classifier (Android Activity Recognition or iOS Motion & Fitness) decides on your device whether you are cycling. Defensive Pedal receives only the cycling start and stop events. It does not receive raw motion or accelerometer data.
- Location: GPS points, collected only while a ride is being recorded. GPS switches on when cycling starts and off when the ride ends. A ride ends after 3 minutes without cycling, so stopping at a traffic light does not split one trip into two.
- The ride itself: distance, duration, start and end times and the GPS trail, stored the same way as a ride you start in the app. The ride is labelled “Auto-detected” in History.
What is not collected
- No location while you are walking, running, driving, on public transport or sitting still. Nothing is recorded between rides.
- Trips that do not look like cycling are dropped and not saved. A trip must cover at least 500 m and last at least 2 minutes, with a median speed between 6 and 45 km/h.
- Nothing is recorded while you are following a route you started in the app. That ride is recorded as an in-app ride.
Consent and withdrawal
Automatic ride logging starts only after you tap the button in the disclosure shown to you and grant the operating-system permissions. That tap is our record of your consent, and we store it with a timestamp. The legal basis for this processing is your consent (GDPR Art 6(1)(a)). Access to your phone's sensors is covered by the rules on device access in ePrivacy (Art 5(3)), and we rely on the same consent for that.
You can turn the feature off at any time in Profile. Turning it off stops all motion and location sensing immediately and clears the consent timestamp. You can withdraw consent at any time, and this does not affect processing that happened before you withdrew. Turning it back on shows the disclosure again before sensing restarts.
Community feed
- An auto-detected ride is not shown on the community feed straight away. It is published after 12 hours, or as soon as you keep it.
- The first and last 200 m of the route are hidden on the feed by default. Start and destination text is not shown. You can choose to show the full route for an individual ride.
- A ride too short to trim safely is not posted to the feed at all.
Discarding a ride and retention
You can discard an auto-detected ride from History. Discarding removes its GPS trail, its feed post and its share, and reverses the XP, impact and leaderboard credit it earned. Badges you have already unlocked are kept. Auto-detected rides are kept for the same period as rides you start in the app (see “How long we keep it” above).
When a ride ends we show a notification on your device. Your phone may also show its usual location indicator while a ride is recorded. This feature adds no new sub-processor. Ride data is stored in the same services listed above.
Your rights under GDPR
You have the right to access your data, correct it, request deletion, object to specific processing, and receive a portable copy of the data you have provided to us in a commonly used machine-readable format (Article 20). See how to delete your account for the in-app and email-based deletion paths and what gets removed. For data export or other rights, contact privacy@defensivepedal.com — we respond within 30 days.
Sub-processors and third-party services
The app and its backend rely on the following providers to deliver the service. Each receives only the minimum data needed for its function.
- Supabase — database, anonymous and email-based authentication. Currently US region; we plan to migrate to EU.
- Google Cloud Run — API hosting, EU region (europe-central2 / Warsaw).
- Mapbox — map tiles, geocoding, terrain elevation, and the standard cycling routing engine. The Mapbox SDK's own anonymous-usage telemetry is disabled in our builds.
- OpenStreetMap (OSRM & Overpass) — our custom safety-scored routing server (osrm.defensivepedal.com, self-hosted on Google Cloud) and the Overpass API for bicycle parking, rental, and bike-shop locations. Receives the GPS coordinates needed to compute the request.
- Open-Meteo — weather and air-quality data shown in the route preview and 9 a.m. weather notification. Receives the GPS coordinates of the location being queried.
- Google OAuth — used only when you choose “Sign in with Google”. Google sees your email and display name as part of the identity exchange.
- Expo Push Service (exp.host) — relays push notifications (hazard alerts, weather warnings, streak nudges) to your device. Receives the push token and notification payload.
- Google Play Install Referrer — Android system service that tells us which install campaign brought you to the app. No PII is collected.
- Sentry — anonymised crash reports, EU region. On by default under a legitimate-interest legal basis (GDPR Art 6(1)(f)) since crash diagnostics are essential to keep the routing service safe and stable. You can object and disable it anytime in Profile → Privacy & analytics.
- PostHog — anonymised product analytics, EU host (eu.i.posthog.com). On by default; disable anytime in Profile → Privacy & analytics and transmission stops immediately. An explicit off choice is never overridden.
- Firebase App Distribution — used for tester preview builds only (not production). Firebase Analytics is not shipped in our builds.
Contact
Privacy and data-subject requests: privacy@defensivepedal.com
For Romanian users, ANSPDCP (the data protection authority) is the competent supervisory authority: dataprotection.ro.