Privacy Policy

01Data we collect

• Account— your email address. With Google sign-in we also receive your Google account identifier and basic profile (name and profile photo). With Sign in with Apple we receive your Apple user identifier, your name (only on your first sign-in) and your email — if you choose Apple's "Hide My Email", we receive and store the private relay address Apple generates and never attempt to uncover your real one. If you sign up with email and password, the password is stored only as a salted hash — we can never read it.
• Profile — display name, profile photo, rider type and riding preferences such as alert thresholds, lean-warning settings and your unit system.
• Garage — the motorcycles you add: brand, model, year, nickname, colour, tank range and, if you choose to enter them, the licence plate and a photo of your bike. A bike photo you attach is uploaded to our storage and shown in your garage and, like the rest of your garage, to friends you have accepted.
• Saved places — places you save, such as home or work, including their label, address and map coordinates.
• Ride & route data — planned and saved routes, and your ride history including the full recorded GPS track, distance, duration, average and top speed, and fun score.
• Riding telemetry— aggregated cornering events from your phone's motion sensors: maximum lean angle, lateral g-force, warning level, time and location. See section 07 for how this works on-device.
• Hazard reports — the hazard type and location you report to warn other riders; reports expire automatically after about 6 hours.
• Ride posts & recaps— the captions you write and the ride cards and recap videos we render from your stored ride, and whether you share them to your friends' feed.
• Social connections — the friends and riders you follow, requests you send or accept, and your standing on distance leaderboards.
• Messages — in-ride group chat and one-to-one direct messages you send to other riders.
• Presence— whether you're online and, while you ride, which group ride you're on — so friends can see you're riding and ask to join.
• Device tokens — push-notification identifiers for your device.
• Device details — when you sign in, the app reports the phone model, OS version and app version it is running on, so we can reproduce the bugs you hit and know which builds are in use. No serial number, advertising ID or phone number.
• Subscription status — your plan and entitlement, provided by RevenueCat and Apple/Google. We never see your card number or full payment details.
• App feedback — if you rate the app under Profile → Help us improve, we store your rating, the area you chose, anything you write, and the app version, platform, device model and OS version you were on, linked to your account so we can follow up. Leaving feedback is entirely optional.
• Website forms — if you use the contact form, join the launch list, apply for the beta or report a bug on this website, we store what you submit (such as your email, name and message, and for a bug report the device details and any screenshot or video you attach) together with your IP address and browser user-agent to prevent abuse.

02Location data

Location is core to Zavoy, so we treat it with extra care. We collect it only for the purposes below.

• Continuous GPS during navigation and free-roam — to draw your position, give turn-by-turn guidance and re-route.
• Background location during active rides — so navigation and ride recording keep working when your screen is off or another app is open. It runs only while a ride is active, and on Android a persistent notification shows whenever Zavoy is recording your ride.
• Ride history — completed rides, including the GPS track, are stored to your account so you can revisit them; you can delete them anytime.
• Cornering telemetry — lean-angle events are tagged with the location where they happened, so you can review them on the map after a ride.
• Service providers — route and location coordinates are shared with the mapping, weather and AI providers listed in section 04, strictly to provide those functions (directions, forecasts, route analysis).

03AI processing

To generate route analysis, trip suggestions and the plain-language ride summary, we send route context to third-party AI services: Google (Gemini) and, as a fallback, Anthropic (Claude).

• What is sent— start, end and stop place names and coordinates, a sampled version of the route geometry, your food, amenity and point-of-interest preferences, fuel range, your current location when you ask for nearby suggestions, and any free-text trip prompt you type. We don't send your account email or your messages.
• Search grounding — Gemini requests may use Google Search grounding, meaning the route and place context can be included in web-search queries to improve suggestions.
• Third parties— processing happens on the providers' infrastructure under their API terms; these API calls are not used to train their models.
• Retention— the generated insights are saved with your route so you don't pay to regenerate them; we don't otherwise retain the prompt context.

04Third-party processors

We rely on these named providers to run the service. Each receives only the data needed for its function.

