Privacy Notice — RideRadar

Last updated: 19 September 2026

This is the same notice you read inside the app: app and website show the same text and are updated together.

1. Data controller and contact details

Service provider and data controller: Giovanni Oliverio, independent developer (natural person), Italy. Email: assistenza@rideradar.it. A person replies, not an automated system. Business activity: development and operation of the RideRadar app and the rideradar.it website. For any question about your data, and to exercise the rights in section 10, write to this address.

2. In brief

The controller is Giovanni Oliverio (assistenza@rideradar.it). We collect your account and the profile you fill in; your location only while you use the map, navigation, rooms, SOS, photos taken in the saddle, speed camera alerts, place search, weather and the assistant, plus an approximate point for your Feed area; the rides you save; your photos, stripped of hidden data; your live voice, never recorded. No advertising, no profiling, no selling of data. Today there is nothing to buy in the app. The data sits on servers in Ireland; the route engine is in Germany. Maps, rooms, voice and the assistant go through providers in the United States, with the safeguards in section 7. A ride you publish also has a web page open to anyone with the link, showing your nickname and the bike on your profile. We keep them for as long as you have your account; error reports for 30 days, usage measurement for 90. You delete everything from Settings > Delete account. If something is wrong, write to us or to the authority in your country (section 10). There is only one version of this notice: the same in the app and at rideradar.it/privacy-policy, updated together. The rest of the page explains it in full.

3. The data we collect, item by item

