Drivemap — Privacy Policy

Last updated: 17 June 2026

Drivemap is a private logbook for your drives and rides. It has no account, no login, and no developer server. This policy explains, in plain language, what the app keeps, where it stays, and which Apple services it relies on.

The short version

• We do not operate a server. There is no Drivemap account and no login.
• Your drives, recorded GPS tracks, vehicles, drivers, photos, and stats are stored on your device, and — if you turn on iCloud — sync only through your own iCloud account's private database.
• We cannot read your data. That private database is encrypted to your Apple Account and is not visible to the developer.
• Drivemap contains no analytics, no advertising, and no third-party crash or tracking SDKs.

What Drivemap stores, and where

• On your device: your GPX route files (the source of truth), a metadata and statistics database, and a cached copy of any vehicle or driver photos you add.
• In your private iCloud database (only if iCloud is enabled): the same drives, tracks, and metadata, synced by Apple's CloudKit on your behalf so your own devices stay in sync. This database lives in your personal Apple Account, counts against your personal iCloud storage, and the developer has no way to list, read, or recover its contents.
• Because there is no developer copy of your data, if you lose access to your Apple Account we cannot restore it. Use the in-app export (below) to keep your own backup.

Recording a drive (location)

• When you start a recording, Drivemap uses your device's GPS to capture the track of that drive. With your permission it keeps recording in the background, so a drive keeps recording with the screen off.
• This location data is used only to build your drive's track. It stays on your device and in your own private iCloud. It is never sent to the developer and is never used for advertising or tracking.
• You control location access in the system permission prompt, and in the iOS Settings app, at any time.

Importing from Apple Health

• If you choose to import workouts, Drivemap reads the GPS routes of your outdoor cycling workouts from Apple Health, read-only, so those rides appear on your map.
• Drivemap never writes anything back to Apple Health. Imported routes are treated exactly like your other drives — stored on your device and in your own private iCloud.
• You can optionally turn on "import new rides when Drivemap opens": when enabled, Drivemap checks Apple Health for new outdoor cycling rides each time you open the app and adds them. It never reads Apple Health in the background.
• Your Health data is used only to show those rides in Drivemap. It is never used for advertising, marketing, or tracking, and is never sold or shared with anyone.

Apple services Drivemap relies on

Drivemap uses Apple's built-in services. Apple's handling of these is governed by Apple's privacy policy, not this one:

• iCloud / CloudKit transports and stores your private database on Apple's infrastructure, under your Apple Account.
• Apple Maps / MapKit draws the map. Viewing or panning the map may send map requests to Apple to fetch the tiles for the area you are looking at.

These requests are made to Apple to provide the feature you asked for. The developer receives nothing back from them and collects nothing.

Local backup and export

• Export is entirely user-initiated and local. When you export, Drivemap writes a portable .zip file to a location you choose; Drivemap does not upload it anywhere. If you then save or share it through another app, cloud drive, or Files provider, that destination's privacy practices apply.
• Please note: this export file is unencrypted and portable — anyone who obtains it can read its contents. Store it carefully (for example on an encrypted disk) and delete copies you no longer need. It is your backup, not a developer-held one.

Deleting your data

There is no developer-held copy of your data, so there is nothing to ask us to delete — removal is entirely in your hands:

• In the app you can edit or remove vehicles and drivers. Archiving a drive only hides it from your lists; it does not erase the drive.
• Deleting the Drivemap app removes its on-device data.
• The synced copy lives in your own iCloud account; you can remove it from the iOS Settings app, under your Apple Account's iCloud storage. To erase everything, delete the app and remove its iCloud data — and if you want to keep a copy first, use the export above.

What Drivemap does NOT do

• No analytics or usage tracking.
• No advertising, and no advertising identifiers.
• No third-party crash-reporting or telemetry SDKs.
• No developer server, and no upload of your drives, tracks, Health imports, photos, or other content to the developer or to any non-Apple service.

Children's privacy

Drivemap is a general-audience app. The developer does not collect personal information from anyone, including children — the information you create stays on your device and, if you enable iCloud, in your own private iCloud database, never with the developer.

Changes that would require updating this policy

The promise above — that your content stays on your device and in your own private iCloud, apart from the Apple system services described above — is the whole design. If a future version ever added something that sends data elsewhere — for example non-Apple map tiles, a share-to-the-cloud feature, a developer server, or any analytics, advertising, or crash-reporting SDK — this policy and the App Store privacy information would be updated, and where appropriate you would be asked for consent, before that version shipped.

Changes to this policy

If this policy changes, the "Last updated" date above will change, and the current version will always be available inside the app and at the published policy address.

Contact

Questions about privacy in Drivemap: privacy@smeingast.eu