CoRoute helps a group of riders stay together: it shows every member of your convoy on a map, lets you send quick status messages and SOS alerts, and provides a live voice intercom. This policy explains exactly what the app collects, why, how long it is kept, and how to delete it. CoRoute is supported by transparent, nominal membership plans. We do not sell data, we show no ads, and we have no third-party analytics or tracking SDKs. Our Terms of Use also apply.
What we collect
| Data | Why | Kept for |
|---|---|---|
| Account: name/callsign, e-mail, phone, vehicle type & number (or pillion), emergency contact name & phone (required before you ride in a convoy), hashed password (or your Google account e-mail and name if you sign in with Google) | To identify you to your convoy and let your ride mates reach you; emergency contact is shown only to members of your convoy | Until you delete your account |
| Medical info (optional): blood group, allergies and short medical notes, only if you fill them in | So the riders who reach you after a crash or SOS know what to tell a doctor | Until you clear the fields or delete your account. A copy goes with an SOS alert only while the alert is open, then it is removed |
| Emergency text setting: whether you agree to receive emergency texts from your ride group | To leave your number out of other riders' emergency texts if you say no | Until you change it or delete your account |
| Nearby rider settings: "Help nearby riders", "Ask nearby riders to help me", "Share medical info with a rider from another group who comes to help me", and when you agreed to the nearby rider network | To decide whether you are asked to help other groups, whether other groups are asked to help you, and what a helper may see | Until you change them or delete your account |
| Safety log: when an emergency was raised, its status changes, how many riders were asked or warned, who answered and how, reports of a false alert, with ids and short codes only (no positions, no names, no messages) | To check that the safety network works and to stop misuse | Deleted after 180 days, and at once when you delete your account |
| False alarm count: the times of your last false alarms that riders outside your group were asked to help with | To limit requests to other groups from accounts that raise many false alarms. Your own group is always alerted | The last 10 are kept; an administrator can reset them; deleted with your account |
| Live location (latitude/longitude, speed, heading), battery level, stop status | Shown to the members of the convoy you are currently in, so the group can stay together and respond to an SOS | The latest position is kept while the convoy is active and removed 90 days after it ends |
| Recorded route: the GPS points your phone records during a convoy (time, position, speed, accuracy) | To show your route, measure distance, moving time and stops exactly, and to let your group replay the ride | Deleted 90 days after they were recorded |
| Ride timeline: who joined, stopped, fell behind, went off route, lost signal, went over the group speed limit, reached or rode past a planned stop, raised an SOS or arrived, closed the app, stopped suddenly at speed, went to help a rider or said they are OK, with the time, how long it lasted and the place name | The shared trip timeline and trip report for the convoy | Kept as part of the trip history; the exact coordinates in it are removed after 90 days, the place name stays |
| Convoy records: convoy name, join code, members, start/end time, settings, planned stops, chat and quick-status messages, SOS alerts | To run the convoy and show your trip history | Kept as part of your trip history; GPS traces inside them and the exact position of SOS alerts are deleted after 90 days |
| Trip history: trip name, members, dates, distance and speed statistics, and the names of the places where each rider started and finished | Your personal ride log | Until you delete the trip or your account; the GPS trail of a trip is deleted after 90 days |
| Voice | Live intercom between convoy members (group, or privately to one rider you choose) | Audio is never stored. It is relayed in real time and discarded. We keep only who talked to whom and for how long, for 7 days, to detect abuse |
| Ride Guardian links: hashed session tokens and capability tokens, optional label, selected tier (Basic, Live, Emergency), hashed PIN, expiry time | To allow family or trusted contacts to monitor ride status or emergency location via PIN-protected web access | Until expired, revoked by the rider, or purged upon convoy deletion or account removal |
| Smart Fuel Profile (local): tank capacity, mileage, reserve buffer | Calculates remaining range on device; only opted-in, fresh usable range estimates (in km) are shared with the convoy for fuel stop planning | Stored locally on your device; raw tank inputs are never uploaded |
| Sweeper & Rider Down reports: sweeper assignment, rider-down incident location and report time | Shared only with the active group to coordinate assistance, and approaching riders as an anonymized road safety warning | Kept during the active convoy and purged with convoy records |
| Technical: server logs with IP address and request time | Security and keeping the service running | Rotated automatically within a few weeks |
Location, including in the background
While you are in an active convoy, CoRoute shares your position with that convoy even when the screen is off, so your ride mates can still see you and your SOS still works. A persistent notification is shown on Android while this is happening. Location sharing stops automatically when you leave the convoy, when the convoy ends, or when you sign out. No location is collected when you are not in a convoy. If your phone has no signal, the points are stored in a local encrypted buffer on your phone and synced when the connection returns.
Recorded route points are retained securely for 90 days to enable personal ride replay and statistics in your trip history, after which raw coordinate traces are permanently purged from the database.
If the theme is set to Automatic, the app uses the last position your phone already knows to work out sunrise and sunset. This happens on your phone only; that position is not sent to us.
Crash detection and the motion sensor
During a ride, above 25 km/h, the app can read the phone's motion sensor to notice a crash. This happens on your phone only. Motion data is not sent to us and not stored. If the phone thinks you crashed, it asks "Possible accident detected. Are you okay?" and counts down for 15 seconds first. If you tap "I'm OK", nothing is sent. If you tap "Need Help" or do not answer, an SOS marked as automatic goes to your convoy with your position, direction, speed before the impact and the time. You can switch crash detection off in the app.
Our server also notices when a rider stops suddenly from high speed and does not move for 2 minutes, or loses signal right after riding fast. It then asks the lead and the nearest riders to check on that rider. This uses only the position and speed your convoy already sees.
Help from nearby riders of other groups
When you raise an SOS or a crash alert, your own group is always alerted first. Our server also looks for a few riders of other groups who are already riding toward your position on the same road and may reach you sooner than your own group. At most 3 riders are asked at a time, never everyone nearby. Before they agree to help they see only the place of the emergency, how far it is and roughly how long it takes to get there. They do not see your name, your group, your phone number, your ride mates or anyone's position other than the emergency point.
If one of them taps "I Can Help", that rider also sees your first name and your vehicle type and colour, so they can find you. Your medical info is shown to them only if you switched on "Share medical info with a rider from another group who comes to help me" (off unless you turn it on). Phone numbers are never given to riders of other groups; they can call emergency services. Your group sees that "a nearby rider" is coming, their first name, how far away they are and their position while on the way, but not their group. When the emergency is closed, the riders of other groups lose access to it at once and their phones drop what they were shown.
Riders of other groups who are riding toward an accident on the same road get a short warning ("Rider accident reported 2 km ahead") with the place only, no names.
You can turn off "Help nearby riders" (you are then never asked) and "Ask nearby riders to help me" (other groups are then never asked for you; your own group still is) in the app at any time. This works the same whether your group is Public or Private.
Groups nearby (optional)
This is off unless the lead of your group sets the group to Public and turns on "Nearby group discovery". Only when two groups have both done this, each group sees the other group's name, how many riders it has, a rounded distance and whether it is riding the same way or toward you, for example "Weekend Riders nearby, 6 riders, about 4.5 km". Never member names, positions, phone numbers or destination. A group can send a one-tap wave; there is no chat. A group with an open emergency is never shown.
Emergency texts when there is no internet
This is off until you switch it on. When it is on and your SOS cannot reach the server, your own phone sends a text message (SMS) with a map link to your position. It goes to your emergency contact, your lead and the nearest riders in your convoy, at most 10 people. The texts are sent from your phone and your SIM, not by us, and your carrier may charge for them.
To make this work, your phone keeps the phone numbers of the other riders in your convoy during the ride. It gets only their numbers and their role in the ride, not their names. The numbers are stored encrypted on the phone, are never shown on screen, and are deleted when the ride ends, when you leave or sign out, or when you switch the setting off. They are used for nothing else.
If you do not want to receive these texts, switch off "Receive emergency texts from my ride group" in your profile. Your number is then not given to other riders for texts. Your ride mates can still see your number on your rider card, as before.
Spoken alerts and the ride notification
The app can read out emergency alerts and warnings using your phone's own text-to-speech engine. The text is spoken on your phone and is not sent anywhere. During a ride the notification shows your destination, the nearest riders ahead and behind with their distance, and quick actions. On the lock screen it shows your own ride only if "Show ride on lock screen" is on; emergencies of other groups show only a short line without names, and phone numbers are never shown there. You can switch spoken alerts, the lock screen view and the large notification off in the app.
Microphone and Voice Intercom
The microphone is used exclusively for live group intercom communication while an active convoy is running. The microphone is OFF by default. It activates only while you physically hold the Push-to-Talk (PTT) button or when you have explicitly armed Voice-Operated Transmission (VOX) mode. Audio streams are encrypted and relayed directly to convoy members in real time over secure WebSockets. We never record, analyze, transcribe, or store audio content. Audio buffers are discarded immediately upon transmission.
Live emergency links
While your SOS or crash alert is open, you or the lead of your group can create a live link and send it to anyone, for example a family member or the emergency services. Nobody else can create one. The link opens a public web page on our site that shows your first name, your last position, the time of that position, the time the link stops working, and a "Call 112" button. Nothing else: no phone number, no group, no other riders, no medical info.
A link works for 30 minutes. It stops earlier when the rider or the lead revokes it in the app, or when the alert is closed. After that the page says only that the link has expired. The link is a random code that we store only as a hash, so a lost link cannot be recovered or reopened. At most 3 links can be made for one alert.
Anyone with the link can open the page. Requests from one network address are rate limited, and the addresses are not stored beyond the normal server logs described above. The page sets no cookies and does not count page views. The map on the page is drawn from OpenStreetMap map images, which the viewer's browser loads from openstreetmap.org. The safety log keeps who created or revoked a link, and that a link was viewed, with the time and the alert id only; never the link itself and never a position.
Ride Guardian links
Ride Guardian links provide PIN-protected web monitoring for family and trusted contacts to follow your ride without needing a CoRoute account. You choose one of three privacy tiers for each link:
- Basic: aggregate status and progress without exact coordinates.
- Live: personal location during active ride only.
- Emergency: location only when SOS or crash alert is open.
Session tokens and capability tokens are stored only as cryptographic hashes on our servers, ensuring raw credentials cannot be extracted from database storage. Observers cannot see other convoy members, group chat, emergency contacts, or rider medical profiles. Grants can be paused or revoked at any time by the rider in the app. Access expires automatically when the ride ends or the chosen expiry duration lapses. All dependent records are purged upon convoy deletion or account removal.
Weather on the route
When you review a planned route and once more when the ride starts, the app can ask for a weather line such as "Rain likely after Warangal around 3 PM". To do this it sends up to 5 points along your planned route, rounded to about 10 km, to Open-Meteo (open-meteo.com) through our server. Our server does not send your name, your account or your exact position, and it keeps the answer for 30 minutes so that other riders at the same places get the same answer without a new request. Nothing is sent when data saver is on. Weather data by Open-Meteo.com.
Nearest hospital
When an SOS or crash alert opens, our server asks OpenStreetMap (Nominatim, the same service we already use for place names) for the nearest hospital to the alert position, once per alert. The result, for example "Nearest hospital: X, 4.2 km", is shown to your group with the alert. Only the position of the alert, rounded to about 1 km, is sent; no names or account details. The answer is kept for 30 days so that a new alert within about 1 km needs no new request. The alert itself never waits for this lookup.
Maps saved on your phone
Before a ride, on Wi-Fi or when you tap "Save route map", the app can download the map tiles along your planned route from OpenStreetMap and keep them on your phone, so the map still shows when there is no signal. The tiles are kept on the phone only, up to 60 MB, and are deleted after 30 days or when you delete the trip. Nothing about this leaves your phone, and we do not know which tiles were saved.
Route Essentials
Route Essentials helps you find critical services along your planned path. Corridor queries search for fuel, puncture repair, food, and medical within 1.5 km of the road.
CoRoute queries OpenStreetMap Overpass without sending rider identities or tracking profiles; queries use only the corridor coordinates around the route. Query responses are cached on the server so riders traveling the same route do not trigger duplicate external requests.
Smart Fuel Profile
Smart Fuel Profile calculates estimated motorcycle range to help convoys plan collective fuel stops. Tank capacity, mileage, and reserve buffers remain stored locally on your device.
Only opted-in, fresh usable range estimates (in km) are shared with your ride group for collective fuel stop planning. Raw tank inputs are never uploaded. You can disable fuel range sharing in your settings at any time.
Sweeper, battery and update gaps
Your battery level and the time of your last position update are already shared with your ride group as part of your live location. Since 3.16 the app also uses them for alerts: the lead can make one rider the sweeper, and the lead and the sweeper are told when a rider's battery is low, when a rider has not sent an update for unusually long, or when a rider drops behind the sweeper. This adds no new data; it only shows what the group already sees in a clearer way.
Sweeper assignments and rider-down incident reports are shared only with the active group (and approaching riders for road safety warnings), with no private personal data leaked. When a rider-down report is filed, approaching riders of other groups on the same route receive only an anonymized road hazard alert and distance warning, without rider names, phone numbers, or group identities.
Indian emergency services
In emergency and safety screens, the app provides quick dialing shortcuts for Indian emergency services: 108 Ambulance, 112 National Emergency, and 100 Police.
Quick dialing for 108 Ambulance, 112 National Emergency, and 100 Police connects through the device native dialer directly to public emergency operators. CoRoute does not record or route emergency calls.
Hard braking count
While crash detection is on, the phone counts hard stops from the motion sensor it already reads. The count is shown only to you on your own post-ride summary. It is kept on your phone, it is never uploaded and your group never sees it.
Medical ID on the lock screen
"Show my medical ID on the lock screen during an SOS" is off until you turn it on. When it is on, and only while your own SOS or crash alert is open, the ride notification on your lock screen shows your blood group, allergies and emergency contact name and number, so that a person who finds you can read them without unlocking the phone. This is shown by your phone only and is not sent anywhere beyond what the section "Who can see your data" already describes.
Bluetooth and Offline Mesh Relay
CoRoute utilizes Bluetooth Low Energy (BLE) strictly for offline peer-to-peer convoy coordination and emergency failover. Outside of active offline convoy mesh relay, CoRoute does not use Bluetooth. Bluetooth is never used for background tracking, advertising identifiers, or third-party beacons. BLE scanning and broadcasting operate only while an active convoy is in progress and terminate automatically when the ride ends.
Trip reviews and group photos
After a ride the app can ask for a rating, a few words and up to three photos of your group. Photos are only sent if you tick the box that lets CoRoute publish your photo and story after review. The app makes each photo smaller before sending it, and the server removes location and camera details (EXIF and similar data) before storing it. Photos are kept in a private folder on the CoRoute server, not on the public website.
The CoRoute team reads every review and looks at every photo. Only what an admin approves, and only the photos an admin picks, appear on the website, with a "Rider #" label instead of your name. Your e-mail address and phone number are never shown. Editing your review takes it off the website until it is checked again. You can withdraw it at any time from the trip report; it and its photos leave the website at once.
Numbers on our website
The home page can show a few totals, such as rides completed, kilometres ridden and riders on the road right now. They are worked out on our server from completed rides and are totals only: never per city, per route, per ride or per rider. Before they leave the server, counts are rounded down to tens (hundreds from 1,000), distance to 100 km (1,000 km from 10,000 km), and anything below 10 shows as nothing, so a small number can not point at you. An average rating is only shown once at least 10 ratings are behind it, and times are given to the hour at most.
The home, safety and features pages can also show "CoRoute impact" totals: kilometres and hours ridden, rides and group rides, the size of the largest group and the length of the longest trip (as a number only, with no name, route, place or date), bikes on CoRoute, and what the safety features did, such as SOS and crash alerts, alerts answered by other riders, the typical response time and road hazards reported. These are coarse aggregates under the same rules: rounded down, nothing below 10, the largest group only once at least 10 group rides exist, the longest trip rounded down to 10 km and only once at least 10 rides exist, and the response time only from at least 10 answered alerts. They never describe a rider, a ride or a place.
The website itself has no login, sets no cookies for analytics and loads no trackers or third-party scripts. It counts visits per page and day (with the name of the referring site), never per person. Your own ride analytics in the app are worked out from your own rides and are shown only to you.
Who can see your data
Members of the convoy you are in see your name, vehicle, phone, emergency contact, live position and messages. If you filled in medical info, they see it only while your SOS or crash alert is open. Medical info is never shown to administrators, never written into the ride timeline and never put in notifications. They can also see your recorded route, stops and timeline entries, but only for the time they were in that convoy themselves. Nobody outside your convoy can see them. Service administrators can see active convoys for safety operations (for example to dissolve an abusive convoy or send a safety announcement), open SOS alerts with who raised them, where and who is going to help, the safety log and false alarm counts; they cannot see medical info or listen to intercom audio. Riders of other groups see only what is described under "Help from nearby riders of other groups" and "Groups nearby".
Ride Guardian viewers see only the individual rider who created the grant, limited strictly to the chosen tier (Basic: aggregate status without exact coordinates; Live: personal location during active ride only; Emergency: location only when SOS or crash alert is open). They cannot see convoy chat, rider rosters, contact numbers, or medical profiles. Sweeper assignments and rider-down incident reports are shared only with the active group, and approaching riders on the same road receive road safety warnings with no private personal data leaked.
Where your data lives
Data is stored in an Oracle Cloud Autonomous Database and relayed by our server, both in the Oracle Cloud Hyderabad region (India). Connections use TLS. Passwords are stored as bcrypt hashes. If you sign in with Google, we receive your e-mail and display name from Google; Google's own privacy policy governs that sign-in.
Your choices and rights
You can edit your profile and delete individual trips inside the app. You can delete your account in the app under Account & security, Delete my account; it is removed at once. This deletes your profile, your trips, your recorded routes, your timeline entries, your safety log rows and false alarm count, and your chat messages, SOS alerts and voice log entries. The rides you shared stay in the other riders' history, but your name there is replaced with "Former rider", and your phone, bike number and emergency contact are removed. If you can no longer sign in, e-mail santhoshbukka5@gmail.com from the address you registered with and we delete it within 30 days. You may also request a copy of your data. You can revoke location and microphone permissions at any time in your phone's settings; the app will then work in a limited mode. You can switch crash detection, emergency texts, help from nearby riders, spoken alerts and the lock screen view off at any time in the app.
Ride Guardian grants can be paused or revoked at any time by the rider in the app, and dependent records are purged upon convoy deletion or account removal. Smart Fuel Profile sharing is entirely optional and can be toggled off at any time, keeping tank inputs stored only on your local device.
Children
Coroute is intended for licensed riders aged 18 and over. We do not knowingly collect data from children.
Changes
If this policy changes we will update this page and the effective date above. Material changes will be announced in the app.
Contact
devmonks.space · santhoshbukka5@gmail.com
See also our Terms of Use.
Back to top