This is a provisional version of this text, dated 15 November 2026. It describes how Roadby works today, but our legal adviser has not reviewed it yet and some details are still to be completed. It may change: when it does, the date shown here changes too, and the reviewed version will replace this one.
Privacy policy
This document explains what data Roadby handles: both in the mobile app and on this website (roadby.app). It is a single document in two parts because Google Play requires one public privacy policy address for the app, and it seems more honest to us that the same address also explains what the website itself does.
Who is responsible
The personal data described in this document is controlled by the operator of Roadby (“we”, “us”), who decides why and how it is processed. Within Roadby, access to that data is restricted to the minimum number of people needed to run the service.
Roadby does not yet publish the legal name, tax number and postal address of its operator: they will appear here when the legal review of this policy is complete. Until then, you can reach the controller about anything in this policy, including exercising your rights, at support@roadby.app, and we will answer from that address.
A. Data the Roadby app handles
Roadby is an app for drivers: it connects people who are physically close to each other by live voice and lets them write to each other and send each other photos and videos, one to one and in groups. What follows describes, in as much detail as possible, what data each part of the app generates, where it ends up and for how long.
A.1 Account
To use Roadby you create an account with your email address, a password, a name and an @username, and you confirm your email through a single-use link, or you create it with your Google account (see A.1a). Either way, you accept the terms of service and this privacy policy and confirm that you are 18 or older. There is no two-factor authentication.
- Your email is used as the account identifier and only you (and Roadby's administrators) can see it; it is never shown to other users.
- Your password is stored as a hash (irreversibly encrypted): nobody, not even Roadby's administrators, can read it.
- To change your email, change your password or delete your account in the app, we ask for your current password again. If your account has no password because you only sign in with Google, the app does not offer to change your email or your password (you can create a password with “Forgot password?”), and deleting the account asks instead for a 6-digit code that we email you. If you ask us by email instead, we confirm it with you as explained on the Delete your account page.
- We store the dates you signed up, confirmed your email and last signed in; that you confirmed you are 18 or older, and when (not your date of birth: we do not verify it); the version of the terms you accepted, and when; and the language you use the app in, so that our emails reach you in it.
- For each session and each sign-in, the authentication system records your IP address and the type of device or browser, in a log of access events (sign-up, sign-in, changes, deletion). The technical logs of the platform we use (Supabase) and of the voice server (LiveKit) also contain the IP address of each connection, as in any internet service.
A.1a Signing in with Google
You can also create your Roadby account and sign in with your Google account (“Continue with Google”). Signing in with Apple is not available yet.
- What we receive from Google. An identifier for your Google account, your email address and whether Google has verified it, your name (first name and surname) and the address of your Google profile photo. We only ask Google for this basic sign-in information: we get no access to your contacts, Drive, Gmail or anything else, and we never post anything to your Google account.
- What we use. Your email address becomes your account's email, and your first name (never your surname) fills in the name of your profile, which you can change before creating the account. You choose your @username. We do not use your Google photo.
- What is kept. Our authentication provider (Supabase) keeps what Google sends, including your full name and the address of your Google photo, linked to your account while it exists, and updates it each time you sign in with Google. Roadby does not use it after you sign up.
- Before the account exists. Between “Continue with Google” and creating your account, the @username and name you choose, your email address, your Google identifier and your two confirmations are kept in a private table for at most one hour, and are then deleted.
- On your phone. The app remembers which Google accounts have signed in on that phone (an identifier from Google and your Roadby account identifier), so that next time it can sign you in faster. Signing out does not remove it; deleting your account on that phone does.
- If you already have an account with that email. Signing in with Google links Google to it. If that account was never confirmed, it becomes yours: its old password, its sessions and any pending links or codes are removed, the “news and offers” box is unticked, and the age confirmation and terms acceptance recorded by whoever created it are deleted.
- Google's role. Google is responsible for its own sign-in, and it will know that you use Roadby: it lists Roadby among the connected apps of your Google account, where you can also disconnect it.
- Roadby's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy.
- Deleting your account. If your account has no password because you only sign in with Google, deleting it in the app asks for a 6-digit code that we email you (it works once, for 1 hour).
A.2 Public profile and photo
Your profile has exactly these fields: display name, @username, an optional bio (up to 80 characters) and an optional photo. Apart from the confirmation that you are 18 or older (A.1), we do not ask for your age, phone number or anything else.
- These people see your card (name, @username, bio, photo): anyone in range of you (see A.3), whether or not you are in the voice lobby; your friends; anyone who has sent you or received from you a friend request; anyone who has you in their history; anyone you have a conversation with, and the members of any group you are in; anyone who has blocked you (in their blocked list, so they can unblock you); and any user who knows your @username.
- Anyone, even without an account, can check whether an @username exists (they do not get your card).
- Anyone who opens your profile sees your card, your badges (see A.6a) and the friends you have in common with them (A.5). The time the two of you have shared in a lobby appears in each other's History (A.6) and next to a friend request that one of you receives from the other.
- Our server also works out some counters about you (total time in lobbies, days in lobbies, people met and number of friends). It only sends them, together with the month you signed up, to your own app, never to anyone else, and the app does not show them today.
- Your profile photo is stored in a public file bucket: anyone with its address can view it without signing in, even if you block them afterwards. It is deleted when you delete your account or replace it with another. There can only be one photo, and today the app does not let you remove it without replacing it; if you want it removed, write to us and we will do it for you.
Automatic photo filter. When you upload a profile photo, we send it to Google Cloud Vision's SafeSearch API (Google LLC) for an automatic check for explicit content, through the service's European endpoint. Google's contractual commitment on data residency for Cloud Vision covers only the text recognition feature, so we cannot guarantee that this analysis is processed solely within the European Union. Google returns a probability across five categories (adult, violent, medical or racy content, and spoofed or manipulated images); Roadby only rejects a photo if Google flags adult or violent content at its highest level, and we do not request any other analysis feature (labels, faces, text). If a photo is rejected, all that remains in the server's technical logs is Google's verdict, without the image and without your account identifier. If the filter is unavailable (a failure or missing configuration), the photo is published without being analysed and a record of that, also without identifying you, is left in those same logs. To limit abuse, you can change your profile photo at most twice every 24 hours (a photo the filter rejects also counts), and we analyse at most 5 photos per account per day. To count this, the server keeps the time and a fingerprint (a cryptographic summary) of each attempt for 24 hours, and a daily counter of attempts that is overwritten on the next day you try; both are deleted with your account. Only profile photos go through this filter: group photos (A.5b) and the photos and videos sent in chats (A.5a) do not.
A.3 Location
This is the most sensitive data in the app and the one we take most care over:
- Outside a voice lobby, your position is only captured while the app is on screen and you are signed in, with the “while in use” location permission. While you are in a voice lobby (from the moment you tap Join until you tap Leave), Roadby keeps capturing and sharing your position even when your screen is off or another app, such as a map, is in front, so that people near you can keep hearing you while you drive. On Android this runs as a foreground service with a persistent notification that shows the lobby is active, and it stops as soon as you leave the lobby. Before your first Join, the app explains this and lets you choose not to join. We never ask for “all the time” (background) location. If your phone gets no new GPS position for two minutes, the app stops sharing your last known position instead of repeating it, and you disappear from the radar until the signal comes back.
- Your exact position travels encrypted to the server and passes through it before being stored; before being written, it is rounded to a grid of roughly 50 metres. We only store your last position: there is no location history of any kind. To count the time you share with other people (A.6), the server also keeps, for up to 5 minutes, a note of which pairs of users were in range of each other and when — never where.
- That position expires after 5 minutes, and stops being visible to others after 45 seconds without an update.
- Another person never receives your position, your distance or your direction. As for your location, their app only receives two things: whether you are in range, and a volume level in four steps (full, three quarters, half and a quarter). The range is the same for everyone and is set by our server: you are in range when you are within about 400 metres of each other. Within about 300 metres the volume is full, whatever the distance between you; between about 300 and 400 metres it gets lower, step by step; beyond about 400 metres you drop out of each other's range and disappear from each other's radar. Between 300 and 400 metres, the volume level narrows the distance between you down to bands of about 25 metres. All distances are approximate: positions are rounded to a grid of roughly 50 metres and, at motorway speeds, can be a few seconds old.
- The server discards impossible positions (jumps that no vehicle could make) and applies the same range to everyone; the app cannot change it.
A.4 Voice
- The voice lobby is provided by LiveKit Cloud. There you are identified by a random code per session, unconnected to your account, your name or your email. The access pass our server gives your phone only allows sending microphone audio (no video, screen or data), and LiveKit never receives your name, @username, email, account, position or messages.
- Your microphone is only connected while someone in your lobby can hear you, and it is disconnected again 2 minutes after the last of them leaves; while you are alone in the lobby, your voice is not connected at all. You can mute yourself at any time.
- Voice is live and is never recorded, exported or transcribed at any point.
- Only the people in range at that moment can hear you (see A.3): at full volume within about 300 metres, then more quietly up to about 400 metres. Nobody you have blocked, or who has blocked you, can ever hear you; in Friends mode, only your friends can.
- On Android, while you are in the lobby, a foreground service with a persistent notification keeps the microphone open and your location up to date even if you lock the screen or open another app. The notification shows how the lobby is doing (for example, how many people are connected, or that it is waiting for a GPS signal) and has Mute and Leave buttons. If you joined without allowing the microphone, the service only keeps your location up to date. It closes when you leave the lobby.
- While your voice session lasts, our server keeps which lobby you are in (Global or Friends), when your phone last checked in, whether your voice is connected and, if you answer a phone call while in the lobby, when the call started and ended (that time does not count in your history). All of it is deleted when the session ends. Separately, the server adds up a single monthly total of voice minutes for all of Roadby, with no names or times, to stay within our voice provider's plan.
A.5 Friends, requests and blocks
- Friend requests stay visible to sender and recipient until they are accepted, declined or cancelled.
- To cap sending at 50 requests a day, the server keeps an internal record for 7 days of who sent each request and to whom; it is not shown to anyone.
- Other users never see your full list of friends: someone who opens your profile only sees the friends you have in common with them, as a list with their names and photos (a friendship made today only appears from the next day).
- If you block someone, that person does not know: the app answers them as if your account did not exist, and in their chats you appear as “Roadby user”. Blocking is immediate and mutual: you stop seeing each other on the radar, in the lobby, in your history and in notifications; any message from them that had not reached you yet is deleted from our server (if it carried a photo or a video, the file itself is deleted automatically within a few days, see A.5a), a message request from them disappears, and your conversation stays on your phone for you to read. In a group you are both in, you both stay members and still see each other's name, @username and photo (so the other person may guess the block), but their messages reach you folded (“Message from someone you blocked.”), their links cannot be opened, and they cannot notify or mention you. You can undo it from Settings › Account › Blocked users.
A.5a Messages and message requests
You can write text messages to other users, one to one and in groups (A.5b). A message can also carry one photo or one video, with an optional caption, chosen from your phone's gallery (the app does not use the camera). You cannot send voice notes or files, and the app does not create link previews.
- Who can write to you. Your friends, and anyone you already have an accepted conversation with, can write to you directly. Anyone else can send you one message request, which you can accept or delete; they cannot send another until you accept. A message request can only contain text: a photo or a video can only reach you from a friend, in a conversation that has been accepted (replying to a request accepts it) or in a group. Reading a request does not tell the sender, and deleting it does not notify them. You choose who can send you requests in Settings › Messages › Who can message you: Everyone (the default), People you've met (anyone who has shared a lobby with you) or Friends only. There is no directory of users: someone can only reach you through the lobby, their history, friends in common or your exact @username.
- Where messages live. Messages live on your phones, in the app's private storage. Our server keeps each message only until it has reached all of the recipient's phones, and then deletes it; a message that nobody collects is deleted after 30 days, and the copies of what you write for your own other phones after 14 days. Photos and videos stay on our server a little longer (next point).
- Photos and videos. Before a photo leaves your phone, the app makes it smaller and removes its hidden data (such as where and when it was taken and the phone model), and our server removes that data again. A video is compressed on your phone, which removes where and when it was recorded and with which phone; our server checks it before letting it through and, if it still carries any of that, deletes it and does not send it. Photos and videos are stored privately, separately from the message, in the file storage of our provider Supabase in Frankfurt (European Union). Only the sender (once it has been sent, and never a view-once one) and the people it was sent to can open one: in a group, the people who were already members when it was sent and still are. The app opens photos through links that expire after 10 minutes, and videos through links that last the length of the video plus 20 minutes (2 hours 10 minutes at most). A photo stays on our server until every phone it was sent to has received it, plus 3 days so that they can download it, and 30 days at most; a video, plus 1 day, and 7 days at most; an upload that is never sent, 1 hour (a video, 3 hours). With each photo or video we keep, for the same time, who sent it, to whom or to which group, in which message, its size, its dimensions (and a video's duration), a fingerprint (a cryptographic summary), a small blurred preview that also travels with the message (none for view-once ones) and, where it applies, when a view-once one was opened or when a video was cancelled while it was being sent. When a photo or video is deleted for everyone, or its sender deletes their account, nobody can get a new link to it from that moment (a link already given keeps working until it expires or the file is deleted), and the file and what we keep with it are deleted within an hour (a video uploaded less than 3 hours earlier, once those 3 hours have passed). To apply limits, we also count how many photos each person has uploaded in the last minute and today and how many videos today, and the total amount of video sent across Roadby each day, without names.
- View once. You can send a photo or a video to be viewed once. The person who receives it sees no preview and no caption in the chat: they can open it once, full screen, and their phone deletes it when they close it (or after 14 days if they never open it); its caption is only shown while it is open. While it is open, the app blocks screenshots and screen recording on Android (for a video, both its image and its sound) and the photo or video does not show in the recent apps screen, although someone could still photograph the screen with another device. The sender cannot view it again. For these photos and videos our server keeps no preview, and their caption travels with the message only to the people who receive them. In one-to-one conversations, when the recipient opens it on one of their phones, it is marked as opened on their other phones (a phone that was offline and had already downloaded it could still open it once). Our server then deletes the image or the video within 15 minutes of it being opened (a video opened less than 3 hours after it was uploaded, once those 3 hours have passed). What we keep with it, including when it was opened, stays until its usual date, and the notice that it has been opened waits on our server, like a message, until the phones that need it have collected it. In groups they are kept like any other photo or video, and each phone that receives one can open it once (A.5b).
- No end-to-end encryption. Messages travel encrypted (HTTPS), but they are not end-to-end encrypted: while a message waits on our server to be delivered (30 days at most), it is stored there in readable form, and Roadby's administrators could technically read it. We do not read messages, except the copies attached to a report (A.7). The same goes for photos and videos while they are on our server: Roadby's administrators could technically open them, but we do not look at them, except those attached to a report.
- What the server keeps without the text. For each conversation: who it is between, when it started, how far each of you has received and read it (for “Delivered” and “Seen”), unread counts, whether it is accepted, a request or declined, whether each of you has muted it, and whether each of you has ever written in it with the car stopped (for a badge, A.6a). This is deleted after 12 months without messages, or when either of you deletes your account. We also keep, without any text, an identifier of each message sent (7 days) so that a retry is not duplicated (if the message is deleted for everyone, the identifier also records when), the phones that collect your messages (until 30 days without use) and your message settings.
- “Delivered”, “Seen” and “Opened”. “Delivered” shows when a message reaches one of the other person's phones. “Seen” only appears in accepted conversations and only if both of you have Read receipts turned on (it is on by default); turning it off works both ways. In one-to-one conversations, a view-once photo or video shows “Opened” to its sender once you have opened it, under the same rule as “Seen”; in groups it does not.
- While driving. If your phone's GPS shows that the car is moving, the app covers your messages and some other screens until you confirm that someone else is driving (“I'm a passenger”). This is worked out on your phone; our server only receives, with each message you send, whether the car was moving, and only to keep the marks described above.
- Deleting. You can delete any message just for you, on that phone (“Delete for me”), and your own messages for everyone (“Delete for everyone”) for up to 60 hours after sending them. Deleting for everyone removes the message from our server if it was still waiting there, and the other people's app replaces it on their phones with “This message was deleted”; a photo or video in it is deleted too (see “Photos and videos”). It does not reach anyone who has blocked you, and phones with an older version of the app keep their copy. If someone replied quoting the message, their reply keeps the quote, hidden in the app. Once a message has been deleted for everyone, it can no longer be reported, except by someone whose phone has kept it (for example, because they had blocked you). Deleting a chat deletes it for you, on all your phones; the other person keeps their copy. Apart from that, what you have sent stays on the phones of the people who received it, even if you delete your account.
- Signing out. Your messages, with their photos and videos, stay on your phone, locked, and come back when you sign in again with the same account; another account on that phone cannot open them.
- Links. Links in messages are detected on your phone and open in your browser, outside Roadby; we do not visit them or create previews, and we do not know which links you open. The website you open sees your visit like any other, and whoever controls it may learn that you read the message. Links that look suspicious are marked and ask for confirmation before opening.
A.5b Groups
- Only your friends can add you to a group, and you do not have to accept; strangers can never add you. A group can have up to 256 members. Inside a group, everyone sees the name, @username and photo of every member, including friends of friends they do not know.
- Group messages work like the other messages (A.5a): each one waits on our server, without end-to-end encryption, until it reaches each member's phones (30 days at most), and then lives only on the members' phones. What you write stays on the other members' phones even if you leave the group or delete your account, unless you delete it for everyone first (A.5a): in a group only its author can do so, not the admins, and the deletion reaches the people who were members when it was sent and still are (people who have left keep their copy). A photo or video sent to a group can only be opened by the people who were members when it was sent and still are (someone who leaves keeps what they had already downloaded); a view-once one can be opened once on each phone that receives it, and shows no “Opened”.
- Mentions. When you mention someone with @, the message carries the list of people it mentions; that list reaches every member, waits with the message and is kept without the text, with the message identifiers, for 30 days. A mention notifies the person mentioned even if they have muted the group (silently while they are in the lobby or driving). Mentions in the caption of a photo or video work the same way, except in a view-once one: there they notify no one.
- Info. For each of your own messages from the last 30 days, you can see who has read it and who has received it, without times. “Read” only shows if both of you have Read receipts turned on and there is no block; “received” shows even if the other person has Read receipts turned off.
- What the server keeps. The group's name, its description, its photo, who created it, who set the name, the description and the photo that are showing (so that a report about the group can be addressed to them), how many members it has and when someone last wrote; and, for each member, whether they are in it, whether they are an admin, who added them, when they joined or left, how far they have received and read it, and whether they have muted it. For people who have left, 30 days.
- Group photo. By default only the group's admins can set or remove it, and they can let every member do so (Group permissions). Each person can set at most 2 group photos every 24 hours, counting all their groups (removing one does not count). Before anything else, our server strips the photo's hidden data (such as its GPS location, date and phone model); group photos do not go through the automatic filter described in A.2. Group photos are stored privately: only the current members can see the one that is showing, through links that expire after 1 hour. For each change we keep who made it, in which group, when and a fingerprint of the photo, for 24 hours. A removed or replaced photo is deleted, unless a report about the group from the last 90 days refers to it; then it is kept until those 90 days have passed. The group photo belongs to the group: it is not deleted when the member who set it deletes their account.
- Leaving and closing. When you leave a group, only the admins see it unless you tick “Let everyone know”; you keep the conversation to read. Admins can remove members, and Roadby can close a group (we keep a note that we closed it for 12 months). Group names are chosen by the members and are moderated through reports.
A.6 Shared-time history
For each pair of users we store the accumulated seconds you have spent together in a voice lobby and the date and time of your first and last encounter; never the place, the list of each encounter or the content of the audio. Only time with people our server put in range of you in the previous 90 seconds counts, with the voice connected and not while either of you is on a phone call. It is a single row shared between the two of you: if one deletes their account, the other also loses that time from their history; if you block someone, the row is not deleted, it is hidden for as long as the block lasts. The app does not yet let you delete individual entries from your history; if you want one deleted without deleting your account, write to us at support@roadby.app and we will do it for you (because the row is shared, the other person also loses that time). When you search your History, what you type is sent to our server only to answer the search, inside the request (never in the web address), and is not stored; the search only covers people you have shared a lobby with.
A.6a Badges
Roadby has five badges with levels from 1 to 10 (Users met, Regulars, Crew, Pen pals and Time shared). They are worked out from your history, your friendships, the marks of your conversations (A.5a) and your time in lobbies. They never use your position, places or kilometres; the only driving data they use is whether the car was moving when you wrote, because Pen pals only counts messages written with the car stopped (a message written while it is moving does not count, even if you said “I'm a passenger”). Anyone who opens your profile sees the level of each badge, a progress bar in steps of 10% and up to 3 badges you have pinned. You can hide them all from other people with Settings › Account › Show badges on my profile (it is on by default). Our server keeps, for each badge, what you have earned and the counts behind it, your pins and whether you hide them and, to prevent cheating, whether an account has been frozen by hand and the days on which it reached the daily cap of 12 hours in lobbies (35 days). All of it is deleted with your account. The Store tab shows paid badges as “Coming soon”: nothing can be bought, and the app does not connect to Google Play's billing.
A.7 Reports
You can report another user from their profile, a conversation or message request from its menu, a single message by holding it, and a group from its menu. The reasons are a closed list: harassment or bullying, hate speech, dangerous behaviour on the road, spam or scam, sexual content or involving a minor, and something else; there is no free text. The report is anonymous to the person reported (and, in a group, to the other members), but not to Roadby's administrators, who can review it.
- When you report from a chat, or report a message in a group, your phone sends a copy of the last 5 messages the reported person sent there (if you report a single message, that one and up to 4 before it), as they reached you (none of yours), with a seal our server added when each was sent, so that nobody can make up evidence. If any of those messages is a photo, or a video of up to 15 MB, your phone also sends the file if it still has it, and our server checks that it is the one that was sent; for a larger video, a view-once photo or video you have already opened, or a file that could not be sent (for example, because the app was closed first), the copy only identifies it by its fingerprint. These files are kept with the copy, for the same time, and only Roadby's administrators can see them. Messages deleted for everyone are not included, unless your phone has kept them (for example, because you had already blocked their sender, A.5a). A report about a group from its menu is addressed to whoever set the photo that is showing or, if there is none, whoever set the name or, failing that, whoever set the description, leaving out anything you set yourself; it keeps the name, the description and the photo that were showing, and who set each of them (A.5b).
- Each new report sends Roadby's administrators a notification that only says there is a new report and how many are unreviewed: never the reason or who is involved.
- Copies of reported messages are kept for at least 90 days after they were made; after that, they are deleted as soon as the report has been reviewed, and 12 months after they were made at the latest. If the reported person deletes their account, the report itself is removed, but the copy of the messages is kept until 90 days after it was made. If you delete your account, the reports you filed are kept without your name.
- Account blocks. We can block an account that breaks our rules, for a time or indefinitely. A blocked account cannot join the lobby, appear on anyone's radar or send messages or requests, but it can still sign in, read its own messages, report, block and delete itself. We keep when the block started and ends and the reason we wrote; the app only knows that it is blocked and until when. This is deleted with the account.
A.8 Push notifications
Roadby sends these notifications: someone wants to be your friend; someone accepted your friend request; someone sent you a message (with their display name and how many, never the text); you have a new message request (without saying who); and, in a group, a new message (with the group's name and the sender's display name), that someone added you to a group, or that someone mentioned you. Notifications are written in the language of the app on each phone, so we keep that language with the phone's token. To deliver them we use a technical token from your device (through Expo and, on Android, Google's Firebase Cloud Messaging), and the notification passes through those two services with the names shown in it; it never includes the text of a message, your photo, your @username or your location. For Android Auto (A.8a), your phone also receives data-only notifications with the sender's display name, the conversation or group, how many messages are unread and, if you were mentioned, the name of who mentioned you, again without the text, so that your phone can fetch the new messages itself. We keep a record for 30 days of who notified whom (kind, time and up to which message), solely to limit how many notifications are sent. Roadby's administrators also receive notifications about new reports and about the use of the voice service, which contain no one's data.
A.8a Android Auto
If you connect your phone to Android Auto, the unread messages from your friends and from your groups (from any member except people you have blocked; at most the last 10 of each conversation, each cut to 500 characters) are shown on your car's screen and read aloud by Google's voice. Photos and videos are shown and read only as “Photo” or “Video”, with their caption if they have one (never the caption of a view-once one); the car never shows the image or plays the video. Messages from people who are not your friends, including message requests, are never read in the car, except inside a group. To reply, you dictate: Google transcribes what you say and Roadby only receives the text, which is sent as a normal message. The chat never opens on the car's screen. This happens between you, your phone and Google, under Google's own terms: Roadby receives no audio and does not control what Google keeps. When you disconnect, the notifications go back to having no text, and signing out removes them.
A.9 Account emails
We send emails to confirm sign-up, recover your password and change your email address and, if your account has no password, the 6-digit code to delete it (it works once, for 1 hour). They are sent through our authentication provider (Supabase) using Resend as the sending server, from no-reply@mail.roadby.app, in the language you use the app in (in English if we do not know it yet). The emails to confirm your sign-up, set a new password or change your email address show their button as an image, which your email program downloads from roadby.app when it displays the email: Cloudflare, which hosts this website (part B), then receives your IP address and the type of email program or browser. The image is the same for everyone who reads that email in the same language, so it does not tell us who has opened it. Our authentication provider may also send you security notices when your password or your email address changes, or when a new way of signing in is linked to your account; these are service emails, not marketing. They are not sent in every case: for example, not when you change your password from Settings › Account, nor when signing in with Google links it to an existing account with the same email.
A.10 News and offers emails (optional)
At sign-up there is an optional checkbox, unticked by default and separate from the mandatory one with which you accept the terms of service and this privacy policy: “Email me Roadby news and offers”. If you tick it, we store that yes with its date; every time you switch it on or off afterwards, we also store that change with its date. Each entry also records where it was made (sign-up, the app's settings or the unsubscribe link of an email) and which version of the wording you saw, so we can show what you consented to and when. You can change your mind at any time from Settings › Account › “News and offers by email”. We only write to confirmed email addresses, and only Roadby's administrators can extract the list of recipients. We have not chosen a provider for these emails yet, and none has been sent to date; we will name the provider here before the first one is sent.
A.11 What stays on your device
Your session tokens (which include your email and your account identifier) are kept in the app's private storage and are deleted when you sign out or delete your account in the app; signing out of Roadby signs you out on all your phones. Your messages live in a database on your phone, in the app's private storage, together with the state of each conversation (unread counts, whether you muted it and any draft you have not sent), your groups, the mentions of each message, the link to each group photo (which expires after 1 hour) and an index of the words of your messages for the Chats search. That database also keeps a card for each person you have a conversation with and for each member of your groups: their name, @username and the address of their photo, whether you have blocked them, whether they now appear as “Roadby user” (A.5) and, in groups, their role and whether they are still a member. The photos and videos of your chats are kept as files in the app's private storage (a video that is not view-once, together with a still image from it), outside Android's backup (A.11a); their small blurred previews and their captions are part of the message database (the caption of a view-once one, only until it is opened). A view-once photo or video has no preview: the phone that receives it deletes it when it is closed, or after 14 days if it is never opened, and the phone that sends it deletes its copy as soon as it has been sent. When a message or a chat is deleted from a phone, its photos and videos are deleted from that phone too. The database stays on the phone when you sign out, together with the photos and videos of your chats, and both are deleted when you delete your account on that phone (if that cannot be done at that moment, the next time the app opens with a connection; if we delete the account for you after an email request, also the next time the app opens with a connection). The app also keeps a random code for that phone for the chat, which Google accounts have signed in on it (A.1a), the language and theme you chose and, for 7 days at most, an invitation link you opened before having an account. Apart from those cards, the radar, your friends list, your history and other people's profiles live in memory and disappear when you close the app; the cropped photo may stay in the temporary cache until the system clears it. The temporary copies the app makes of a photo or video you send (for a video, the original until it has been compressed) are deleted as soon as they are no longer needed (if the app closes first, they are cleared later, by the app or by the system). Device settings (lobby mode, audio settings, lobby sounds, Mute when parked and Leave when parked) are stored locally: they survive signing out, as they belong to the device and not to the account, and are reset to their defaults when you delete your account from that device. The Back up messages switch (A.11a) also belongs to the phone, for every account that signs in on it: deleting your account does not change it, and it stays as you left it until you change it or uninstall the app.
Test versions of the app (the ones we share by hand while Roadby is being finished, never the version for Google Play) also keep a timing log on the phone: when you join and leave the lobby, how long the voice takes to connect, voice cuts, the time Roadby spends in the background, failed requests to our server and app errors, without account identifiers, names, @usernames or positions. It only keeps the last two times the app was opened, it is deleted when you sign out, and it only leaves your phone if you share it yourself with “Share timing log”, in Settings › Account › Help & support.
A.11a Your messages in your phone's backup
If your phone backs up apps to your Google account and has a screen lock, Android can include Roadby's message database in that backup, encrypted with your screen lock (at most once a day, and only up to 25 MB). Nothing else from Roadby goes into it. That database includes the small blurred previews and the captions of the photos and videos in your chats (the caption of a view-once one, only until it is opened), but not the photos and videos themselves: they are never part of the backup and do not move to another phone. You can leave your messages out with Settings › Messages › Back up messages (on by default, for each phone); the next backup then leaves them out, usually within a day. When you move your data directly from one phone to another, your messages move with it even if that switch is off. On a new or restored phone, the photos and videos that are still on our server (A.5a) can be downloaded again; older ones appear as “Photo unavailable” or “Video unavailable”. The backup lives in your Google account: Roadby cannot see or control it.
A.12 Who we share data with (processors and other recipients)
| Provider | What we use it for | Head office | Where the data is processed |
|---|---|---|---|
| Supabase Inc. | Database (including messages waiting to be delivered), authentication, storage of photos and videos, server functions (including the one that receives the photos sent in chats and checks videos) and the real-time channel that tells your phone there is something new (it carries no content and Supabase keeps it for 3 days). | United States | Database, photos and videos: Frankfurt (European Union). Server functions: Supabase runs them on its global network, by default in the region closest to each request; we have not fixed a region. |
| LiveKit Inc. (LiveKit Cloud) | Live voice lobby (microphone audio only). | United States | The data centre closest to each user, which may be outside the European Union: on our current plan the region cannot be fixed. |
| Expo (650 Industries, Inc.) | Building the app, delivering push notifications and delivering app updates over the internet (EAS Update). Each time the app checks for updates it sends a random installation identifier (not your account or device identifier), the app version, the platform and, if the app last closed because of an error, the text of that error. | United States | United States. |
| Google LLC (Firebase Cloud Messaging) | Delivering push notifications on Android, including the data-only ones for Android Auto. We do not use Google Analytics or Crashlytics inside the app. | United States | United States. |
| Google LLC (Google Sign-In) | Signing in with Google, if you choose it (A.1a). Google acts as an independent controller of its own sign-in. | United States | United States. |
| Google LLC (Cloud Vision) | Automatic content filter for profile photos (see A.2). | United States | European endpoint of the service; Google does not contractually guarantee that this analysis stays within the European Union. |
| Google (Google Play services, on your phone) | They resolve the GPS position the app asks for, as in any Android app; this is outside Roadby's control. | United States | On your own phone. |
| Google LLC (Android Auto and Google Assistant) | If you use Android Auto: showing and reading aloud messages in your car and transcribing what you dictate (A.8a). A direct relationship between you and Google. | United States | Your phone, your car and Google's own systems, under Google's terms. |
| Google LLC (Android backup) | If you have it on: the backup of your message database to your Google account (A.11a). A direct relationship between you and Google. | United States | Your Google account. |
| Cloudflare, Inc. (Turnstile) | Checking that whoever creates an account, signs in, asks for a new password or resends the confirmation email is not a bot. Not switched on yet: until it is, the app loads nothing from Cloudflare. When it is, Cloudflare receives your IP address and technical details of the app's browser view, which it says it uses only to detect bots. | United States | Cloudflare's global network. |
| Resend Inc. | Technical sending of account emails (including deletion codes and security notices) and of our replies from support@roadby.app. | United States | United States. |
| Porkbun, LLC | Forwarding the emails sent to support@roadby.app to our mailbox. | United States | United States. |
| Google LLC (Gmail) | Mailbox where we receive, answer and keep the emails sent to support@roadby.app, including account deletion requests and child safety reports. | United States | Google's data centres, which may be outside the European Union. |
Where a provider has its head office or processes data outside the European Economic Area, there may be an international transfer of data. Our legal adviser is confirming which safeguard covers each of these transfers (for example, the European Commission's standard contractual clauses), and this section will name it for each provider when the review is complete.
A.13 What Roadby does not do, and what permissions it asks for
The app uses no analytics, advertising or tracking tools of any kind (the update service described in A.12 receives, at most, the text of the last error that closed the app). The video player built into the app reports nothing to Roadby, but on Android 12 and later it may share information about how videos play, such as playback events and performance data, with Android itself, which may pass it on to Google if you have allowed your phone to share usage and diagnostics data. The app does not access your contacts or the camera (the camera permission is blocked in the app); it does not ask for permission to read your photos or files: it only opens the system picker when you choose a profile or group photo, or a photo or video to send in a chat, and it only receives the image or video you select; it never records, stores or transcribes the voice of the lobby (what you dictate in Android Auto is transcribed by Google, A.8a); it does not use fingerprint, face or PIN unlocking; and it does not request “all the time” location: it only uses your location with the app in the background while you are in a voice lobby, as described in A.3. These are the permissions the app declares on Android, and what each one is for:
- Location (precise and approximate, only while the app is in use): to know who is near you (A.3).
- Microphone: for your voice in the lobby (A.4); the app asks for it after you create your account, on a screen that first explains why, or when you tap Join.
- Foreground service for the microphone and location: keeps the lobby working, with its persistent notification, while the screen is off or another app is in front, and stops when you leave the lobby (A.3 and A.4).
- Notifications: to show you the notifications described in A.8 and the lobby's notification.
- Receiving push notifications (Firebase Cloud Messaging): so that those notifications reach your phone (A.8).
- Bluetooth: so that the lobby's voice can go through your car's Bluetooth, and so that Mute when parked and Leave when parked can tell when your car's Bluetooth disconnects; this is worked out on your phone and is not sent to us. On Android 12 and later, the app asks for it together with the microphone.
- Managing its own calls: would let the lobby work as a call on Android, so that Android itself sends the voice to your car and a real phone call puts the lobby on hold; it is switched off today, and the app does not use it.
- Google Play billing: comes with the library for buying badges in the Store; today nothing can be bought, and the app does not connect to Google Play's billing (A.6a).
- Install referrer: comes with a library that the notifications use, and would let the app ask Google Play where it was installed from; Roadby never asks.
- Closing system dialogs (only on Android 11 and earlier): comes with the library that shows the lobby's notification, and gives access to no data.
- Technical permissions, which give no access to personal data: internet, network state, audio settings (to send the voice to the speaker, the earpiece or Bluetooth), vibration (for the app's touch feedback and for notifications) and keeping the device awake (for the lobby, and to finish compressing, sending or receiving a video, including one attached to a report, while the screen is off).
A.14 Legal bases
Data protection law requires a legal basis for each use of your data. These are the ones we rely on:
- Providing the service you signed up for (performance of a contract, Article 6(1)(b) GDPR): your account and profile, signing in with Google, location and the voice lobby, friends, messages (including their photos and videos) and groups, your history and badges, notifications, account emails and deleting your account, that is, what the app needs in order to work as the terms of service describe.
- Keeping Roadby safe (our legitimate interest in protecting the people who use it and the service itself, Article 6(1)(f) GDPR): the photo filter for profile photos, the limits on requests, messages, photos, videos and photo changes, the access logs, reports and copies of reported messages (with their photos and videos), account blocks, the technical logs of our providers and the emails about a request to delete an account, so that we can show how we handled it.
- Your consent (Article 6(1)(a) GDPR): news and offers emails (A.10), the newsletter (B.3) and, once they are switched on, this website's optional cookies (B.1). You can withdraw it at any time; doing so does not affect what was done before.
- Legal obligations (Article 6(1)(c) GDPR): keeping the record of what you consented to and when, and keeping or handing over information when the law requires it, for example to the authorities under our child safety standards.
Our legal adviser is reviewing these legal bases as part of the review of this policy; this section may change when the review is complete.
B. Data this website handles (roadby.app)
This part covers only the public site you are reading now: the home page (which holds every section — how it works, privacy, help and news — plus the donation window), this policy, the terms, the cookie policy, the page on deleting your account, the child safety standards, the pages our account emails and invitations link to, and the button images that some of our account emails show (A.9). It shares no systems with the mobile app, except two kinds of page: roadby.app/confirm/, where the links in our account emails take you, which talks directly to our authentication provider (Supabase) to confirm your email or set a new password, keeps the session only in that tab's memory and loads no third-party script; and invitation links (roadby.app/add/ followed by an @username), which only carry that @username, which is already public, and ask our servers nothing. This website is hosted by Cloudflare (Cloudflare Pages), which also manages its domain: like any host, Cloudflare's network receives your IP address, your browser and the page you ask for on each visit.
B.1 Cookies and measurement
Before you accept anything, we only use what is strictly necessary for the site to work (for example, remembering your choice about cookies, stored in your browser). The cookie notice also asks whether you accept two optional categories:
| Category | What for | Provider |
|---|---|---|
| Analytics | Understanding how many people visit the site and which pages they use (Google Analytics 4). | Google, through Google Tag Manager |
| Advertising | Measuring how future Google Ads campaigns perform (conversion tag). It does not enable personalised ads or remarketing. | Google, through Google Tag Manager |
Measurement is not switched on yet: today this site loads no Google script and sets none of these cookies, even if you accept them. Before we switch it on, we will update this policy and the cookie policy.
Once it is switched on, it will only start if you accept: until then, this website will load no Google script and send Google nothing (Google Consent Mode v2 in basic mode). Your decision is stored in your browser along with its date; we will ask you again after 24 months, or sooner if the categories change. You can change it whenever you want from the cookie button in the corner of any page.
The cookie policy lists every cookie by name, with what it is for, how long it lasts and who stores it.
B.2 Donations
The “Buy us a coffee” button takes you to our page on Ko-fi (ko-fi.com/roadby), where payments are processed by Stripe or PayPal. Roadby never receives your card or payment details: that relationship is directly between you and Ko-fi and its payment providers, under their own privacy policies. Ko-fi shows us the details of each donation that it shares with creators (such as the name or alias and the message you leave, and the amount). The button never appears inside the app or on these legal pages.
B.3 Newsletter
The sign-up form has a single purpose: to send you Roadby news by email. By signing up you are asking to receive it, and we use your email address for nothing else. The form has one required tick box, unticked by default, with which you confirm that you have read this policy and accept the terms of service. Your tick is stored with an identifier of the exact wording you agreed to (terms-web-v1), so that it can be shown later.
We send the newsletter on the basis of your consent (Article 6(1)(a) GDPR), which you give by signing up and confirming your address. You can withdraw it at any time by unsubscribing; doing so does not affect the emails sent before.
Your email address, that record and a note that you signed up on roadby.app would be stored with the email provider we use to send the newsletter. The newsletter is not running yet: the sign-up form is switched off and sends nothing, and we will name that provider here, with the country where it is based, before it starts. That provider will send you a confirmation email first, and you are only added to the list once you follow the link in it. You can unsubscribe at any time from the link in any email we send you. This list is separate from the news checkbox in the app itself (section A.10).
B.4 Help and contact
If you write to us at support@roadby.app or from the Help section of the home page (the “Email support” button), we use your email address and the content of your message to reply to you. If you asked us to delete your account, we keep those emails as explained under “How long we keep data”; if you told us about a concern for a child's safety, we may keep it and share it with the authorities, as explained in our child safety standards. Emails to support@roadby.app reach us through Porkbun's forwarding service into a Gmail mailbox, and we answer them through Resend (see A.12).
How long we keep data
- Account, profile, photo, friendships, blocks, history (with the dates of your first and last encounter), badges, pins, counters, your age confirmation, the terms you accepted, your message settings and the language of your account: for as long as your account exists, or until you undo them.
- Reports: those you receive are deleted with your account; those you file are kept in anonymised form. The exception: before we close an account for child sexual abuse or exploitation, we keep a copy of the account details, the reports, any copies of reported messages (with their photos and videos) and the access records for the authorities, as explained in our child safety standards.
- Consent to news emails: for as long as your account exists, with the date of the yes and, if you withdraw it, the date of the withdrawal.
- Last position: up to 5 minutes.
- Record of which users were in range of each other (no positions): up to 5 minutes.
- Voice session: until you leave the lobby, with a maximum of 1 hour without renewal.
- Internal record of friend requests sent: 7 days.
- Record of notifications sent: 30 days.
- Profile photo attempts (time and fingerprint): 24 hours; the daily attempt counter is overwritten on the next day you try.
- Messages waiting on our server to be delivered (including the notices that a message was deleted for everyone or that a view-once photo or video was opened): until they reach the phones they are for, and 30 days at most; copies of what you write for your own other phones: 14 days.
- Photos and videos sent in chats (A.5a): a photo, until every phone it was sent to has received it, plus 3 days, and 30 days at most; a video, until then plus 1 day, and 7 days at most; one that is never sent, 1 hour (a video, 3 hours). The image or video of a view-once one in a one-to-one conversation is deleted within 15 minutes of being opened (a video opened less than 3 hours after it was uploaded, once those 3 hours have passed). What we keep with each photo or video, including when a view-once one was opened: the same periods. If one is deleted for everyone, or its sender deletes their account: within an hour (a video uploaded less than 3 hours earlier, once those 3 hours have passed).
- Counters of the photos and videos each person uploads, used for limits: overwritten as they go, and deleted with the account; the daily total of video sent across Roadby, without names: reset every day.
- Conversation data without text (A.5a): 12 months without messages.
- Message identifiers: 7 days (in groups, with the list of mentions and without text: 30 days), with a note of when, if the message was deleted for everyone; phones that collect messages: 30 days without use; after an account is deleted, the random code of each of its phones: 90 days.
- Groups: while the group exists; members who have left, 30 days; a closed group is deleted after 30 days, and our note that we closed it after 12 months; records of group photo changes, 24 hours; a removed group photo cited by a report, 90 days.
- Copies of reported messages, with their photos and videos: at least 90 days after they were made; then until the report is reviewed, and 12 months at most.
- Account blocks: until the account is deleted.
- Sign-up with Google in progress (A.1a): 1 hour at most. Records of the codes requested or tried to delete an account: 60 to 75 minutes.
- Emails about a request to delete your account: 3 years after the account is deleted, or after our last reply if the request is never confirmed.
- Other emails to support@roadby.app: for as long as we need them to deal with your question; the period after which we delete them will be published here when the legal review is complete. Those about a child's safety, as explained in our child safety standards.
- Record of your changes of consent to news emails: for as long as your account exists.
- Device notification token and the language of that phone: 60 days without use, or when you sign out.
- Sessions: until you sign out (signing out of Roadby signs you out on all your phones) or delete your account. The access audit log of the authentication system (which also records your email address) and database backups: we are confirming with our provider (Supabase) how long they are kept, and will publish it here; they may outlive the deletion of your account.
- Newsletter email address: until you unsubscribe.
- Analytics or advertising cookies: as listed one by one in the cookie policy, and always revocable from the cookie button in the corner of the page.
What happens when you delete your account
You can delete your account yourself in the app (open the Profile tab, tap the gear at the top right, then Account › Delete account, and type your current password or, if your account has no password because you only sign in with Google, the 6-digit code we email you) or, if you no longer have the app, ask us to delete it by writing to support@roadby.app from your account's email address, as explained on the Delete your account page. We aim to reply within 24 hours and, once you confirm, we delete the account within 7 days. No other user can delete your account. Whichever way it is done, when the account is deleted the deletion takes effect in the database at once: the account is removed and, in cascade, so are the profile, the position, the voice session, requests, friendships, blocks, history (for the other person in each pair as well), your conversations on our server and anything still waiting to be delivered, your membership of groups, your badges, pins and counters, your age confirmation and accepted terms, any block on the account, the reports other users filed about you, notification tokens, the notification record, the internal record of requests sent, the records of your profile photo attempts and of your group photo changes, the counters used to limit the photos and videos you send and the record of your consent to news emails; your profile photo is then deleted from its bucket, and on the phone where you delete the account the app also deletes your messages and their photos and videos. From that moment nobody can get a new link to the photos and videos you sent that are still on our server (a link already given keeps working until it expires, at most 10 minutes for a photo and 2 hours 10 minutes for a video, or until the file is deleted); they, and what we keep about them, are deleted within an hour (a video uploaded in the previous 3 hours, when those 3 hours have passed). Photos and videos that other people sent you, including any that had not reached you yet, belong to whoever sent them: they stay on our server, with what we keep about them (such as who they were sent to), until they are deleted automatically (A.5a), usually within a few days, as when you block someone (A.5). What survives deletion: the messages, photos and videos you sent, on the phones of the people who received them (unless you had deleted them for everyone, A.5a); a group photo you set, which belongs to the group; your message database and the photos and videos of your chats on a phone where you had already signed out, and your last Android backup (which never includes the photos and videos themselves) until the next one replaces it; the reports you filed, anonymised; copies of messages attached to reports about you, with their photos and videos, for up to 90 days after they were made; the random code of each of your phones, for 90 days, so that they delete your messages, photos and videos when they next open; the access audit log of the authentication system (account identifier, email address, action and IP address) and backups, for the periods set out under “How long we keep data”; settings stored locally on your phones (deleting the account in the app resets them on that phone only; if we delete it for you after an email request, they stay on every phone); the notification token already known to Expo and Google, whom we do not ask to delete it; and, if you asked us by email, your request and our replies, for 3 years after the deletion, as a record that we handled it. If we close an account under our child safety standards, we first save a copy of the information the authorities may need, as explained on that page; that copy is kept outside the account until they no longer need it, even if the owner later deletes the account.
Your rights
You can access your data, ask us to correct it, ask us to delete it, object to a particular use, or ask for portability of whatever is technically possible. Today you can do so as follows:
- Access: the essentials are visible in the app (profile, email under Change email, friends, requests, blocked users, history with its dates, your messages, photos and videos on your phone and your badges); for the rest (sign-up date, the counters described in A.2, reports you filed, registered devices, technical logs) or for a full copy, write to us and we will prepare it by hand.
- Rectification: directly in the app, under Edit profile, Change email and Change password.
- Erasure: Settings › Account › Delete account, in the app (with your password or, without one, a code we email you), or by email without the app, as explained on the Delete your account page. You can also delete a message (any message just for you, on that phone, or your own for everyone up to 60 hours after sending it), delete a chat (for you), delete a message request, leave a group or remove a group's photo (if the group lets you, A.5b).
- Objection and restriction: operating system permissions, blocking users, Friends mode, Mute, Who can message you, Read receipts, Back up messages, Show badges on my profile, muting a conversation or a group, Mute when parked and the “News and offers by email” switch.
- Any other request (including portability or unsubscribing from the newsletter): by writing to support@roadby.app; we handle it manually.
You also have the right to complain to the Spanish Data Protection Agency (aepd.es) if you believe we have not handled your request properly.
Minors
Roadby is only for people aged 18 or over. When you create an account, in the app or with Google, you must confirm that you are 18 or older; we only store that you confirmed it and when, not your date of birth, and we do not verify it. If we learn that an account belongs to someone under 18, we may block or close it.
Our child safety standards explain what we do to protect children and how to report a concern.
Security
All information travels encrypted (HTTPS/WSS). Passwords are stored as hashes; the most sensitive tables (location, voice, reports, tokens, messages, badges, age, accepted terms and account blocks) are not readable even by their own owner from the app, only through server functions with fixed rules. Messages are not end-to-end encrypted (A.5a). Photos and videos sent in chats are stored privately: the app can only open them through links that expire (a photo's after 10 minutes; a video's after the length of the video plus 20 minutes, 2 hours 10 minutes at most), and only for the people allowed to see them (A.5a); those attached to reports cannot be opened from the app at all. Administrative access is limited to the minimum number of people needed to run the service.
Changes to this policy
If we change this document, we will update the date shown at the top. While this is a provisional version, it may still change after the legal review. Once it is final, if we make an important change we will also let you know.
Contact
For any question about this policy or about your data: support@roadby.app.