Rumbo Maps privacy policy
Rumbo Maps is a phone map of Texas: search, directions, turn-by-turn guidance and traffic. No account is required, and it has no ads. This page says exactly what it sends, what it never sends, what our server can still see, and how long anything is kept. It also says what the app does not protect you from, because you should know that too.
Who runs Rumbo Maps
Rumbo Maps is run by Rumbo Maps, Austin, Texas, USA (“we”, “us”).
Questions, or a request about your data: alfredo@atxnexus.com.
The short version
- No account needed, no location sharing, no ads. Where you are, what you search for, where you go and what you save stay on your phone, except, with Help improve traffic on, the streets you drive, the traffic lights you wait at, what each drive taught Rumbo about your streets and junctions and, after a drive you navigated, the ways you took instead of Rumbo's (below). Signing in to a NEXUS account is optional and only copies your saved places and display choices to it (below).
- The map runs on the phone. The map, search, directions, turn-by-turn and voice are part of the app. No map, search or routing service is asked anything.
- Two things can leave the phone by themselves, each behind its own switch in Settings, both explained on the first screen before anything is sent: Help improve traffic (how fast traffic moved on road segments, never a position; and, after a drive you navigated, a way you took instead of Rumbo's with both times, which is not anonymous; and, while Learn from my drives is on, what each drive taught Rumbo about your streets, turns and turn-round places, which is not anonymous either) and Share usage statistics (counts of what was used in the app, never what you typed, never a place, never a location). Both start on.
- Two more go only when you tap them: a road report (what, and where you are to about 11 m) and a “Still there?” answer (which report, yes or no).
- You can see everything it sent: Settings → What this phone has sent.
- Music is your music app's own (Spotify, Apple Music, Pandora and others), a separate service. Rumbo Maps sends it nothing and holds no login of it: you sign in inside that app, and its own privacy policy applies there.
- What our server can still tell: every connection shows it your phone's internet address, and our hosting service logs that address for 7 days. While few phones use Rumbo Maps, whoever runs the server could use that log to tell which uploads came from the same phone, and could put a trip's traffic uploads back together into most of the route; since 17 October 2026, even while the drive is still going, about 2 to 30 minutes behind it. Nobody does this, and nothing joins them, but it is possible.
- Nothing is sold. There are no advertisers and no data brokers.
What stays on your phone
The app keeps these in its own storage on the phone. They are never sent.
| What | Kept | How to remove it |
|---|---|---|
| Your settings (units, voice, map style, the switches…) | until changed | Settings |
| Home, Work and up to 500 places on each list (Favorites, Want to go, Starred, Bookmarked), and which lists show on the map | until you remove them | Saved → remove |
| Recent searches and places (the last 30) | until cleared | Settings → Clear history |
| Your drives (the last 30): for each drive you navigated, the destination's name, when, the time and distance next to the recommended route's, how much of the way was on it and how many times you left it; no position, no track | until cleared | Settings → Your drives → Clear |
| Learned from your drives (switch: Learn from my drives, on unless you turn it off): how long each street you have driven and each turn or crossing you have made really took, at weekday rush hours and at other times, and the places you turned round. Worked out on the phone from each drive's GPS, which is held in memory during the drive and never written down; errands, parking lots, drive-throughs and circling are left out. No position, no track; these running figures are never sent and never copied to an account. It does show which streets you drive. Your own routes and arrival times use it once three drives agree. (What each drive teaches them is sent with Help improve traffic on: Learned times; and a navigated drive's best way: Best ways) | a street or junction not driven for 120 days goes; the rest until deleted | Settings → Learned from your drives → Delete |
| What Rumbo drivers taught: the street speeds, junction waits and turn-round places pooled from 3 or more drivers' uploads that agree, as our server publishes them to every Rumbo phone (Learned times). The same for every phone, nothing of yours; one copy, replaced by each answer | not used after 14 days without a new answer | turn Learn from my drives off (it is then not used) |
| The random id for usage statistics | 30 days at most | turn usage statistics off |
| The list of what this phone has sent (the last 200) | until cleared; the exact contents of traffic uploads, reports and answers only 24 hours | What this phone has sent → Clear this list |
| An upload waiting for its delay or a connection | traffic 11 hours, a traffic light, a best way or learned times 47 hours, statistics 46 hours, a report or answer 30 minutes, at most | turn its switch off; it also goes as soon as it can |
Uninstalling the app, or clearing its storage in Android's settings, removes all of it. The app does not allow Android to back it up.
Your location
Rumbo Maps asks for your location only while you are using it, never in the background. It uses it on the phone to show where you are, to guide you and, only if Help improve traffic is on, to measure traffic speeds as described below. During turn-by-turn the drive keeps going with the screen off; Android shows a notification the whole time, and End stops it.
Your position itself is never written to storage (a place you choose to save keeps its own position, on the phone), and a trip is held only in the phone's memory, each part of it only until it is handed to the upload queue (as the drive goes, since 17 October 2026: below).
With precise location allowed, the app listens to the phone's GPS alone. It never asks the phone's network or “fused” location, because on most Android phones those are answered by Google's location service, which sends the Wi-Fi networks and cell towers around the phone to Google. If you allow only approximate location, Android can give one only through its network location service, so the app uses that, and that service may consult Google. Nothing of this passes through Rumbo Maps or reaches our server.
Before the GPS answers (since version 3.0.46, 19 October 2026), the app may plan a trip from where the phone last was: the position Android itself keeps from the phone's last fix, read from the phone, which asks nobody anything. It is used only when it is at most 30 minutes old, labelled with its age, and only as a trip's start, as a start you type would be: never shown as where you are, never traffic or a traffic light. The first real GPS fix replaces it.
Help improve traffic
On by default, explained on the first screen, switch in Settings → Privacy.
What is sent
While you drive and after, small uploads like this one, each at its own random moment 2 to 20 minutes after it was handed over (as the drive goes since 17 October 2026; until then all of them after the trip ended):
{ "v": 1,
"graph": "austin@2026-09-28T19:33:16.550Z",
"batch": "3f6b1c2e-8d4a-4e7b-9a51-0c2d7e9f4a18",
"segs": [ [29052, "2026-09-28T15:10:00Z", 47],
[50426, "2026-09-28T15:05:00Z", 12] ] }
graphnames the road map inside the app, so the numbers mean the same on the server.batchis a new random id for this one upload, never used again and not tied to you, your phone or any other upload.- each entry in
segsis [road segment, 5-minute slot, speed in km/h]: a numbered piece of street (and its direction) on the app's own road map, the 5-minute slot of the day, and a whole-number speed. An upload holds at most 12 segments of the streets handed over together (the last 5 minutes of the drive, or its last 36 streets; the whole trip before 17 October 2026), dealt out in the order driven so that streets that follow one another never share an upload.
What is never sent
Not a coordinate. Not a time finer than the 5-minute slot (a traffic light carries its second: below). Not a device id, an install id or anything that identifies the phone. Not the accuracy of your GPS. But the whole trip is sent, its first and last streets included (since 2 October 2026), so the streets a trip starts and ends on, often your home or work, are among them.
How it is made, on the phone, before anything leaves
- Only real, precise GPS positions count, and only while driving (faster than about 7 mph for at least 10 seconds). Walking and a simulated drive never count.
- The phone matches its own GPS to streets and times each road segment it drives.
- Nothing is cut from the start or the end of a trip (since 2 October 2026; until then the first and last 500 m to 1 km were cut, and a trip under about 2 km sent nothing). Every street you drive is sent, short errands too.
- The streets are dealt into uploads of at most 12 segments, at least three uploads each time, so streets that follow one another never share one; each upload has its own random id and its own random delay of 2 to 20 minutes. Since version 3.0.17 (4 October 2026) they wait in the app's private storage on this phone and are sent when their delay has passed, even if you closed the app; turning Help improve traffic off deletes the ones still waiting.
- As the drive goes (since 17 October 2026: drives whose app was closed before they ended had sent nothing at all, and the owner chose to send as you drive): the streets already driven are handed to that queue at least every 5 minutes of driving, or once 36 of them wait, and each traffic light once you are 40 m past it; the rest when the trip ends. Each still waits its own 2 to 20 minutes from then, so a street can reach the server while you are still driving, about 2 to 30 minutes after you drove it, and a drive cut short loses at most its last few minutes of driving (streets crawled at under about 11 km/h wait until the car speeds up again or the trip ends). A street goes once per trip.
- What is not road travel is not sent (since 20 October 2026: the owner decided that how people really drive must feed the whole navigation engine). On Austin's map the trip's positions also go through the engine that learns from drives (in the phone's memory only, keeping nothing, whether Learn from my drives is on or not), and a street it reads as an errand, a parking lot crawled, a drive-through, circling, a turn-round or a GPS glitch is not sent. It sends less, never more; a crawl on the streets is a jam and is sent. To judge a stretch it must see what came after it, so the streets of the last 2 minutes wait for the next hand-over, and a street in a stretch still unfinished up to 5 minutes more: up to about 10 minutes later than before. Not yet on a drive routed across Texas beyond Austin's streets.
What the server does with it
A street's speed can only be read as the middle value of two or more separate uploads in the last 15 minutes. One upload's speeds are never shown to anyone. The individual rows are deleted after 24 hours.
What this does not hide. The random ids, the dealing and the delays stop the uploads themselves from saying which belong together. But each one arrives from your phone's internet address (see Your internet address), and while only a few phones use Rumbo Maps, the uploads that arrive from one address during a drive and up to 20 minutes after it, over streets that join one another, can be put back together into most of a route, including the street where it began and the street where it ended. Nothing is cut from a trip's ends any more, so an upload can show where a trip started and stopped, often your home or your work. Since 17 October 2026 the uploads go as the drive goes, so this could be done while the drive is still going, about 2 to 30 minutes behind it. If that matters to you, turn Help improve traffic off.
Also: the app's server key is public, as it must be for an app where accounts are optional, so anyone can send made-up speeds. The server limits how often one address may send; it cannot stop it entirely.
Traffic lights (since 2026-09-30)
So Rumbo Maps can learn when each light turns green (no public source in Texas says so), the same switch also sends this: when your car stood before a traffic light for 3 seconds or more and then drove through it, which light (its place as the map knows it, never a reading of your GPS), the way you came (one of 8 compass points), the second you pulled away, and how far back you stood (to 5 m). Since 2026-10-02 it also sends, the same way, a light you drove straight through (at 18 km/h or faster, the second you were nearest it) and the second you stopped as the first car at one, so Rumbo Maps can learn how long each green lasts. Since 2026-10-03 each also says whether you went straight on or turned left (read from your heading 40 m past the light), so a left-turn arrow is learned apart from the straight-on light; a right turn is never sent. Since 2026-10-17 a wait that cannot say when the light changed is never sent either: a pull-away counts only once your car has crossed the light (a queue moving up and stopping short of it says nothing, and its later pull-away is the green); a car that stood past the light while it waited, stood in the junction just after going through, or moved up and stood again only a few seconds (at a light mapped at the middle of its junction, moved up near it and stood under 20 seconds), cannot tell which move was the green; and a left turn during which it crawled forward, moved up and stood again right at the light, or stood again just past it, was made on a gap in the oncoming traffic, which says nothing about a left-turn arrow. Less is sent, nothing new. Any light of the trip, the first and last included, one light to an upload, each with its own random id and delay, handed over once you are 40 m past it (since 2026-10-17), and at most 40 of one trip; never from a simulated drive.
The server keeps each light, way, moment and second (for a pull-away, when the green began) and how far back the car stood, with no upload id and no address, for 84 days (28 until 21 October 2026, when the owner chose 84: in 28 days one driver's commute could never teach a light its cycle; keeping the rows longer also keeps a series of them longer). It shows only a light's learned cycle, once 9 or more greens on 3 or more separate days agree closely, could not have bunched by chance, each day is predicted by the others and the cars that drove through or stopped first do not contradict it ("Green in about 12 s" while you stand at it), and, once 20 or more drive-throughs show how long its green lasts, the light's estimated colour on the drive screen (always an estimate, never a reading of the lamp).
Only for the quarter hours it holds for (since 21 October 2026, the owner's choice): with few drivers a light's cycle is pinned down only near the times they pass, so each countdown is published with the quarter hours of the day where it holds (for example weekdays 07:15 to 07:45), and the app shows it only then. While one person's drives teach a light, that window says roughly when someone drives through there, on which days and from which direction, with no name, no id and no address. This is a precise place and second, and it arrives from your phone's internet address like every upload (see Your internet address).
Best ways (since 20 October 2026)
On 20 October 2026 the owner was offered pooling the best ways across every Rumbo driver, which needs a new upload, and said to do it, calling it anonymous information (paraphrased). It is not anonymous, and this page does not call it that. After a drive you navigated on Austin's map, the phone compares the way you drove with the route Rumbo recommended. Where you left Rumbo's route at a junction and came back to it at a later one, up to 3 such ways of the drive (picked at random) go, one to an upload, exactly like this:
{ "v": 1, "batch": "3f6b1c2e-8d4a-4e7b-9a51-0c2d7e9f4a18",
"graph": "austin@2026-10-05T01:39:49.237Z", "period": 0,
"mine": [365729, 132293, 182389], "rumbo": [159064, 159066],
"mine_s": 290, "rumbo_s": 347 }
periodis 1 when the drive was in a weekday's rush hours (6 to 9 and 15 to 19, Austin time), else 0; nothing finer.mineandrumboare the streets of your way and of Rumbo's way between the same two junctions, as road segment numbers of the app's own map;mine_sandrumbo_show long each took (Rumbo's at the live traffic of that moment), in whole seconds;batcha new random id.- Never sent: a coordinate, a time of day finer than rush hour or not, a date, a junction's number, the start or the end of your trip (a way that ends the trip, or begins with its first street, is never sent), any id but the upload's own. A drive you did not navigate, a simulated drive and a drive across Texas beyond Austin's streets send none.
- Behind Help improve traffic, listed in What this phone has sent as “Best ways” before it goes, each with its own random delay of 2 to 20 minutes; turning the switch off deletes those still waiting.
- The server keeps the map, the period, the two ways, the two times and the day it arrived, no upload id and no address, for 56 days. It shows only ways pooled from 3 or more separate uploads that were quicker than Rumbo's on average (with Rumbo's usual way, how many uploads and the mean time saved), inside the traffic answer every Rumbo phone already asks for, and the app then prefers that way when it plans. Three uploads can be one person's: the server cannot tell phones apart, so a way you drive three times can be published like any other; it carries no name, phone, date or time of day, but it is a way somebody drives often.
What this does not hide. No name, no account and no device id are sent, and no coordinates or times of day. But our server sees each phone's internet address (our hosting service's request log keeps it 7 days: Your internet address), and while few phones drive, a series of these uploads can be tied to one phone. A person's usual ways say where they live and work. If that matters to you, turn Help improve traffic off.
Learned times (since 20 October 2026)
On 20 October 2026 the owner decided (paraphrased) that what Rumbo's path engine learns from how people really drive must feed all of its navigation and be contributed to every Rumbo driver. It is not anonymous, and this page does not call it that. While Learn from my drives runs the engine and Help improve traffic is on, each drive it follows on Austin's map, with directions or without, is cleaned on the phone (stops for errands, parking lots, drive-throughs, circling, turn-rounds and GPS glitches are taken out), and what it taught goes in small uploads, exactly like this:
{ "v": 1, "batch": "3f6b1c2e-8d4a-4e7b-9a51-0c2d7e9f4a18",
"graph": "austin@2026-10-05T01:39:49.237Z", "period": 0,
"streets": [[132295, 46], [202271, 56]],
"moves": [[269536, 133700, 12]], "uturns": [401002] }
streets: a street driven cleanly end to end, as its road segment number and its speed in whole km/h;moves: a junction you went through, as the segment you came in on, the one you left by and how many whole seconds it took beyond driving through freely (0 to 180), never the junction's own number;uturns: a place you really turned round, as the segment whose end it is;period1 in a weekday's rush hours (6 to 9 and 15 to 19, Austin time), else 0, nothing finer;batcha new random id.- At most 12 items an upload, and a drive's items are dealt in the order driven so that no two in one upload touch the same junction and those of one upload lie 3 or more streets apart; at least 3 uploads when there are 3 items or more (6 once there are 6); each item once a trip; at most 240 items a trip.
- Never sent: a coordinate, a time of day finer than rush hour or not, a date, a junction's number, a device id, any id but the upload's own. A simulated drive and a drive across Texas beyond Austin's streets send none. The start and the end of a drive are not cut: the streets a drive starts and ends on, often home and work, can be among them.
- Handed over as the drive goes: a stretch every 10 minutes of driving, up to about 6 minutes behind the car (longer while a stretch is unfinished: a crawl, a lot), and the rest at the drive's end. Listed in What this phone has sent as “Learned times” before it goes, each with its own random delay of 2 to 20 minutes; turning either switch off stops them and deletes those still waiting, and turning Learn from my drives off also forgets the drive being followed at once: nothing more of it is learned or sent.
- The server keeps each item alone (the map, the period, the kind, the segment numbers, the speed or the seconds, the day it arrived), no upload id, no address, nothing that says which items came together, for 56 days. It publishes only figures pooled from 3 or more separate uploads that agree (their median and how many), rebuilt every hour, inside the traffic lights' timing every Rumbo phone already asks for when a drive starts; every phone uses them for routes, arrival times and where a car can turn round, beneath its own learned figures. Three uploads can be one person's: the server cannot tell phones apart, so a street you drive three times can be published like any other; it carries no name, phone, date or time of day, but it is a street somebody drives.
What this does not hide. No name, no account and no device id are sent, and no coordinates or times of day. But our server sees each phone's internet address (our hosting service's request log keeps it 7 days: Your internet address), and while few phones drive, a series of these uploads can be tied to one phone. A person's usual streets say where they live and work. If that matters to you, turn Help improve traffic off (or Learn from my drives).
Road reports and “Still there?”
Only when you tap them. There is no switch, because nothing is ever sent by itself.
A road report
Tap Report, then one of six: Jam, Crash, Object on road, Closure, Construction, Work zone. There is no police or camera report. Exactly this is sent, and nothing else:
{ "v": 1, "kind": "crash", "lng": -97.7417, "lat": 30.3025, "bearing": 190 }
That is the kind, where the phone is, rounded to about 11 m, and the direction you were driving to the nearest 10 degrees (or none when you were not moving). No id, no account, no accuracy; the server notes the minute it arrives. If there is no connection it waits at most 30 minutes, then is dropped.
Who sees it: every Rumbo driver, once a second person confirms it. Reports of the same kind close together are merged, and only when two or more different people stand behind one does it appear to others: its kind, its place, its direction, when it was first reported, how many confirm it, and when it expires. Nobody sees who made it, and the server does not store who.
A report lives 45 minutes (jam), 60 minutes (object on road), 90 minutes (crash), 6 hours (closure), 12 hours (work zone) or 24 hours (construction), half as long again for each different person who confirms it, and never more than twice that.
“Still there?”
When you drive past a confirmed report, the app may ask Still there?. If you do not answer, nothing is sent. An answer is exactly which report and yes or no. The server keeps one answer per person per report as a scrambled code made from your internet address, a secret key and that report, which cannot be linked to your answers on other reports. A report is removed when enough people say it is gone.
What a report tells the server
A report is, by its nature, a note of where you were when you made it. It is anonymous in our database, but like every upload it reaches the server from your phone's internet address, which the hosting service's log keeps for 7 days, so whoever runs the server could match a report to the address it came from.
Work zones
The map also shows work zones from traffic-control companies that use NEXUS Fleet, a fleet-management app, and chose to publish them: only the stretch of road and until when, never the company, customer, job, crew or truck. Nothing about you is sent to them.
Usage statistics
On by default, explained on the first screen, switch in Settings → Privacy.
Only these eleven things are counted, each with a few coarse details at most: the app was opened; a
search was made (how many results, in steps: 0, 1, 5, 10 or 20); a category such as Coffee or Gas was
browsed (which one, and the result count in steps); a place's card was opened; directions were found
(drive or walk, distance in steps); turn-by-turn started or ended (drive or walk, distance and time in
steps, and whether you arrived); a new route was found on the way; a place was saved; a place was shared;
something went wrong (a short error code such as map_failed).
{ "v": 1,
"install": "0b8e0d5e-3c52-4c7e-9f0e-2b7f6a1d9c44",
"app": "0.2.123",
"events": [ { "e": "app_open", "h": "2026-09-28T15:00:00Z", "p": {} },
{ "e": "search", "h": "2026-09-28T15:00:00Z", "p": { "results": 5 } } ] }
installis a random id so that counts from one phone can be told apart from counts from many. It says nothing about you or the phone, is replaced every 30 days, and is forgotten when you turn usage statistics off.appis the app's version;his the hour, never the minute.- Never what you typed, never a place's name, never a street, never a position.
They are sent when the app starts, every 30 minutes while it is open, when it goes to the background, and (since 17 October 2026) when a drive ends. They are deleted after 90 days.
What the app asks our server
To show traffic, road reports and work zones, and to plan routes around them, the Android app asks our server for the current traffic, at most about every 2 minutes, only while the app is on screen. That question carries only the road map's name, nothing about you. It is asked even with both switches off, but never before you have finished the first screen: the first time you open the app, nothing at all is sent until you have read it and chosen. The answer holds street speeds (each the middle value of two or more trips, or of two or more NEXUS Fleet trucks, and marked with where it came from), the City of Austin's public traffic incident reports of the last 30 minutes, the city's traffic signals, the confirmed road reports, the published work zones and (since 20 October 2026) the best ways pooled from 3 or more uploads.
When a drive with directions starts, and every 10 minutes while it lasts, the app asks for the traffic lights' learned timing (the countdown at a light). That question carries nothing. Since 20 October 2026 its answer also carries what every Rumbo driver's drives taught (Learned times) for the newest Austin map; the phone keeps one copy of it, the same for every phone. No new question was added for it.
About once a day, while the app is open, it also asks which Rumbo Maps version is the newest. That question carries nothing, not even the app's own version (since the release after 0.2.86 its request says only "RumboMaps"; before, the request's User-Agent named the version), and like every call it comes from your internet address. The phone compares for itself and, when a newer one is out, shows a notification and a line in Settings that open rumbomap.com's download in your browser. The app never downloads or installs anything by itself; Android asks you before installing. Only the copy from rumbomap.com asks this (since 17 October 2026): the copy from Google Play never asks and is updated by Google Play.
If you sign in to a NEXUS account (below), the app also calls five account functions on the same server: to trade the sign-in page's one-time code for your account's key, to check it, to read and write the two documents below, and to sign out.
The weather
Since version 3.0.19 (4 October 2026) a line under the search bar shows the weather for the area the map is looking at, from the US National Weather Service, and opens to the next hours, the coming days and any alert. To get it the phone asks our server for one map square (about 42 miles across, the same name a map download sends) and nothing else: not your position, not where you are going, no id. Each ask is in What this phone has sent. Our server fetches the forecasts from the Weather Service itself; the Weather Service never hears from your phone.
Since version 3.0.22 (4 October 2026) the square is the one you are in, not the one the map shows (until the phone knows where it is, it is the map's). So it tells our server which ~42-mile area you are in, as a map download for where you stand already does, and with your internet address in the gateway's log it can be tied to a phone. The town the line names is worked out on the phone and never sent.
Bringing your lists from another map app
Since version 3.0.23 (5 October 2026) Saved → Bring your lists reads the data export you download from your other map app yourself (a .zip, or the CSV and JSON files inside it), picked with Android's own document picker. It is read in memory on your phone: nothing in it is sent anywhere and no link in it is opened. A place keeps the position its file gives; where the file has only a name, Rumbo looks for exactly one place of that name in its own map, on the phone.
Map downloads
Rumbo Maps covers all of Texas. The app carries the whole state's big roads, water, parks and towns, and Austin's streets. The streets, places and addresses of the rest of Texas come in areas about 42 miles (67 km) across, which the app downloads when the map rests on an area at street level, when you plan a trip through it (a trip's areas are asked for together, never one by one as you drive), when you send a search for an address that names its town (that town's one area, so its addresses can be found; never while you type; a place's name is found from the app's own list of every named place in Texas, with no download), or when you choose Download all of Texas in Settings.
A download is a plain request for that area's public map file on the same server the app already uses: no key, no id, no cookie. It tells the server which area, never where in it you are; Download all of Texas tells it only that. Like every call it comes from your phone's internet address, which the hosting service's log keeps with the time for 7 days (below), so an area asked for is a rough place your phone was looking at or going to. An area stays on your phone until you remove it (Settings → Maps of Texas), and every download is listed in What this phone has sent.
In a web browser (since 17 October 2026). The web app at rumbomap.com/app/ downloads the same public files itself, and only what you need: the one area under the middle of the map when it rests at street level (when the map follows your location, that is the area you are in, so the server learns an area near you, and the next one as you cross into it), the areas a trip goes through, and a town's area when you send a search for an address in it. It never downloads all of Texas, opening the page downloads nothing by itself, and with your browser's data saver on, looking at the map downloads nothing (a trip still gets its areas). Each request is a plain one with no key, no cookie and no referrer; the server learns which area and sees your internet address. An area is kept in browser storage only when its size and fingerprint (SHA-256) match the published list, until you remove it (Settings → Maps in this browser) or the browser clears it.
Reviews and place boards
Rumbo has its own ratings: for a place on the map, an overall rating of 1 to 5 stars, any of ten areas (taste, cleanliness, presentation, service, value, atmosphere, speed, consistency, menu, accessibility) and a few words, and a board for each place where people ask and answer questions. Rumbo copies no review from any other service.
The city's health inspections (since 2026-10-03). Beside Rumbo's own rating, an Austin-area restaurant shows the City of Austin's latest health inspection score from the city's public list, labelled as the city's record and never counted in a Rumbo rating; its board has a button to talk about whether it is right. The scores come inside the same area read below, so nothing more leaves your phone, and the place they belong to is worked out on your phone.
Nothing is read until you say so. The first time you open a place, the app asks: Show reviews or Map only, and you can change it in Settings → Reviews & boards. Reading needs no account: the app asks our server for the area about 42 miles across that the place is in, never which place you opened, and each read is listed in What this phone has sent. With reviews shown, the search screen's suggestions read the same area's answer for where they are; with Map only nothing is read.
Writing needs a NEXUS account and happens only when you tap Post. A review or a post is public on Rumbo under your NEXUS username (never your full name or email), with the place and the date; the place is the map's own, never where your phone is. Removing your own hides it at once (it is marked removed, not erased); three different accounts flagging something hide it; deleting your NEXUS account erases everything it wrote. Opening hours you add for a place the map has none for are an ordinary board post (the hours as text): public under your username, shown as a Rumbo user's word, never as the map's. Places connected to the Rumbo Maps team (Este and Suerte) say so and can never win a Rumbo award.
Posting terms and blocking. Before your first review or post the app shows our posting terms and sends nothing until you agree. The server then keeps one record per account saying that you agreed to which version, and when; it is erased with your account. Blocking someone hides their reviews and posts on your phone. The list of people you blocked stays on your phone only: it is never sent to us, and nobody is told they were blocked.
What NEXUS Fleet reads from Rumbo Maps
NEXUS Fleet, a fleet-management service run by the same people, uses Rumbo Maps' map and traffic to route its trucks. It reads only what every Rumbo driver can already see: the map files built from OpenStreetMap, and the traffic answer (street speeds combined from two or more separate uploads, confirmed road reports, and published work zones), at most every 5 minutes while one of its maps is open.
It never reads your uploads, your unconfirmed reports, your answers or the usage statistics, and it cannot learn who you are or where you drove: nothing Rumbo keeps would tell it.
What NEXUS Fleet trucks add to the traffic
The owner decided on 2026-09-30 (paraphrased) that NEXUS Fleet and Rumbo Maps feed each other's traffic. So the street speeds on the map now come from Rumbo drivers and NEXUS Fleet trucks. No phone sends anything new for this, not yours and not a fleet driver's: our server works it out from the position reports the trucks' trackers already send to NEXUS Fleet, and only for companies whose fleet admin switched Share our trucks' road speeds with Rumbo Maps on. It starts off for every company; NEXUS's own trucks are on, by the owner's decision of the same day.
Only reports that are recent, accurate to about 30 m and carry a speed and a direction of travel are used (a missing direction is never guessed), and nothing within about 300 m of a place where a truck stood still for 3 minutes or more, so no depot, job site or stop can be read from it. For each street and 5-minute slot the answer gets one number, the middle speed, and only when two or more different trucks agree. It never carries a truck, a driver, a position or the company, and the worked-out speeds are deleted after 24 hours. Each street speed says where it came from (Rumbo drivers, NEXUS Fleet trucks, or both), and the map's traffic panel shows it. Nothing about you is sent to NEXUS Fleet for this.
Your internet address
Like any connection on the internet, every upload and every traffic question shows our server your phone's internet address. Two things keep it:
- Our own tables use it only to limit how often one address may call (120 traffic uploads, 60 statistics uploads, 20 reports, 120 answers, 120 best ways, 600 learned-times uploads and 600 traffic questions an hour). They keep it only scrambled with a secret key, and delete it after 2 hours. The key stays inside the database; the database's administrators can read it.
- Our hosting service's request log (Supabase, whose service runs behind Cloudflare) records every call in the clear: the internet address, the approximate place and network it belongs to, the app's name and version (for the update question, the name only), the exact time, and which function was called. It is kept for 7 days, and whoever runs the project can read it. The app cannot switch this off.
That log is what would let a determined person on our side tie your uploads to each other and to your address. We do not do this, and nothing in the app or the database joins them; but it is possible, and you should know it.
How long things are kept
| What | Where | Kept |
|---|---|---|
| Traffic uploads (the individual rows) | our database | 24 hours |
| When a light's green began (and how far back the car stood), or a car drove through it or stopped first at it (no id, no address) | our database | 84 days |
| A best way: your way and Rumbo's, the two times, rush hour or not, the day it arrived (no id, no address) | our database | 56 days |
| Learned times: each street speed, junction wait or turn-round place alone, rush hour or not, the day it arrived (no id, no address, nothing tying it to its upload) | our database | 56 days |
| Usage statistics | our database | 90 days |
| A review or a board post you wrote (public, under your username) | our database | until you remove it or delete your NEXUS account (removing hides it; deleting the account erases it) |
| A road report | our database | its life above (45 minutes to 48 hours at most), then deleted one to two hours after it ends or is removed |
| “Still there?” answers | our database | deleted with their report |
| Scrambled internet address for the call limits | our database | 2 hours |
| Internet address, approximate place, time and function of every call | the hosting service's request log | 7 days |
| Anything above that was already deleted | the database's daily backups | up to 7 more days |
Deletion runs every hour on its own, so each time above can run up to an hour longer; nobody has to ask for it.
Who else handles it
Our server is a Supabase project (database hosting), whose service runs behind Cloudflare. They store and carry the data above for us and for nothing else. We share nothing with anyone else: no advertisers, no analytics companies, no data brokers, and nothing is sold. We would disclose data only if the law required it, and there is very little to disclose: nothing we keep names you.
Your music app (Spotify, or another you choose) is its own app and its own service: we are not in between and send it nothing (see Music).
The app also switches off two things the phone's built-in web component would otherwise do: its own usage reports to its maker, and its “Safe Browsing” address lookups (the app only ever shows its own bundled pages).
Your choices
- The two switches (Settings → Privacy). Turning Help improve traffic off drops the trip being held and every traffic, traffic light, best-way and learned-times upload still waiting, at once, and nothing more is measured. Turning Learn from my drives off stops the path engine and drops the learned-times uploads still waiting. Turning Share usage statistics off drops the waiting counts, forgets the random id, and nothing more is counted.
- What this phone has sent (Settings) lists every upload, newest first: when, what kind, whether it went, and the exact contents (for traffic, lights, best ways, learned times, reports and answers, for 24 hours).
- Road reports are never sent unless you tap one.
- Location: you can refuse it, or allow only approximate location, in Android's settings. Search and directions from a place you choose still work.
- Deleting what we hold. Everything is deleted automatically on the schedule above. Because nothing we keep names you, we usually cannot find your records. Your usage statistics are the exception: the random id is shown in What this phone has sent; send it to alfredo@atxnexus.com and we will delete the statistics that carry it.
Things you start yourself
Share opens Android's share sheet with the place's name, address, coordinates and a link to that spot on openstreetmap.org; you choose where it goes. Call opens the phone's dialer; nothing is dialled for you. Website opens the place's website in your browser. “Open in maps” links from other apps open the place in Rumbo Maps; nothing about them is sent. Nothing is sent on your behalf.
Music (the app you choose)
Your music plays in the music app you choose in Settings → Music or on the drive's music sheet: Spotify, Apple Music, Amazon Music, Pandora, SoundCloud, Deezer, TIDAL, iHeart, Audiomack or Qobuz (since 17 October 2026; Spotify before). Each is a separate app and a separate service. Rumbo Maps can open it and work its play buttons. What follows says Spotify; it holds the same for the app you choose.
- Your choice stays on your phone. Rumbo Maps remembers which app you chose, on this phone only: it is never sent and never copied to an account. The app is told which one by a single number (its place in the list), and nothing else. It names all ten in its manifest, as Android requires, so it can tell which are installed; that is not a permission and reads nothing from them. With Notification access (below) it reads the music controls of the app you chose alone, and lets the old one's go when you change. Liked Songs and "Device broadcast status" are Spotify's own and appear only with Spotify chosen.
- You sign in inside Spotify's own app (from your phone's app store), once, and it keeps you signed in. We never see your login, and nothing of Spotify's is kept in Rumbo Maps. Spotify's own privacy policy applies in Spotify's app, not this one.
- Rumbo Maps sends Spotify nothing. Not where you are, not your route, not your searches or saved places, not an id. Rumbo Maps cannot reach Spotify's servers at all. It can open Spotify's app (or your phone's app store at Spotify's page), and its play, next and back buttons press your phone's own media keys, like a car's steering-wheel buttons: they work on whatever is playing.
- To know whether Spotify's app is on your phone, the app names it in its manifest, as Android requires; that is not a permission and reads nothing from Spotify's app.
- Liked Songs and the song playing. A Liked Songs button opens your Liked Songs inside Spotify's own app. If you turn on "Device broadcast status" in Spotify's settings, Spotify's app tells your phone which song is playing, and Rumbo Maps shows its title and artist while you drive. The song stays on your phone: it is held only while the app is open, and never stored, sent, counted or copied to an account. Turn that Spotify setting off and no song is shown.
- The cover, the album and where the song is, only if you allow it. Android lets one app see another app's music controls (the ones on your lock screen) only with a permission Android calls Notification access. Rumbo Maps asks for it once, from the Spotify sheet; you turn it on, or off again at any time, in Android's own settings. Rumbo Maps uses it for nothing else: it reads no notification, and it reads the music controls of Spotify alone (any other app's are ignored): the song, artist, album, cover, length, where the song is, and Spotify's own buttons such as like and shuffle. Dragging the bar or tapping one of those buttons hands Spotify one number (a place in the song, or which button) and nothing else. All of it stays on your phone: held only while the app is open, never stored, sent, counted or copied to an account.
- Up next, shuffle and repeat (since 25 October 2026, with the same access). Rumbo Maps also reads what the music app says plays next (titles and artists, at most ten) and shows it on the music sheet. Tapping one of those songs, or shuffle or repeat, hands the music app one number (which song, or which setting) and nothing else. Music apps do not tell other apps whether shuffle or repeat is on, so the sheet shows only what you picked there. Like the rest, it stays on your phone.
A NEXUS account (optional)
Rumbo Maps works the same without an account, and nothing asks you to make one.
Open since 3 October 2026 (Rumbo Maps 3.0.9). Until then the service was still being built, and the app offered no Sign in and asked nothing about an account.
- Signing in happens in your phone's browser, on the NEXUS Accounts page, not inside Rumbo Maps. Rumbo Maps never sees your password or your email. The page sends your browser back to the app with a one-time code, which the app trades once for a key to your account, kept encrypted by your phone's own keystore.
- While you are signed in, two things are copied to your account, and nothing else: your saved places (Home, Work and your Starred places: each one's name, a line of address or kind, and its position; your Favorites, Want to go and Bookmarked lists, and which lists show on the map, stay on this phone) and your display choices (units, voice, map style and its day/night schedule, the traffic layer, avoid highways, places on the map, the speed chime), so they follow you to a new phone.
- Never: your recent searches, a trip, your location, traffic, a traffic light, the random install id, or the two sharing switches (each phone keeps its own).
- Each copy is listed in Settings → What this phone has sent. Signing out keeps everything on your phone and stops the copies; your account keeps its copy until you delete it at accounts.atxnexus.com (Settings → Account → Delete account opens it in your browser), where you can also download it or forget your Rumbo Maps data. Because each copy carries your account's key, it is tied to your account: that is its purpose.
Children
Rumbo Maps is a driving app for adults. It is not directed to children, and we do not knowingly collect personal information from children under 13. Nothing it sends names a person, so we could not tell a child's upload from anyone else's; if you believe a child has used it and want something deleted, write to alfredo@atxnexus.com.
Where it works
On Android, Rumbo Maps provides streets, directions and address search across Texas. Austin's streets are bundled; other areas download as described under Map downloads. The browser app has the Texas overview and Austin's streets, and downloads other areas only as you need them, from the same public files (see Map downloads, "In a web browser"), without a key, account, location payload or cookie. An area is available offline only after its size and SHA-256 checks pass and it is kept in browser storage; when persistent storage is unavailable, it is available only for the current session. Uploads still need the Android app. Our server and its hosting service may store data in the United States or elsewhere.
Changes to this policy
If what the app sends or keeps changes, this page changes with it, and the date at the top changes too. If a change would let something new leave your phone, the app will say so on screen before it is sent.