• Mapbox — maps, tiles, directions, elevation profiles and static route images; receives route and viewport coordinates.
• HERE — place search; receives your search text and approximate location.
• OpenStreetMap (Nominatim & Overpass) — geocoding fallback and fuel-station / road-surface data along a route; receives search text and route-corridor coordinates.
• CARTO — offline map tiles; receives the map-region tile coordinates you download.
• Google (Gemini) & Anthropic (Claude) — AI route analysis and trip suggestions; receive the route and place context described in section 03.
• OpenWeather — forecasts and route weather alerts; receives coordinates.
• Google Sign-In — authentication; we verify your Google ID token, which carries your email, name and photo.
• Sign in with Apple— authentication on iOS; we verify your Apple identity token, which carries your Apple user identifier and email (or Apple's private relay address if you hide it). Your name is shared only on first sign-in.
• RevenueCat, Apple App Store & Google Play — subscription billing; receive an app user id and purchase/receipt data. Payment details stay with Apple/Google.
• Expo — push-notification delivery and over-the-air app updates; receives your push token and standard device/update metadata.
• Firebase Cloud Messaging (FCM) & Apple Push (APNs) — push-notification delivery; receive your device token.
• Cloudflare — storage of the ride images and recap videos we render for you.
• Render — hosts our backend; account and ride data are processed on its infrastructure.
• Spotify (iOS, optional)— if you connect Spotify for the in-ride media controls, sign-in and playback control happen through Spotify's own app and SDK; what you're playing stays on your device and is never sent to us.
• Plausible Analytics — cookie-free visit statistics for this website (zavoy.io); receives the pages you view, the referrer, browser and device type, and your country (derived from your IP address, which is not stored). No cookies, no persistent identifier, no cross-site profile; data is processed and stored in the EU.

The app contains no analytics, advertising or crash-reporting SDKs, and we never sell your data. This website uses cookie-free, aggregate-only visit statistics — see section 08.

05Your GDPR rights

If you're in the EU/EEA (and many other regions grant the same), you can:

• Access — request a copy of the data we hold about you.
• Rectification — correct inaccurate details (most are editable in-app).
• Erasure — delete your account and data — see Delete your account & data.
• Portability — receive your routes in a portable format (GPX export covers route data).
• Objection — object to a particular processing activity.

To exercise any of these, email [email protected] — or, for erasure, use the request form on Delete your account & data. You also have the right to complain to your local data-protection authority.

06Data retention

• Account, profile, garage, saved places, routes, ride history, posts and social connections — kept while your account is active; permanently deleted within 30 days of account deletion.
• Chat messages, direct messages, notifications and cornering telemetry — automatically deleted after 6 months, even if you keep your account.
• Live group-ride locations — deleted within 24 hours of the ride.
• Hazard reports — expire after about 6 hours.
• Place-search caches — kept between 24 hours and 30 days to avoid repeating identical lookups.
• Payment records — retained where law requires (typically up to 7 years).
• Operational logs & backups — short-lived server logs may contain request data and rotate automatically; backups are rotated out within the normal backup cycle after deletion.

07Device permissions we use

The app requests these device permissions only to power specific features. Several work entirely on your device and send nothing to us.

• Location — turn-by-turn navigation and ride recording, including in the background while a ride is active (covered in detail above).
• Motion & fitness sensors — raw accelerometer and gyroscope readings are processed live on your phone to estimate lean angle and cornering forces, and are never uploaded. What we store are aggregated cornering events — maximum lean angle, g-force, warning level, time and location — attached to your ride and deleted automatically after 6 months. You can turn lean tracking off in settings.
• Notifications — to deliver ride invites, messages and hazard alerts (see device tokens above).
• Phone status (Android) — we detect when a call is ringing or active so navigation can stay on screen. We do not read your phone number, contacts or call log, and nothing about your calls leaves your device.
• Display over other apps (Android) — lets the turn-by-turn overlay stay on top of the incoming-call screen. It grants no access to any data.
• Media— to show and control what's currently playing from the ride HUD. On Android this uses notification access to read only the active track's metadata; on iOS it works only with Spotify through its official SDK. We never access your library or listening history, and nothing about your listening leaves your device.
• Storage / files — to download and keep offline map tiles on your device for areas with no signal.
• Photos / media library — to save your ride posts and recap videos to your device gallery, and to let you pick a photo of your bike for your garage. We only add the media you choose to save and only receive the photos you explicitly pick through the system photo picker — we never browse or scan your library. A bike photo you attach is uploaded to our storage so it can be shown in your garage; you can replace or remove it at any time, which deletes the stored copy.
• Bluetooth (camera pairing)— if you choose to pair an action camera (currently GoPro), Zavoy uses Bluetooth Low Energy to connect to it and exchange camera control commands only — the device identifier needed to keep the pairing, and status signals such as whether it's recording and its battery level. We never access, collect or store footage, photos or any media from the camera, and the pairing stays on your phone — nothing about your camera is sent to us. You can unpair it at any time in Camera settings, which stops all Bluetooth communication with it.

You can review or revoke any of these at any time in your device settings; features that rely on them simply stop working until you re-grant them.

08Cookies & analytics

The app contains no analytics or tracking SDKs. This website uses Plausible Analytics, a privacy-first tool, to count visits in aggregate — pages viewed, referrers, countries and device types. Plausible sets no cookies, stores no IP addresses and builds no visitor profile — nothing identifies you personally and there is no cross-site tracking, which is why this site shows no cookie banner. Measurement data is processed and stored in the EU.

09Children

Zavoy is not directed at children under 16 and we do not knowingly collect their data.

10Contact

Privacy questions and rights requests: [email protected]. Zavoy is operated from Serbia (EU data-protection standards applied).