• Account data: email and sign-in identity (including Google sign-in). We also keep your age declaration (section 11) and the date you made it.
• Profile: nickname (you choose it, and it signs everything you publish), handle, avatar, bio, your gender if you choose to state it (it does not appear on your profile and no other user sees it), riding statistics (total kilometres and rides) and, if you enter them, the name you want to be greeted by and the bike model given in your profile — or, if you have a Garage, the make, model and year of your main bike. Your profile is visible to other registered users. For moderation purposes your profile also carries a trust score, a strike count and, where needed, a watchlist flag (section 5): the app does not show these to other users.
• Feed and social: who you follow and who follows you, the likes and comments you leave on published rides, and the fact that you have shared a ride: other registered users can see them. When you start navigation on a ride published by another rider, the server notes that you have ridden it, for the count shown under that ride. Bookmarks (the rides you set aside) and the list of rides you hide from the Feed are private: only you see them.
• Feed area: to show you the rides in your area, the server keeps an approximate point (a cell of about 10 km, not your exact location) that comes from your phone's location the first time you open the Feed, and that you can move yourself by choosing a town or tapping “Use my location”, at most once a day; the search radius goes from 25 to 200 km. It is private: no other user sees it.
• Garage: make and model of your bike and, if you choose to enter them, number plate, frame number, insurance details, photos of the bike, logbook and insurance document, refuelling and maintenance. The make, model and year of your main bike appear on your profile; everything else is private: no other user sees it.
• Rides: while you ride, the track stays on your phone. When you save a ride, the track — position, time and speed of every point, with the system flag that says whether the location was mocked — goes to our server, together with start, finish, dates, durations, statistics and, if measured, the number of leans detected and the maximum lean angle. This is needed to keep the ride in your ride log and to check that it is real before crediting the coins: it is part of the feature you asked for. If the check finds something anomalous — a mocked location, impossible jumps, off-the-scale speeds — the server records a flag with your identifier, lowers your trust score, puts you on the controller's watchlist and does not credit the coins for that ride (section 5). While saving, the coordinates of the starting point are sent to Photon (or to Nominatim, section 7) to work out the name of the municipality shown under the ride: only the name stays on the ride, not the point.
• Published rides: if you publish a ride, other registered users see it in the Feed, with the track trimmed at the start and at the finish. The ride also has a web page on rideradar.it, reachable by anyone with the link, without an account: it shows the title and description you wrote, your nickname, the bike on your profile, the starting place (the name of the municipality, not the exact point), the date, the kilometres, the duration and the statistics of the ride, and the track with start and finish trimmed. You are the one who gives out the link, from the Share button; the page asks search engines not to index it; whoever opens it reads the data from our database, which sees the visitor's network address. If you unpublish the ride, the page disappears.
• Ride and profile photos, with the point where they were taken. The point comes only from the app's GPS: before saving, our server regenerates the image and throws away the camera's hidden metadata (EXIF, coordinates). Photos taken near where you started or finished stay private and do not appear on the public map, unless you choose to show them. You can delete them whenever you like.
• Other people in your photos: if a photo shows recognisable people or number plates, it is up to you to have their consent before publishing it; we do not identify them and do not analyse them. Anyone who sees themselves in someone else's photo can ask for it to be removed by writing to assistenza@rideradar.it.
• Contributions on mountain passes: the photos you upload, the comments you write and the star ratings you give on the pass pages. They are public content, visible to all registered users with your nickname. You can delete them whenever you like, and for these photos too the server regenerates the image and discards the hidden metadata.
• Location: during a navigation session or inside a group room we collect your real-time location — even with the screen off, through an Android foreground service with a notification that is always visible; the app does not ask for the background location permission — to let you navigate, record your route, warn you of hazards and show you on the map to the members of your room. When you leave the room or stop navigation, sharing stops. If you pause navigation, the destination, the stops, the track and the point where you stopped stay on your phone until you resume or delete it. Your location leaves your phone only for a feature that needs it and while you are using it: map, navigation, room, SOS, photos taken in the saddle, speed camera alerts, place search and weather, Feed area, the name of the starting municipality when you save a ride, and the assistant when you ask it something.
• Speed camera alerts: they come from the provider's catalogue (section 7). To show them to you, the app asks our server for the points around you or along your route: your location reaches our server, never the catalogue provider. The app does not collect reports from riders: submission has been switched off since 19 August 2026. The few reports collected before then remain in the database, with the reported point, the reporter's location and their identifier; they are not shown to anyone and disappear with the account of whoever made them. If the feature comes back, this notice will change first. In Germany, France and Switzerland, where the law prohibits them, the alerts are switched off.
• Telemetry and sensors: speed, heading, accelerometer and gyroscope are used for navigation, crash detection and the ride statistics you asked for (average and maximum speed, maximum lean angle), which you find in your ride log and can choose to publish or to share with the assistant. They stay on your phone until you save the ride.
• SOS: if crash detection triggers and the call for help goes out, your location is sent to the riders in your room, and to them only. If you are not in a room, the SOS does not go out, and your phone tells you so. It is not an emergency service and it is not a medical device: if you are in danger, always call 112.
• Voice: in voice rooms your voice reaches the other members live through LiveKit's servers. We do not record your voice and we do not ask LiveKit to record it: it just passes through. We keep only a usage log — room attendance, counted sessions and the seconds of voice used per day — to enforce the limits of your plan.
• Voice dictation: when you dictate a search or a question, the transcription is done by your phone's speech recognition service (on Android, normally Google's), which depending on the phone may also process the audio on its own servers. We receive only the transcribed text, never the audio.
• AI Rider assistant, only if and when you use it: the text of your questions and the previous questions in the same conversation, which the app keeps in memory only until you close it. With every question your current location, if the app knows it, and the day and time are also sent: they are used to suggest rides from where you are. Your Garage bike data (make, model, year, engine size, kilometres) is sent only in Mechanic mode; the numbers of the ride you have just finished (distance, duration, ascent, hairpins) only in Telemetry mode. If you do not use it, nothing is sent. AI Rider is an artificial intelligence system, not a person: the answers come from a language model provided by Anthropic (section 7). Conversations are not saved: neither on our servers nor on your phone. Only the count of daily requests remains, for the limits of your plan.
• Medical details and emergency contacts: blood group, allergies, medical notes and contacts you enter yourself. They stay encrypted on your phone only (Android Keystore): they never reach our servers, they are wiped if another user signs in on the phone and they disappear when you uninstall the app. On a phone updated from an older version an unencrypted copy of these details may also remain until you reopen the page where they are filled in: that page moves it into the encrypted store and deletes the original. If crash detection triggers and the call for help goes out (or fails to go out), these details open by themselves on the screen, read-only, so that whoever comes to your aid can read them from your phone; they close by holding the screen down for five seconds, and they reopen from the SOS panel or from the profile menu. The phone's lock screen stays in place: if the phone is locked, or if another app is in front at that moment, the details are not visible until someone brings RideRadar back to the front. After an SOS a line also appears on the lock screen, saying how the call for help went and that there are rescue details on this phone: that line contains none of these details. The message to the room does not contain them. Fill these details in knowing that, at that moment, they are read by whoever is holding your phone.
• Reports: if you report a ride, a photo, a comment or a rider, the server keeps the report: who reported, who or what was reported, in which room if it happened there, the reason chosen from a closed list, the date, and when a person saw it and took it on. There is no free text. The controller reads it, for moderation (section 5).
• Blocked riders: if you block someone, the server keeps the pair — you and that person — and the date. It is used to make you disappear from each other: the block works both ways. The list is private and only you see it, in Settings > Blocked riders; the blocked person receives no notice and has no way of knowing it exists. The entry disappears when you remove the block or when either of the two accounts is deleted.
• Technical device data (model and operating system): we read them only when we compile an error report (section 4).
• Notifications: no push tokens and no third-party notification services. Notifications originate on your phone or from entries written in our database and visible only to you.
• Payments and advertising: today there is nothing to buy in the app and there is no advertising. We do not collect payment data and there is no advertising network. If we introduce subscriptions, this notice will change first.
• Rate counters: to stop abuse, the server counts how many times your account calls certain features in a given period, for example the Feed. They are numbers and times, with no content.
• Error reports and usage measurement: they have a section all of their own, section 4. They are not anonymous and they are not only about crashes.

