Privacy Policy

1Who I am and how to contact me

RiderNav is provided by Chris Wild, an individual based in the United Kingdom. For UK data protection law, I am the data controller for the limited personal data described in this policy. For anything about this policy or your data, contact me at chris@ridernav.app.

2What this policy covers

This policy explains how the RiderNav app (for iPhone and Android), and the ridernav.app website, handle your data. RiderNav is currently in beta.

3The data RiderNav uses

3.1Location. When you navigate, RiderNav uses your device's location, including precise GPS location, to show where you are and to follow your planned route. A ride keeps running until you end it: on Android it runs as a foreground service with a visible notification, and on iOS it uses the location background mode, so guidance continues when your screen is off or another app is in front. Outside a ride, RiderNav reads your location once, at the moment you press a control that needs it, such as Find fuel now or the map overview while you are in a ride group.

3.2Debug data (beta only). While RiderNav is in beta, it records diagnostic logs on your device during a ride, including a log of your location during that ride, to help find and fix problems. These logs stay on your device and are not sent anywhere automatically. The production version of RiderNav will not record this.

3.3Routes and maps. Routes you import (for example GPX or KML files) and maps you download for offline use are stored on your device.

3.4Email. If you request beta access on the website, or email me, I receive your email address and your message.

3.5Ride groups (optional). A ride group lets friends riding the same route see each other on the map overview and navigate to each other. It is off until you join a group, and it stops when you leave. While you are in a group, RiderNav sends three things to a small service of mine: the rider name you typed (use a first name or nickname), a fingerprint of the route you have loaded (a one-way hash of its coordinates, used only to check that everyone joining has the same route), and your position, about every 12 seconds, but only while a ride is running or the map overview is open. Sharing continues with a running ride while your screen is off, until you end the ride. Nothing is sent from any other screen or when the app is closed. The app shows "Sharing with group" and the group code whenever it is sending, and shows you a plain summary of this before your first join.

3.6Ride group invites. When you create a group, RiderNav also sends the service a copy of the route, encrypted on your phone with a key that is created for that group and never sent to the service. The key travels only inside the invite link (the part after the # sign) and the QR code you choose to share, so the service holds bytes it cannot read, and only a phone that has the link can open the route. This is what lets a rider you invite receive the route with one tap instead of having to import the same file. The encrypted route is deleted with the group, when the last member leaves or 24 hours after its last activity, and 7 days after it was created at the latest. Anyone you send the link to can join the group and see the route, so share it as you would a private message. Groups created before this feature carry no route copy.

3.6RiderNav does not require an account, and apart from the rider name you choose for a ride group, does not ask for your name, contacts, photos, or other personal information.

4How your data is used

• Location is used to provide live navigation and to follow your planned route.
• Your routes and maps are used to let you ride offline and to review and manage your routes, on your own device. In the beta, on-device debug logs are used only to diagnose and fix problems.
• Your email is used only to reply to you and, if you asked, to contact you about the beta.
• Your ride group name and position are used only to show you to the other riders in your group and to let them navigate to you.

I do not use your data for advertising or profiling, and I do not build any profile of you.

5Sharing, and what leaves your device

5.1To calculate and follow routes, RiderNav sends location and route information to Mapbox, the mapping and routing service it uses. This is necessary to generate and display your route. Mapbox processes this as my service provider.

5.2The Mapbox software includes optional usage and location "telemetry" that is switched on by default. In RiderNav that telemetry is turned off, so Mapbox receives only what is needed to provide routing.

5.3RiderNav's maps are built on OpenStreetMap data (© OpenStreetMap contributors). Using the maps does not send your personal data to OpenStreetMap.

5.4Your imported routes, downloaded maps and any beta debug logs stay on your device. They are not sent to me or to anyone else automatically. If you choose to help troubleshoot a problem, you can email me a beta debug log yourself; because it includes your location during a ride, only send one if you are happy to share that.

5.5Any email you send is delivered to me. Beta-access requests made on the website are delivered to me using Amazon Web Services (email delivery only).

5.6Ride groups. When you join a group, your rider name and latest position are sent to a small program of mine running on Cloudflare's network, and are shown to the other members of your group: that is anyone who has both the group code and the same route loaded, so share the code only with people you are riding with. Cloudflare processes this as my service provider and, like any website you connect to, receives your IP address. Each group's data is held by Cloudflare at the location nearest the rider who created the group. My own service logs record only the kind of request and its result code. Cloudflare's platform logs for the service record, for 3 days, each request's address (which contains the group code and a member id), its result, your IP address and the details Cloudflare derives from it, such as country and city. They never contain what your phone sent, so your position and your name are not in them, and access tokens are redacted from them.

5.7I do not sell your data, and I do not share it with advertisers or data brokers.

6What RiderNav does not do

• No advertising and no ad networks.
• No analytics, usage tracking or crash-reporting services.
• No selling or renting of your personal data.
• No account, and no tracking of you across other apps or websites.
• No location sharing unless you join a ride group, and none once you leave it.

7Keeping and deleting your data

7.1On your device: your routes, downloaded maps and any beta debug logs remain until you delete them in the app or uninstall RiderNav, which removes them from your device.

7.2Email: I keep emails only for as long as needed to deal with your message or the beta, and then delete them. You can ask me to delete your email at any time.

7.3Ride groups: only your latest position is kept, and each update overwrites the one before it, so there is no history and no ride trail. If your phone stops sending, you disappear from the other riders' maps after 30 minutes. Leaving the group deletes your name and your position at once. The whole group is deleted 24 hours after its last activity, and no group lives longer than 7 days. Cloudflare's platform logs described in 5.6 are kept for 3 days.

8Security

I take reasonable steps to protect the limited data I hold. Data stored on your device is protected by your device's own security. No method of storage or transmission is completely secure, so I cannot guarantee absolute security.

9Sending data outside the UK

Mapbox, Amazon Web Services and Cloudflare may process data outside the United Kingdom, including in the United States, under their own safeguards for international data transfers.

10Your rights

Under UK data protection law you have rights over your personal data, including the right to access it, to have it corrected, to have it deleted, and to object to its use. For ride groups, leaving the group in the app deletes your data on the service at once, and because that data is short-lived and not linked to an account there will usually be nothing left to provide. To exercise any of these rights, email me at chris@ridernav.app. If you are unhappy with how your data has been handled, you can also complain to the Information Commissioner's Office (ICO) at ico.org.uk.

11Children

RiderNav is not intended for or directed at children under 13, and I do not knowingly collect personal data from them.

12Changes to this policy

I may update this policy as RiderNav develops. The current version is always published at ridernav.app/privacy.html, with the date it was last updated shown at the top. If the changes are significant, I will make that clear.

13Contact

For any question about this policy, or any request about your data, contact Chris Wild at chris@ridernav.app.