Privacy Policy

Last updated: 21 October 2026

MileVoy was formerly called WeRide. Only the name has changed. Our old website, werideapp.in, and our email addresses at werideapp.in still reach us.

1. What we collect

MileVoy collects two kinds of data. The first is what the App needs to work, to keep your account secure and to be fixed when something breaks: it is collected from every rider, and you accept it when you sign up. The second, which features of the App you use, is optional: it is on unless you switch it off, the same for every rider wherever they are, and you can change it at any time.

1.1 What we need to run the service, from every rider

We collect this because we cannot give you the service without it: to provide what you signed up for, and, where it keeps the App secure and working, because it is necessary for that. It is never sold and never given to advertisers. Some of it is also used to choose which of MileVoy's own offers and news reach you (section 2).

What you give us

• Account: Your name, and the email address, phone number or Google account you sign in with, plus a profile photo if you add one or sign in with Google. If you change your email address, we keep the earlier addresses on your account (the last twenty), for support and so that a Google sign-in still finds your account; they are never shown to other riders. The App signs you in with Google, with Apple or with a one-time code, and does not use passwords. If a password was set on your account in an earlier version of the App, we keep only a one-way scrambled copy of it, until you close your account
• Sign-in and verification codes: When you sign in with your email address, we email you a six-digit code. When you sign in with your mobile number, or verify it, we send the code by WhatsApp, through Meta's WhatsApp Business Platform, which receives your number and the code; if WhatsApp cannot reach you, the code goes to your account's verified email address instead, and that email shows only the last digits of the number. To verify or change your email address, we email a code to it. A code works for ten minutes. A code sent to sign in by email is kept as it was sent, only to check it, and deleted about an hour after it stops working; every other code is kept only as a one-way scrambled copy. When a code goes to your mobile number, the number is kept encrypted with it. We keep whether your email address and your mobile number have been verified, how and when. A new email address gets its own code, and your old address, if it was verified, is told of the change. If another account later proves the same mobile number, the number is taken off yours
• Profile: Nickname, phone number, address, country and state, and gender (male or female), all optional, and for Race mode a race number and color. You can also choose whether your groups see when you are online and when you were last online. Country, state and gender are never shown to other riders; we use them to understand where our riders are and who rides with us. If your profile says you are a woman, you can switch on the Women riders cards: only then is your gender used to award them, counting rides with other riders who have switched them on too. You can switch them off at any time
• Your answers: When you accepted our Terms and this Privacy Policy and which versions, and your choices for Share Usage Data and Offers and News, each with when you made it (the last twenty changes)
• Your settings: Kilometers or miles, and the way your phone writes numbers (from its language setting), kept on your account so your cards and notifications read your way
• Vehicles: Make, model, year, registration, fuel type and odometer, a photo of the vehicle, the icon you pick for it on the map, fuel fill-ups you log (amount, cost, odometer and the station), service reminders you set, and any vehicle documents you upload, all optional. When you pick from our list of models, its published details (engine size, power and so on) are filled in for you. A make or model you add that is not on the list may, once we have checked it, be added to the list other riders choose from; they are not told who added it
• Emergency card and contacts: Blood group, allergies, conditions, medication, health insurance provider and policy number, your doctor and their phone number, anything else a responder should know, and your license and ID documents. Your emergency contacts: up to ten people, each with a name, a phone number and how they are related to you; the first is the person to call first. All optional
• Home and Work: If you set them (under Home & Work on the You tab, or the first time you tap Head Home), the two places you call Home and Work. They are used only to route you home. They are kept encrypted on your phone and on our server, where only you read them back, and your group is told only that you are heading home, never where. All optional
• Where your ride finishes: On a group ride, where your own ride ends: Home, Work, a place you choose or a pin you drop, or that you will decide later. It is kept encrypted and only you read it back. Your group sees only that you are heading home or heading to your own finish, never where, and the ride's organizers see only whether you have set one. While you share your position on the ride, it is checked against your finish: when you come within 150 m of it, the App asks whether you have arrived: End Ride, Stay Here or Ride Back Later (later today or tomorrow, which keeps your ride open until the end of that day). If you do not answer, your ride stays open; it never ends by itself when you arrive
• Messages and media: Messages, photos, videos, voice notes, files, polls and locations you share in groups or in private chats
• Photos and notes on your rides: If you add them, up to 20 photos, a star rating from 1 to 5, a note and up to 30 road remarks (Great Road, Road Warning or Note) on a ride, a race session, a rally stage or an Endurance tour. A photo comes from your camera or from your phone's own photo picker, which gives the App only the photo you pick. Before it leaves your phone it is made smaller and saved again as a new picture with no camera details, place or time inside it, and our server removes any such details again before keeping it. A photo is placed on your ride by the time it was taken, never by the place stored in it, and you can move it. Each photo and each remark, and your note and rating together, has its own setting for who sees it: Only Me (the start for everything), My Group (the riders of the same group ride, only on a group ride) or Everyone (your ride page and the pictures you share). Photos are stored in Cloudflare R2, in a folder named by a code that does not show your account
• Ride answers: On a group's planned ride, your I'm In or Not This Time, the meeting point you choose to join at, and whether Got Home Safe is on for you
• Groups: The groups you create or join, your role in each, and the trips, routes, stops, itinerary and expenses you add for a group ride. A group can plan several trips ahead, each with its own name, kind, date and places; the trips it has ridden, or whose date went by, stay in its Trip History, and a deleted trip can be brought back for 30 days
• Who invited you to MileVoy: If you joined through another rider's invite link or card, the account that invited you, when you joined, and when your mobile number or email was verified, so the invite can be counted. Every rider has a random invite code (not related to their name or account number) that is added to the invite links they share. It is included in Export My Data and deleted when you close your account; if the rider who invited you closes theirs, their link to you is removed
• Feedback: Bug reports, feature requests and screenshots you send us, with your name, email address and your phone's details. A screenshot is sent only if you attach it, and any mark you draw on it is part of the picture. Each one is also emailed to our own support inbox (Gmail) so that we see it
• Problem reports (diagnostics): When the App hits an error or closes because of a crash, or when you report a problem, it sends what is needed to fix it: your name on MileVoy, the screen and riding mode you were in, the App version, your phone's make and model (its model number and the name it is sold under, for example "Samsung Galaxy Note10+ (SM-N975F)" or "iPhone 15 Pro"), its Android or iOS version and system build number and, on Android, its security patch level, your language and the screen's orientation, which permissions are on (including whether the App may send an SOS text), whether location services are on, GPS accuracy (not your position), battery level and charging, the phone's memory and the App's memory use, which App features are switched on, whether an SOS, a tour or crash detection was running, the random code made when the App was installed, and the last steps the App took, such as which feature it opened. The other screens you visited and the buttons you tapped before the problem are included only if Share Usage Data is on. Message text, contacts' numbers and positions are never included, nor your phone's IMEI, serial number, MAC address or kernel version. Reports made with no signal wait on your phone and are sent later. When the App closed because of a crash or stopped responding, the next time it opens it also sends the technical record your phone's system kept of it (Android's crash and "not responding" records, Apple's MetricKit diagnostics): which part of the App's code was running, the App's memory use, and nothing of yours. The App also counts its network requests that failed, by address and error, without their content
• App sessions: Each time the App opens, comes back to the screen or goes to the background, it tells our server. It sends a random code for that session, a random code made once when the App was installed, the App's version and build, whether the phone is Android or iPhone, and your account if you are signed in. This is how we know how often a version of the App crashes or stops responding, and how many riders use the App each day. It is sent whether or not Share Usage Data is on
• Ride diagnostics: While a ride is recorded, the App keeps a short log of how the phone and the App behaved, so that problems on group rides can be found and fixed: when the connection to MileVoy dropped and came back, how many positions were sent or could not be sent each minute (never the positions themselves), GPS accuracy and gaps, battery level and charging, power saver, the network type, the screen turning on and off, whether notifications are allowed and the App could register for them, navigation starting, stopping and rerouting with the destination's name, ride stage changes, and SOS and crash alarm events, whether location is allowed, when the App went to the background and came back, which MileVoy server it was connected to, and what it heard about the other riders on the ride (their names, and when they joined, paused or dropped out). It is kept with your name and the group. It is sent when the ride ends, or the next time the App opens
• Phone performance on rides (diagnostics): While a ride is on, and only then, the App notes once a minute how hard it is working your phone: the battery level and whether it is charging, the battery's temperature and health and its charge cycles where your phone reports them, the phone's temperature status (how hot the phone says it is running, when that changed, and how close it is to slowing itself down to cool), the processor load (how much of the processor the App uses) and how much memory it uses, whether the phone warned the App it was short of memory, how many screen frames were slow or dropped, whether the screen is on and how bright it is, whether the App is on screen or in the background, and how many GPS fixes arrived (a count, never a position). Your phone also notes the speed band of each minute (stopped, town, road or fast), so that heat, processor load and battery use at speed can be told apart; the speed band stays on your phone and only the totals for the ride are sent. When the ride ends, your phone works out a short summary from these, such as the battery used per hour with charging time left out, the hottest temperature, the time spent at each heat level and when it changed, the highest and average processor load, and for each speed band the minutes spent in it with the processor load, temperature and battery use in that band, and sends it with the minute-by-minute figures, your phone's make and model, its system version and the App's version: a few kilobytes a ride. It is linked to your account and to the random code made when the App was installed, and to nothing else: no position, no message or other content, and no other identifier. Nothing is recorded outside rides. We use it only to find and fix battery drain, overheating and slowness on particular phones and system versions. Like problem reports, it is part of the App's diagnostics and is always on
• Phone and App performance (diagnostics): Once a day at most, the App sends a short record about the phone it runs on: its memory size; on Android, how much storage is free; the screen's size and sharpness and the text size you have chosen; your language and time zone; whether the permissions the App relies on are allowed (precise or approximate location, location in the background, location services, notifications, and Motion & Fitness on iPhone), which the App only reads and never asks for in doing so; whether power saver or Low Power Mode is on; the kind of network (Wi-Fi, 4G, 5G or none, never its name, address or carrier); and how long the App took to start each time it was opened from cold. On iPhone it also sends the daily performance figures Apple's MetricKit gives the App: how long it took to start and to resume, how long it froze, how much processor and graphics time it used, how long it ran in front and in the background, how long it used GPS at each accuracy, how much data it sent and received over Wi-Fi and the mobile network, its memory and storage writes, how smoothly it scrolled, how it was closed (by the system or normally, as counts), the signal strength in bars, and how bright the screen was. On a ride, the phone performance figures above also note the kind of network each minute and whether power saver was on. All of it is numbers about the phone and the App, linked to your account and to the random code made when the App was installed, and to nothing else: no position, no message or other content, no advertising identifier, no hardware number such as the IMEI, serial number or network address, no list of your other apps, no contacts, nothing from other apps, and nothing you type or copy. Like problem reports, it is part of the App's diagnostics and is always on
• Reports and blocks: When you report something (a message, a place shared in chat, a rider, a group, a trip suggestion, or a photo, note or road remark on a ride), your report (the reason and any note) and a copy of what you reported, with the name of the rider who posted it. The riders you block
• Permanent bans: If we ban a rider permanently for breaking our Terms, we keep each email address, phone number, Apple ID and Google ID their account used, only as a one-way scrambled copy made with a secret key of ours, with the banned account's number and the report it came from, so that none of them can sign in or make a new account. They are removed if the ban is lifted

