Privacy Policy
Last updated: September 2026
Mini Detour plans errand stops along a route you are already driving. It works without an account, and it is built to send as little about you as possible. This policy says what the app collects, what leaves your phone, where it goes, how long it is kept, and what stays behind. Where we do not control what happens next, it says that too. The English version is authoritative.
No account, no tracking, no advertising
Mini Detour has no sign-up, no login and no user account. We never ask for your name, your email address or your phone number, and we keep no profile about you on any server. The app contains no advertising SDK, no analytics SDK and no crash-reporting SDK. It contains no third-party code at all — only Apple's own frameworks. It does not read the advertising identifier, does not ask for tracking permission, and does not follow you across other apps or websites. We do not sell personal data, and we have none to sell. Beyond location, the app asks for no permission of any kind: no contacts, no calendar, no photos, no camera, no microphone, no notifications. Spoken guidance is generated on your device, and nothing is ever recorded.
Location
Location is the one thing the app genuinely needs. It is used to work out where you are starting from, which places lie along your route, how far off that route each one is, and when you would arrive. Mini Detour only ever asks iOS for the "While Using the App" level of access. It never asks for "Always". In this build the prompt comes from the CarPlay side of the app: if you only ever use Mini Detour on the phone, you are never asked, the app has no position, and it plans from the addresses you type. Once you have granted access, the phone side uses your position too, from the next launch onwards. When idle it reads your position coarsely — to about 100 metres, and only after you have moved 500 metres — and it briefly asks for a precise fix at the moment CarPlay plans a trip. While you are navigating in CarPlay it switches to full navigation accuracy, updates about once a second, and keeps doing so with the app in the background and the screen locked; iOS shows the blue location indicator for the whole of that time. You can withdraw location access at any point in iOS Settings. The app will then work only from addresses you type in.
What leaves your phone when you plan a detour
Planning a detour means asking outside services three kinds of question: which places of a given kind are near a point, how long the road detour to each candidate costs, and what the route is. All three are asked every time you plan — on the phone as well as in CarPlay. What we send to answer them is coordinates: your starting point (in round-trip mode, that is your current position), your destination, the candidate stops being compared, and, when a driving route is computed, the shape of that route as a list of points. Alongside the coordinates goes the category being looked for, such as pharmacy, bakery or parcel point, taken from a fixed list built into the app, and the two-letter code of your device language so that road and place names come back in a language you read. What you type is not part of it: your own words go to Apple's map search and nowhere else. There is one exception worth naming — when CarPlay works out which entrance of a named place to drive to, that place's name is sent with the request. There is no account, no device identifier and no advertising identifier to attach to any of this. Your IP address travels with the request, as it does with anything your phone fetches.
Our own servers
Most of those requests do not go to a third party directly. They go to our own servers first. There are two, both hosted on Fly.io: drivechargeeat-backend.fly.dev in Paris, France, and drivechargeeat-backend-us.fly.dev in Ashburn, Virginia. The hostnames still carry the name of the app this one grew out of. Which server answers is decided by your device's own current position — not by the coordinates in the request, not by your language, and not by your account, because there is no account. Roughly: a device in North America reaches Virginia, everything else reaches Paris, and when the app has no position fix at all it uses Paris. These servers are pass-through proxies. They add our API keys to a request, forward it, and hand the answer back. They write no trip history and no profile. They do use a database, but it holds only a static copy of public charging-station data — nothing about you and nothing from your requests. Answers are cached in each server's own memory, keyed by a hash of the request: five minutes for places and routes, and up to twenty-four hours for the elevation lookup, whose key is derived from the shape of a route. Within that window two people asking about the same neighbourhood share one cached response instead of causing two lookups. Fly.io, as our hosting provider, may keep ordinary connection logs — IP address, timestamp, path — at the platform level. That logging is not ours to switch off; we do not use it to build anything about you, and the retention that applies to it is [FLY.IO LOG RETENTION].
What Apple sees
Apple's frameworks do much of the work, and Apple receives what they need to do it. Everything you type into a search field goes to Apple Maps search, together with a rough region around you so the results are local; when you search from CarPlay, that happens as you type, character by character. Turning a coordinate into an address also goes to Apple — that is what happens when you set your Home from your current position, and again when CarPlay resolves your position or a destination into an address. Apple Maps is also the last-resort fallback for computing a route, used when the other engines fail. If CarPlay plans a driving route for an electric vehicle, three sampled points along that route go to Apple Weather. Your subscription runs through the App Store. All of this is governed by Apple's own privacy policy and by identifiers Apple manages, not us.
Google, OpenStreetMap and the other data sources
Place details and opening hours come from Google Maps Platform, and Google is also the first choice for computing a road route. Those requests pass through our servers rather than leaving your phone directly, so what Google sees is our server and our key — not your device or its address. The app has no setting for supplying a Google key of your own. Detour costs and turn-by-turn routing use a Valhalla routing engine, also reached through our servers. This one matters, because it runs on every plan you make, on the phone as much as in CarPlay: comparing candidate stops is a single batched travel-time request, and it carries your starting point, your destination and every candidate stop as coordinates. Behind our proxy the upstream is either a Valhalla instance we run ourselves or Stadia Maps, a third company. Which of the two answers is a server-side setting that can change without an app update, so we will not promise you here that it is always ours. Road data from OpenStreetMap works differently: it is fetched straight from your phone, from four public Overpass mirrors (overpass.kumi.systems, overpass-api.de, overpass.private.coffee and overpass.osm.ch), which therefore see your device's IP address and a request header that names the app. These lookups happen only when you use CarPlay: the corridor along your route when CarPlay plans a trip, and, while CarPlay navigation is running, your current position at most once every eight seconds, so speed limits and lane guidance stay correct. Two further sources are reached only through our servers, and only when CarPlay plans a trip. OpenChargeMap is queried for charging points when a CarPlay trip plan still needs them — it is skipped when Google has already answered — and that query is a plain web request with a latitude and longitude in its address. An elevation lookup, which sends up to 400 points of the route shape, runs only for an electric vehicle, and only when energy-optimised routing is switched on. OpenStreetMap data is © OpenStreetMap contributors, under the Open Database Licence.
Handing your route to a navigation app
When you tap Start driving, Mini Detour does not drive you there itself. It hands the plan to a navigation app, and that hand-off is a link. What the link carries depends on which app you pick: Apple Maps and Google Maps get the whole chain — every stop in order, then the destination, all as coordinates; Waze has no multi-stop link, so it gets the first stop only; A Better Route Planner gets the destination, because it plans its own stops. From the moment the link opens, your route is in that app's hands and under its privacy policy. To know which of those buttons to offer, Mini Detour checks whether Google Maps and Waze are installed. That check happens entirely on your phone and its result is sent nowhere.
What is stored on your phone, and how to remove it
Everything the app remembers, it remembers locally. That includes your settings and vehicle profile; your Home location, with its name and coordinates; custom stops you have added, up to thirty, each with a label and exact coordinates, saved automatically as you add them; the last plan the app computed, including start and end points, every stop and the route shape, which is discarded once it is more than six hours old; the last twelve destinations you navigated to from CarPlay, with their names and coordinates; the answers you gave during onboarding; and a small record of your subscription status. The app also keeps caches of places it has looked up: a local database of service areas holding names, addresses and coordinates, and whatever the system's ordinary web cache retains — which for the charging-point lookup includes a latitude and longitude inside the cached address. None of it syncs to iCloud, and none of it is copied to our servers. There is no single "delete everything" button in the app today. Saved custom stops can be removed one at a time. The CarPlay destination list has no clear control at all and does not expire on its own. Deleting the app removes all of it. One item survives deletion: a keychain entry holding the expiry date of an App Review access pass, and nothing else.
Diagnostic logs, and who can read them
The app writes a diagnostic log file each time it launches and keeps the last ten. These files are detailed. They record GPS fixes accurate to about a metre — roughly every two seconds while you are navigating, and about every five seconds the rest of the time the app is running with location granted, so the file holds a position trace whenever the app is awake, not only during navigation. They also record the coordinates and names of your start point, destination and every planned stop; your Home location's name; your vehicle settings and preferences; which navigation app you opened and the destination handed to it, and in CarPlay the entire hand-off link including every coordinate in it; and your device model, iOS version, locale and time zone. Nothing uploads them — there is no code path in the app that sends a log anywhere. Two things do let them off the device. You can share them deliberately, from Settings, through the iOS share sheet. And the app's Documents folder is exposed to the Files app, so the logs are visible under On My iPhone and to any Mac your phone is trusted to; anyone holding your unlocked phone can read them. The same lines are also written to the iOS system log without redaction, which means they can appear in a system diagnostic report. If you send us logs for support, look at what you are sending first.
Subscriptions
Mini Detour is a paid subscription and needs one to work. Purchases are handled entirely by Apple through the App Store, using StoreKit on your device. We never see your payment details, your card or your App Store account. No receipt and no transaction is ever sent to our servers — they have no endpoint that could receive one. The app keeps a small local note that your subscription is active and when it expires, so a poor connection or a flight cannot lock you out of something you have paid for. From Apple we receive the standard App Store sales and subscription reporting every developer gets; it carries neither your name, nor your email address, nor your payment details, and we cannot tie it to anything the app does.
Why we are allowed to process this
For readers under the GDPR, here are the grounds we rely on. Planning your stops, computing routes and running your subscription are the service you asked for, so that processing rests on performance of a contract (Article 6(1)(b)). Sending place and routing requests through our own servers instead of straight from your phone rests on our legitimate interests (Article 6(1)(f)): it keeps our API keys off your device, keeps one cached answer serving several drivers instead of one lookup each, and lets us keep the service working and unabused. The diagnostic log rests on the same ground — being able to explain a fault that happened in a moving car. Location access itself is a permission you grant to iOS and can withdraw at any time. We process no special-category data, we build no profile, and nothing about you is decided automatically.
How long things are kept
On our servers, an answer sits in memory for five minutes — up to twenty-four hours for the elevation lookup — and is then gone; nothing else about a request is written down by us. The platform-level connection logs our hosting provider keeps are outside our control, and the retention that applies to them is [FLY.IO LOG RETENTION]. On your phone: the last ten diagnostic log files; the last computed plan for six hours; up to thirty saved custom stops and the last twelve CarPlay destinations, which stay until you remove them or delete the app; settings and caches for as long as the app is installed. If you send us logs for support, we treat them as confidential and delete them once the issue is closed, and in any case within [SUPPORT LOG RETENTION].
Data crossing borders
Because our two servers sit in France and the United States, and because the server is chosen by where your device is rather than where you live, a lookup you make can be handled outside your own country. A European driver on a trip through North America has their coordinates answered by the Virginia server, and the reverse holds too. Apple, Google, the routing engine and the Overpass mirrors likewise operate internationally. What travels is more than a coordinate and a category word: it is your starting point, your destination and the stops being compared; the shape of your route when one is computed, up to 400 points for the elevation lookup; a destination's name when CarPlay resolves its entrance; your device language; and your IP address. To the Overpass mirrors it is your position plus a header naming the app. None of it carries an account, a name or a device identifier, because there is none to carry. For the Virginia deployment we are the exporter and our hosting provider is the importer, and the mechanism covering that transfer is [TRANSFER MECHANISM]. Apple and Google publish their own transfer terms for their platform services; we rely on those and do not control them. The Overpass mirrors are volunteer-run public services with which we have no contract and no transfer mechanism at all — those lookups happen only when you use CarPlay.
Children
Mini Detour is a driving tool. It is not directed to children under 13, we do not knowingly collect anything from them, and the app has no feature that asks for or estimates anyone's age.
Your rights and who is responsible
Under the GDPR and comparable laws you can ask to access, correct or delete your personal data, object to or restrict its processing, and ask for it in a portable form. In practice almost all of it is already in your hands, because it sits on your phone and nowhere else. We hold no account and no profile to look up — which also means that if you write to us, there is nothing on our side keyed to you that we could retrieve or erase on your behalf. For anything else, write to us. The data controller is LyteFast, a French société par actions simplifiée with its registered office at 60 rue François Ier, 75008 Paris, France (RCS Paris 988 054 227), reachable at [CONTACT EMAIL]. You also have the right to complain to your local data-protection authority; in France that is the CNIL (cnil.fr).
Changes and contact
If this policy changes in a way that matters, the text here changes and the date at the top changes with it. Questions about any of it: [CONTACT EMAIL].
Mini Detour