4. Error reports and usage measurement

These are the only two processing operations the app starts on its own. They are separate, have two different legal bases and two distinct switches, which you find in Menu > Report a problem.

What an error report contains. It is compiled when the app runs into an error, when it notices that the previous session ended abruptly, or when you request it yourself from the “Report a problem” screen. It contains the following, and nothing else:

• Installation identifier: a random 128-bit number generated by the app the first time you open it. It is not a phone identifier, it cannot be read by other apps, it does not follow you elsewhere and it disappears when you uninstall RideRadar. It is used to tell “a hundred phones with the same defect” apart from “one phone that runs into an error a hundred times”.
• Your account identifier, but only if you were signed in at that moment. It is used to find the report again if you write to support: that is its only intended use.
• Technical data: model, manufacturer, operating system version, app version and build number.
• State of the phone at the time of the error: free and total memory, free disk space, battery level and whether it was charging, connection type (wifi, mobile data, none — never the network name), system language, system text size.
• Sequence of the app's most recent state changes (fifty at most), each with how many seconds earlier it happened: which screen was opened or closed, chosen from a closed list; navigation started, ended or recalculated; entering and leaving a room; GPS signal lost and regained; ride saved and published; name of the network operation that failed. Only the name of the event: never where you were, never which route, never what you wrote.
• Technical description of the error: type, message and the first six lines of the stack trace. The message goes through an automatic clean-up that removes email addresses, web addresses, keys, tokens and geographic coordinates. One thing you should know: an error message is written by the program that ran into the error, and it may contain a fragment of the text that caused it. The reports you send yourself from the “Report a problem” screen you see in full before sharing them; automatic reports go out without passing through you. If you would rather always see them, turn the switch off and send them by hand whenever you like.

What usage measurement contains. It serves to answer four questions about the product: how many people open the app, how many complete a ride, how many publish, and at what point they stop. It is made up of just ten event names, each accompanied by the moment it happened: avvio_app, primo_avvio, accesso_mostrato, accesso_riuscito, posizione_concessa, posizione_negata, navigazione_avviata, giro_completato, giro_salvato, giro_pubblicato. There is no parameter next to these names: not which route you published, not where in any form, not how long it lasted or how long it was, no text written by anyone. This data does not carry your account identifier (the table that stores it simply has no such column) and does not carry the installation identifier of the error reports either: it travels with a second key, drawn separately, which makes it impossible to trace back either to the reports or to your account. If you do not turn usage measurement on, that key is not even generated.

The two switches, and how they start out.

