Privacy Policy

Effective date: 11 November 2026 · Odoma Tracker · Tallinn, Estonia

GDPR · Article 13 disclosure

1. Who we are

This Privacy Policy applies to the mobile application Odoma Tracker (the "app"). Throughout this document, "the app" means Odoma Tracker.

The app is developed and maintained by Odoma Digipädevuse Selts ("we", "us", "our"), a non-profit association registered in Estonia (reg. no. 80659718), Tallinn, Harju maakond. Odoma Digipädevuse Selts is the data controller within the meaning of the GDPR.

For privacy-related questions, please contact us at privacy@odoma.ee.

2. What data the app processes on your device

Odoma Tracker processes the following categories of data on your device:

  • GPS / location data — Used to detect trip start and stop, calculate distance, and generate eco-driving and safety scores. Location data is processed on your device. It leaves the phone only in the cases described in section 3.4 (link to your employer and diagnostic logs), in your own backup (below), and through the operating system's map and address services (section 6).
  • Motion and activity data (CoreMotion) — Used to distinguish driving from walking or stationary states. Processed on-device only.
  • Bluetooth proximity data — Used to detect your paired car as a trip start signal. Device names and identifiers are stored locally on your phone and are not transmitted to our servers.
  • Trip records — Trip start and stop time, distance, eco score, safety score, and trip purpose are stored locally on your device. Individual trips are not sent to our servers unless your phone is linked to your employer (section 3.4); summary figures are described in sections 3.1 and 3.2.
  • Scanned receipts — The receipt image and the recognised fields are stored locally on your device. They are not sent to our servers except in the cases described in sections 3.3 and 3.4; the company registration number printed on a receipt may be looked up as described in section 3.5.
  • Backup — On iOS the app copies your data (trips with routes and addresses, receipts with photos, cars, places and settings) to your own iCloud account. On a new installation this backup is on by default unless you choose to start from scratch; you can turn it off in Settings. On Android a backup is saved only to a location you choose. We have no access to these backups.

3. What data is sent to our servers

Unless your phone is linked to your employer (section 3.4), our servers receive aggregate or bucketed metrics and the technical requests described in section 3.5 — not raw GPS tracks, route histories or trip-by-trip location data. Each subsection states whether the data is sent always, only with your consent, or only on your action.

3.1 Impact statistics (always) and public leaderboard (opt-in)

The app regularly sends our server an anonymous summary of your driving: at launch (at most every few minutes on iOS and every six hours on Android), after each trip, and after an app update. This happens on every installation; the app has no switch for it (you can object — see section 4). The summary contains no coordinates and no individual trips:

  • anonymous_id — A randomly generated device identifier created on first launch and stored on your device — in the Keychain on iOS, in the app's private storage on Android. The same identifier is used for the optional Research participation Tier B (see 3.2) and for the technical requests in 3.5.
  • Scores — average and median eco-driving score, the average for your first week and for the last 30 days, the recent trend, your longest streak, the scoring version, and a summary computed by the next scoring version under test.
  • Trips and distance — the number of trips (in total and in the last 30 days), the total distance including distance the app estimates for stretches it did not record, and the share of city and steady cruising driving.
  • CO₂ — estimated excess CO₂ associated with driving style (in total and per 100 km) and the CO₂ norm for your vehicle.
  • Vehicles — the fuel type you selected and how many vehicles of each kind you have in the app (for example, cars, electric cars, bicycles).
  • Region and time — the country code (ISO 3166-1 alpha-2) and region taken from your device settings, not from GPS; your time zone (for example, America/New_York), which shows your approximate region; the date of your first trip; and a technical counter of statistics resets.
  • On Android, also the app build number and the platform.

If you turn on leaderboard participation in Settings (default: off), the summary also includes your display name, your current streak and your best trip, and you appear on the public leaderboard at odoma.ee/<language>/impact/leaderboard. If you decline, the app sends that choice. The summary feeds public impact statistics.

