Local Drive Log
Language

Privacy Policy

Local Drive Log · Last updated 9 July 2026

Local Drive Log is a local-first app: your driving data lives on your phone, not on our servers. We have no account system and no backend for your trips — so there is very little for this policy to be about. This page explains, plainly, the few times any data leaves your device, to whom, and your rights under the GDPR.

The short version. We don’t have your trip data — it never leaves your device except when you deliberately use two online features (route estimation and, if you turn it on, address lookup), which send only coordinates. There is no account, no cloud sync, no analytics, no advertising, and no trackers. Deleting the app deletes everything.

1. Who is responsible (data controller)

The controller for the limited processing described here is Jussi Mäkelä. You can reach us about privacy at [email protected]. This is the only contact we require you to have; we do not ask for or publish a postal address.

2. What data the app handles — and where it is stored

When you use the app, it creates and stores the following only on your device:

All of this is held in the app’s local database and local files on your phone. We do not receive, see, collect, or store any of it. There is no account to create, no server-side copy, and no cloud sync. A backup you export is a file that stays entirely in your hands — you choose where to share or store it.

3. Location and tracking

Recording is manual: a trip is recorded only after you tap to start it, and only while it is running. The app uses location only in the foreground / “while in use” (with a temporary notification while a drive is being recorded, so recording continues if your screen locks). It does not use background or “always” location, does not track you when you are not recording, and does not use motion/activity recognition. Location points are written to your device only.

4. When data leaves your device

There are three situations, each described honestly below. In none of them do we keep a copy.

4a. Route estimation and address lookup (the routing service)

Two explicit, online, user-initiated actions send data off the device:

What is sent: only coordinates — 2 to 10 points for a route, or a single point for an address — rounded to about one metre before they leave your device. Nothing else is sent: no trip identifier, no user or device identifier, no purpose, no times, no account data.

Our proxy is stateless. The coordinates go first to our own small relay (a Cloudflare Worker) that exists so the routing provider’s API key never ships inside the app. It logs nothing, stores nothing, has no database or cache, and keeps nothing between requests. It also strips your IP address and device details and makes a fresh request, so the routing provider never sees your IP — only our proxy’s.

The providers:

4b. Maps

To display a map (for example on a trip’s detail screen or when picking a point), the app — like any map app — downloads map images for the area you are viewing from the OpenStreetMap Foundation. This reveals the map area you look at (which corresponds roughly to that trip’s location) and your IP address to them. Your trip data itself is never uploaded; only the request for the map tiles is made, and only when a map is on screen. See the OpenStreetMap Foundation privacy policy.

4c. Purchases

If you buy Pro, the purchase is handled by Google Play or the Apple App Store, with RevenueCat, Inc. (USA) as our subscription-management processor. They handle the transaction and receive purchase/transaction identifiers and an app-generated anonymous identifier used to recognise your entitlement; RevenueCat may be contacted when the app checks whether Pro is active. We never receive your payment-card details. See the policies of RevenueCat, Google, and Apple.

5. Legal bases (GDPR Art. 6)

6. International transfers

The routing/geocoding provider (HeiGIT/OpenRouteService) is in Germany (EU). Cloudflare (proxy host) and the app stores are US companies; transfers rely on Standard Contractual Clauses and equivalent safeguards under their data-processing terms.

7. Retention

We hold no personal data about you, so there is nothing for us to retain. Your on-device data stays until you delete it; third parties (above) retain data under their own policies. Where you keep tax records for the retention period your tax authority requires, that record lives on your device and in any backup you choose to keep.

8. Your rights

Under the GDPR you have the right to access, rectification, erasure, restriction, portability, and objection, and to lodge a complaint with a supervisory authority. Because your data is on your device and we don’t hold a copy:

In Finland you may complain to the Office of the Data Protection Ombudsman (Tietosuojavaltuutetun toimisto, tietosuoja.fi); in other EU/EEA countries, to your national supervisory authority.

9. Children

Local Drive Log is a tool for self-employed people and is not directed at children. We do not knowingly collect data from children.

10. Changes to this policy

If we change this policy we will update the date at the top and, for material changes, note them here. Continued use after an update means you accept the revised policy.

11. Contact

Questions about this policy or your data: [email protected].