What the App records as you ride

• Location while riding: Your GPS position while you are sharing it with a group on a ride, and while you are recording a ride, tour, race session or rally stage. On a group trip of several days that you have chosen to record, the App records your position from the first day to the last whenever you are moving, including between the days' rides, and stops keeping positions once you have been still for ten minutes; the notification shows while it records. With each position the App also sends how accurate it is, the speed your phone's GPS reports, your battery level, your arrival estimate and whether the phone reported it as coming from a mock-location app. On Android a ride keeps recording, and your group keeps seeing you, if you swipe the App away mid-ride, until the ride ends; the notification shows while it does. On iPhone that happens only if you switch on Keep Recording If MileVoy Is Closed (You > Privacy), which asks for "Always" location. If you stop and do not answer Still Riding?, your ride rests: the App stops recording and sharing your position, your group sees you as resting at your last spot, and the App checks your position only now and then, so that it records again by itself when you ride on. A ride with no movement for 24 hours is closed where you stopped. Sharing can be paused or switched off per group at any time. Apart from that, the App does not record your position when you are not riding with it: background location is used only during rides
• Ride data: Distance, time, speed, route, which of your vehicles you rode, the weather where a group ride or Race session started and, in Race mode, lean angle. Our server checks the speeds your phone reports against the distance and time between your positions, and keeps the top speed your phone reported beside the checked one
• Hazard reports: When you report a hazard or a closed road to your group, its type, its position, how accurate your phone's GPS said that position was, any note you add, and your name. It is shown on the maps of that group's riders, including in Endurance and Rally, and a closed road on a rider's route makes their navigation go round it
• Safety data: Accelerometer and gyroscope readings for crash detection and lean angle, only while those features are running (on an Endurance tour the App also uses them to tell whether the vehicle leaned through corners, and sends only how many corners it counted and how many were leaned, which keeps a train or bus journey from earning a country card); each SOS you raise; and each crash alarm the phone raises, with the sensor readings around it and whether you said it was a real crash, which is how the detector is tuned. A hard knock that does not become an alarm (for example because you rode on) is also sent, with the phone's model, so that false alarms and missed crashes can be told apart. When an SOS is sent, a crash alarm goes off or a hard knock is sent during a ride, we keep your phone's motion, speed and location readings from 30 seconds before to 30 seconds after, and your answer to "What happened?", to make crash detection more accurate. A practice SOS keeps nothing. When you switch crash detection off or on, for every ride or for one riding mode, the App notes the change on your phone and sends it (on or off, which mode, and when), whether or not Share Usage Data is on, so that we know whether crash detection was watching when it mattered
• Battery: Your phone's battery level, shared with your group during a ride, and with Race Control and your Pit Crew during a Race session. On a group ride, when your phone first drops to 15%, and again at 5%, the ride's crew (the Lead, co-leads, Sweeps and Marshals, and the group's creator and managers) is told once, never while you have an SOS open; we keep which of those alerts went out on that ride
• Ride roles: On a group ride, whether you led, swept or marshaled, and, when the Lead's position goes quiet for five minutes while others ride on, which rider stood in as lead and when. The group is told who is leading for now
• Who you rode with: After a group ride, our server works out, from the positions each rider shared, who rode with you and when: each other rider's first name and their positions only at the moments you were within 500 m of them, after their privacy zones and their own start and finish are cut out. It is kept with your ride so it is not worked out again, and your App keeps a copy to tell the story of your ride in Ride Stats and your ride video. You can switch Show Me in Who Rode With You off (You > Privacy); other riders then get nothing of yours for it, and your own Who Rode With You is hidden too
• Your country: When you sign up, and once for an account made before we did this, we work out the country you use the App from: from your phone number's country code, or if there is none, from the country of the network you connect from (as our hosting provider reports it with each request; we do not keep your IP address for this), or else from the region your phone is set to. If a more reliable one of these later says another country, we update it, and your starting units with it unless you chose them yourself; a country you picked yourself is never changed. We keep the country and which of these it came from, and use it to set your starting units (kilometers or miles, and degrees Celsius or Fahrenheit), which you can change at any time in the You tab, and for our own counts of where riders are. It shows on your profile as your country, where you can change or clear it, and is never shown to other riders
• Your region: We work out your country and state from the last position the App recorded for you, and prefer it over a country we only guessed. We keep only the country and state, not the position itself, and use them only for our own counts of where riders are
• Where your rides happen: From the positions already recorded for your rides, tours, race sessions and rally stages, we work out the country (and state) each one happened in: where it started, or for a tour the countries it rode through. It is never shown to other riders and adds nothing to what is recorded

What keeps the App working and secure

• Sign-ins: Phone make and model, Android or iOS version, app version and a device identifier (on Android the ID the system gives the App, on iPhone Apple's identifier for apps from one developer), used to recognize your signed-in devices, and the IP address each sign-in came from, kept with that sign-in for security. The model, system and app version of each sign-in are brought up to date each time you open the App, so the list of your signed-in devices stays right. The same device identifier also counts toward the daily limit on verification codes that can be asked for from one phone, and ties the one free trial of a paid mode to the phone, so that it cannot be taken again with a new account. It is never used for advertising or to follow you across other apps, and we do not collect your phone's advertising ID
• Device check (Android): When you sign in, the App may ask Google Play Integrity whether it is the genuine MileVoy app from Google Play, running on a genuine device. Google sends back a verdict (for example, whether the device passes Google's integrity check and whether Play recognizes the app), which we keep with that sign-in, and the latest one on your account, to spot tampered copies of the App. It is recorded only: it does not stop you signing in or riding. It is not asked on iPhone
• App version with each request: The App tells our server its version, build and platform (Android or iOS), the system version and your phone's language setting (for example en-IN) with each request, so we know which build a problem comes from, when a rider was last active and on which days they opened the App (the date, with the App version and platform, for counting active riders), and can write numbers your way. A version too old to sign in securely is refused at sign-in, with a message to update
• Whether the App is still installed: The delivery results of our notifications tell us whether MileVoy is still on each of your phones. If you have not opened the App for three days, our server may send your phone a silent notification that shows nothing and makes no sound, only to get that result. For this we keep the result and when it came, alongside a one-way scrambled copy of the notification token rather than the token itself
• Your phone, kept current: Make and model, Android or iOS version, app version and build, your language, time zone and the region your phone is set to, your distance units and the size class of your screen. Sent each time the App starts and at most once a day while it is open, so we can find problems that only happen on some phones or some versions
• How the App performs on a ride: Once per ride, a summary of how your phone held up: battery level and whether it was charging, battery used per hour, whether low-power mode was on, the App's memory use, how many GPS fixes a second your phone delivered and how accurate they were, and the speed band of the ride (stopped, town, road or fast). The phone's temperature status is included where the phone reports it. No extra position is collected for this
• Crash and error reports: When something goes wrong in the App, what went wrong, where in the App it happened, the app version and the phone and system it happened on
• Counts per country: From the country each ride happened in, we count how many riders in each country use each riding mode and how far they ride. These are totals only, never about one rider

1.1a What a ride records

While a ride records in any mode (a Race session, a rally stage, an Endurance day, a group ride or a group-trip day), the App keeps a record of that ride. It powers Ride Stats, your ride sheet and cards, and your exports. It is part of the mode, not usage data, so it is kept even if you switch off Share Usage Data.

• The ride itself: moving and total time, distance, top speed, climb, descent and highest point (from GPS and, where the phone has one, the barometer), heading, and the weather during the ride
• How you rode: a summary worked out on your phone from its motion sensors (accelerometer and gyroscope): corners and lean, braking and acceleration, wheelies, road roughness, smoothness. Only the summary leaves the phone
• Race sessions only: the full motion stream (100 readings a second) is uploaded too, so laps, corners and braking points can be analyzed. It is about 2 to 5 MB an hour
• Safety and the road: posted speed limits and any time over them, stretches with no signal, and links to any crash alarm, SOS, fuel or expense logged during the ride. Speed limits are looked up from OpenStreetMap (Overpass) by position, with no identity sent
• Your phone during the ride: battery level every minute, the phone's make and model, its Android or iOS version, system build number and (on Android) security patch level, and the app version
• Heart rate (only if you switch it on): under You > Privacy > Heart Rate · Health Connect (on iPhone, Heart Rate · Apple Health), off unless you turn it on; before your phone asks for access, the App says what it will read and why, and nothing is read unless you tap Continue. The App then reads heart-rate samples from the health store on your phone (Health Connect on Android, Apple Health on iPhone), where your watch or chest strap saves them, every ten seconds while a ride records and the screen is on. It shows the latest reading on the ride dashboard, keeps the ride's series on your phone for Ride Stats and your ride sheet, and in Endurance may suggest once that a longer break might help when your heart rate at breaks is higher than earlier in the day. It is not a medical reading. Only the ride's average, highest and lowest heart rate, with how many readings there were and the times of the first and last, are sent with the ride record; the readings themselves never leave your phone, no heart-rate data is shared with other riders or with anyone unless you share a ride card that shows it, and it is never used for advertising or sold. The App never writes to the health store. Switching it off stops the reading at once and asks nothing of the store again
• After the ride: when you open Ride Stats, our server works out the roads, twistiness, climbs, regions, landmarks and toll plazas of the route from map data (our own map tiles, OpenStreetMap and public elevation services, sent map areas or points only)

Only you can read your ride records. They are deleted with the ride, or when you close your account, and they are included in Export My Data.

Insights and Wrapped: your records, streaks, the next card you are close to, and your year or month in story cards are worked out on your phone from the rides, tours and cards the App already has. Nothing new is collected for them, and the pictures are made on your phone and leave it only if you share them. They name no place inside your privacy zones or at a ride's own two ends.

Privacy zones: you can mark up to 10 places, such as home, under You > Privacy > Privacy Zones. Each hides a 250 m circle. They are stored encrypted, and every ride you share (maps, videos, cards, files and your ride page) leaves out the roads inside them. Every ride you share also leaves out 250 m round its own first and last point, so a ride that starts or ends at your door does not show it; race sessions and rally stages, which start and end at a track or a rally's own controls, are not cut at their ends. A photo or road remark pinned inside any of these circles is never shown to anyone but you. While you are inside a zone, your group sees only that you are on the way and how far, not your position. The people who run MileVoy see how many zones you have and their names, never where they are.

1.2 Which features you use (usage data)

When you create an account, the App asks you to accept our Terms and this Privacy Policy. On the same screen it tells you that MileVoy uses data about which features you use to improve the App, that you can turn this off at any time in You > Privacy, and that crash reports and diagnostics are always sent. Using which features you use is on unless you switch it off, the same for every rider wherever they are. If you switched it off, or chose not to share in an earlier version of the App, that choice stays. Your rides and safety features work the same either way.

• Features and modes: Which features and riding modes you use, for example Race, Rally, Endurance and group rides
• Screens and buttons: Which screens you open and which buttons you tap, with the group or tour they belong to and figures such as a speed or a count where a feature has one; never a position, a message or your heart rate
• Rides, start to end: When a Race session, a rally stage, a tour day or a group ride starts and ends, with its distance, length and number of riders and stops
• Notifications you open: Which kinds of notification you open (for example a ride starting or a chat message), with the notification's own id and the time. Never what it said or who it was from. On our side we count how many of each kind were sent and delivered, as daily totals with no names
• Sign-up progress: How far you get through signing up and starting out: the welcome screen, starting sign-up, the code sent and entered, your profile, your first group and your first ride, each with the time (no names, numbers, messages or places). Before your account exists these steps are kept under a random number made for this installation of the App; when you sign in they are joined to your account. In the EU, the EEA and the UK nothing is sent before you accept the Terms and Privacy Policy, and if you switch usage data off, none is sent or joined

To turn it on or off: in the App, open the You tab, open Privacy and use the Share Usage Data switch. Off takes effect straight away and nothing more of this kind is sent. What was sent before is kept until you close your account; to have it deleted sooner, write to us.

All of the data in section 1 goes to our own server only. No third-party analytics service is used, and none of it is sold or shared. We do not collect an advertising identifier, your phone's hardware numbers (such as its IMEI, serial number or network address), your phone's contacts list (emergency contacts are only the ones you type in), the other apps on your phone or their data, what you type or copy, or any location beyond what your rides already record.

1.3 What we get from others

• Google Sign-In: Name, email address and profile picture, if you sign in with Google
• Sign in with Apple: On iPhone, if you sign in with Apple: an identifier Apple gives MileVoy for you, the email address you choose to share (which may be a private relay address that forwards to your own), and your name if you choose to share it. We also keep, encrypted, the token Apple gives us for your sign-in, only so that we can revoke it with Apple when you close your account. When you close an account you sign in to with Apple on an iPhone, Apple asks you once more, and we use that answer to revoke MileVoy's access to your Apple ID
• Push notifications: A push token from Firebase Cloud Messaging on Android, or from the Apple Push Notification service on iPhone, so the App can notify you, kept with whether the phone is Android or iPhone so each notification is sent the right way. Our server sends notifications through Expo's push service, which passes them on to Google or Apple
• Calls on iPhone: A separate call token from Apple (VoIP push), so a MileVoy call can ring your iPhone like a phone call even when the App is closed. It is kept with the sign-in it came from and removed when you sign out. When someone calls you, our server sends Apple the call's details (who is calling, the call type and the group) to ring your phone

2. Why we collect it

• To show your position to your group, navigate you to the rally point and warn the leaders when someone falls behind
• To end your own ride at your own finish, tell your group you are heading home, and, if Got Home Safe is on, tell your group's chat that you got home safe (never where)
• To help a ride's organizers get the group ready: who has answered I'm In or Not This Time, who has chosen a meeting point and who has set a finish (only whether, never where), and to send each rider still missing one a reminder when an organizer taps Remind All (at most once every 30 minutes for each list), and one reminder the evening before a ride to riders who have not answered
• To tell a ride's crew when a rider's phone battery runs low, who is still coming to a stop and how far away they are, and who is leading when the Lead goes quiet
• To show the photos, note, rating and road remarks you add to a ride to the people you chose, and to show your ride page to anyone you give its link
• To keep a group's planned trips and its Trip History
• To show your groups the hazards and closed roads their riders report, and to route you round a road reported closed
• To record your rides and show your history, recaps, achievements and leaderboard place
• To carry group and private chat, voice notes and calls
• To raise an SOS to your group and to message your emergency contacts, when you ask for one or a crash is detected, and on a rally stage to ask your emergency contacts to check on you when you have stopped and do not answer
• To let a group's leaders read your emergency card in an emergency, if you have chosen to share it
• To track and split group expenses
• To send you notifications about your groups, messages and rides
• To send you MileVoy's own offers and news (new features, Pro offers and events), as a notification, a card when you open the App, or a banner. They are on by default, and the App says so when it asks to send you notifications. To choose which ones reach you, we use your country and state (from your profile, or worked out from your rides), the town in your address, the kinds of vehicle in your garage, which riding modes you have used, when you joined and were last active, your App version and your time zone, and we hold them back while you ride. We do not use which features you use (section 1.2) or any device identifier for this. Turn them off at any time in the App under You, Notifications, Offers and News, or in your phone's notification settings for MileVoy (on Android, the Offers and News category). If you turn them off we keep that choice and when you made it, and send you no more. They never reach you during a ride or navigation, never between 21:00 and 08:00 in your own time zone, and at most two offer notifications a week and one card a day. Ride alerts such as SOS, group rides and calls are separate, on their own notification categories, and never carry offers. A rare notice about the service itself, such as an update you must install, is not an offer and can reach every rider, at most two in 30 days
• To keep your signed-in devices list accurate and your account secure, and to prove that an email address or mobile number on an account belongs to its rider
• To prevent fraud and abuse: your phone's device identifier limits how many verification codes one phone can ask for in a day, and lets each phone have the free trial of a paid mode only once
• To know how many riders still have the App, and to stop sending notifications to phones it has been removed from
• To find and fix crashes and errors, and faults that only happen on some phones, systems or versions, and to make the App lighter on battery and steadier on GPS, from the phone details, ride summaries, phone performance on rides, phone and App performance and crash reports in section 1.1
• Unless you switch off Share Usage Data: to see which features and modes riders use and where they give up, so we can improve them
• To count, per country, how many riders use each riding mode. These are totals only, never about one rider
• To answer your feedback and bug reports
• To review reports of abusive or objectionable content within 24 hours, remove what breaks our Terms and suspend the riders who posted it, and ban permanently the riders whose abuse is serious or repeated. Removing a report's content can also take a rider's chosen name, nickname and picture, or a group's name, description and icon, off MileVoy
• To hide the riders you block from you, and you from them: their messages, private messages, places they share, polls and pinned messages, in chat and in chat search; their photos, notes and remarks on rides; and their place in who rode with you and in the Riders sheet. Calls between you are refused both ways
• To keep abusive words out of what other riders read: an automatic filter masks a list of slurs and obscenities in messages, names, captions, notes, remarks, trip and group details and the other words riders type for others to see

3. Who sees it

• Your group: Members of a group you join see your name, nickname, photo, location, speed, battery level, ride status, the hazards you report and the messages you send there. They also see your I'm In or Not This Time and the meeting point you chose, whether you are heading home or to your own finish (never where), and, if Got Home Safe is on, a line in the group's chat when your ride ends at your finish
• Leaders, tails and organizers: Can fetch your emergency card, emergency contacts, phone number, documents and vehicles in an emergency, unless you have switched that sharing off. Every fetch is announced in the group chat and logged, and the log keeps a copy of what was read until you close your account. Before a ride, the group's organizers see who has not answered, not chosen a meeting point or not set a finish (only whether, never where). During a ride, the crew is told when your battery drops to 15% and 5%, and sees how long you are from the next stop
• Riders you rode with: After a group ride, the riders who rode it can see, and download as a spreadsheet (the Riders sheet), the name each rider goes by with their distance, moving time, average and top speed, number of stops, when and in what order they reached the group's destination (or that they did not), and whether they led, swept, marshaled or stood in as lead for a while. It never includes a position. Riders who have left or been removed from the group, and riders you have blocked or who have blocked you, are left out; a stop or an arrival inside one of your privacy zones, and a stop at your ride's own start or finish, is not shown
• Who rode with you: Each other rider of the same group ride can get your first name and your positions only at the moments they were within 500 m of you, after your privacy zones and your own start and finish are cut out. Their App uses it for their Ride Stats and their ride video, which can show your first name and the part of the ride you rode together; if they share those, the people they share them with see it. Riders you have blocked, or who have blocked you, get nothing, and nobody gets anything if you switch Show Me in Who Rode With You off
• Riders at a known circuit: In a Race mode Track Day or Race at a circuit in our list, while your session is on, these people see your race number, race color, first name, lap times, position on the track and the gaps to the riders ahead of and behind you: the other MileVoy riders in a session at that circuit at the same time, whoever runs or watches Race Control there, and the Pit Crews of the riders there (the people each rider invited with a code), who can watch from anywhere. Never your profile or phone number. You leave the moment you end the session
• Riders on the same track: In a Race mode Track Day on a track that is not in our list, the other MileVoy riders lapping the same track at the same time, and their Pit Crews, see your race number, race color, first name, lap and position on the track while you lap there, and riders about to start there see your number, color, first name and lap. Never your profile or phone number. Your first completed lap there may draw the track's outline that they see; we keep that outline, the track's start point and when it was last lapped, with nothing that names you, and delete it once nobody has lapped there for an hour. You leave the moment you end the session or ride off the track. You are shown by default each session; switch off Show Me to Riders Here on the Race screen before you arm to be hidden for that session; you then see nobody either
• Photos and notes you add to a ride: Only you see them, unless you choose otherwise for each one. My Group shows it to the members of the group who rode the same group ride, in the App, with your name and picture. Everyone also puts it on your ride page and on the ride pictures you share. A pinned photo or remark inside your privacy zones, or near your ride's own start or finish, is not shown to anyone but you. Riders of your group can report what you show them there
• Anyone with your ride page link: If you tap Make a Link on a ride, anyone who opens milevoy.com/r/<link> sees the ride's kind and title (a group ride is named by the group's destination, never the group), your first name and the first letter of your last name, the ride's date and how long it took (never the time of day), its distance, moving time, average and top speed, climb and number of days, the route with your privacy zones and its own start and finish cut out, and only the photos, note, rating and road remarks you marked for Everyone, each placed only to within about 50 m. A group ride says how many rode, and nothing else about them. The link is a long random code and the page is kept out of search engines. Stop Sharing ends the link at once; an address for a photo that a visitor has already opened keeps working for up to two hours
• Removing a rider: A group's managers can take a rider off a ride or out of the group, and the host of an open-road ride or a shared rally stage can take a rider off it. In a race or a championship, Race Control can remove a rider, disqualify them for misconduct, or ban them from the rest of the championship, with a reason the rider is shown. The rider is told, and we keep a record of who removed, disqualified or banned whom, from what, when and why, and who let them back or lifted the ban, to settle disputes and deal with abuse
• Anyone with your live link: If you share your own live link (Share My ETA), anyone who opens it sees the group's name, meeting point, destination and schedule, and your first name or nickname, photo, precise position, battery level, arrival estimate, whether you have paused sharing and when you were last updated. Because you chose to share it, your privacy zones do not hide you on that link. It shows no other rider. The link stops working 30 minutes after your ride ends, after 24 hours, or when you end it, whichever comes first; once it has stopped, we keep no position on it
• Emergency contacts: When an SOS is raised, every emergency contact on your list is sent a message with your name, what happened and a link to your live position. On Android, if you allow the App to send SMS, the text goes from your own phone and SIM without a tap (your usual SMS charges apply); otherwise your messages app opens with it ready to send. MileVoy may also send it by WhatsApp from MileVoy's own business number, through Meta's WhatsApp Business service, which then receives your contacts' numbers and the message. A position is sent only when the phone has a fresh, precise fix; until then the message says the location is being confirmed, and every position sent states how accurate it is and when it was taken. The live-position link works only while the SOS is active and for at most 24 hours, and shows nothing afterwards. For each message sent by WhatsApp, we keep with the SOS the contact's place on your list, the last four digits of their number (never the whole number) and the times Meta reports it was sent, delivered, read or failed, so that we can tell whether the alert reached them. This is in your copy of your data and is deleted with the SOS when you close your account. MileVoy does not tell your contacts when you add them, so please let them know; they hear from MileVoy only in an SOS and in a rally check-on (below). Each WhatsApp message names you and says it was sent because they are your emergency contact, and they can write to us at [email protected]
• Emergency contacts on a rally stage (check-on): On a rally stage, if you have not moved for two hours and do not answer the App's three alerts, your emergency contacts are sent a message asking them to check on you, with your first name and your last known location and when it was taken: by WhatsApp from MileVoy's own business number, through Meta, or, if that cannot be sent, as a text from your own phone, as an SOS text is sent. It is labeled a check-on, not an SOS, and your group is not alerted. Moving on or answering the App stops it. We keep with it when it started, your last position, and for each WhatsApp message the last four digits of the contact's number (never the whole number), whether it was sent and when. This is in your copy of your data and is deleted when you close your account
• Leaderboards: Your first name and distance ridden can appear on the public leaderboard on this website, and on its boards by engine size and by riding style your nickname (or name), profile photo, machine and distance; the names of groups and how many riders they have can appear too. Your nickname, distance and vehicle class appear on the boards in the App
• Service providers: MongoDB Atlas (database), Cloudflare R2 (file storage, including the photos you add to rides, our nightly backups and our long-term archive), Railway (hosting), Google Firebase (sign-in and notifications), Expo (delivering notifications to Google and Apple, and app updates), Resend (emails with sign-in and verification codes, and our own emails about reports), Meta's WhatsApp Business Platform (sign-in and verification codes, and SOS messages to your emergency contacts) and Google's Gmail (our support inbox, which receives the feedback, bug reports and reports of content you send, with a copy of what you reported, and from which we answer you and send a sign-in or verification code when Resend cannot) hold or process data on our behalf. The routing and map services in section 9 receive the positions and routes they need to answer
• The people who run MileVoy: Can see the information we hold about your account on our admin dashboard, to support you, deal with reports and keep the service working. That includes your profile, your signed-in devices, your rides by date, mode, distance, country and the names of the places they started and ended, your emergency card and contacts, and whether your account is suspended or banned. Content that is reported to us, such as a ride photo, note or remark, is shown with the report. It does not show the text of your messages, the positions your rides recorded, your Home, Work or ride finishes, or your notification and sign-in tokens. It shows when you changed something on your account and which fields changed, but not the earlier text of your messages, emergency card, emergency contacts, privacy zones or Home and Work. Every look at and change made on the dashboard is recorded: who, what, when and about which account (section 5)
• The law: We may disclose information if required by law or a valid legal process

We do not sell your personal information. We do not share your data with advertisers. There are no advertisements from anyone else in the App; the only promotions are MileVoy's own offers and news (section 2).

4. Where it is kept and how it is protected

Your data is stored in MongoDB Atlas, on servers in Mumbai, India, which encrypts it at rest. Files and media are stored in Cloudflare R2. The server runs on Railway. We protect your data with:

• Encrypted connections between the App and the server (HTTPS and WSS)
• Field-level encryption on the server for sensitive fields such as your emergency card and emergency contacts (and the copy kept when a leader reads them), your phone number, your Home and Work, where your rides finish and the token from Sign in with Apple, and the earlier versions we keep of what you change (section 5)
• Your mobile number is kept encrypted on our server, on your account and with any code sent to it. So that we can find your account when you sign in with your number, we also keep a one-way scrambled copy of it, made with a secret key of ours; it never leaves our server
• Photos you add to rides saved again with no camera details, place or time inside them, on your phone and again on our server, and shown to others only by short-lived addresses
• A session token stored in your phone's secure keystore
• A copy of your own emergency card kept on your phone so it can be read with no signal. It is removed twelve hours after you last opened it, and when you sign out
• What the App keeps on your phone is left out of your phone's backups (your Google account's backup on Android; iCloud and computer backups on iPhone), and your sign-in never leaves the phone: after you delete and reinstall the App, or move to a new phone, you sign in again. The one exception is your display choices - such as light or dark mode, map style, chat appearance, voice guidance, invite card style and the screen tours you have already seen - and nothing else. They are kept in one small record of a few kilobytes so they come back when you reinstall: on Android in your own Google account's backup of the App, which you can switch off in your phone's settings; on iPhone in your phone's Keychain, which iOS keeps when an app is deleted and includes in an encrypted backup. We never receive that copy, and if it is not found the App simply starts with its default settings
• A copy of your emergency contacts' names and numbers kept on your phone, so an SOS text can reach them with no data signal. It is removed when you sign out
• What the App keeps on your phone (chats, group members, expenses, tours, and the copies of screens it shows at once while it fetches fresh ones: your groups, trips and trip plans, garage, cards and leaderboards) is kept in a database encrypted with a key that lives only in your phone's secure keystore (Android Keystore, or the iPhone Keychain). Sign-in tokens, passwords, codes and signed links are taken out of those copies before they are saved. Signing out or closing your account deletes the database and its key, with the card pictures and ride videos the App kept for you

The text and captions of messages are encrypted at rest on the server; poll questions and answers, file names and the notes the App writes in a chat are not, and photos, videos, voice notes and files are kept in Cloudflare R2 without our own extra encryption. Messages are not end-to-end encrypted.

5. How long we keep it

• Account data: Until you close your account. That includes your emergency card and contacts, your settings, your earlier email addresses and whether your email and mobile are verified
• Earlier versions of what you change: When you change your name, nickname, photo, mobile number, email address or other profile details, your emergency card or contacts, your garage, your privacy zones, your Home and Work or your notification settings, or edit or delete a message you sent, we keep what it was before, encrypted, with when it changed. Replaced profile and garage photos stay in storage too. This is kept while your account is open, is included in your copy of your data (section 6), and is deleted when you close your account. The words of a message set to disappear are never kept. When you delete a private conversation, its messages disappear from both phones but are kept, encrypted, with each sender's account, and deleted when that sender closes their account; to have them deleted sooner, write to us
• Changes to a group: Earlier versions of a group's name, icon and members' roles, and of its trip plans and trips, are kept with who made the change, for the life of the group, and deleted with it. If you close your account, a change you made stays without anything that leads back to you
• Deleted when you close your account: Everything that is yours alone.
  • Your rides, tours, race sessions and rally stages
  • Crash alarms, SOS raised during a ride, their sensor readings and your answers to "What happened?"
  • Your stops, and the country and state worked out for you
  • Your blocks, both ways
  • Your own rally routes and group cards
  • Your sign-ins, and failed sign-in and join attempts
  • Your own Pit Crew and pit board
  • Verification codes, your usage counts and your SOS records
  • Your rally check-ons, with what was kept of the messages to your emergency contacts
  • Your photos (from storage too), notes, ratings and road remarks on rides, and your ride page links
  • Your Home and Work, where your rides finish, and your Got Home Safe setting
  • Who you rode with on each ride, and your positions in other riders' copies of who rode with them
  • Your low-battery alerts and the times you stood in as lead
  • The offers and news sent to you
• Kept for other riders when you close your account: Only what they still need, with your name, picture and anything that leads back to you removed.
  • Hazards still live in groups that carry on
  • Race results and starts
  • An open-road ride you are hosting, until its code expires
  • The plans, trips, Trip History and expenses of groups that carry on, with your answers and suggestions in them no longer pointing to you
  • Makes and models you added to our list
  • Your read receipts and poll votes
  • Your messages in groups, shown as from a deleted rider
  • The notes the App wrote in the group chat about you (stops, arrival times, SOS, role changes and emergency card fetches), with your name taken out
• Sign-in and verification codes: A code works for ten minutes, and what we keep of it is deleted within a day
• Group messages and content: For the life of the group. If a group's creator or a manager sets disappearing messages (24 hours, 7 days or 30 days), each message sent after that is deleted, with its photo, video, voice note or file, that long after it was sent, on our server and on the phones that have it; earlier messages and the App's own notes in the chat are not affected
• When a group is deleted: Its creator can leave it, and it carries on under a manager or its longest-standing member, or choose Delete for Everyone. Every member is told, and the group is deleted 24 hours later unless a manager (or any member, in a group with no managers) keeps it or the creator cancels; never while its ride is on. Then its messages, photos, voice notes, files, icon, plans, trips, Trip History, ride recaps and live locations are deleted for everyone. Each rider keeps their own rides, cards and the photos and notes they added to their rides; anything they had shown to the group becomes theirs alone
• Trips: A group's planned trips stay until they are ridden, moved to its Trip History, or deleted; a deleted trip is kept for at least 30 days so it can be brought back, and deleted after that the next time the group's trips are opened. The Trip History goes with the group
• Ride history: Until you close your account. A tour, race session or rally stage can also be deleted on its own; a group ride cannot yet, and goes when you close your account
• Photos and notes on rides: Until you remove them, delete the tour, race session or rally stage they are on (its photos are deleted from storage too), or close your account
• Ride page links: Until you tap Stop Sharing, delete the tour, race session or rally stage, or close your account
• Who you rode with: Kept with your ride, worked out again if a rider changes their privacy zones, and deleted when you close your account. The copy on your phone is removed when you sign out
• Ride roles and low-battery alerts: The record of who stood in as lead is kept for the group's ride reports and deleted with the group or when you close your account. Low-battery alerts are kept per ride and deleted when you close your account
• Tours, race sessions, rally stages, mapped tracks and ride videos: Kept on the server so they follow you to a new phone, and deleted with your account
• Ride recaps, call history and the emergency card access log: These are also other riders' records, or an audit trail, so they are kept after you close your account with your name and photo removed. A random account number remains, which no longer points at anybody. The access log keeps who fetched your card and when, but the copy of your card, phone number and contacts kept with each fetch is erased. We keep a note that the account was closed and what was removed, as counts only
• Your privacy requests: The requests you made through Privacy Requests or by writing to us are in your copy of your data while your account is open. When you close it, each one is kept, as proof that it was handled, with only its kind, the dates it was made and answered, its status and a random reference; your words, our answer and anything that leads back to you are removed
• After you close your account, for 12 months: A sealed record, encrypted and read only to answer a request we are legally bound to answer (for example from the police or a court). It holds the account number, when the account was opened and closed and whether you or MileVoy closed it, how you signed in, your country, the phones and computers it was signed in on (model, system and App version, and the network (IP) address of each sign-in), and a scrambled copy of your email address and mobile number that can confirm a number or address someone already has but cannot be turned back into it. Nothing else of yours is in it. It is deleted automatically 12 months after the account closed. Indian law sets minimum periods for this kind of record: the IT Rules 2021, CERT-In's directions and the Digital Personal Data Protection Rules 2025
• Totals with nobody in them: Each day and each month we count riders, rides, distance, riding modes, countries and states, App versions, features used, sign-ups, closed accounts, messages, safety alerts, crashes and our own costs. These are numbers only, with no account, name or place finer than a state, so they are not about you, and we keep them indefinitely
• Long-term archive: Each month and each year we keep a copy of our business and audit records (those totals, our costs, the notes of closed accounts, the records of removals and emergency card fetches, groups and their trip histories, and the record of what the people who run MileVoy did) in Cloudflare R2, with names, email addresses, phone numbers, addresses, network addresses, places and message text taken out and every account number replaced by a code that does not show who it was. We keep the archive indefinitely
• What the people who run MileVoy do: Every look at and change made on our admin dashboard is recorded with who did it, what it was, when, and which account or group it was about, never the information itself. We keep this record for years, to hold ourselves to account
• Live location: Your latest position per group, plus a trail of about 200 recent points per group that draws the route behind you on the map. Both are deleted when you leave the group or close your account
• Sign-ins: Each sign-in, with its device details and the IP address it came from, is kept until you sign out on that device, remove it from your signed-in devices, or close your account
• Verification code limits and free trials: The daily count of verification codes asked for from one phone is kept with a one-way scrambled copy of its device identifier, never the identifier itself, and deleted after two days. The record that a phone has had its free trial is kept with its device identifier and when the trial started, including after you close your account but without anything that leads back to you, so that the trial cannot be taken again
• Feature use, ride summaries and phone details: The features you use (unless you switched Share Usage Data off), the per-ride summaries and each phone snapshot are kept while your account is open and deleted when you close it. Your latest phone details are kept on your account, replaced by each new snapshot
• Crash and error reports: Crash records and problem reports are kept while your account is open, to track the faults they describe, and are deleted when you close it
• Feedback: Kept as the record of what you told us, and deleted with your account; the copy in our support inbox is kept until we delete it
• Ride diagnostics: Kept in our database for 90 days, then moved to our long-term storage in Cloudflare R2, in a folder of your own. Kept while your account is open, included in your copy of your data, and deleted, from both, when you close your account
• Phone performance on rides, and phone and App performance: Kept while your account is open and deleted when you close it. The detailed samples from test versions of the App move to our long-term storage after 30 days, in a folder of your own, and are deleted from it when you close your account
• App sessions and the days you open the App: Kept while your account is open, and deleted when you close it
• Crash alarms, hard knocks and SOS readings: Kept, with where they happened, their sensor readings and your answer to "What happened?", to tune the crash detector, and deleted with your account
• Hazard reports: Shown for about two hours (an hour more each time a rider confirms it) or until cleared, and kept after that as the record of the road; deleted when their group is deleted. When you close your account, your ended or expired reports are deleted, and a report still live in a group that carries on stays for the riders behind you, with no name, picture or anything that leads back to you
• Whether the App is still installed: Kept on your account, and deleted with it
• Device check results and call tokens: Kept with the sign-in they belong to, and deleted when you sign out on that device or close your account. The latest device check result is also kept on your account until you close it
• Removals: The record of who removed a rider from a ride or group, and who let them back, is kept as the record of what was done, like reports of content, including after the group ends or either account is closed
• Reports of content or riders: Kept while we deal with them and after, as the record of what we did and why. Reports other riders filed about you are kept after you close your account, as evidence for moderation and in case the law requires it. Blocks last until you unblock the rider, and are deleted, both ways, when either account is closed
• Permanent bans: The scrambled copies of a banned rider's email addresses, phone number, Apple ID and Google ID are kept for as long as the ban stands, including after the account is closed, and are deleted if the ban is lifted
• Where your rides happen: The country and state are kept on the ride, tour, race session or rally stage and go when it is deleted
• Backups: A copy of our whole database is made every night and kept for 30 days, so something you delete, or an account you close, is gone from the backups within 30 days. The sealed record kept for 12 months after an account closes, the totals with nobody in them and the long-term archive (all above) are not backups and follow their own periods
• On your phone: Media and files you have downloaded stay on your phone until you delete them. The pictures of the cards you have earned are kept on your phone until you sign out

6. Your choices

• Pause or stop location sharing: Pause it during a ride, or switch it off for a group
• Photos and notes on your rides: Each starts as Only Me. Change who sees each photo, remark, and your note and rating, at any time in Photos and Notes on the ride, or remove them there
• Your ride page: Make a link only if you want one. Stop Sharing ends it at once
• Got Home Safe: On unless you switch it off, for all your groups under You > Privacy > Got Home Safe, or for one group under My Ride on its ride
• Show Me in Who Rode With You: On unless you switch it off under You > Privacy. Off, other riders of your group rides get nothing of yours for their Ride Stats and ride videos, and your own Who Rode With You is hidden
• Show Me to Riders Here: On by default, and back on each time you open Race mode and after each session ends. You can switch it off on the Race screen (My Race Settings), before you arm a Track Day on a track that is not in our list; it stays off for that session only. Off, the other riders lapping there do not see you, and you do not see them
• Your finish: Choose Home, Work, a place or a pin, or I'll Decide Later, and change it at any time from My Ride. Set Home and Work, or clear them, under Home & Work on the You tab
• Heart rate: In the App, open the You tab, open Privacy and set Heart Rate · Health Connect (on iPhone, Heart Rate · Apple Health) to Off. Nothing is read from the health store from then on; you can also withdraw the App's access in Health Connect or in the Health app. The ride summaries already on your ride records (average, highest, lowest) stay with those rides until you delete them or close your account
• Which features you use: In the App, open the You tab, open Privacy and use the Share Usage Data switch. Off takes effect straight away and nothing more of this kind is sent. What was already sent is kept until you close your account; to have it deleted sooner, write to us. The data in section 1.1 is needed to run the service and is not covered by this switch; it goes when you close your account
• Crash detection: On from the start, so that a crash can raise an alarm on every ride. Switch it off or on again at any time on your Emergency Card (every ride), or for one riding mode under Ride Features in Race, Rally or Endurance. The App asks before it goes off, and each change is recorded as safety data (section 1.1)
• Emergency card: Choose whether groups can read it. Add, change, reorder or remove your emergency contacts at any time
• Your email and mobile number: Verify or change them at any time under Account Information on the You tab
• Women riders cards: Switch them on or off under Account Information
• Close your account: In the App, open the You tab and tap Close Your Account. It takes effect straight away. If you cannot open the App, see how to delete your account
• Get a copy of your data: In the App, open Account Information on the You tab and tap Export My Data. You get one file with everything we hold about you - your account, rides with their routes, messages you sent, your emergency card, cards, garage, your photos, notes and remarks on rides (the photos are listed, not copied), your ride page links, where your rides finish, your low-battery alerts, the offers sent to you, the earlier versions we keep of what you changed, your diagnostics from our long-term storage and the rest - to save or share. Other riders appear in it without their names or words, and who rode with you is left out, because it holds other riders' positions. You can do this once a day; if you cannot open the App, write to us at the address below
• Notifications: Control them in your phone's settings. MileVoy's own offers and news are on by default; turn them off in the App under You, Notifications, Offers and News, or switch off the Offers and News category in your phone's notification settings on Android, without touching ride alerts
• Leave a group: At any time, to stop sharing with its members. If you created it, you can instead choose Delete for Everyone (see section 5)
• Ask us about your data: Use Privacy Requests (You > Privacy) in the App, or write to [email protected], to ask for a copy, a correction or a deletion, or with any other question about your data. We answer within one month

6a. If you are in the European Economic Area or the United Kingdom

This section is for riders in the European Economic Area (EEA) and the United Kingdom, where the GDPR and the UK GDPR apply. The "controller" of your data (in those laws' words, the one who decides why and how it is used) is Sunil Ranganath, trading as MileVoy, in Bengaluru, India. You can reach us at [email protected]; we give a postal address for formal notices on request.

Why we are allowed to use your data. The law lets us use personal data only for a reason it recognizes (its "legal basis"). For each kind of data in section 1, ours is:

• To provide the service you signed up for (our contract with you): your account, sign-in and verification codes, profile, settings, vehicles, groups, trips and expenses, messages and media, photos and notes on your rides, ride answers, Home and Work, where your ride finishes, your position while riding, ride data and ride records (section 1.1a), hazard reports, battery alerts, ride roles, who you rode with, Race mode and its live timing, crash detection, SOS and the rally check-on, your ride page and your live link, the push and call tokens, and what the routing, map, weather, notification and update services in sections 3 and 9 receive so they can answer. Without these the App cannot do what you use it for
• To keep MileVoy secure and working (our legitimate interests in protecting accounts, preventing fraud and abuse, and finding and fixing faults): sign-ins and the IP address of each, your phone's device identifier (for sign-ins, the daily limit on verification codes and the one free trial per phone), the Android device check, the App version with each request, problem reports and crash and error reports, App sessions, ride diagnostics, phone performance on rides, phone and App performance, your phone's details, whether the App is still installed, your earlier email addresses, reports, blocks, removals, Race Control's disqualifications and championship bans, permanent bans and the abusive-word filter, the record of what the people who run MileVoy do on the admin dashboard, and our nightly backups
• To understand and improve MileVoy (our legitimate interests in knowing how, where and by whom MileVoy is used, and in making it better): which features you use (section 1.2), your country (worked out as section 1.1 describes, or given by you), your state and gender if you give them, who invited you to MileVoy, your region and the countries and states your rides happen in, the counts per country and the totals with nobody in them, the crash alarms and hard knocks used to tune the crash detector, your feedback, and the visit counts on this website (section 8). You can object to the use of which features you use at any time with the Share Usage Data switch, which stops it straight away; it is the same for every rider, and the App tells you about it when you sign up. To object to anything else on this list, write to us
• To keep a record over time (our legitimate interests in supporting riders, settling disputes and keeping our business and audit records): the earlier versions we keep of what you change, the changes to a group, and the long-term archive (section 5)
• To tell you about MileVoy (our legitimate interest in promoting our own service): MileVoy's offers and news, chosen with the details listed in section 2. You can turn them off at any time, and we then send no more
• Your emergency contacts: the people you add are told about your SOS, and on a rally stage may be asked to check on you, so that help can reach you. We use their names and numbers for that alone, in your interest and ours in your safety, and, when an SOS is raised, to protect your life and health. We do not tell them when you add them, so please let them know; each WhatsApp message we send them names you and says why they received it
• Because you chose to (your consent): heart rate from your watch and the health details on your emergency card are health data, and we use them only with your explicit consent. The App reads heart rate only after you switch it on, and switching it off withdraws your consent. You add the emergency card's health details yourself and choose whether your group's leaders can read them; you can change or remove them at any time. The Women riders cards use your gender only after you switch them on. Withdrawing consent does not affect what was done before
• To meet legal duties: the sealed record kept for 12 months after an account closes, and what we disclose when the law or a valid legal process requires it (section 3). These duties come from the law of India, where MileVoy is run; for riders in the EEA and the United Kingdom we rely on our legitimate interest in meeting them, and on a legal obligation where EEA or UK law itself requires it

If you do not give us data. The data needed to run the service (section 1.1) is needed to make an account and ride; without it we cannot provide the App. Everything marked optional in section 1 is your choice, and the App works without it.

Your rights. You have the right to:

• get a copy of your data (Export My Data under Account Information gives you one at once), and receive the data you gave us in a file you can take elsewhere
• have wrong data corrected (most of it you can change yourself in the App)
• have your data deleted: Close Your Account deletes it as section 5 describes, and you can ask us to delete particular data sooner. We will, unless section 5 gives a reason we must keep it
• ask us to restrict how we use your data while a question about it is settled
• object to any use based on our legitimate interests, and stop offers and news at any time
• withdraw any consent you gave, at any time

To use any of them, use Privacy Requests (You > Privacy) in the App, or write to us (section 12). We may ask you to confirm that the account is yours. We answer within one month of receiving your request; if a request is complex, or you send many, we may take up to two more months, and we tell you within the first month why. You also have the right to complain to a data protection authority: in the EEA, the one in the country where you live or work, or where you think the problem happened; in the United Kingdom, the Information Commissioner's Office (ICO). We would like the chance to put it right first, so please write to us too.

Where your data goes. MileVoy is run from India. Our database is in India (MongoDB Atlas, in Mumbai). Our server (Railway) and our file storage (Cloudflare R2) run in their providers' data centers, and the other service providers in sections 3 and 9 (such as Google, Apple, Meta, Expo and Resend) handle data where they run their services. So your data is sent out of the EEA and the United Kingdom, mainly to India. MileVoy has no office and no appointed representative in the EEA or the United Kingdom; write to us directly at the address in section 12.

How long we keep it. Section 5 gives each period. In short: what is yours alone is kept while your account is open, deleted when you close it, and gone from our backups within 30 days; a sealed minimum record is kept for 12 months after the account closes, for legal requests only; what other riders still need, and our audit records, are kept with your name and anything that leads back to you removed; and the totals with nobody in them, and the long-term archive with names, contact details, places and message text taken out and account numbers replaced by codes, are kept indefinitely.

7. Children

MileVoy is for riders aged 18 and over, or the age of majority where they live if that is higher, as our Terms of Service say, and we do not knowingly collect personal information from anyone younger. If you believe a child has given us personal information, contact us and we will delete it.

8. This website

When you visit milevoy.com we count the visit on our own server. We store a random identifier in your browser so that a second visit is not counted as a second person, along with the page you looked at, the site that sent you, the width of your window, your country (as our hosting provider, Cloudflare, works it out from your connection) and whether you tapped through to Google Play or the App Store. There is no third-party analytics service, no advertising identifier and no cookie. The random identifier tells us nothing about who you are, is not linked to any MileVoy account, and clearing your browser storage removes it. These visit counts are kept with no fixed limit.

The sign-in page uses Google Firebase Authentication. A live-link page loads its map tiles from OpenStreetMap.

Ride pages (milevoy.com/r/...): a ride page is not counted as a visit. It fetches the ride from our server, loads its map code from unpkg.com, its map tiles from OpenStreetMap, its type from Google Fonts and the rider's photos from Cloudflare R2, so those services see your IP address. It never sends them the page's own address (the link to the ride), and remembers your choice of kilometers or miles in your browser's storage.

9. Third-party services

The App uses these services, each with its own privacy policy:

• Google Sign-In and Firebase Authentication (Google)
• Google Play Integrity, on Android, which tells us whether the App and the device are genuine (Google)
• Firebase Cloud Messaging for notifications on Android (Google)
• Sign in with Apple and the Apple Push Notification service, including call (VoIP) pushes, on iPhone (Apple)
• Google Maps, which draws the maps in the App (Google); your phone fetches the map of the area on screen from Google, which sees that area and your phone's IP address. On iPhone, the two maps where you set your Home and Work and your privacy zones are drawn by Apple Maps instead (Apple)
• MongoDB Atlas (database)
• Cloudflare R2 (file storage) and Cloudflare (TURN relay for calls)
• Railway (server hosting)
• Expo's push service, which carries our notifications to Firebase Cloud Messaging and the Apple Push Notification service
• Expo's update service (EAS Update), from version 3.0: as it starts, the App asks Expo's servers whether there is an update to the App and, if there is, downloads it. Expo receives your IP address and basic information about the device and the App, such as whether the phone is Android or iPhone, the App's version and which update it is running, with a random identifier that Expo's update code makes once for this installation of the App. Nothing about your account or your rides is sent (Expo's privacy policy)
• Resend, which emails you a code when you sign in with email or phone, or verify or change your email address or mobile number; if Resend cannot send it, the code goes from our Gmail account instead (Google)
• WhatsApp Business Platform (Meta), which sends you a code when you sign in with or verify your mobile number, and SOS messages to your emergency contacts; it receives the phone number and the message
• Google's Routes API for routes, traffic and toll prices, asked by our server: the start, the destination, any stops along the way and whether the route is for a car or a two-wheeler (from the vehicle you ride) are sent, nothing that identifies you
• Google's Places, Geocoding, Elevation and Roads services, asked by our server within their free allowance: what you type in a destination search, or the points of a route, is sent, nothing that identifies you. On an Endurance or Rally map with no route drawn, the App also asks our server about every 15 seconds while you move to place your last few positions on the road, and our server sends those positions to Google's Roads service, with nothing that identifies you, up to a daily limit. When an allowance is used up, the OpenStreetMap-based services below answer instead
• Valhalla, a route planner run on the free server of FOSSGIS e.V. (valhalla1.openstreetmap.de), for routes that keep a motorcycle off roads closed to it, asked by our server: the start, the destination and any stops are sent, nothing that identifies you
• Google's Navigation SDK, for turn-by-turn directions in group rides, solo rides and Head Home, when it is available: while it guides you, Google receives your location and route to provide navigation, under Google's own terms, which the App shows you before first use. If you decline them, or Google's navigation is unavailable, MileVoy's own navigation guides you instead
• Services based on OpenStreetMap, each run by its own operator: OSRM for routing, asked by our server; Photon (photon.komoot.io, run by komoot) and Nominatim (nominatim.openstreetmap.org, run by the OpenStreetMap Foundation) for place search and for naming a place on the map; and the Overpass API (overpass-api.de and its mirror overpass.private.coffee) for fuel, food, parking and other places, for road details such as speed limits, speed cameras, bridges, flyovers and toll plazas, and for the outline of a track. Some of these requests go through our server, and some go straight from your phone: naming a place you pick or pin on the map (Photon), searching for a place or naming a town when our server cannot answer (Photon and Nominatim), and the places and road details around you or along your route (Overpass). What you type in a search, and the position or route the answer is about, are sent to them; a request straight from your phone also shows them your phone's IP address, but never your name or your account. We keep no record of who searched; to answer a repeated search faster, our server keeps the words searched with an area of about 10 km, and nothing that links them to you
• Open Charge Map, for electric vehicle charging points when Google's allowance is used up, asked by our server: the area searched is sent, nothing that identifies you
• MET Norway (the Norwegian Meteorological Institute) for weather along a route and during a ride. The request goes through our server, so MET receives only an area of about 1 km, never who you are. Only if our server's weather service cannot be found does the App ask MET (api.met.no) directly, and MET then sees your phone's IP address and the position to about 10 m, still with nothing that names you. Sunrise and sunset are worked out on your phone, with nothing sent
• Open-Elevation and OpenTopoData for the heights along a route, asked by our server (and by the App directly from your phone, through Open-Elevation, if our server cannot be reached, which then also shows it your phone's IP address); the route's points are sent, nothing personal
• jsDelivr and Google Fonts, from which the App loads its video-drawing code and type when you make a ride video on your phone; they see your IP address, and your ride stays on your phone

10. Permissions

The App asks for these permissions on Android, and the matching ones on iPhone, each when a feature first needs it:

• Location: To show your position to your group and navigate. The App uses the "while in use" permission with a foreground service, so sharing continues while the screen is locked during a ride. It does not ask for background location. On iPhone it uses "While Using the App", and the blue location indicator shows whenever a ride keeps recording or sharing with the screen locked. It asks for "Always" only if you switch on Keep Recording If MileVoy Is Closed (You > Privacy, off unless you turn it on), so that a ride you close the App in keeps recording and your group still sees you; it is used only during a ride, and you can take it back in the iPhone's Settings at any time
• Camera: To take photos and videos for chat, photos for your rides, bug reports and video calls, and on iPhone to scan a group's QR code. On Android a group's QR code is scanned by Google's own code scanner, which needs no camera permission and gives the App only the code it read
• Microphone: For voice notes, videos you record for chat, calls and the group voice channel
• Photos and files: To choose images, videos and documents to share, and to save ride cards and videos. A photo for a ride is chosen in your phone's own photo picker, which needs no permission and gives the App only the photo you pick
• Notifications: To tell you about messages, calls, SOS alerts and rides, and to bring MileVoy's own offers and news, which you can turn off on their own
• Phone (Android): To show incoming MileVoy calls like phone calls
• SMS (Android, optional): Only to send an SOS text to your emergency contacts by itself, from your own SIM, when an SOS is raised. The App sends no other texts and never reads your messages. If you do not allow it, an SOS opens your messages app with the text ready to send
• Sensors and physical activity: Accelerometer and gyroscope for crash detection and lean angle. On Android 10 and later this is the "Physical activity" permission, asked when you switch crash detection on or a ride first starts watching for a crash; on iPhone it is Motion & Fitness. MileVoy does not count steps or guess what you are doing
• Health Connect (Android), Health (iPhone), optional: Only if you switch on Heart Rate · Health Connect (Heart Rate · Apple Health on iPhone), to read heart-rate samples your watch or chest strap saved there. Read only; the App never writes to it, and reads nothing else from it
• Fingerprint or face unlock (Android), Face ID (iPhone): Only in Race mode, including Open Road, to sign the declaration before a session. No other mode asks for it. The App is told only whether it matched; your fingerprint or face never reaches the App or us
• Notification access (Android, optional): Only if you turn it on for the music controls on the ride map: it lets the App show what your music player is playing and skip tracks. The App reads only the player's track and controls, and none of it leaves your phone

11. Changes to this policy

We may update this policy. When we do, we post the new version in the App and on this page, change the "Last updated" date and say what changed at the top of this page. When a change affects what we share or with whom, the App tells you about it the next time you open it.

12. Contact us

Questions about this policy or your data:

• Email: [email protected]
• Privacy and legal requests: [email protected], answered within one month
• Who we are: Sunil Ranganath, trading as MileVoy, Bengaluru, India. We give a postal address for formal notices on request
• Website: https://milevoy.com