• Error reports: they start out on. To make them work, the app writes the random installation number to your phone on first launch and reads it back with every report. We do this without asking for your consent because we consider it strictly necessary to keep the service you asked for stable: this is allowed by the European ePrivacy Directive (Article 5(3)) — in Italy Article 122 of the Privacy Code, in Germany the TDDDG Act, in France the Informatique et Libertés Act, in Slovenia the Electronic Communications Act. This is a reading that some European authorities dispute, and for that reason you can turn the reports off whenever you like. When you turn them off we throw away whatever was waiting to be sent; the installation number stays written on your phone until you uninstall the app, and is used only if you send a report by hand yourself. On our side, the processing of the reports rests on our legitimate interest (Art. 6(1)(f) GDPR) in keeping the service secure and stable: they are technical data and profile no one. You can object (Art. 21) simply by turning them off.
• Usage measurement: it starts out off. It is not necessary to provide the service, so it requires your consent (Art. 6(1)(a) GDPR and the same rules on the phone). Until you turn it on yourself, no usage event is sent or written to your phone. It is not a form of payment: the app works exactly the same with the switch off. You can withdraw your consent whenever you like from the same switch: we throw away whatever was queued and send nothing more; the key already drawn stays on your phone, unused, until you uninstall the app.
• A third number, which is not ours: the Mapbox map kit writes a random identifier to your phone with which Mapbox counts active installations and bills us for the service. We consider it necessary for the map you asked for, by the same reasoning as the error reports; it contains no name, email or location and is not linked to your account (section 7).

Where they go, how long they stay, who else sees them.

• No third-party provider: no Firebase Crashlytics, no Sentry, no behavioural analytics tool. The data goes straight into the RideRadar database and does not leave it.
• No coordinates and no addresses: neither the reports nor usage measurement contain your location, in any form.
• One counter per day: so as not to be flooded, the server counts how many reports and how many usage events it receives each day from each installation. It is a number next to a key, with no content, and it disappears after 2 days.
• Retention: an automatic job runs every night on the server and deletes error reports after 30 days and usage events after 90 days.
• Account deletion: the error reports linked to your account are deleted together with the account, at the same instant. Reports sent without being signed in were never linked to you and delete themselves anyway within 30 days.

5. Automated processing of content and moderation

This section describes what the system does today: if one day we do more, it will change first, not afterwards.

Photographs are cleaned before they become visible. When you upload a photograph, the server regenerates it and reduces its size. In the regeneration the file's hidden data is thrown away, starting with the GPS position that many cameras write into the shot. This is to prevent a photo of your bike in the garage from telling anyone where you live. It is a technical process: it does not look at the content of the image, it rebuilds it.

A word filter. Before publication, an automatic filter compares the text of rides, comments, name and profile against a list of words that insult a person for who they are: if it finds one, the text is not published and we tell you. The filter knows only Italian and does not read context. It is the only automatic rejection of content that exists in the app. Everything else is published immediately and is checked by a person, on the basis of reports. If a text of yours is stopped, you can write to assistenza@rideradar.it and a person will read it again.

What we do not do. No automated system looks inside your photographs: we do not recognise number plates, we do not recognise faces, we do not classify the subject. No artificial intelligence analyses your images.

The checks on rides. When you save a ride, an automatic check reads the track (section 3). If it finds a mocked location, impossible jumps or off-the-scale speeds, it records a flag with your identifier, lowers your trust score, puts you on the controller's watchlist and does not credit the coins for that ride. It does nothing else: it does not touch your content and does not close anything. If you think it got it wrong, write to assistenza@rideradar.it and a person will review the ride.

Decisions about your account. To protect the community, your profile carries a trust score, a strike count and, where needed, a watchlist flag, fed by reports from other users and by the checks on rides. Automatic enforcement of penalties is switched off (verified on 5 September 2026): no algorithm adds strikes, reduces the visibility of your content or closes your account. The decisions that matter — reducing the visibility of your public content, suspension, closure — are taken by a person, not by an algorithm; if one day we turn automatic penalties on, we will update this notice first. If a decision concerns you and you disagree with it, you can ask for it to be reviewed by writing to assistenza@rideradar.it: a person will look at the decision again from scratch.

