Updated 7 October 2026
This is a translation. Roaden is run from Spain and the Spanish version of this document is the one that is legally binding. It is at /privacidad. This English text is here so it can be read, and if the two ever disagree, the Spanish one is the one that counts.
The important part, first. A route says where you ride. That is data about you, and we treat it as such: your routes are born private, publishing one is a step you take yourself, and the photographs you upload lose the coordinates of where they were taken before they leave your device.
| Controller | Antonio Olmedo Navajas · Tax ID 26259640B |
|---|---|
| Address | C/ Sevilla, 5B — 18339 Romilla (Granada), Spain |
| Contact | info@roaden.app |
| Your email | It is your account and it is how you get in: we send you a six-digit code. Basis: performance of the service you asked for (art. 6.1.b GDPR). |
|---|---|
| Your alias and language | The alias is what other people see on your public routes — one is generated for you and you can change it. The language decides which one we write to you in. Basis: performance of the service. |
| Your routes | The points, the line, the tags and the notes. They are the service. Basis: performance of the service. |
| Your photographs | The ones you upload to a route. Basis: performance of the service. |
| Your reviews | The stars and the comment you leave on somebody else's route. They are read before they are published, one by one and by a person on our team — see below. Basis: performance of the service. |
| Your recorded rides and the GPX files you upload | If you record a ride, we keep where you went and six figures your phone works out: moving time, average and top speed, climb and lean. If you upload a GPX, we keep the track the file brings. They are born private, like routes, and publishing them is a step you take. Basis: performance of the service. |
| Your subscription | If you pay, we keep which plan you have, whether it is still active and until when it is paid for, plus the identifier the payment gateway or the store gives us so we can recognise your purchase at each renewal. We never see your card: the payment details travel to Stripe, to Apple or to Google, not to us, and all we know is whether a charge went through. Basis: performance of the contract (Art. 6.1.b GDPR), and legal obligation for invoicing (Art. 6.1.c). |
| Your phone's identifier, if you turn notifications on | When you allow notifications, the app registers on our server a token identifying that installation — not your phone and not your number — together with the platform and the language the device reported. It is what makes a notice reach that phone and no other. You can turn them off, by type, from your profile or from the system settings; and the token is deleted when you uninstall, when the store tells us it is no longer valid, or when you delete your account. Basis: performance of the service. |
| The road alerts you post | What you are warning about, the exact point, and that it was you — so that you can remove it and so that somebody answers for what it claims. Any rider passing there sees it, without your name, and after six hours the alert stops being shown and your name is stripped from it. It is all in Road alerts. Basis: your consent when you tap it. |
| Server logs | IP address, date and what was requested. They keep the service working and let us spot abuse. Basis: legitimate interest in keeping it up and secure (art. 6.1.f). |
A photograph taken on a phone usually carries inside it the coordinates of where it was taken. If that photo was taken in your garage, those coordinates are your house.
So Roaden re-encodes the image on your own device before uploading it: it is shrunk and written out again, and in that step every piece of metadata is lost, including the coordinates and the camera model. What reaches the server is a photograph with none of that.
Before a review is visible to anybody else, and before it counts towards a route's average, it is read. It is how the first offensive review does not also become the first one somebody sees.
That reading is done by a person on our team. No automated system decides whether your review is published.
If we do not publish your review, you can ask us why by writing to info@roaden.app. We will answer, without asking you why.
If some of that reading is ever done by an automated system, we will say so here before it happens, and you will still be able to ask for a person to look at it.
Whoever reads it sees the text, the stars and which route it belongs to. They do not see your email or anything else from your account. If we do not publish it, we tell you why.
No automated system decides anything about you: not your reviews, not your account, not your subscription, not your routes. And if at any point an outside provider does that reading, we will say so here, with its name and its country, before we start using it.
This is the part we most want to get right, because a route app is exactly where somebody would expect to be followed around. We do not do that, and these are the four times your position reaches us. There is no fifth.
There were three until 5 October 2026. The fourth — posting a road alert — is new, and we say so up here rather than burying it in the list, because it is the only one where a position of yours is kept.
| Finding what is near you | When you ask for routes or meet-ups near you, your phone sends those coordinates so we can filter. They are not saved to your account and they are not tied to you in any table: they are used for that search and they end there. What does happen, and we say it because it is true, is that the request stays in the server logs like any other, with its IP, and those are deleted after 90 days. If you do not give location permission the search still works: it shows you what there is, without sorting by distance. |
|---|---|
| Recording a ride | If you record, your phone keeps where you pass, with the screen off and the app in the background too, because otherwise the recording would have holes. It is uploaded when you finish and it is born private. This never starts by itself: you switch it on and you stop it. |
| Sharing it inside a meet-up | So the people riding with you can see you. It is the only case where your position reaches other people with your name beside it, and it has its own rules: they are all below. |
| Posting a road alert | If you warn that there is gravel, loose animals or the road is blocked, you send the exact point where you are at that moment, because the alert IS that point. We keep it, any rider passing there sees it — that is what it is for — and it stays tied to your account, so that you can remove it and so that somebody answers for what it claims. Your name and your alias never appear beside it: other people see «bad surface, 2 hours ago, reported by 3 riders» and nothing else. Everything there is to know is in Road alerts. |
Navigating, on the other hand, sends nothing: the route is already on the phone and the following is done by the phone alone. If you are not recording and not sharing inside a meet-up, we do not know where you are.
On a meet-up you can switch on sharing your position so the others can see you on the map while you ride. It is always off until you switch it on, and these are all the rules:
Basis: your consent, given when you switch it on and withdrawn when you switch it off. Your phone will also ask for its own permission, and you can take it away from us in your system settings at any time.
Think twice before switching it on if you are leaving from home: while it is on, the people on that meet-up can see where you are. That is exactly what it is for, and it is why you decide every time.
Inside a quedada you can tell the group three things with a single tap — «I need fuel», «I need a break» and «I have a problem» — and it reaches them as a notice on their screen. It is the opposite of a road alert, so it is worth seeing side by side:
Basis: your consent when you tap it.
You can warn about what is on the road so that the riders behind you see it: bad surface (gravel, potholes, a slick patch), loose animals and road blocked (roadworks, a landslide, snow). Three and no more, on purpose: with gloves on and moving, nobody picks from five.
Reading an alert is free and asks nothing of you. Posting one does, and this is what happens when you do:
| What you send | The exact point where you are at that moment, what you are warning about, and the time. The alert IS that point: without it there is nothing to tell. |
|---|---|
| Who sees it | Any rider passing there, which is what it is for. An alert only your friends could see protects nobody. |
| What they see of you | Nothing. They see «bad surface, 2 hours ago, reported by 3 riders». Your name, your alias and your photograph do not appear — not on the map, not when tapping the alert, nowhere. |
| What we keep about you | That it was you, for three specific reasons: so that you can remove it; so that somebody answers for what it claims — an alert nobody answers for is a road full of invented hazards; and so that you cannot report the same thing twice. That last one is what makes «reported by 3 riders» mean three people and not three taps. |
| For how long | As long as the alert lasts: six hours. After that (plus a day of margin, in case somebody confirms it and it comes back) a nightly task strips your name from it. The alert stays, with no owner and with no way to tell whose it was. And the number of people who saw it stays too: that is still true and it no longer points at anybody. |
You need «visible» switched on to post one. That is not a whim: it is the same thing said the other way round — an alert carries somebody who answers for it, so it cannot be posted by somebody who wants nothing known about them. Looking is free; claiming carries your name behind it, even though nobody but us sees it.
And if you delete your account, the alert does not go with you: it is left without a name. The gravel is still in that bend even though you are gone, and removing it because you left would take away information that protects the riders behind you. What goes is the link to you, which is what the right to erasure actually asks for.
Basis: your consent when you tap the alert. And for the alert once it has no owner, our legitimate interest — and that of anybody riding through that bend — in that information staying there: by then it is no longer data about you, because it cannot be tied back to you.
Two things you can do at any time: remove an alert of yours from the map itself, and say that somebody else's is no longer there — one person saying so is enough to withdraw it. We would rather err on the side of too few: one alert that is not true teaches people to believe none of them.
It is the «I let myself be seen while I ride» switch. It does two things: let you post road alerts and draw you on the map of the other visible riders around you.
That second part is new as of 7 October 2026. Until that day being visible sent your position to nobody outside a quedada, and this very page said that if one day you could see who is riding nearby it would be a new feature and it would be said here. This is that feature and this is us saying it.
Basis: your consent, given when you switch it on.
The app shows the fixed speed cameras and the average-speed sections on the road. There is no data of yours in this, and it is worth saying where they come from and what we do not do:
Basis: legitimate interest in the map's information being on the map. There are no personal data to handle here.
Only whoever is needed for this to work:
| OVH Groupe SAS | The server where everything lives, and the mail your code is sent from. France · EU |
|---|---|
| Google Ireland Ltd. | Several different things, and they are worth not confusing: the planner — its map is drawn by Google, in your browser on the web and with its own component inside the app, so in both cases it receives your IP and what you look at on the map; the maps on your routes, on Explore and on meet-ups are ours and go through nobody; the information about places, which our server asks for, not you; on Android, the notifications (Firebase Cloud Messaging) and the subscription (Google Play); and the crash reports its components send when something breaks inside the app — which version, which phone model and where it failed —, which we use to fix it. Ireland · EU, with possible access from the USA. |
| Apple Distribution International Ltd. | On iPhone, the notifications and the subscription if you took it out inside the app. Ireland · EU, with possible access from the USA. |
| Stripe Payments Europe Ltd. | The payment, when you pay from the web. Your card details travel to Stripe and not to us; we only receive your email, whether the charge went through, and the identifiers with which to recognise your subscription. Ireland · EU, with possible access from the USA. |
| Microsoft Ireland Operations Ltd. | Analytics on the presentation page, only if you accept and today not even switched on. Never inside the application. See Cookies. Ireland · EU, with possible access from the USA. |
Any transfers outside the European Economic Area that may occur with Google, Apple, Stripe and Microsoft rely, as all of them declare, on the EU–US Data Privacy Framework and on standard contractual clauses.
The text of a notice is written by our server — "Marta likes your route", "somebody is asking for a place on your meet-up" — because it is the only way for it to reach you in the language you chose and not in the phone's system language. That means Apple or Google see that text as they deliver it, the way a mail service sees the subject of a message.
That is why a notice never carries more than fits on one line of a lock screen: the alias of whoever did something, and what it is about. Your email never travels, nor your position, nor the line of a route. And if you turn them off in your profile, nothing goes out — the notices are still kept in your tray inside the application, which is ours.
We say it here and not in small print, because it is the exception to «they go with it»:
There is nothing else. Not your routes, not your photographs, not your reviews, not your meet-ups, not your alias, not your address anywhere else.
You can ask for access, rectification, erasure, objection, restriction and portability by writing to info@roaden.app from your account's address. We answer within a month at the most.
Two of them you can exercise yourself without asking us for anything: download any route as GPX, and delete it, photographs and all, from "My routes".
If you think we are getting it wrong, you can complain to the Spanish Data Protection Agency. We would rather you wrote to us first.
If this changes in any meaningful way, we will tell you by email before it happens. The date at the top is the date of the current version.