DriveMotion Privacy Policy

1. What this policy covers

This policy applies to the DriveMotion mobile app for Android and iOS (package and bundle identifier com.inceptionapps.driver).

2. No account, no identity

You do not register, log in, or give us a name, e-mail address or phone number to use DriveMotion. The app creates no user identifier of its own, and it does not read any device serial number or hardware identifier. There is nothing for us to attach your driving to, because there is no “you” in our systems.

3. What the app stores on your device

All of the following is written to app storage on your phone — a local database and local files. None of it is transmitted to us.

• Trip records — start and end time, distance, average and maximum speed, moving and resting time, number of rests, altitude and total climb, driving score and economy score, counts of hard braking, hard acceleration and high-speed stretches, fuel used and fuel price.
• The route of each trip — a list of GPS points (latitude, longitude, altitude, speed, timestamp), recorded roughly every 10 seconds while a trip is being recorded. This is the most sensitive data the app handles, and it is the reason the app is designed to keep it local.
• Driving events — hard braking, hard acceleration, high speed and rest stops, each with the position and time at which it happened.
• Photos you attach to a trip, stored as files in the app’s own folder.
• Saved routes — the province and district you chose as start and end, with their coordinates.
• Vehicle data read from an OBD-II adapter — speed, engine RPM, coolant temperature, battery voltage, fuel level and consumption. Live values are shown on the dashboard; what is kept is the trip summary derived from them.
• Fault code (DTC) history — codes read from your car and the date they were cleared. Code descriptions are looked up in a table shipped inside the app; no fault code is sent anywhere for lookup.
• Settings — vehicle profile, fuel type and price, language, warning preferences.

The speed camera and speed-corridor database is shipped inside the app and copied to local storage on first launch. Checking whether you are near a camera is a lookup in that local database. Your position is not sent anywhere to answer that question.

4. Permissions and why they are asked for

The app asks for three things when it starts, and none of them block you from using it. You can decline any of them, and change your mind later in system settings.

Location

This is the core permission. Without it neither trip recording nor speed camera warning can work at all. Location is used to record your route, to calculate speed, distance and altitude, and to compare your position against the local camera database.

Background location. While a trip is being recorded, the app keeps receiving location when it is not on screen — otherwise your route would break up every time you locked the phone. This happens only during an active recording and stops when you stop the trip.

• On Android the recording runs as a foreground service of type location, which means a permanent notification is visible for as long as the recording is running. The app may additionally ask for “Allow all the time” location access and for an exemption from battery optimisation, because Android otherwise kills the recording after a few minutes and the trip is lost. Both are recommendations, not requirements — the app runs without them.
• On iOS background location is requested only when you start a trip, and the blue location indicator stays visible in the status bar while it is active, deliberately, so it is never a surprise. An ongoing Live Activity shows the trip in progress.

Notifications

Used to show the ongoing trip recording and to deliver warnings. Optional; declining it only means the recording is less visible to you.

Nearby devices / Bluetooth

Used solely to find and connect to your OBD-II adapter. The app does not use Bluetooth to derive your location, and the Android scan permission is declared with the never for location flag. Optional; without it you can still use the app on GPS alone.

Photos

Requested only at the moment you use the feature that needs it: adding a photo to a trip, or saving a trip video or share card to your gallery. On Android, picking a photo uses the system photo picker, which needs no permission and gives the app access only to the picture you chose. The app never browses your photo library on its own.

Not requested at all

DriveMotion does not ask for the camera, the microphone, your contacts, your calendar, your phone number, call logs, or SMS.

5. Advertising, consent and the advertising identifier

The free version of DriveMotion shows ads supplied by Google AdMob. They appear as occasional full-screen interstitials, and as rewarded ads you choose to watch in exchange for an hour without ads. There are no banner ads and no ads on the driving dashboard.

To serve ads, Google uses your device’s advertising identifier — the Advertising ID on Android, or the IDFA on iOS. This is a resettable identifier maintained by the operating system, not by us. You can reset or limit it in your device settings at any time.