6. Why we use them, and on what legal basis

We use your data for: the map and navigation, with speed camera alerts and speed limits; group rooms with real-time location and voice; safety (crash detection and SOS); your ride log, with statistics and photos, and their publication if you choose it; the Feed and the social features (who you follow, likes, comments, bookmarks, shares); the Garage with reminders and due dates; in-app progression (RR Coin, missions and levels) and the limits of your plan; moderation and defence against abuse; fixing the app's defects. Your location leaves your phone only for a feature that needs it and while you are using it (section 3); outside a session, all that remains on the server is your Feed area — an approximate point, not a track — and the rides you chose to save.

Every processing operation rests on a stated basis:

• Account, navigation, map, Garage, rooms and voice, Feed and social, RR Coin, missions and levels, the assistant when you are the one asking it, and the content you choose to publish: performance of the contract (Art. 6(1)(b) GDPR). These are the things you installed the app for.
• Location during navigation and rooms, and in the other features in section 3 that need it: performance of the contract (Art. 6(1)(b)). The system permission remains yours and can be revoked from your phone at any time: from that moment the feature stops working, and that is your right.
• Crash detection and SOS message: performance of the contract (Art. 6(1)(b)) and, at the moment of sending, vital interests (Art. 6(1)(d)).
• Medical details and emergency contacts: they have no basis in this list for a simple reason: they stay encrypted on your phone only and never reach our servers, so we do not process them.
• Security, abuse prevention, automatic checks on rides, rate counters, moderation and error reports: legitimate interest (Art. 6(1)(f)). You can object (Art. 21).
• Usage measurement: consent (Art. 6(1)(a)), which you give and withdraw from its switch.
• Legal obligations, such as keeping a deletion request received by email so as to be able to prove that we carried it out, and disclosures to the authorities in the cases in section 7: legal obligation (Art. 6(1)(c)).

What is compulsory and what is not. To have an account you need an email (or Google sign-in), a username and the age declaration: without them, the account is not created. The location permission is needed for the map and navigation, rooms, SOS, the point of the photos you take in the saddle and, the first time you open the Feed, to set your area: if you refuse it these features do not start, you choose your Feed area by hand and the rest of the app works; the permission remains yours and you revoke it from your phone. Garage, photos, contributions on passes, assistant, voice, dictation and usage measurement are optional: if you do not use them you miss out on nothing. Medical details stay on your phone only.

7. Providers and transfers outside the European Union, one by one

The providers below are of three kinds. The first ones process data on our behalf and follow our instructions: Supabase, Mapbox (for the maps), Cloudflare, Hetzner, LiveKit, Anthropic, Hostinger. Others are services that decide for themselves how to process what they receive, under their own rules: Google for sign-in and for system dictation, Mapbox for the count it bills us on and for what its kit collects by itself, and the open place-search and weather services (Photon by komoot, Nominatim by the OpenStreetMap Foundation, Overpass, Open-Meteo), which have no contract with us. The last ones receive none of your data: SCDB, from which the speed camera catalogue comes to us, and the house-number archive copied onto our server. When a request goes out from your phone (maps, place search, weather), that service also sees your phone's network address. We do not sell your data to anyone. Error reports and usage measurement do not go through any of these: see section 4.

