DriveDNA: Trip Tracker — Privacy Policy

Last updated: 6 May 2026

← Back to DriveDNA

DriveDNA was designed around a simple idea: your drives never leave your phone unless you choose to share them. This policy explains exactly what that means in practice.

1. The short version

  • All raw trip data — coordinates, polylines, addresses, notes — is stored on your iPhone.
  • If you opt in, we sync that data across your Apple devices using Apple’s CloudKit. We do not run a server that sees it.
  • We do not sell, rent, share, or analyse your driving data. We do not train AI on it.
  • You can delete every trip from inside the app.

2. Data we collect on the device

To make DriveDNA work, the app stores the following locally on your iPhone:

  • Location and motion data — GPS coordinates, speed, heading, elevation, and CoreMotion signals captured during a drive, used to detect trip start/end and draw your route polyline.
  • Trip metadata — start and end addresses (resolved on-device via Apple’s reverse geocoding), distance, duration, top and average speed.
  • Your inputs — vehicle profiles, trip categories (Business, Personal, Commute, Medical, Charity), purpose notes, photos.
  • App preferences — units, paywall state, widget settings.

3. Data we do not collect

  • We do not collect your contacts, calendar, photos library, microphone, camera roll, or health data.
  • We do not use third-party analytics SDKs, ad SDKs, or attribution SDKs.
  • We do not have a server that receives your routes or coordinates.
  • We do not run any AI or LLM on your driving data, on-device or otherwise.

4. iCloud sync (optional, Pro)

If you enable iCloud sync, DriveDNA uses Apple’s CloudKit to copy your DriveDNA data to your private iCloud container so it can sync to your other Apple devices signed in to the same Apple ID. CloudKit’s private database is end-to-end inside Apple’s pipe; we cannot read your CloudKit data, and no third party is involved. Apple’s handling of CloudKit data is covered by their own privacy policy.

5. Subscriptions

DriveDNA Pro is sold via the Apple App Store. Apple processes your payment under your Apple ID. We use RevenueCat as a thin client-side SDK to validate App Store receipts; RevenueCat receives an anonymous installation identifier and your subscription status, but no trip data, no name, no email, and no precise location.

6. Permissions and what they’re for

  • Location — Always: required to auto-detect drives in the background. We use Apple’s Significant-Location-Change service to wake the app, then activate higher-precision GPS only while a drive is in progress.
  • Motion & Fitness: used to distinguish driving from walking or cycling, so we don’t log non-drives.
  • Notifications: optional, used for personal-record celebrations and monthly recap reminders.
  • CarPlay: optional, lets you glance at trip stats and quick-categorize while connected.

You can revoke any of these permissions in iOS Settings at any time. The relevant features will simply stop working.

7. CSV exports and shared trip cards

When you export a CSV mileage log or share a trip card, the file is produced on your device and handed to iOS’s share sheet. From that point on it is in the destination app’s hands (Mail, Files, Messages, etc.) under that app’s own privacy terms. We have no copy of what was exported.

8. Data retention and deletion

  • Free tier retains the most recent 30 days of trips on your device.
  • Pro tier retains data until you delete it.
  • You can delete any trip individually, or wipe all DriveDNA data via Settings → Reset.
  • Uninstalling the app removes local data. To remove the iCloud copy, sign in to iCloud.com or use Settings → iCloud → Manage Account Storage on your device and remove DriveDNA data.

9. Your rights (GDPR, UK GDPR, CCPA and similar)

Because we do not operate a server that holds your driving data, the practical answer to most data-subject requests is: the data is on your device — you already have direct access, the right to export it (CSV), and the right to delete it (in-app reset). For any rights you believe are not satisfied by these controls — including access, rectification, restriction, objection, portability, or a complaint to a supervisory authority — write to akhaneva.co@gmail.com.

We do not sell or share personal information for cross-context behavioural advertising. There is nothing to opt out of in that sense.

10. Children

DriveDNA is intended for licensed drivers and is not directed to children under 13 (or the equivalent age in your jurisdiction). We do not knowingly collect data from children.

11. Security

Local data is protected by iOS’s standard data protection. iCloud sync uses Apple’s CloudKit private database, accessible only by your Apple ID. We do not run any servers that hold driving data, so there is no DriveDNA server for an attacker to breach.

12. Changes to this policy

We may update this policy from time to time. The “Last updated” date above will reflect the latest revision, and material changes will be surfaced in-app.

13. Contact

Questions, requests, or curiosities? Write to akhaneva.co@gmail.com.