Consent (EEA, UK and other applicable regions). Before the ads SDK is started at all, the app runs Google’s User Messaging Platform consent flow. Where consent is required, you are shown a consent form and the ads SDK is initialised only once a valid choice exists. If you are not in a region where a form is required, no form appears.

App Tracking Transparency (iOS). On iOS the system tracking prompt is shown before the ads SDK starts. Declining does not remove ads; it only makes them less relevant. As the prompt itself says, this concerns the advertising identifier only — your trips, location history and vehicle data are never shared for advertising.

Ads are personalised unless your consent choice or your ATT decision says otherwise. What Google does with ad requests is governed by Google’s own policies, linked above.

Pro subscribers see no ads at all, and the ads SDK is not used for them.

6. Subscription and payments

DriveMotion Pro is sold as a monthly or yearly auto-renewing subscription through Google Play on Android and the App Store on iOS.

We never see your payment details. Card numbers, billing addresses and store account identities are handled entirely by Google and Apple and are never passed to the app. We do not operate a server and we do not keep any purchase records of our own — when the app needs to know whether you are a subscriber, it asks the store on the device and gets a yes or no.

Managing or cancelling a subscription is done in your Google Play or App Store account settings, not in the app.

7. Device backups

This one deserves to be stated plainly, because it is the one case where your trip data can leave the phone without you pressing anything.

If you have your operating system’s backup feature switched on, it may include DriveMotion’s app data — including the trip database and attached photos — in that backup. On Android this is Google’s Auto Backup; on iOS it is iCloud Backup or an encrypted local backup. The same applies when you transfer your data to a new phone.

That copy goes to your own Google or Apple account, under their terms, not to us. We have no access to it. If you would rather it did not happen, you can turn off backup for DriveMotion in your device settings.

8. Export, share cards and videos

Everything in this section happens only when you ask for it.

• Backup / export. Settings → Data creates a single JSON file containing your trips, their full GPS routes, events, saved routes, attached photos and a few settings. The file is written to temporary storage on your device and handed to the system share sheet, where you choose what happens to it. It is not uploaded anywhere by the app. Treat that file carefully — it contains your complete location history.
• GPX export works the same way, for a single trip.
• Share cards and trip videos are rendered on the device. Videos are saved to your gallery (Movies/Trafic on Android, your photo library on iOS) and handed to whichever app you pick from the share sheet. Nothing is uploaded by DriveMotion; what happens after you pick an app is governed by that app.

9. If you write to support

The in-app feedback screen does not send anything itself — it prepares a message and opens your own mail app, and nothing leaves until you press send there. There is deliberately no e-mail field in the app, so we do not collect an address you did not choose to write from.

An optional diagnostics block, which you can switch off before sending, appends the app version, platform, device model, app and device language, whether you are a Pro subscriber, and how many trips you have recorded. It contains no identifiers and no location data.

10. What we do not do

• We do not use analytics — there is no Google Analytics, no Firebase Analytics, no third-party analytics SDK of any kind in the app.
• We do not use a crash-reporting service.
• We do not sell, rent or share your personal data, and we do not share it for cross-context behavioural advertising.
• We do not upload your trips, routes, photos or vehicle data to us or to anyone else.
• We do not track you across other apps or websites.
• We do not require an account, and we do not build a profile about you.

11. Children

DriveMotion is intended for drivers and is not directed at children. We do not knowingly collect personal data from children, and the app is not configured for child-directed treatment in the ads SDK. If you believe a child has provided us with personal data through a support e-mail, please contact us and we will delete it.

12. Keeping and deleting your data

Because your data lives on your device, you control how long it is kept — we do not hold it and therefore cannot have a retention period for it. You can delete individual trips in the app, and uninstalling DriveMotion removes the app’s database and files with it.

Full instructions, including how to remove the copy that may exist in your device backup, are on the data deletion page.

13. Contact

For any privacy question or request about DriveMotion, use the contact page. We aim to answer within 30 days.