Summary: RoadBook records your drives entirely on your device. MW Supply Limited operates no servers of its own and never receives your location or trip data — your trips stay on your device or, if you are signed in to iCloud, inside your own iCloud account. The new Driving Mode looks up public road-safety and parking information (camera locations, car-park availability, traffic cameras) directly from third-party open-data providers; those requests go to the data providers, never to us, and carry no account or trip data (Section 9). RoadBook has a free, ad-supported plan: when ads are shown, they are delivered through the Unity LevelPlay mediation platform and the ad networks it runs an auction across — Unity Ads, AppLovin, Meta Audience Network, Mintegral and Vungle — which may collect device and advertising identifiers and ad-interaction data as described in Section 7. The optional RoadBook Pro subscription removes all ads.
None directly. We operate no servers of our own and receive no personal data from RoadBook. The app has no account system, no login, and no user profile, and it makes no network requests to MW Supply Limited. Your trips, routes and preferences are never sent to us. The only information that reaches us at all is anonymous, aggregate product-usage statistics gathered through a privacy-focused analytics service (Section 9) — counts of events such as “app launched” or “trip saved” — which contain no routes, no coordinates and nothing that identifies you.
RoadBook does make three kinds of request to other companies, never to our own servers: advertising requests on the free plan when ads are shown (Section 7), which the advertising companies handle under their own control; the product analytics just described (Section 9); and, in Driving Mode, read-only lookups of public open data from the data providers described in Section 9. None of them carries your name, your account (there is none), or your trip data.
While you are recording a drive, RoadBook reads your location from iOS Core Location and stores each trip on your device as a list of GPS samples (latitude, longitude, altitude, speed, course, timestamp, and Apple’s reported accuracy). Each finished trip is saved as a single JSON file in the app’s own sandbox. From those samples the app computes distance, duration, max and average speed, elevation gain, and the route polyline you see on the map.
RoadBook also stores your in-app preferences (units, auto-start/auto-stop thresholds and toggles) using iOS’s standard UserDefaults mechanism.
If you are signed in to iCloud on the device and have iCloud Drive enabled, RoadBook stores trip files in your own iCloud Documents container (iCloud.com.edfd.DrivingRecorder). This is Apple’s CloudKit Documents feature: the files are stored under your Apple ID, synchronised between your own devices by Apple, and are not accessible to MW Supply Limited. (Cross-device iCloud sync is part of RoadBook Pro.) If iCloud is not available, trips are stored only on the device.
Recording a drive requires location access. The app uses the lowest-privacy permission that gets the job done:
Your precise location is used to record your current drive on your device. MW Supply Limited does not collect, transmit, or share your location, and RoadBook never passes your location to the advertising or analytics SDKs, so it is not used for advertising. There are three functional exceptions, all of them in Driving Mode, all of them optional in the sense that they happen only when you use the feature concerned, and none of them reaching MW Supply Limited:
None of these requests carries your identity, any identifier we create, or any of your recorded trips.
With your permission, the app posts local notifications when it auto-starts and auto-stops a recording. These are generated and delivered entirely on-device by iOS.
You can export a finished trip as a GPX or JSON file from the Trip detail screen. The destination of that export (Files, Mail, AirDrop, etc.) is chosen by you through the iOS share sheet. We are not involved in that transfer.
You can also share a trip with another person in two ways. Both are started explicitly by you, and MW Supply Limited is never part of the transfer:
.roadbooktrip file (the same trip data, in JSON) and hands it to the iOS share sheet, so you can send it via AirDrop, Messages, Mail, or save it to Files. Whoever you send it to can open it in RoadBook. The transfer happens through whichever app you pick; it does not pass through us.So that a recipient knows who a trip came from, the optional display name you set in Settings → Sharing is included with any trip you share. It is shown only to the people you share a trip with; it is never sent to us. Trips that other people share with you appear in your Trips list under “Shared with you,” tagged with the sender’s name, and you can remove them at any time.
Public leaderboard (optional, off by default). If you join the public leaderboard, the app publishes a small summary of your driving to a public leaderboard held in Apple’s CloudKit: your display name, your country, whether you subscribe to RoadBook Pro, and aggregate figures — your top speed, total distance, time driven above 150 km/h, and your maximum acceleration, maximum deceleration and maximum vehicle g-force — for the current day, week, month, year, and all time. It never includes your routes, individual trips, or any location coordinate. It does carry the time your entry was last updated, and an identifier derived from your iCloud account which is what lets the app find and delete your own entries when you leave; to work out your country the app reverse-geocodes only the last point of a drive to a country code, on your device. The g-force figure counts only motion the app has confirmed came from the vehicle, so handling or knocking your phone is excluded. If you have told the app in Settings that you ride a motorcycle, that choice is published too — it is what places your drives on the separate “Two Wheels” board in addition to the main one. It is a setting you choose, never something the app detects, and it says nothing about which vehicle you own. Drives published as a motorcycle carry no g-force figure at all — a phone carried on a two-wheeler measures the movement of its own mount as much as the cornering itself, so that measurement is not published or ranked for riders. The leaderboard is public to other RoadBook users: your entry is ranked on a worldwide board as well as on your own country’s, and any RoadBook user can browse either. You can leave at any time, which also deletes the entries you have published; if you are offline when you leave, the deletion completes the next time the app can reach iCloud. This data stays inside Apple’s CloudKit. Because a leaderboard has to be public to work, these entries — unlike your drives — are readable by other RoadBook users and by us; that is the whole point of a ranking, and it is why joining is off by default and takes an explicit opt-in.
Community road reports (optional). In Driving Mode you can tap Report to warn nearby drivers about a police check, a mobile speed camera, a hazard, an accident, or a road closure at your current position. A report is published only when you choose to post one. A report you post is written to a public database held in Apple’s CloudKit and contains the report type, the GPS coordinate of the spot you are reporting (your location at that moment), the time, and an anonymous reporter tag — no name, no account, and none of your recorded trips. The reporter tag is a salted, one-way hash that changes every day, so it is never your identity and cannot be used to follow you from one day to the next; it exists only so that duplicate and abusive reports can be filtered. Reports are public to nearby RoadBook users, who can confirm or dismiss them. A report stops being shown to anyone after a few hours. That is a display rule: the underlying record is not automatically erased, so an expired report may persist in the database after it has stopped being visible to anyone. Police- and camera-related reports are shown and accepted only where the law where you are driving permits them — that decision follows your own position, never the part of the map you happen to be looking at. This data stays inside Apple’s CloudKit. Like the leaderboard, and unlike your drives, a shared warning has to be public to be useful, so these reports are readable by other RoadBook users and by us.
RoadBook’s free plan is supported by advertising. Ads are shown only when advertising is switched on in the version of RoadBook you are using; while it is switched off, the app initialises no advertising SDK, requests no ads, reads no advertising identifier and shows no tracking prompt. Everything in this section describes what happens on the free plan, when ads are shown. Pro subscribers never see any of it.
Ads are delivered through Unity LevelPlay (the ironSource mediation platform, now part of Unity), which runs an auction for each ad slot across the advertising networks built into the app:
Where ads may appear on the free plan: a banner on the Record, Trips and Route map screens, a medium rectangle on the Trip detail screen, an occasional sponsored row in the Trips list, and a short rewarded video when you save a drive. There are no full-screen interstitial ads.
To select, deliver, measure and cap the frequency of these ads, and to detect invalid traffic and fraud, these SDKs may collect:
RoadBook does not pass your location, your routes, your recorded trips, or any account information to these SDKs.
Before any advertising identifier can be read, iOS shows Apple’s App Tracking Transparency prompt. RoadBook asks only after you have answered the system location and notification prompts, and never before your subscription status has been checked:
This advertising data is collected and processed by the advertising companies listed above as independent controllers, not by MW Supply Limited. We never receive it; we see only aggregate, non-identifying earnings and performance reports. Their handling of this data is governed by their own policies: Unity (Unity Ads, LevelPlay and ironSource), AppLovin, Meta, Mintegral, and Vungle / Liftoff. You can change your tracking choice at any time in iOS Settings → Privacy & Security → Tracking.
RoadBook Pro removes all ads. While you are a Pro subscriber the app does not display ads, does not initialise the advertising SDKs for ad serving, and the App Tracking Transparency choice has no effect on you.
RoadBook Pro is an auto-renewable subscription (Monthly or Yearly) sold through Apple’s In-App Purchase — the only in-app purchase in the app. Your purchase, payment and renewals are handled entirely by Apple under your Apple Account; MW Supply Limited never receives your name, your Apple ID, or any payment details. Apple provides us only with aggregate, non-identifying sales reports. Subscriptions are managed and cancelled in iOS Settings → [your name] → Subscriptions.
Two kinds of third-party SDK are bundled in RoadBook. The first is the advertising stack: the Unity LevelPlay mediation SDK (ironSource) together with the Unity Ads, AppLovin, Meta Audience Network, Mintegral and Vungle SDKs it mediates, used solely to show ads on the free plan (Section 7). The second is TelemetryDeck, described next. The app contains no crash-reporting service other than Apple’s own first-party crash reporting (which runs only if you have opted in to Share With App Developers in iOS Settings → Privacy & Security → Analytics & Improvements). The first-party Apple services it uses on your device are Core Location, MapKit (including place search, and — when you start navigation — Apple’s directions service, which receives your starting point and your destination as described in Section 4), CLGeocoder (to label countries and cities on the Route map, to put a street address on a drive’s start and end in your mileage reports, and to detect which country you are driving in so Driving Mode shows the right data and respects local rules), iCloud / CloudKit Documents, and StoreKit (for subscriptions).
Product analytics. RoadBook uses TelemetryDeck, a privacy-focused analytics service, to count coarse product events — for example “app launched”, “recording started”, “trip saved” or “paywall shown” — so we can see which features are used and whether the app is failing. A signal carries the event name, coarse device and app information (device model, operating-system version, language and region, and the RoadBook version), and a per-installation identifier that the SDK hashes (SHA-256) on your device before it is sent. TelemetryDeck does not use the advertising identifier and is not used to track you across other companies’ apps or websites, and no route, coordinate, trip content, or personal detail is ever included.
Driving Mode open data. Driving Mode overlays public road-safety and parking information on the map. To do that it makes read-only requests to public open-data providers:
static.data.gov.hk and resource.data.one.gov.hk) — live car-park availability, on-street metered-parking occupancy, traffic-camera locations, and the traffic-camera snapshot images shown when you tap a camera, in Hong Kong. Hong Kong speed- and red-light-camera locations are built into the app and involve no request at all. These requests fetch territory-wide public datasets; they do not include your location — the app filters the results to your area on the device.api.data.gov.sg, api-open.data.gov.sg and images.data.gov.sg) — live car-park availability, traffic-camera locations and their snapshot images, and published speed-camera locations, in Singapore. As with Hong Kong, these requests fetch country-wide public datasets; they do not include your location — the app filters the results to your area on the device. Some of these datasets have been unavailable to the app since 29 August 2026, which is why Singapore camera locations currently come from OpenStreetMap instead (next bullet). Live car-park availability is not affected: as of 31 August 2026 the list of car-park locations is built into the app and needs no network request at all, and only the live vacancy count is fetched, from api.data.gov.sg. That change removed a request the app used to make and added none — api-open.data.gov.sg is no longer contacted for parking at all.overpass-api.de) — two things. First, fixed speed-camera locations in the regions RoadBook has no government source for, and in a region that has one (currently Singapore) whenever that government feed cannot be reached. Second, when you use the parking search, the map of footpaths, steps, crossings, escalators and lifts around the area, which is what lets the app rank parking spaces by the real walk rather than by straight-line distance. As noted in Section 4, both requests include an approximate (rounded) map coordinate so the provider can return what is near you. When camera locations are being served this way, the app credits OpenStreetMap on the map itself, alongside the region’s own credit.s3.amazonaws.com, the public elevation-tiles-prod dataset) — terrain-elevation tiles, used only by the parking search to work out how much climb a walk involves, so that a space at the top of a hill or a staircase is not presented as being as easy to reach as a level one. A request identifies a map tile roughly 2.4 km across and nothing finer; it carries no identity, no identifier and no trip data. The data is published by Mapzen and Amazon from public sources including NASA SRTM and the USGS.As with any internet request, these reveal your device’s IP address to the provider you are contacting; that is inherent to how the internet works and is handled under each provider’s own policy. RoadBook sends them no account information (there is none), no identifier we create, and none of your recorded trips. Camera, parking and red-light-camera locations are shown only where permitted by local law, and the underlying data is provided by these third parties “as is” — it may be incomplete or out of date, so always follow the road and posted signs. Speed-camera, red-light-camera and proximity alerts in Driving Mode are available for free; live parking availability and traffic-camera images are part of RoadBook Pro.
Open-data attribution: car-park, traffic-camera and camera information in Hong Kong © Transport Department, the Government of the Hong Kong Special Administrative Region; car-park, traffic-camera and speed-camera information in Singapore © Land Transport Authority, the Housing & Development Board and the Singapore Police Force, via data.gov.sg, licensed under the Singapore Open Data Licence; speed-camera data elsewhere — and in Singapore whenever the OpenStreetMap fallback described above is in use — © OpenStreetMap contributors, licensed under the Open Database License (ODbL); footpath data used by the parking search © OpenStreetMap contributors (ODbL); terrain-elevation tiles courtesy of Mapzen and Amazon Web Services, derived from public sources including NASA SRTM and the USGS.
RoadBook is intended for adults who drive. We do not knowingly direct the app to, or collect personal data from, children.
You stay in control of your data:
If we ever change how RoadBook handles data, we will update this page and the “Last updated” date above. Material changes will also be reflected in the App Store privacy labels for the affected version of the app.
Questions about this privacy policy can be sent to mwsupplylimited@gmail.com.