Privacy Policy

Roadze is a map of public traffic cameras, on the web at roadze.com and as an Android app. On the web you can use most of it without an account and without giving us anything; the Android app asks you to create one before the map opens, because favourites, recordings and location sharing all live in that account. This page explains exactly what we keep when you have one, and what the app does on your phone.

The short version

  • On the web, watching cameras needs no account and no personal data. The Android app asks for an account before the map opens.
  • We do not sell your data, we do not share it with data brokers, and there is no advertising in Roadze.
  • Your location never leaves your phone unless you start a trip or deliberately share it with someone you chose.
  • We keep no location history. While someone is watching you we store one position — the current one — and it is deleted the moment nobody is.
  • You can delete your account and everything in it from inside the app or from the website, whenever you want.

Who we are and what this covers

Roadze is made by WorkBook Studios. This policy covers the website at roadze.com and the Roadze app for Android (com.roadze.app). They are the same service and share the same account, so one policy covers both; where the app does something the website cannot, it says so.

For questions about privacy, or to exercise any of the rights below, write to workbook.corp@gmail.com. A person reads it.

What we store, and only if you give it

DataWhyHow long
Email addressTo create your account, sign you in, and send account emails (confirmation, password reset).Until you delete the account
Username, name and profile photoYour @username is how other people find you to share location. The name and photo only if you add them, or if they come from the provider when you sign in with Google, GitHub or Discord.Until you change or delete them
PasswordStored hashed by our authentication provider. Nobody at Roadze can read it — not even us.Until you delete the account
Recordings you makeSo you can find them again in your account. They are kept in a private bucket that only your account can read.Until you delete them
Who you share your location withSo the people you chose can see you and you can see them: who asked, who accepted, and when it expires.Until you stop sharing or the share expires
Your current position, while you are sharing itSo the people you chose can see where you are. One row, overwritten as you move — not a trail.Deleted as soon as nobody is watching
Home and work, and places you saveSo the app can tell you how long it takes to get there, and so the same places show up on your phone and on the web. They travel with your account encrypted on your device: the server stores a package it cannot read.Until you delete them
Favourites, language, map settingsTo keep the app the way you left it. On the web they live in your own browser; in the app, on your phone.Until you clear the app's data or your browser data
Changes to your email addressSo you can undo one if it wasn't you who made it. We keep the old address and the date.Until you delete the account
The browser and system you sign in with, and the IPTo email you when your account is opened from a browser it hasn't been opened from before. It's how you find out on the day it wasn't you. No version numbers, and the IP is shown in the notice but never decides on its own.Until you delete the account
A device token, if you use the appA random, signed identifier for your phone, so the app can ask whether someone has requested your location while it is closed. It is not an advertising ID and it tells us nothing about you or your phone.Until you sign out or uninstall

Location: when the app uses it, and what for

Location is the one thing worth reading carefully, so here is every case, including the ones that run with the screen off.

WhenWhat happensDoes it leave your phone?
You open the mapYour position draws the blue dot and sorts cameras by how close they are.No
You drive with navigation onYour position follows the route, announces turns and warns about cameras ahead. It keeps working with the screen off, and a permanent notice sits in your status bar the whole time.Only the coordinates needed to calculate the route, and only to Mapbox
You share your location with someoneYour current position is sent to our server so the people you chose can see it, until you stop or the share expires. A permanent notice sits in your status bar while it is on.Yes — to the people you chose
A home-screen widgetShows the nearest camera or your time home. The position is read on your phone.Only what Mapbox needs to calculate the travel time
The app is closed and you are not sharingNothing. No position is read, sent or stored.No

The app asks for background location only because of the two cases above — a trip and an active share — and Android shows a permanent notification whenever either is running. You can say no to the permission and still use the map, the cameras, the search and your recordings. On the website there is no background anything: the browser only knows where you are while the page is open and you allowed it.

Sharing your location with people you choose

Sharing is off until you turn it on, person by person. You pick who, and for how long: one hour, eight hours, a day, or until you switch it off. They get a notification asking them to accept, and either side can cut it at any moment.

While a share is active we store a single row with your current position, and we overwrite it as you move. We do not build a history and we cannot show anyone where you were yesterday. When the last person stops watching — because it expired, because you stopped it, or because they did — that row is deleted, so your last position is not left sitting there.

The people you share with see your position, your @username, your name and your photo. That is the point of it, and it is the only case where another person receives anything of yours.

Notifications

The app asks for permission to send notifications so it can tell you when someone requests your location, and to show the permanent notice while a trip or a share is running. If you say no, everything else keeps working.

We do not use Firebase or any push provider. Instead your phone asks our server, every so often, whether there is anything pending for it, using the signed device token described above. Nothing is sent to Google about you for this.

Recordings

A recording is a clip of a public traffic camera that you chose to capture. There is no microphone: the app never asks for it and cannot record sound. Cameras are public government feeds, and we do not add anything to them.

Recordings you save go to a private bucket that only your account can read, so they are yours and not public. You can delete any of them, at any time, and they go with your account if you delete that.

Where the map opens

