DriveLog Privacy Policy

Effective date: 24 June 2026 · Applies to DriveLog Android app v0.3.5 and later

The short version: DriveLog records your driving locally on your phone. Your GPS trips, vehicles, and notes never leave the device — there is no cloud account, no analytics, no advertising. The only network request DriveLog makes is a small version.json check to see if a newer version is available.

1. Who we are

DriveLog is developed by BlueberryS s.r.o. (Slovakia), trading as BlueberryS Digital. Developer contact: info@blueberrysdigital.com.

2. What data the app collects and where it lives

2.1 GPS location (precise + background)

DriveLog uses ACCESS_FINE_LOCATION and ACCESS_BACKGROUND_LOCATION to record the GPS trace of your drives. Locations are stored exclusively in a local SQLite database on your device (kniha_jazd.db in the app's private storage).

Why background location: the core feature of an automatic mileage logger is to start, record and stop a trip without you having to open the app at every traffic light. The location service runs as a foreground service (visible notification) and continues recording while the phone is locked or in your pocket.
What is stored: GPS coordinates (latitude, longitude, altitude, speed, accuracy, timestamp), aggregated into trip start, end and the path between.
Where it goes: nowhere outside your device. There is no upload, sync, or backend.

2.2 Physical activity recognition (sensor classification)

DriveLog uses ACTIVITY_RECOGNITION together with Google Play Services to detect when you have entered a vehicle (an IN_VEHICLE signal). This lets the app start the GPS faster than waiting for a speed threshold from raw location samples.

Classification of sensor data (accelerometer, gyroscope, magnetometer) is performed on-device by Google Play Services.
DriveLog only receives the resulting transition signal (entered vehicle / left vehicle). Raw sensor readings never leave the device.
This permission is optional. The app works without it; detection just takes a bit longer.

2.3 Vehicle metadata and trip annotations

Vehicle names, license plates, initial odometer values, trip purpose, notes, and trip type (business / private) — all entered by you, all stored locally.

2.4 App preferences

Settings (theme, accent color, detection thresholds, tracking on/off) stored in the local database.

3. What we do not collect

No account registration, no email, no password — DriveLog has no user account at all.
No analytics, telemetry, crash reporting, or third-party SDKs (no Firebase, Google Analytics, Crashlytics, Sentry, Mixpanel, Facebook SDK).
No advertising identifiers, no advertising SDKs.
No contacts, calendar, photos, or other personal data outside the app's own database.
No automatic cloud backup. Android's system-level "Backup & Restore" is disabled for DriveLog (android:allowBackup="false") so that not even Google Drive can capture your trip database without your action.

4. Network access

DriveLog requests INTERNET permission for one purpose only:

On launch, the app fetches a small JSON manifest from https://blueberrysdigital.com/drivelog/version.json to check whether a newer version is available. If yes, an in-app banner appears with release notes and a download link. No personal data, no identifiers, and no payload other than a standard HTTP GET request is sent.

That is the entire network footprint of the app. There are no other API calls, no telemetry pings, no error reporting.

5. Sharing and third parties

We do not share or sell your data to anyone, ever. We have no backend, so we have nothing to share even if we wanted to. The only third party involved is Google Play Services (on-device, for Activity Recognition) — see §2.2.

If you tap the "Map" button next to a trip's start or end coordinates, DriveLog hands that single coordinate to whichever map app you have installed (Google Maps, Mapy.cz, OsmAnd, etc.) via Android's standard geo: intent. That map app then becomes responsible for what it does with the coordinate — please consult its own privacy policy.

If you tap "Export CSV", DriveLog writes the file to wherever you choose via Android's Save-as dialog (Downloads, Drive, etc.). What happens to that file afterwards depends on where you put it.

6. Your rights and controls

Delete a single trip: open it in the trip list → Delete.
Delete all data: Settings → "Wipe all data" wipes the database (vehicles, trips, settings).
Uninstall: uninstalling DriveLog from Android removes the entire local database. Nothing is retained anywhere.
Revoke permissions: Android Settings → Apps → DriveLog → Permissions. You can revoke Location or Activity Recognition at any time; the app will degrade gracefully (manual tracking still works).
Export your data: Settings → "Export CSV" produces a portable CSV of your trips that you can keep, edit in Excel, or import back later.

7. Children

DriveLog is intended for adult drivers. It does not knowingly collect data from children under 13.

8. Changes to this policy

If we ever materially change how DriveLog handles data, the in-app update banner will surface a new release whose changelog calls out the change. The latest version of this policy is always at blueberrysdigital.com/drivelog/privacy.html.

9. Contact

Questions, requests, or concerns: info@blueberrysdigital.com.