Keepwright

Notebook · 8 June 2026 · 5–6 min read · Alpesh Patel

What every mileage app asks for.

Before we built ours, we sat down and installed the popular mileage trackers one after another — the way a new user would. The striking thing wasn’t any single feature. It was how much each one asks you to hand over before it will log a single mile.

The first five minutes

Install a typical subscription mileage tracker, and the first few minutes look something like this. Not every app does every step, and the order varies — but across the leading ones, this is the shape of it:

None of this is a scandal. Each step has a reason from the app-maker’s side: the account anchors a subscription, the email and number feed lifecycle marketing, the cross-app tracking feeds ad attribution, the bank link feeds an expenses upsell. It’s a coherent machine. It’s just a machine you’re feeding before you’ve got anything back.

By the time a typical tracker has let you log your first mile, it can know your email, your phone number, and have asked to follow you across other apps.

What ours asks for

Mileage Tracker opens to the app. There is no account screen, because there is no account. To do its one job — notice when you’re driving and log the trip — it asks for the permission it genuinely needs: location, including in the background, so it can catch a drive even when the app is closed. We ask for that one honestly, and we tell you why at the moment we ask.

That’s the ask. Here’s the rest of the list — the things we’ve designed the app so it never has to request:

Why the difference isn’t really about virtue

It would be easy to frame this as us being the principled ones. The more honest framing is that the long onboarding and the short onboarding are each a direct consequence of a business model.

An app funded by a monthly subscription needs the account — that’s where the billing relationship lives. An app that wants to keep you needs your email and your number to win you back when you drift. An app that monetises attention needs the cross-app tracking. The asks aren’t bolted on; they’re the foundations of how that app makes money from you over time.

We make our money once, when you buy the app, and then the relationship is essentially done — in the good way. We don’t need to retain you, re-market to you, or profile you, so we didn’t build the machinery that would. The short onboarding isn’t a feature we added. It’s what’s left when you remove the reasons for the long one.

The one thing we will always ask

We’re not going to pretend we ask for nothing. Background location is a real, meaningful permission, and a mileage tracker that captures drives on its own can’t work without it. So we’ll always ask for that one, we’ll always explain it in plain words before the system prompt appears, and the deal attached to it is simple: that location data stays on your device — there’s no account, and we don’t run it through a Keepwright server or any analytics that follows you. Drawing your route on a map does send those points to an open mapping service, but never to us; a built-in privacy view shows you exactly what’s stored on the phone, so you can see for yourself.

One honest ask, explained, with the data kept where you can see it. That’s the whole arrangement — and after the first five minutes with the alternatives, it’s the part we’re most glad we got right.

See the side-by-side on the alternatives page, or work out what you could claim with the free Mileage Calculator.

Previous: How we test reliability → · Back to Notebook