When you first open Roadze on the web, the map has to point somewhere. Instead of always starting in Las Vegas, our server looks up the rough city your IP address belongs to and starts there. That is all it is used for.

Three things worth being clear about. Your browser never talks to that service — our server asks, so your IP is not handed out from your machine. The answer is city-level, often the city of your internet provider rather than yours, which is why it is never drawn as your location: it only chooses the starting view. And if you have used the site before, your last map position wins over any of this.

This is separate from the location permission. Roadze only knows where you actually are if you turn that on yourself.

What we do not do

We do not build advertising profiles, we do not sell data, and we do not share it with data brokers. We do not track you across other websites or other apps. There is no advertising in Roadze, on the web or in the app.

There is no analytics SDK, no crash-reporting SDK and no advertising ID in the app. On the website we count visits with Google Analytics 4 — pages opened, country, device, where people came from — with the advertising features switched off and without your IP address being stored; the Cookie Policy explains it. Beyond that count, where no account is needed, we do not know who you are while you browse the cameras.

Companies that process data for us

Running the service means relying on a few providers. Each only receives what it needs to do its job, and none of them is allowed to use it for anything else:

ProviderWhat it handles
SupabaseAccounts, sign-in, your profile, who you share with, and stored recordings. Receives your email and any profile details.
BrevoDelivers account emails (confirmation, password reset, welcome). Receives your email address.
Google (Google Analytics 4)Counts visits to the website: pages opened, country, device and where you came from. Receives your IP address to work out the country and does not store it. Never receives your email, your account or your location. Not present in the Android app.
MapboxDraws the map, calculates routes and searches addresses. Receives the technical requests your device makes, including your IP address, and — when you navigate or search — the coordinates or text needed to answer.
Google, GitHub, DiscordOnly if you choose to sign in with one of them. They tell us your email, and your name and photo if you have them. We never receive your password there.
ipwho.isTurns an IP address into a rough city, so the map opens near you instead of always in Las Vegas. Our server asks, not your browser, and the answer is kept for 12 hours. City-level only — it is never shown as your location.
RailwayHosts the service. Handles the traffic between your device and Roadze.
Google PlayDistributes the Android app and tells us how many installs and crashes there are. It never receives your account or your location from us.
State DOTsThe camera images themselves come from public government feeds. We request them; they do not receive anything about you.

What the app asks your phone for

PermissionWhat it is forCan you refuse it?
Location (while using the app)The blue dot, cameras near you, navigation, travel times.Yes — the map, cameras, search and recordings still work
Location (in the background)Keeping a trip or an active share alive with the screen off. Android shows a permanent notice while either is running.Yes — trips and sharing then only work with the app open
NotificationsLocation requests from other people, and the permanent notice during a trip or a share.Yes
StorageSaving the clips you record onto your phone.Yes — you then cannot save recordings to the phone
Stay awake and audio settingsKeeping the screen on while you drive and speaking the turn instructions out loud. No sound is ever recorded.Not asked — these collect nothing

Every permission can be taken back at any time from Android Settings, and the app keeps working without them, minus whatever that permission was for.

How we look after it

Everything travels encrypted over HTTPS, on the web and in the app. Passwords are hashed by our authentication provider and cannot be read by anyone, us included. Recordings live in a private bucket, and the database refuses, row by row, to hand your data to another account — that rule is enforced by the database itself, not only by our code.

We ask for as little as we can, and what we do not store cannot leak. That is why there is no location history here.

Deleting your account and your data

In the app: Settings → Account → Delete account. On the web: Settings → Account. Same button, same account, either place.

When you do, it is scheduled for deletion and kept for 30 days — a grace period so an accidental or angry deletion can be undone. During that time you can recover it by signing in again. After 30 days it is deleted permanently by an automatic job, together with your recordings, your profile, your shares and anything else attached to it. That deletion is final: we cannot bring it back.

If you cannot get into your account, write to workbook.corp@gmail.com from the address on the account and we will delete it for you.

Your rights

Wherever you live, you can ask for a copy of what we hold about you, ask us to correct it, or ask us to erase it. Write to workbook.corp@gmail.com from the address on the account and we will handle it within 30 days. Most of it you can do yourself, without asking anyone, from Settings.

If you are in the European Economic Area, the United Kingdom or Switzerland, we handle your data to perform the contract you accepted when you created the account (having an account, sharing location with people you chose), to meet a legal obligation, or on our legitimate interest in keeping the service running and secure. You also have the right to portability, to object, and to complain to your local data protection authority.

If you are in California, we do not sell your personal information and we do not share it for cross-context behavioural advertising — we never have. You can ask what we collected, ask us to delete it, and we will not treat you differently for asking.

Where your data lives

Roadze is run from the United States and our providers store data there. If you use it from outside the US, your data is transferred there — with the standard contractual clauses where the law requires them.

Children

Roadze is not aimed at children and we do not knowingly create accounts for anyone under 13. If you believe a child has an account here, write to us and we will remove it.

Changes to this policy

If we change how any of this works, we update this page and the date at the top. If the change is significant and you have an account, we will email you rather than hope you notice.

Last updated: 15 September 2026