DRIVENOTE
Privacy Policy.
1. Who we are
Odolog is a mileage and trip tracking application published by CodeEnsis Ltd. ("we", "our", "us"), Χριστόδουλου Σώζου 2, EIFFEL TOWER, Floor 3, Flat/Office 301, 1096 Λευκωσία, Κύπρος. This policy explains what data Odolog collects, what we do with it, and your rights.
2. Data stored on your device
The following lives in Odolog's local storage on your phone, in an SQLite database in the app's private storage area. Other apps cannot read it. It is not transmitted to our servers unless you sign in (see §3).
- Trip records - start time, end time, distance, duration, average and maximum speed, route as a list of GPS points, and any tag or category you assign.
- Geocoded start and end addresses (resolved by your device's built-in geocoder, on-device, where available).
- App preferences - units (km/mi), auto-detection toggle, Bluetooth wake-up device, and similar settings.
- Diagnostic logs - recent foreground-service and detection events, kept on the device for support purposes. You can review and clear these at any time.
If you uninstall Odolog without signing in, all of this data is removed with the app.
3. Data synced to the cloud (only if you sign in)
If you sign in to Odolog with Google, your trips and trip metadata are synced to a private collection in Google Firebase Firestore under a path keyed to your unique account ID. Only you, while signed in to that account on a device with Odolog installed, can read or write to that collection.
- The data we sync is the same trip data described in §2 (excluding diagnostic logs).
- We do not access your Firestore data ourselves except where strictly necessary to investigate a support request you have explicitly asked us to look into, and only on data you provide.
- Firestore is operated by Google LLC. Storage region depends on the Firebase project default and may be in the United States or the European Union.
- You can delete all synced data at any time from Settings → Permissions / Data → Delete all data, which removes both the local and the cloud copies.
If you choose Continue without account, no data leaves your device.
4. What we do not collect
- No advertising identifiers. No third-party advertising SDKs.
- No location data is shared with anyone outside the app or your private Firestore collection.
- No contacts, microphone, photo library, or call log access.
- No selling, renting, licensing, or sharing of your trip or location data.
- No use of your data to train any AI model.
5. Permissions Odolog asks for
- Location (precise) and background location - to detect when a trip starts, record its route, and finalize it when you stop. Background access is what allows tracking to continue when the screen is off.
- Activity recognition - to tell driving from walking or cycling and avoid wasting battery on non-driving movement.
- Notifications - to show the live trip notification while a drive is in progress.
- Bluetooth (Nearby devices) - only if you enable Bluetooth wake-up to start trips automatically when your car connects.
- Boot completed - to re-arm trip detection after a device restart.
- Battery optimization exemption (optional, recommended) - so Android does not kill the trip detection service in the background.
You can revoke any permission at any time in your device's system settings. Odolog shows the current state of every permission in Settings → Permissions.
6. Optional Firebase services
Odolog uses the following Google Firebase services to operate cloud sync and improve reliability:
- Firebase Authentication - to identify your account when you sign in. Authentication uses Google Sign-In; we receive your account email and a unique account ID.
- Cloud Firestore - to sync trips between your devices, as described in §3.
- Firebase Crashlytics - to capture crash stack traces (no trip or location data is included in a crash report). Off by default in development, may be enabled in production builds for stability.
Firebase services are operated by Google LLC. Google's privacy practices are described at policies.google.com/privacy and Firebase's at firebase.google.com/support/privacy.
7. Subscriptions
If Odolog offers a paid subscription, the purchase is processed by Apple (App Store) or Google (Google Play). We do not see or store your payment information. Subscription entitlement may be verified through the platform's billing API or, if used, a third-party receipt-validation service such as RevenueCat (privacy policy), which receives an anonymous user identifier and your subscription status only.
8. Children
Odolog is a general productivity tool for drivers. It is not directed at children under 13, and we do not knowingly collect data from children under 13.
9. Your rights
You may, at any time:
- Export your trips as CSV or PDF from Settings → Data → Export Trips.
- Delete all trips (local and synced) from Settings → Account → Delete All Data.
- Sign out, which removes the local copy on this device. Cloud trips remain in your account and are restored if you sign back in.
- Uninstall Odolog, which removes everything stored on the device.
- Request access to, correction of, or deletion of any personal data associated with your account by emailing [email protected]. We respond within 30 days.
If you are in the European Economic Area, the United Kingdom, or California, you have additional rights under GDPR, UK GDPR, and the CCPA respectively, including the right to lodge a complaint with your local data protection authority.
10. International transfers
If you sign in, your data may be processed and stored on Google Cloud servers in the United States or another country where Google operates Firebase infrastructure. By signing in, you consent to this transfer. Google maintains contractual safeguards (Standard Contractual Clauses) for international transfers as required by EU law.
11. Security
Local storage is protected by Android's per-app sandbox. Cloud data is protected by Firebase Security Rules that restrict every document to its owner. Network transport uses TLS. No system is perfectly secure; if you suspect unauthorized access to your account, contact us immediately at [email protected].
12. Changes to this policy
We may update this policy as Odolog evolves. Material changes will be reflected here with an updated "Effective" date above. Continuing to use Odolog after a change means you accept the updated policy.
13. Contact
Questions or requests about this policy: [email protected]. General support: [email protected].