Your private GPS drive files stay on your device or in your own iCloud unless you choose to share them. Versions using shared vehicle plans and Business trip credits also send a limited set of purchase, installation, vehicle and trip-reference data to a RoadBook licensing service operated by MW Supply Limited on Cloudflare (Sections 1 and 8). That service does not receive GPS routes, vehicle names or registration plates, business/client/project names, purposes, photos or report contents. Optional public community features, sharing, maps, analytics and advertising have the separate data flows described below. Pro and Business Pro remove ads.
RoadBook does not require a separate username or password. For shared licensing, Apple provides an app-specific purchase identity that lets us recognize the same purchasing account across devices. We associate it with a generated licensing account token, verified purchase history, installation verification records, shared vehicle slots and Business access on original trip references. These identifiers are pseudonymous and linked to the licensing account; they are not anonymous. They do not disclose the Apple Account email, password or payment-card details. Section 8 describes this data in more detail.
RoadBook communicates with Apple for location-related services, maps, directions, iCloud, sharing, community features, app integrity and purchases; with the RoadBook licensing service when configured; with advertising companies when ads are shown (Section 7); with TelemetryDeck for optional coarse usage analytics (Section 9); and with public open-data providers (Section 9). Public contributions are readable by other users and by us as described in Section 6. Private route files and coordinates are not sent to the licensing, advertising or analytics service.
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 preferences, vehicle details, mileage categories, purposes, client/project labels and any odometer readings you enter. Classification runs on-device using your rules and confirmed drives. Business rules, report filters, odometer entries and saved report versions are local to each device; eligible private trip fields use the existing trip-sync path. App verification and interrupted-recording proofs use protected local storage. Raw device-clock samples remain on-device.
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. RoadBook does not pass your location to the advertising or analytics SDKs. If you choose to post a community road report, its reported coordinate is published to Apple’s public CloudKit database and can be read by other RoadBook users and by us (Section 6). Choosing to share a trip sends its route to your selected recipients. The following Driving Mode features also send location information to their service providers:
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 for automatic recording and an optional monthly mileage-review reminder. These are scheduled and delivered on-device by iOS; no server push notification service is used for these reminders.
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 asks Apple’s geocoding service for the country of a drive’s last point and publishes only the resulting country code. 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.
Friends leaderboards (optional). Group driving summaries and membership records use the group owner’s private CloudKit database and are shared with approved members. Joining also creates public CloudKit coordination records containing a group identifier, your app-specific iCloud identifier, display name, request time and approval status; approval and access records can also contain the group’s sharing link. These records reveal a relationship between an account and a group, and are readable by us. They contain no address-book contacts, phone numbers or email addresses. Leaving a group or deleting a licensing account does not automatically erase these public coordination records.
Community road reports (optional). When you choose to post a report in Driving Mode, RoadBook publishes its type, exact reported coordinate, time and a daily changing reporter tag in Apple’s public CloudKit database. Confirming or dismissing a report creates a vote linked to that report. These contributions contain no private trip files or display name, but CloudKit records the creating account’s app-specific identifier, so reports and votes are account-linked rather than anonymous. Other RoadBook users and MW Supply Limited can read these public records. Reports stop appearing after their display lifetime. During later refreshes, the app attempts to delete expired reports it remembers creating on that device. This is best effort: offline use, removal of local state, changing iCloud accounts or not reopening the app can leave records in CloudKit. This cleanup does not delete vote records. Police- and camera-related reports remain subject to RoadBook’s regional restrictions. The policy follows your own position, never the part of the map you happen to be looking at. Availability is not a guarantee of legal permission; follow applicable local rules.
RoadBook’s free plan is supported by advertising. Live ads are available only on eligible free-plan App Store installations. TestFlight, review sandbox, development and simulator installations do not initialise advertising SDKs or request live ads. From version 1.3.0 build 162, eligible free-plan release sandbox installations can show the same Apple tracking-permission flow for testing and review, without enabling advertising or reading an advertising identifier. Pro and Business Pro subscribers are not asked for tracking permission or shown ads.
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 SDK starts, RoadBook checks Apple’s App Tracking Transparency status. If a choice is needed, it asks while the app is active, after subscription verification, the initial location/notification requests and onboarding, with no other dialog or purchase open. iOS may suppress the prompt when tracking requests are disabled or restricted, or a choice already exists. An unresolved or system-dismissed request keeps advertising off until the status is resolved. Tracking and access to the advertising identifier require your authorization:
From version 1.3.0 build 162, RoadBook does not treat Apple tracking authorization as separate legal consent: it sends no positive GDPR consent to the advertising SDK and requests no sale or sharing under the SDK’s CCPA setting. 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.
Apple processes in-app payments. RoadBook Pro subscriptions are available in supported versions. When shared vehicle plans and Business trip credits are available, Pro and Business Pro offer monthly or annual vehicle plans, and trip-credit packs are separate consumable purchases. Availability and local prices are shown before purchase. Manage or cancel subscriptions in iOS Settings → [your name] → Subscriptions. Deleting RoadBook, a drive or a licensing record does not cancel Apple billing.
When shared licensing is enabled, the app and Apple send the licensing service:
We use this information to provide the purchased allowance across devices, verify when a drive was covered, restore credits and access, apply refunds, prevent duplicate spending and correct licensing errors. A later Business subscription alone does not cover earlier uncovered drives. The service does not receive report files, routes, precise coordinates, vehicle names/plates or business/client/project labels. Licensing account and transaction identifiers, installation proofs, vehicle/trip references and licensing records are not supplied to advertising or analytics providers. When optional usage analytics is enabled, the app separately sends coarse purchase and restore events to TelemetryDeck as described below.
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, StoreKit (for subscriptions and trip credits), and DeviceCheck/App Attest (for installation verification).
Shared licensing hosting. MW Supply Limited operates the licensing service using Cloudflare Workers and Durable Objects. Cloudflare processes the request and connection information, including the source IP address, as the hosting provider. RoadBook does not persist IP addresses in its licensing database or enable Worker request logs. Encrypted operational backups are also held in controlled developer storage. See Cloudflare’s privacy policy. The app does not upload its private trip files to this service.
Optional product analytics. From version 1.3.0 build 162, usage analytics is off by default, including after updating. You can opt in under Settings → Privacy → Share usage analytics and turn it off there at any time. App features and purchases do not depend on this choice. The analytics SDK does not initialise or send events before opt-in. Turning the option off stops new collection and cancels pending analytics requests; data already received by the service cannot be recalled by cancelling a request. When enabled, 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 vendor-scoped device identifier (Apple’s IDFV), which the SDK hashes on-device before sending. Purchase events include the selected plan or credit-pack category, trial status, purchase result and restored entitlement status; they do not include transaction or licensing-account identifiers. TelemetryDeck does not use the advertising identifier and is not used to track you across other companies’ apps or websites. No route, coordinate or trip content is 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 have a built-in fallback and refresh from official territory-wide catalogues while Driving Mode is visible. 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. RoadBook uses the government camera source when available; if it fails, the app can obtain camera locations 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 (including 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 these open-data providers no licensing-account information, no identifier we create, and none of your recorded trips. Camera, parking and red-light-camera availability depends on RoadBook’s regional policy and data coverage, 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.
Shared purchasing account. When shared licensing is available, open Membership → Shared purchasing account to review and delete its records. The app verifies your purchasing account and installation, shows the credits and vehicle history affected, and asks you to confirm. Any verified phone using that purchasing account can request deletion for the whole shared account. Other phones learn of the deletion when they next connect.
What deletion removes. Confirmed deletion erases the active licensing account, unused trip credits, earlier Business access and unlock proofs, purchase associations, registered and retired vehicle history, installation registrations and linked support-operation records. It affects every phone sharing the purchasing account. Your private drives and saved reports remain on your device or in your own iCloud; save any reports you need before deleting, because erased access and credits cannot be restored.
Purchases and a later account. Deletion does not cancel an Apple subscription or a purchase awaiting approval. Use Manage or cancel subscription if you no longer want renewal. Apple may complete a pending trip-credit purchase after deletion; those credits cannot be delivered to a new account, and the app provides Apple refund guidance. Ordinary cancellation keeps earlier eligible drives, unused credits and vehicle history. Creating a new shared account is an explicit action; it can restore a verified current subscription at the same vehicle limit with a fresh vehicle list, but cannot restore erased credits or old access proofs. Apple retains its own purchase records under its policies.
Retention and recovery. We keep active licensing records while the shared account remains open, including after subscription cancellation, so that non-expiring credits, earlier eligible drives, shared allowances and refunds continue to work. After confirmed deletion, a separate minimal recovery record holds the account reference, erased account generation, deletion identifier and timestamps for 30 days to prevent an older backup from bringing the account back. It does not retain the erased trips, vehicle registry, credit balance or access proofs. Ordinary app requests and Apple notifications cannot create an absent account.
Operational archives are encrypted and scheduled to expire after 30 days. Restoration rejects expired archives and requires current deletion evidence before a restored ledger can serve requests. Local and iCloud recovery copies are removed by scheduled maintenance; if a device or storage destination is unavailable, expired copies are removed on the next successful maintenance run and remain excluded from restoration. Storage providers may retain their own temporary recovery copies under their service policies. The recovery key is stored separately from the encrypted archives.
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.