• Supabase Pte. Ltd (Singapore): database, accounts and files (avatars, ride and pass photos, bike photos and documents). The data sits in our project's European region, in Ireland, on AWS servers; the data processing agreement with Supabase contains the European Commission's standard contractual clauses for technical access from outside Europe; its sub-providers are listed on its sub-processor page. The database has daily backups, kept for 7 days (section 9).
• Mapbox, Inc. (Washington DC, United States): the maps. It receives your location to draw them and, with every request, your phone's network address (which it states it deletes within 30 days) and a random billing identifier, written by the kit to your phone, not linked to your account and kept for longer. The usage events its kit would collect on its own we turn off at app launch on Android; what remains is the count of active users that Mapbox bills us on, which no setting disables and which does not say where you have been. Basis for the transfer: EU-US adequacy decision (Data Privacy Framework), active certification.
• Cloudflare, Inc. (101 Townsend St., San Francisco, CA 94107, United States): hosts and protects the rideradar.it website (Cloudflare Pages) — like any hosting provider, it sees the technical browsing data of those who visit it —; runs the real-time channel of the rooms, receiving the position, heading and speed of the riders in a room for as long as the room is open; protects our route engine, and therefore passes through to it the calculation requests (start, stops and destination) and, for speed limits, the points of the calculated route; acts as the gateway for the connection to the voice service (LiveKit, below). Basis for the transfer: EU-US adequacy decision (Data Privacy Framework), active certification.
• Hetzner Online GmbH (Germany): the server our navigation engine runs on, in the Falkenstein data centre, in Germany. It receives the start, stops and destination of the routes you ask it to calculate and, for speed limits, the points of the calculated route.
• LiveKit, Inc. (San Jose, California, United States): the voice in the rooms, in transit only. It receives your voice stream and your account identifier, to connect you to the right room. We do not record your voice and we do not ask LiveKit to record it. Basis for the transfer: EU-US adequacy decision (Data Privacy Framework), active certification.
• Anthropic, PBC (United States): the language model behind the AI Rider assistant. It receives data only if and when you use it: the text of your question and of the previous questions in the same conversation; with every question also your current location, if the app knows it, and the day and time; in Mechanic mode your Garage bike data; in Telemetry mode the numbers of the ride you have just finished. The request goes out from our server, not from your phone: Anthropic sees the server's address, not yours. Anthropic states that it deletes questions and answers within 30 days, except for violations of its usage policies (up to 2 years, with the classification scores alone up to 7 years), and that it does not train its models on the content of API customers. We do not save the conversations: neither on our servers nor on your phone, only the count of requests. Basis for the transfer: the European Commission's standard contractual clauses, in the data processing agreement with Anthropic (Anthropic is not enrolled in the Data Privacy Framework).
• Google LLC (Mountain View, California, United States): Google sign-in, if you choose to use it — we receive the email and identity of your Google account — and your phone's speech recognition service (on Android, normally Google's), only when you dictate by voice. Google processes this data under its own rules. The fonts are bundled in the app and are not downloaded from Google's servers. The store you install the app from (Google Play) processes the installation data under Google's rules. Basis for the transfer: EU-US adequacy decision (Data Privacy Framework), active certification.
• SCDB / Eifrig Media (Germany): the provider we buy the speed camera data from. The flow goes from them to our server: none of your personal data reaches them.
• Photon (komoot GmbH, Schönefeld, Germany): address and place search and the conversion of a point into a place name (for example the starting municipality of the rides you save). It receives what you type in the search, the point to search around or to convert, and your phone's network address.
• Nominatim (OpenStreetMap Foundation, United Kingdom): the same search and the same conversion, when Photon does not respond. It receives what you type, the point to search around or to convert, and your phone's network address. The United Kingdom is recognised as adequate by the European Commission (Decision 2021/1772, renewed by Decision 2025/2574, valid until 27 December 2031).
• Overpass API (overpass-api.de server, run by FOSSGIS e.V., Germany): the points of interest along the route (cafés, petrol stations, passes). It receives the area you are searching in and your phone's network address.
• Open-Meteo (OpenMeteo GmbH, Bürglen, Switzerland): the weather along the route. It receives the coordinates of a few points on the route (to four decimal places), without any identifier, and your phone's network address; it states that it keeps server log files for 90 days. Switzerland is recognised as adequate by the European Commission.
• House numbers: they come from the national ANNCSU archive (Agenzia delle Entrate and Istat, open data CC BY 4.0) copied onto our server. Searching for a house number does not leave our systems and none of your data goes to the archive.
• Hostinger, UAB (Vilnius, Lithuania, European Union): the support mailbox. It receives what you write to us.
• Police or judicial authorities: only if a piece of content gives rise to suspicion of a criminal offence that threatens someone's life or safety (Article 18 of the European Digital Services Act, Regulation (EU) 2022/2065), or by order of an authority. Basis: legal obligation (Art. 6(1)(c)).