3.2 Research participation — Crowd Dataset (opt-in, default off)

When you opt into Research participation (Settings → Research, or via the in-app prompt after your fifth qualifying trip), one or both of the following levels apply:

Basic study (Tier A)

For each completed self-driven trip, we send a record containing:

  • 28 numeric features in coarse buckets (no exact values): average and maximum speed, duration, distance, number of harsh acceleration and braking events, Safety Score, Eco Score, time-of-day bucket, day-of-week bucket
  • Country code (ISO 3166-1 alpha-2)
  • Operating-system major version (iOS or Android)
  • App version
  • row_id — A fresh random identifier generated for that single upload. It is not stored on your device and is never reused. This makes longitudinal analysis structurally impossible at the Basic level — we cannot link two trips back to the same device.

Individual study (Tier B)

Tier B is an additional, separately consented level. When enabled, each Crowd Dataset record described above is sent with anonymous_id instead of a fresh row_id. The anonymous_id is the same on-device identifier described in section 3.1, allowing us (and, in the future, our research partners) to analyse changes in your personal driving style over time.

We do not transmit, in either Tier A or Tier B:

  • GPS coordinates (start, finish, or route)
  • Addresses or place names
  • Bluetooth device names
  • Exact timestamps (only buckets)
  • Device manufacturer or model
  • Operating-system minor or build version
  • Your name, email, contact data, or any directly identifying information

On iOS, each request to our servers is signed with Apple App Attest so that we can verify it came from a genuine, unmodified instance of the official Odoma Tracker app; the signing key never leaves your device's Secure Enclave. On Android the hardware-backed equivalent (Play Integrity) is not yet enabled — those submissions are validated on the server only. This affects how we verify the sender, not what is sent.

3.3 Receipt-recognition feedback (anonymous, on your request)

The app can scan a receipt (for example, a fuel receipt) with the camera and recognise its fields. The receipt itself, its image, and the recognised fields are stored only on your device (see section 2) and are never transmitted automatically.

If a receipt was recognised inaccurately, you may — by your explicit action — send feedback "for study" to help us improve the recognition algorithm. Before sending, the app shows a preview of exactly what will be sent.

