On the phone
The service log, OBD readings, workshop reports and preferences are the working copy, on the device.
Skip to content
AutoDiag Congo · Google Play
Your service log stays on the phone. The cloud keeps the chassis number.
AutoDiag is local-first. Maintenance records, OBD scans and photos live on your device first. We keep the chassis number (VIN) so history follows your account if you change phones. ExpertDiag mirrors are backups of that vehicle identity — not a commercial profile.
Last updated: 18 August 2026
Vehicle identity
The chassis number (VIN) is the permanent key. Not the ECU: a computer can be swapped, the chassis cannot.
Backup mirror
A copy indexed by chassis may be kept in the ExpertDiag hub so history can be restored after reinstall. This is not a social network.
Three layers, one goal: history follows the car
The same pattern used by serious OBD apps (local log, VIN as identity, optional continuity cloud) — for Congo, with no advertising.
1 · Phone
You scan, you log an oil change. That data is for you, here and now.
2 · Chassis
The VIN ties events to the right vehicle, even after an engine swap or a new phone.
3 · Mirror
A technical backup (identity + chassis-linked history) so a lost phone does not erase the log.
We do not collectYour GPS position
We do not collectThe phone address book
We do not collectSMS or call logs
We do not collectBank card data (licences are handled in-app / via support)
We do not collectAn advertising ID
1. Controller
The AutoDiag Congo app (Android package com.autodiag.congo) is published by Établissements RAND SARLU, Brazzaville, Republic of the Congo, under the ExpertDiag Congo brand.
This page is the official privacy policy required by Google Play. It covers AutoDiag Congo. The online shop (shop.expertdiag-congo.com) has a separate checkout / delivery policy.
Governing law: Act No. 29-2019 of 10 October 2019 on personal data protection in the Republic of the Congo, plus Google Play Data Safety rules.
2. Local-first principle
We do not sell your data. We do not run targeted ads. We do not build a marketing profile.
Usage data (log, scans, photos, notes) is stored on the phone first. A backup mirror, indexed by chassis number, may be kept on our Firebase servers so history can be restored if you reinstall or change devices.
We keep the chassis number because it is the vehicle’s permanent identity. Without it, account history is meaningless in a market where engine and ECU swaps are common.
- Working copy: the phone (Android storage, local database).
- Cloud identity key: chassis number (VIN) tied to the account.
- Mirror: continuity copy (vehicle + linked history), not a public showcase.
3. What we process
The table matches the Play Store Data Safety form. If a practice changes, this page is updated first.
| Data | Where | Why |
|---|---|---|
| Chassis number (VIN) | Cloud (identity) + phone | Attach history to the vehicle, including after a phone change |
| Make, model, year, fuel, mileage, plate | Phone + backup mirror | Service log, Congo-aware reminders, garage restore |
| Account (Google email or Firebase ID) | Cloud (authentication) | Protect the garage, licence, diagnostic-help quotas |
| Google name and profile photo (if you sign in with Google) | Firebase account | Show the account in the app — never sold |
| OBD scans, fault codes, service log | Phone first, mirror indexed by chassis | Vehicle memory and restore |
| Workshop reports (PDF / job sheet) | Phone (local database); automatic expiry | Read a report offline, then purge |
| Notification token (FCM) | Cloud, tied to the account | Oil / fault reminders — can be turned off in the app |
| Crash logs (Crashlytics) | Google Firebase | Fix bugs. No ads. No selling. |
| Fault codes + vehicle card (make, model, km) | Transient AI processing (if you request an analysis) | Produce diagnostic help. Not a public profile. |
The “Contribute to the technician knowledge base (anonymised)” switch is off by default. If you turn it on, technical excerpts (codes, vehicle context) may improve ExpertDiag knowledge — without your name.
4. Android permissions — what they are for
A permission is not collection. AutoDiag asks for system access to work; we do not use it to track you.
- Location: only to discover the Bluetooth OBD adapter (Android requirement). We do not collect, store or share GPS coordinates.
- Bluetooth: connection to an ELM327 / compatible adapter. The adapter address may be remembered for faster reconnect.
- Camera: ExpertDiag QR codes and photos you take. No background camera access.
- Microphone: only if you use assistant dictation. Speech recognition may then go through the Android / Google service you chose.
- Internet: sign-in, licence, backup mirror, analyses you request, notifications.
5. Processors
We use infrastructure vendors, not ad networks. No data is sold.
- Google Firebase (project autodiag-congo, region us-central1): Auth, Firestore, Cloud Functions, Cloud Messaging, Crashlytics, App Check. TLS in transit; Google encryption at rest.
- ExpertDiag hub (DiagSync): vehicle-identity mirror (chassis) for workshop / shop continuity — not a public directory of drivers.
- AI providers (Google Gemini and/or DeepSeek): only when you run an analysis. The prompt includes fault codes and vehicle context, not your address book.
- Google Play: app distribution and, where applicable, Google account information under Google’s policy.
These processors may handle data outside the Republic of the Congo (including the United States). The transfer is limited to running the service.
6. Retention
We keep the minimum needed for vehicle history and the licence.
- On the phone: until uninstall or Android data clear.
- Chassis and backup mirror: for as long as the account exists, so history can still be attached to the vehicle.
- Crash logs: short technical retention at Google (weeks).
- AI processing: transient; we do not train a public model on your name.
- After account deletion: personal data tied to the account is erased within 30 days, except legal holds (licence / dispute evidence).
7. Your rights and deletion
You may access, correct, restrict or request erasure of personal data about you.
To delete the AutoDiag account: email info@expertdiag-congo.com (cc romeo@mutuka.pro) with subject “AutoDiag account deletion” and the account email. Timeline: 30 days after identity check.
Uninstalling the app deletes the local copy. To also erase the cloud mirror (chassis / account history), a written request is required.
- Reminders and alerts: Profile → Notifications.
- Anonymised contribution: Profile → Privacy.
- WhatsApp support: +242 04 48 44 422.
8. Children
AutoDiag is for drivers and vehicle owners. It is not directed at children under 16. We do not knowingly collect children’s data. If an account was created by mistake, contact us to delete it.
9. Changes
If we change this policy in a material way, the date at the top will be updated. For a major change (new purpose, new sharing), we will notify in the app where possible.
10. Google Play Data Safety mapping
Copy this into Play Console → App content → Data safety. “Collected” means sent off the device. Data that stays only on the phone is not “collected” under Play rules.
| Play | Collected? | Purpose |
|---|---|---|
| Email address | Yes (account) | App functionality, account management — not sold |
| Name | Yes if Google | Account management — not sold |
| User IDs | Yes (Firebase UID) | App functionality — not sold |
| Device IDs (FCM) | Yes | Notifications — not sold |
| Photos | Optional | Vehicle / profile photo — not sold |
| Crash logs | Yes | App stability — not sold |
| Vehicle info (VIN / chassis) | Yes | Account history — not sold |
| Location | Not collected | Bluetooth permission only, no stored GPS |
| Contacts, SMS, personal files | No | — |
| Ads, data sale, cross-app tracking | No | No ad SDK in AutoDiag |
Bluetooth OBD QR / photos Optional dictation
Contact
RAND SARLU — ExpertDiag Congo, Brazzaville. We aim to reply within 30 days.
Parts orders and delivery: separate policy at shop.expertdiag-congo.com/politique-confidentialite.