Transfers outside the European Union. Mapbox, Cloudflare, LiveKit, Anthropic and Google are based in the United States: data sent to them is a transfer outside the Union (Chapter V of the GDPR). For Google LLC, Cloudflare, Inc., Mapbox, Inc. and LiveKit, Inc. the European Commission's adequacy decision of 10 July 2023 (EU-US Data Privacy Framework) applies: we verified their enrolment on the official list on 5 September 2026; in addition, and for Anthropic as the only safeguard, the European Commission's standard contractual clauses apply. With Supabase the contract is with a Singapore company, with the standard contractual clauses; the data sits in Ireland. Nominatim (United Kingdom) and Open-Meteo (Switzerland) are in countries recognised as adequate. You can ask for a copy of these safeguards by writing to assistenza@rideradar.it. The safeguards apply regardless of how you use the app; on top of that, be aware that the assistant and group rooms are optional features: without them, the only parts of your location that go to US providers are the requests with which the Mapbox map is drawn around you and, when you calculate a route, the start, stops, destination and route points, which pass through Cloudflare's network to our engine in Germany.

8. The rideradar.it website

The rideradar.it website uses no cookies, neither technical nor profiling ones, loads no third-party scripts, fonts or analytics tools and tracks no one: that is why there is no cookie banner. It is served by the network of Cloudflare, Inc., which in providing the service processes technical connection data (network address, request headers) as a processor on our behalf. The shared ride page (rideradar.it/p/…) reads the data from our database (Supabase), which sees the visitor's network address. The account deletion form on the website is an email: it opens your email program addressed to assistenza@rideradar.it.

9. Retention

We keep the data for as long as the service needs it. The periods with a number are the ones an automatic job actually enforces on the server:

• Live location in rooms: minutes. An automatic check runs every two minutes: it removes from the room anyone who has been silent for more than 15 minutes, deletes positions left without a room and older than 15 minutes, and closes rooms that have been empty for more than 5 minutes.
• Error reports: 30 days. Usage events: 90 days. Daily diagnostics counter: 2 days (section 4).
• Voice log: counted sessions are deleted after 3 days by a nightly job; attendance records last as long as the session; the daily counts of voice seconds and of requests to the assistant remain for the life of the account.
• Feed area: for the life of the account, until you change it.
• Profile, rides, photos, contributions on passes, Garage: until you delete them or delete your account.
• Feed and social (who you follow, likes, comments, shares, bookmarks, hidden rides), notifications, flags from the checks on rides and rate counters: for the life of the account; no automatic job deletes them earlier.
• Old speed camera reports (collected before 19 August 2026): for as long as the account of whoever made them exists.
• Age declaration: the date you made it stays for as long as the account exists.
• Blocked riders: until you remove the block or either of the two accounts is deleted.
• Reports you make or receive: for as long as moderation needs them; they disappear when the account of the reporter or of the person reported is deleted.
• Emails to support: for as long as handling the request needs them. Account deletion requests received by email or from the website form (which is an email): we keep that email for as long as needed to prove that we carried it out; deletion done from the app leaves no record.
• Backups: the database has automatic daily backups, kept for 7 days by the provider and then overwritten: a deleted item can survive there for that long. They are used only for restoration in the event of a failure: they are not used to recover data you have asked to have deleted.

10. Your rights and how to exercise them

The European Regulation grants you these rights, and we list them all so that you know you have them:

• Access (Art. 15): to know which of your data we process and to get a copy of it.
• Rectification (Art. 16): to have incorrect data corrected. Profile, Garage and rides you can also correct yourself, in the app.
• Erasure (Art. 17): from the app, from the website or by email (section 12).
• Restriction (Art. 18): to ask that the data be kept on hold, without being used, while a dispute is ongoing.
• Portability (Art. 20): to receive them in a machine-readable format, to take them elsewhere. Your rides you export as GPX directly from the app, from the rides screen; profile, Garage and comments we send you in a machine-readable format if you write to us.
• Objection (Art. 21): to object to processing based on our legitimate interest.
• Withdrawal of consent (Art. 7): where processing rests on consent, you can withdraw it whenever you like. It applies from that moment onwards and does not make what was done before unlawful.

