If someone you love is about to ride one of these, the question isn't which features the app has. It's whether it's careful, and whether it's honest when it isn't sure. Here is what SlowGo checks, what it refuses to do, and what it will tell you it doesn't know.
One rule, and the rest follows
SlowGo builds routes around roads posted 35 mph and under. That's the whole idea, and everything else on this page is what happens when a road isn't that. When a trip can't avoid a short faster stretch, that stretch is drawn in amber and named before you ride — the road, how far it runs, and its posted limit, or where there isn't one, the words speed limit unposted. A road over 45 mph is never part of a route you'd travel along — whether we found that posted, or decided it because the road had no limit on record. Briefly crossing one at an intersection is a different thing — sometimes unavoidable — so SlowGo names the crossing and tells you to slow down and check for traffic rather than pretending it isn't there.
Checked before you can start
Before the Start button will unlock, SlowGo checks the route you picked, piece by piece, against speed data on its own servers. While that's running, the button says Checking speed limits… rather than letting you go. If the check can't finish — a gap in the data, a stretch it couldn't read — the answer is not "probably fine." Start stays locked, and the card tells you why: We couldn't confirm the speed limits out here. A check that covers part of a route is treated as a failure, not as a result.
Paths get a second question
Some routes use a real stretch of path rather than road. Where that stretch is long enough to matter, SlowGo asks the shared map one more thing before you go: is this path recorded as open to golf carts? While that question is out, Start waits and the button reads Checking path access… That wait is the only moment this check holds the button.
The answer is disclosed, never used to block. Where the map carries no cart-access note on those paths, the route reads Includes 0.4 mi of paths — cart access not confirmed. Where the question couldn't be answered at all, it reads Couldn't check path access — ride these sections with local knowledge. Both of those routes still start. A missing note is missing information, not a prohibition — the map is patchy about cart access, and a rider standing at their own gate knows that street better than the map does. The two checks are worth keeping apart: the speed check is about posted limits and its answer can refuse Start, while this one is about what the map records and only ever tells you what it found.
When we don't know, we say so
Plenty of roads carry no posted speed limit in the map data at all. SlowGo does not invent a number for them. It judges them conservatively by the kind of road they are, and then says exactly that on the route — 0.4 mi unposted, judged by road type — instead of a tidy figure it never read. The flat phrase 35 mph and under is reserved for routes where every limit came off an actual sign.
When a road has no speed on record
Not every road has a speed limit on record. Sometimes there's no sign. Sometimes the sign exists but nobody wrote it down in any public dataset. Either way, we don't know the number — and we never invent one.
What we do instead is look at what kind of road it is. A quiet residential street gets treated like a quiet residential street, and we'll route you on it with the label you'll see elsewhere on this page. But a road built like a fast road gets treated as over 45 and kept out of your route, and the app tells you why: treated as over 45 — no posted limit on record. The phrase treated as is doing real work. It means this is our call about the road, not a number we found posted on it. We'd rather send you around a road that turns out to be fine than down one that turns out not to be.
No route beats a bad route
Sometimes there is no way to get where you're going that stays on slow roads. SlowGo says so and stops. The screen reads That one's a NoGo. It will not quietly put you on a fast road to make the trip work — that's the app telling you the truth about the roads, not the app failing.
Your eyes are still in charge
All of this runs on map data, and map data can be incomplete, wrong, or behind what's actually on the pole. Where a posted sign and SlowGo disagree, the sign wins, every time. Whether a cart belongs on a given street is a local question — the rules vary town by town, and SlowGo doesn't decide it for you or claim a route is legal. That's a design decision, not fine print: the app is a careful second opinion about the roads, and the rider is the one driving.
Your privacy, in one breath
No account, no sign-in, nothing to log into. Routes are calculated and their speed limits verified on our own servers, so no outside routing company receives your trip. Your saved rides stay on your phone, and you can turn saving off or clear them in Settings. We don't sell your location and we don't show ads. The whole of it is in the Privacy Policy.
How it's tested
SlowGo's routes are tested by measurement: surveyed realistic cart trips — house to town square, neighborhood to grocery store — run against the same servers the app uses. Those trips come from the two Florida markets where our measured testing concentrated — The Villages and Delray Beach — and from Georgia around Peachtree City, and they sit alongside adversarial probing that tries to make the router do something it shouldn't, plus a series of code audits before launch. Rides can begin anywhere in Florida and Georgia; the measured testing sits in those markets. And the honest limit, said plainly: no one has ridden these routes in a cart yet. A rider beta in The Villages comes before wide release.
SlowGo is built by one person, nights and weekends, in Lockport, New York — with every intention of riding these routes too, not only measuring them. If anything on this page reads like a bigger promise than the app keeps, tell me: hello@slowgoapp.com.