Privacy policy

Last updated: 24 October 2026

This policy explains what personal data RevZoom (“the app”) collects, why, and what rights you have. The app is operated by Development Technologies SRL (“we”). Contact: contact@revzoom.eu.

What we collect

Account: your email address and password (stored only in hashed form by our sign-in provider), your username and display name. If you choose Continue with Google (Android) or Sign in with Apple (iPhone), that company confirms who you are and gives us your email address — with Apple, a random relay address if you chose to hide yours — and your name if you share it; we never see your Google or Apple password, and we create the account with no password of its own.
Profile (optional): profile photo, a short bio, your area (a place name you type; we don't show your exact location), the year you started riding, your preferred road types and whether your profile is public.
Garage (optional): your motorcycles (make, model, year, engine size, nickname, photo), their service entries and documents with expiry dates. Service entries and documents are private: only you can see them. Photos of your motorcycles and of your profile are stored so the app can display them, and anyone holding the exact link to such a photo can open it; the links are long and random, and we never publish them.
Routes you create: the points you place on the map, the calculated line, title, description, area, road scores and photos. Drafts are private; published routes are visible to everyone, including people without an account.
Community activity: routes you save, reviews and replies you write (public), riders you follow, and reports you send (visible only to moderators).
Crews (optional): the crews you create or join and your role in them, the rides proposed in a crew (title, note, time, meeting point and, if chosen, a route), who replied that they are coming, and the crew chat. All of this is visible only to the members of that crew.
Subscription (RevZoom Plus, optional): if you subscribe, the payment is handled entirely by Apple (App Store) or Google Play; we never see your card or bank details. We receive which plan you have, when it renews or ends and which store it was bought from, so that the app can unlock Plus.
Technical data: when the app loads map tiles, photos or data, the servers involved receive your IP address and basic device information, as with any internet service.
Security: when you type a wrong invite code for a crew or a group, our server notes your account and the time — not the code you typed — so that nobody can find codes by guessing them one after another. On your phone, the app also counts wrong passwords and codes so that it can impose a short pause; that count never leaves the phone.

Location, and the rides you record

Location is at the centre of what this app does, so it gets its own section.

While you record a ride, the app reads your phone's precise location continuously, including with the screen off, until you finish the ride. On Android a permanent notification stays visible for as long as this runs; on iPhone, a blue indicator in the status bar and a Live Activity with the ride on your lock screen. We ask for the permission the first time, and you can withdraw it at any moment in the phone's settings.
What a recorded ride contains: the line you rode, as points with times and altitude; distance, duration, speed including the maximum, elevation gain, counts of hard acceleration and braking, and — if your phone is mounted on the bike — an estimate of the maximum lean angle. A ride can also be linked to one of your motorcycles.
Your rides are yours. They are not public, and no other rider can read them. The single exception is the group statistics described below, which you enter by choosing to ride with a crew.
The explored map (“fog”). From the rides you upload we keep a coarse grid of the areas you have ridden through, so the map can show where you have been. It is a record of your movements. It lives on your phone and on our server, tied to your account, and it goes when you delete your account.
Approximate location without a ride. When you open the map, the app may read your location once to centre it, if you have given permission. When you open Explore, it reads the position your phone already knows — without asking you for anything and without switching the GPS on — so that the roads nearest you come first. Neither reading is sent to us, and neither is stored.
Which country you are in. If you have not given location permission, Explore uses the country of your mobile network (on Android) or the region set on your phone (on iPhone), so that it can still put roads from around you ahead of roads from the other side of the world. This needs no permission, it is never more precise than a country, and it does not leave your phone. We do not read the language your phone is set to for this.
The app never asks for background location permission, and it does not follow you when you are neither recording a ride nor sharing on purpose.

Sharing your location with other riders

This is always something you start, and it always ends by itself.

With a crew (people you joined using an invite code): you choose 15 minutes, 1 hour, 8 hours, 24 hours, or for as long as your current ride lasts. You can extend a session, but never beyond 24 hours in total. While it runs, the other members of that crew see your position on their map in near real time, with your name and profile photo. The deadline is enforced by our server, not only by the app: once it passes, your position is refused even if the app tried to send it. You can stop earlier whenever you want. On Android a notification with a countdown stays visible the whole time. On iPhone the blue indicator in the status bar stays visible the whole time, and a Live Activity shows the countdown on your lock screen; iOS closes the Live Activity after about 8 hours, while the sharing goes on until its deadline and can still be stopped from the Crew tab.
With a group (a temporary code, at most 24 hours): while you record a ride, the riders holding that code see your position. Nothing from these groups is kept after they expire.
SOS. If you send an SOS, the members of your crew and of your group receive an alert with your name and, when it is known, your position — including on phones where the app is closed. Sending an SOS also starts sharing your location for one hour, so that people can reach you. You can cancel it at any time, and it closes by itself after six hours.
Group statistics. After a crew ride, members of that crew can see figures from the rides recorded during that outing: distance, duration, speed, elevation, the number of hard accelerations and hard braking events, the maximum lean angle, a chart, a replay of how the group spread out along the ride's elevation profile (without a map), and a small leaderboard. It covers only rides recorded during that shared outing, only inside that crew, it is never shown anywhere else, and the crew owner can switch the leaderboard off for everyone.
Being a member of a crew shows other riders nothing about your position unless you are actively sharing.

Why we use it

To run your account and show your content (performance of our agreement with you).
To record and show your rides, and to build your explored map, because that is the service you asked for (performance of our agreement with you).
To share your live position with riders you have chosen, and to send SOS alerts — on the basis of your consent, which you give by starting the sharing or sending the alert, and withdraw by stopping it.
To calculate routes: the coordinates of the points you place are sent, through our server, to the routing service openrouteservice. When you ask the app to guide you to a meeting point or to a crew member, your current position and that destination are sent the same way. They are not linked to your name.
To notify you about your crews (messages, proposed rides, SOS). For this we store one notification token per device you use.
To understand which features are used and to fix errors, if you turn usage statistics or error reports on in Settings → Privacy (consent, which you withdraw by turning them off).
To keep the community and your account safe: reports, hiding reported reviews, moderation, and limiting how many passwords and invite codes can be tried (legitimate interest).
To send account emails, such as confirmation and password reset.

We don't sell your data, we don't show ads and we don't use your data for advertising. We don't use your location for anything beyond the features described above.

Who processes it for us

Supabase: database, sign-in, file storage and server functions.
RevenueCat (RevenueCat, Inc., USA): managing RevZoom Plus subscriptions, only when the app shows you the RevZoom Plus offer (the Plus screen, or the Plus card in your profile or after a ride), when you subscribe or when you restore a purchase. RevenueCat receives your account's random identifier (not your name or email), the purchase receipts from Apple (App Store) or Google Play and basic device information.
Google (Sign-In) and Apple (Sign in with Apple): confirming who you are, only if you choose to sign in with them.
Google (Firebase Crashlytics): error reports, only if you turn them on in Settings → Privacy. They are off until you do. A report contains the technical details of the failure, the model of your phone and its Android or iOS version, a random installation identifier, and what the app was doing at the time — whether a ride was recording, whether it had a route, whether you were sharing with a crew. It never contains your location, your name or your email. You can turn it off again at any time.
Google (Firebase Analytics): how the app is used, only if you turn it on — on the “Before you ride” screen after sign-up, or in Settings → Privacy. It is off until you do. We see which screens are opened, which features are tapped, where a free limit is reached. Counts only, added together. An event never carries your location, the text you write, route or crew names, your email or anything else that points at you; distances are sent in bands (for example “75–150 km”), not exactly. Advertising identifiers are off and we do not personalise ads — we have no ads. You can turn it off again at any time; on iPhone, turning it off also asks Google to delete what was collected from that device.
Google (Firebase Cloud Messaging): delivering notifications to your phone. Google receives a notification token for your device and the content we send. That is why a crew message is sent as a signal rather than as its text, and the text of chat messages never leaves our server. SOS alerts are the exception: they carry a short text, so that they arrive even when the app is closed.
Apple (Apple Push Notification service): the same, for iPhones: Apple receives a notification token for your device and the content we send, under the same rules.
openrouteservice (HeiGIT gGmbH, Germany): route calculation.
OpenFreeMap: map tiles (map data © OpenStreetMap contributors).
Google Play and Apple (App Store, TestFlight): app distribution and updates.

Some of these providers may process data outside the European Economic Area. Where that happens, the transfer relies on the European Commission's standard contractual clauses or on an adequacy decision.

How long we keep it

As long as you have an account, except where a shorter period is given below. When you delete your account (Settings → Delete account), your profile, garage, photos, routes, rides, explored map, reviews, replies, saved routes and follows, your crew memberships, the crew messages you wrote, the rides you proposed and your replies are deleted immediately. Copies in encrypted backups disappear when those backups expire, after at most 30 days.

Subscription status: as long as you have an account. The payment records themselves are kept by Apple (App Store) or Google Play and RevenueCat under their own policies and the law (for example, tax records).
Crew chat messages: 90 days.
Live positions: not stored. They travel between phones and are never written down; what remains is only the record that a sharing session happened.
Sharing sessions: they end at their deadline, at most 24 hours, and the old records are cleaned up.
Road hazards you report: 24 hours, or sooner if several riders say the hazard is gone.
Groups with a code: deleted a day after they expire.
SOS alerts: closed automatically after 6 hours.
Notification tokens: removed when a device has not been seen for 270 days, or when you sign out.
Error reports: 90 days, and only if you turned them on.
Wrong invite codes: 24 hours.

This website

revzoom.eu sets no cookies, runs no analytics and loads nothing from anyone else — no fonts, no scripts, no tracking pixels from third-party servers. Everything the page needs is served from this domain, so visiting it does not hand your IP address to a company you did not choose to visit. Our hosting provider keeps standard server logs.

Your rights

Under the GDPR you can access, correct, export or delete your data, object to or restrict its processing, and withdraw any consent. You can do most of this directly in the app; for anything else, write to contact@revzoom.eu. You can also complain to your data protection authority; in Romania this is ANSPDCP (www.dataprotection.ro).

How to delete your account

Children

RevZoom is not intended for people under 16.

Changes

If this policy changes, we'll update the date above and, when the change is significant, tell you in the app.