To exercise them, write to assistenza@rideradar.it: we reply within one month (Art. 12(3)). If the request is complex the period may be extended by two months, and in that case we tell you within the first month, explaining why.

After your death. You can leave us instructions on what to do with your data — keep it, delete it or hand it over to a person you name — by writing to assistenza@rideradar.it: we honour them. If you leave no instructions, anyone with an interest of their own to protect, your heirs or a person appointed by you can ask us to close the account and delete the data, or to receive it. In Italy you can also, by a written declaration you send us, prohibit others from exercising these rights over your data after your death.

If you think something is wrong. You have the right to lodge a complaint with a supervisory authority (Art. 77). You do not need to write to us first, but if you do we try to sort it out straight away. The Italian Garante is the lead authority; you can also turn to the authority of the country you live in:

• Italy: Garante per la protezione dei dati personali, Piazza Venezia 11, 00187 Roma, www.garanteprivacy.it.
• Austria: Österreichische Datenschutzbehörde, Barichgasse 40-42, 1030 Wien, dsb@dsb.gv.at, +43 1 52 152-0 (the complaint must be lodged within one year of your discovering the matter and in any case within three years).
• Germany: the authority of the Land you live in, from the list kept by the Bundesbeauftragter (bfdi.bund.de > Anschriften und Links); in Bavaria it is the Bayerisches Landesamt für Datenschutzaufsicht, Promenade 18, 91522 Ansbach, poststelle@lda.bayern.de, www.lda.bayern.de.
• France: CNIL — Commission nationale de l'informatique et des libertés, 3 Place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, +33 1 53 73 22 22, www.cnil.fr; the complaint must be written in French.
• Slovenia: Informacijski pooblaščenec, Dunajska cesta 22, 1000 Ljubljana, +386 1 230 97 30, gp.ip@ip-rs.si, www.ip-rs.si.

11. Minors

By our own choice the service is reserved for those aged 16 or over, the same in every country where the app is offered: it involves riding on the road, and we have raised the bar. The law of your country may allow you to give digital consent on your own even earlier — in Italy and Austria from 14, in France and Slovenia from 15, in Germany from 16 — but with us under-16s do not get in, and our threshold applies even where the law sets a lower one. We do not ask for parental consent and we do not ask for your date of birth: since 27 August 2026 we ask you for an explicit declaration, at registration and, if you sign in with Google, on first entry; without it, you do not get in, and we keep nothing else (data minimisation, Art. 5(1)(c) GDPR). We keep the date you made it. If we discover that an account belongs to someone under 16, we delete it, with all its data (Art. 17(1)(f) GDPR). If you are 16 or 17 you are still a minor: this notice is written to be understood by you too.

12. What happens when you delete your account

You can delete your account in three ways: in the app (Settings > Delete account), on the website at the page rideradar.it/cancella-account (which is an email), or by writing to assistenza@rideradar.it. Requests received by email are carried out by a person, within the one-month period in section 10. The operation is irreversible.

What happens, in full. First the files in our storage are deleted (avatars, ride and pass photos, bike photos and documents): if even one of them resists, the operation stops and nothing is left half done. Then the account is deleted and, in a chain with it: profile, rides, photos, comments, ratings and likes, bookmarks, shares, who you follow and who follows you, hidden rides, notifications, contributions on passes, Garage and documents, coins, missions, statistics, Feed area, age declaration, linked error reports, voice usage log, assistant counter, flags from the checks on rides, rate counters, old speed camera reports, room attendance, blocks you placed or received, reports you made or received. The rooms you had created are closed. With the account your public content also disappears — comments, photos and published rides — and the web page of every shared ride: they remain visible to no one. All that remains is usage measurement, which was never linked to your account and disappears on its own within 90 days, and the backup tail in section 9 (7 days). If the request came by email, we keep that email for as long as needed to prove that we carried it out (section 9). Your medical details were never on our servers: they disappear from your phone along with the app.

13. Contact

For any request about this notice or about your data: assistenza@rideradar.it. A person replies. Controller: Giovanni Oliverio, independent developer, Italy.

Terms of Service