The submitted record contains:

  • Structural receipt fields (these do not identify you): vendor, date, total, currency, VAT rate and amount, net amount, category, payment method, receipt number, document code, store registration code;
  • The list of fields you corrected manually — this is the useful learning signal;
  • Schema version, record creation time, app build number, locale;
  • Redacted receipt text. Hard-form personal data is automatically stripped from the recognised text and replaced with placeholders: IBAN → [IBAN], Estonian isikukood → [ISIKUKOOD], card numbers → [CARD], names (by the "Müüja/Teenindaja/Kassapidaja" anchors and by the device owner's known names) → [NAME]. You see on screen the exact redacted text that will be sent, and you decide whether to send it or not.

Anonymity. The record contains no device identifier, anonymous_id, or any other identifier. The client adds no such fields; additionally, the server checks every submission and rejects it in full, without storing it, if it contains any known identifier field (anonymous_id, pseudo_id, device_id, user_id, and the like). Submissions therefore cannot be linked to each other, to the user, or to your other data in Odoma Tracker.

Integrity. On iOS each submission is signed with Apple App Attest to confirm it came from a genuine, unmodified instance of the official app; the signing key never leaves the device's Secure Enclave. On Android the hardware-backed equivalent (Play Integrity) is not yet enabled.

Server-side storage. Received records are stored append-only, admin-only, are not part of any published or partner-shared dataset, and are used solely to improve receipt-recognition quality. Retention is up to 12 months from receipt, after which the record is automatically deleted.

Legal basis. GDPR Article 6(1)(a) — your consent, given separately for each submission. Because the record is anonymous by construction and minimal in scope, a specific submission cannot be withdrawn after the fact (it cannot be located — it is linked to nothing); you control the transfer before it happens via the preview (see also section 7 on GDPR Article 11).

The app can work linked to your employer's dashboard Odoma for companies (dashboard.odoma.app). The link is enabled only by you: you enter the company's invitation code in the app. Until there is a link, not a single trip or receipt leaves the phone for our servers.

After linking, only trips marked as work trips and the receipts you chose to hand over to the company are sent to the dashboard server: date and time, start and end addresses, distance, odometer readings, purpose, site, compensation amount and a simplified route line (no more than a few dozen points) from which the dashboard determines the site and the time spent there; for a receipt — the photo and the recognised fields. Also sent: your work places with their coordinates and radius, odometer readings and, in Poland and Sweden, the home address you enter. Personal trips are never transferred. If you change a work trip to personal, its server copy is deleted.

The dashboard operator is the commercial company ODOMA SERVICES OSAÜHING (reg. code 17589729); it processes this data on behalf of your employer, and the employer is the controller of this data. Details, retention periods and your rights regarding this data are in the dashboard privacy policy. The link can be broken in the app at any time: after that no new trips go to the server, and the deletion of data already transferred is agreed with your employer.

The phone's diagnostic logs, which include coordinates and raw location points, are uploaded to the dashboard server only from phones of the Odoma team's own organisations, which we use to test the app. Our server refuses them from any other phone, including phones of other users linked to an employer. The app has no switch for this. Otherwise the logs stay on the phone.

3.5 Technical requests (always)

  • Which phone records the trip. So that only one of your phones records a trip, the app sends our server your anonymous_id, a random device identifier, the platform, whether a trip is in progress and, if you are linked to an employer, your pseudonymous driver ID. This is sent at launch, at the start and end of each trip, and every 5–20 seconds while the app is open and you have more than one device. When you hand recording over to another phone, the car's licence plate and name are included.
  • Service status. At launch the app checks our server status; the request has no content, and the server sees your IP address and the app version.
  • App Attest (iOS). Once per installation the app registers an Apple App Attest key; signed requests carry that key's identifier, which stays the same for the installation.
  • Supplier lookup. When a scanned receipt shows a company registration or VAT number, the app asks our server for the company's name. Only that public number is sent; this also happens without a link to an employer.
  • Ideas board. When you open the ideas board, vote or submit an idea, the app sends your anonymous_id, the interface language, your vote and the text of your idea.

4. Legal basis for processing (GDPR Article 6)

Article 6(1)(a) GDPR — Consent

The following processing relies on your explicit consent, which you may withdraw at any time in Settings:

  • Public leaderboard participation (your display name, current streak and best trip, and appearing on the leaderboard)
  • Receipt-recognition feedback (section 3.3) — consent is given separately for each submission
  • Research participation (Tier A, Basic study)
  • Research participation (Tier B, Individual study)

Article 6(1)(f) GDPR — Legitimate interests (impact statistics and app operation)

We process the limited aggregate metrics described in Section 3.1, linked to your anonymous_id, in order to measure the environmental and behavioural impact of the app. This processing is necessary to:

  • Demonstrate the effectiveness of our non-profit environmental mission;
  • Improve the eco-driving and safety scoring algorithms shipped to all users in future versions;
  • Understand how the user base evolves over time.

We also rely on legitimate interests to operate the app reliably: the technical requests in section 3.5, crash reports on Android (section 6) and diagnostic logs of our own test phones (section 3.4), which are used only to find and fix faults.

We consider this processing proportionate because the data is aggregate, contains no raw GPS or directly identifying information (the time zone shows only an approximate region), and is linked only to a device-generated identifier.

You have the right to object at any time by contacting us at privacy@odoma.ee.

5. How long we retain data

  • On-device trip data — Stored until you delete individual trips or uninstall the app. This data remains under your control.
  • Public leaderboard entry — Removed within 7 days after you disable leaderboard participation.
  • Impact statistics (section 3.1) — Kept while the app keeps sending them. The app has no button to delete them; to have them deleted, write to privacy@odoma.ee.
  • Crowd Dataset Tier A (Basic study) — Retained for up to 24 months from upload date, then automatically deleted.
  • Crowd Dataset Tier B (Individual study) — Retained for up to 24 months from your last contribution. After 12 months of inactivity, your records are automatically purged. You may also request immediate deletion at any time by tapping "Delete my data" in Settings → Research.
  • Receipt-recognition feedback (section 3.3) — Up to 12 months from receipt, then automatically deleted. A record cannot be linked to you or deleted on request, because it is anonymous by construction.

6. Data sharing and third parties

We do not sell or rent your data, and we do not share it with advertising networks or data brokers. The apps contain no advertising or analytics SDKs and do not use an advertising identifier. One exception concerns the website only, never the app: the odoma.ee site loads Google's tag to measure our Google ads. The tag sets no cookies unless you arrive from a Google ad and press "Agree" in the banner; then Google is told that the ad led to a tap on an app store button — see the Cookie Policy.

Crash reports (Android). The Android app includes Firebase Crashlytics (Google). When the app crashes or records an internal error, a report with the stack trace, the device model and operating-system version, the app's state and a Firebase installation identifier is sent to Google, which processes it on our behalf and may process it outside the EU, including in the United States. The app has no switch for this. The iOS app uses Apple frameworks only and sends no crash reports to us.

Maps and addresses. To turn coordinates into addresses and to show maps, the app uses the operating system's services: Apple on iOS and Google on Android. Coordinates are sent to them under their own terms; our servers are not involved.

Fuel prices (United States). To suggest a fuel price in the car editor, the app downloads public data from the U.S. Energy Information Administration. No personal data is sent; that service sees your IP address.

Our server infrastructure is hosted on Google Firebase in the EU region (europe-west3, Frankfurt, Germany): functions, files and the Firestore database are all located there. Until 22 September 2026 the database was hosted in the europe-west2 (London, United Kingdom) region under the European Commission's adequacy decision; all of this data is now kept in the EU. Firebase hosts our backend API and the data described in section 3. If you use the app outside the EU — for example, in the United States — this data is sent to and stored on our servers in the EU. We use Firebase under Google's applicable data processing terms.

Future insurance pilots (Tier B only)

We are exploring partnerships with insurance companies to enable discount programs for careful drivers, based on Crowd Dataset Tier B data. No such program is currently active. Before any sharing of your anonymous_id-linked records with an insurance partner takes place:

  • A written joint controller or data processor agreement (GDPR Art. 26 / 28) will be in place;
  • The specific partnership and data flow will be disclosed in the app and on this page;
  • We will obtain your explicit, separate opt-in consent for that specific program before any sharing happens. Existing Tier B consent does not by itself authorise sharing with a specific insurer.

If you have only Tier A consent (not Tier B), your data carries no anonymous_id and is structurally non-linkable to you, so it cannot be shared with insurance partners as your data.

7. Your rights under GDPR

If you are located in the EU/EEA, you have the following rights:

  • Access (Art. 15) — Request a copy of the data associated with your anonymous_id.
  • Rectification (Art. 16) — Request correction of inaccurate data.
  • Erasure (Art. 17) — Request deletion of all server-side data associated with your anonymous_id. The fastest way is the in-app "Delete my data" action in Settings → Research:
    1. Collection pauses immediately.
    2. A signed withdrawal request is sent to our server.
    3. All records linked to your anonymous_id in the Tier B Crowd Dataset are deleted within 30 days.
    4. You may continue using all app features, including the Basic study (Tier A), without anonymous_id linkage.
  • Restriction (Art. 18) — Request that we restrict processing while a dispute is being resolved.
  • Data portability (Art. 20) — Request your data in a structured, machine-readable format.
  • Objection (Art. 21) — Object to processing based on our legitimate interests.
  • Withdraw consent (Art. 7(3)) — Disable any opt-in toggle at any time in Settings.

Processing not requiring identification (GDPR Art. 11). Some data is anonymous by construction — primarily receipt-recognition feedback (section 3.3) and Crowd Dataset Tier A. Such records contain no identifier and cannot be matched to you. Under GDPR Article 11, where the controller is unable to identify the data subject, the rights of access, rectification, erasure, and portability (Art. 15–20) do not apply to that data, because we cannot locate "your" records among the anonymous ones. We are not required to, and will not, collect additional data solely in order to identify you. Control over such data is exercised before submission — through the opt-in toggles and the pre-send preview.

To exercise any right, contact privacy@odoma.ee. We respond within 30 days. You also have the right to lodge a complaint with the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon) at aki.ee.

8. Children

Odoma Tracker is not directed at children under the age of 16. We do not knowingly collect data from anyone under 16. If you believe that a child has used the app and transmitted data to us, please contact us so that we can delete it.

9. Changes to this policy

We may update this Privacy Policy as the app evolves. Material changes will be communicated in the app release notes and on this page together with an updated effective date. Continued use of the app after a material change takes effect constitutes acceptance of the updated Privacy Policy.

Change log

  • 2026-11-11 (v1.8.0) — Corrected the description of what the app already sends; nothing new is collected. Impact statistics (3.1) are sent on every installation, not only with leaderboard participation, and the full list of fields is given; leaderboard participation adds the display name, streak and best trip. Added 3.5 "Technical requests": which phone records the trip, service status, App Attest, supplier lookup, ideas board. Diagnostic logs with coordinates: accepted only from phones of the Odoma team's own organisations, not by a switch in the app. Section 2: backup to your own iCloud (on by default on a new iOS installation) and the operating system's map services. Section 3.4: work places, odometer readings and the home address in Poland and Sweden. Section 6: crash reports on Android (Firebase Crashlytics), maps and addresses, fuel prices for the United States, data of users outside the EU is stored in the EU. Section 5: retention of impact statistics.
  • 2026-09-22 (v1.7.1) — The Firestore database was moved from the europe-west2 (London, United Kingdom) region to the EU region (europe-west3, Frankfurt): functions, files and the database are now hosted in the EU and no basis for a transfer to the United Kingdom is needed any more; section 6 updated. No change to what is collected, why, or with whom it is shared.
  • 2026-09-04 (v1.7.0) — Added section 3.4 "Link to your employer — Odoma for companies": what goes to the employer's dashboard and when (only work trips and handed-over receipts, a simplified route line), who operates the dashboard, a link to its policy; the database region clarified (europe-west2, London) and the basis for the transfer.
  • 2026-08-22 (v1.6.0) — Android release. The policy now names both apps (iOS and Android) where it previously named only iOS. The Crowd Dataset field "iOS major version" is described as the operating-system major version (nothing changed on the wire — the app has always sent only the major version); the on-device identifier store is named per platform (Keychain on iOS, app-private storage on Android); App Attest is scoped to iOS, with the Android status stated plainly. No change to what is collected, why, or with whom it is shared.
  • 2026-05-16 (v1.4.0) — Added section 3.3 "Receipt-recognition feedback": anonymous by construction (server rejects known identifier fields), per-submission consent, pre-send preview, automatic text redaction (IBAN/isikukood/cards/names), App Attest, 12-month retention. Added corresponding lines to sections 2 and 5 and a GDPR Article 11 note (processing not requiring identification) to section 7. Defined "the app" as Odoma Tracker in section 1.
  • 2026-05-09 (v1.3.0) — Added Crowd Dataset (Research participation) section: Tier A (Basic study, fresh row_id per upload, no longitudinal linkage) and Tier B (Individual study, linked to device pseudonym). Added withdrawal mechanics (in-app "Delete my data" → server-side deletion within 30 days). Disclosed shared anonymous_id between leaderboard and Tier B. Disclosed future intent for insurance partnerships under separate opt-in.
  • 2026-04-30 (v1.2.0) — Initial public version.

Questions or requests: privacy@odoma.ee Odoma Tracker · Tallinn, Estonia · odoma.ee