Effective date: 30 April 2026
Version: 1.3
App: Transmission (Android, iOS to follow)
Publisher: Transmission App
This policy explains what Transmission does — and does not — do with your data. We have written it in plain English so you can actually read it. If anything below changes, we will bump the version and the effective date and surface a notice in the app on next launch.
- Your data stays on your device by default. Vehicle profiles, fuel and charging logs, photos, and notes are stored only in Transmission's private storage on your phone.
- We do not collect, sell, or share personal information. No advertising IDs. No third-party analytics SDKs.
- No account is required to use the app. An optional Google sign-in lets you enable cloud backup — you must explicitly opt in.
- Photos are processed on-device. They are compressed locally before being uploaded if cloud backup is enabled.
- Cloud backup is end-to-end encrypted. Sensitive fields (station names, notes, payment method labels) are encrypted on your device before upload. We cannot read them.
- Location is used only for the charger map feature. When enabled, your location is sent to the Open Charge Map API to find nearby EV charging stations. It is not stored in our database.
- Bluetooth is used only to connect to your OBD-II adapter. Only the device name and MAC address of your paired adapter are stored locally. Nothing is transmitted to our servers.
- You can export or delete everything you've logged at any time.
Transmission only handles the information you choose to enter. Specifically:
| Category | Examples | Where it lives |
|---|---|---|
| Vehicle data | Vehicle name, type, fuel type, tank/battery capacity, initial odometer | On-device, app-private storage |
| Fuel & charging logs | Date, odometer reading, volume / kWh, price, payment method label, optional station name, optional notes | On-device |
| Maintenance logs (future phase) | Service type, cost, odometer, due-by date | On-device |
| Photos | Receipts, odometer snapshots, service invoices — captured via camera or selected from gallery | On-device, app-private storage; compressed before saving; EXIF location data is stripped |
| Settings | Currency, unit system, default vehicle, opt-in toggles | On-device |
| Location | Precise device location when you open the Charger Map screen | Sent to Open Charge Map API (ocm.io) only; never stored on-device or in Firebase |
| OBD-II adapter info | Bluetooth device name and MAC address of your paired ELM327 adapter | Stored locally in SharedPreferences; never transmitted |
| Anonymous device identifier | A random ID generated when the app is installed | On-device only; never transmitted unless you explicitly enable cloud sync in a future release |
We do not collect: your name, email, phone number, contacts, advertising ID, browsing history, or any biometric data.
- ❌ No advertising and no ad networks.
- ❌ No third-party analytics or tracking SDKs (no Google Analytics for Firebase data collection, no Meta SDK, no Mixpanel, etc.).
- ❌ No persistent or background location tracking. Location is used only in-session on the Charger Map screen and is never stored.
- ❌ No reading of SMS, contacts, call logs, or other apps' data.
- ❌ No sale or sharing of personal information with anyone.
- ❌ No use of your data to train machine-learning models.
- ❌ No Bluetooth data transmitted to any server.
The app only requests the permissions it needs for the features you actively use.
| Permission | Why | Optional? |
|---|---|---|
| Camera | Capturing receipt or odometer photos. | Yes — only prompted when you tap the camera button. |
| Photos / media access | Attaching an existing photo to a log entry. | Yes — only when you choose to attach. |
| Storage / Media | Saving compressed receipt photos to app-private storage. | Yes — only when you attach a photo. |
| Notifications | Local push alerts for mileage anomalies and maintenance reminders. No notification content is sent to any external server. | Yes — you can decline or disable later. |
| ACCESS_FINE_LOCATION | Finding nearby EV charging stations on the Charger Map screen. Your location is sent to Open Charge Map API (ocm.io) — a third-party open data service. Location is not stored by Transmission. | Yes — Charger Map feature will be unavailable if denied. |
| BLUETOOTH_SCAN / BLUETOOTH_CONNECT | Discovering and connecting to your ELM327 OBD-II adapter for vehicle diagnostics. | Yes — OBD-II features will be unavailable if denied. |
| Internet | Charger Map (Open Charge Map API) and the optional cloud backup feature. | Yes — Charger Map requires connectivity; cloud sync is opt-in. |
You can revoke any of these permissions at any time in your phone's system settings.
All calculations — mileage, cost-per-km, monthly spend, anomaly alerts — are performed locally on your device. When the future receipt-scanning feature ships, the optical character recognition (OCR) model also runs on-device. Photos never leave your phone for any of these features.
Receipt scanning uses Google ML Kit Text Recognition, which runs entirely on-device. No image data is sent to Google's servers.
Transmission requests the ACCESS_FINE_LOCATION permission only when you open the Charger Map screen to find nearby EV charging stations.
- Your device's precise location is sent to the Open Charge Map API (ocm.io), a free open-source global EV charging station directory. You can review their privacy policy at openchargemap.org.
- Location data is not stored by Transmission on your device or in Firebase.
- Location is not accessed in the background. It is requested only when the Charger Map screen is active.
- If you deny this permission, the Charger Map feature will be unavailable; all other app features continue to work normally.
Transmission requests BLUETOOTH_SCAN and BLUETOOTH_CONNECT permissions to discover and connect to ELM327 OBD-II Bluetooth adapters for live vehicle diagnostics.
- The device name and MAC address of your paired OBD adapter are stored locally in the app's SharedPreferences so the app can reconnect automatically on next launch.
- No Bluetooth data (device name, MAC address, OBD-II readings) is transmitted to Transmission's servers or any third party.
- OBD-II data (vehicle speed, RPM, fault codes, etc.) is processed on-device and stored only in the app's local database.
- If you deny Bluetooth permissions, OBD-II features will be unavailable; all other app features continue to work normally.
Transmission may send local push notifications for:
- Mileage anomaly alerts (e.g., unusually high or low reported consumption).
- Upcoming maintenance reminders.
All notifications are generated and delivered entirely on-device. No notification content is sent to any external server. You can disable notifications at any time in your phone's system settings or via Settings → Notifications inside the app.
The following third-party services are used by Transmission. Each service's own privacy policy governs the data it receives.
| Service | Purpose | Data sent | Link |
|---|---|---|---|
| Google Firebase Auth | Optional sign-in identity for cloud backup | Email address, Google UID | Google Privacy Policy |
| Cloud Firestore | Encrypted cloud backup of vehicle logs | Encrypted log data | Google Privacy Policy |
| Firebase Storage | Receipt photo cloud backup | Compressed JPEG photos | Google Privacy Policy |
| Google ML Kit | On-device receipt OCR | None — runs entirely on-device | Google Privacy Policy |
| Open Charge Map API | Finding nearby EV charging stations | Your device location (foreground only) | openchargemap.org |
No analytics, advertising, or crash-reporting SDKs are included.
Transmission includes an optional cloud backup and multi-device sync feature powered by Google Firebase (Spark free tier). This feature is off by default and requires your explicit opt-in.
| Data | How it's stored |
|---|---|
| Google account email and display name | Used to identify your backup; stored by Firebase Auth |
| Vehicle logs, maintenance logs, payment method labels | Uploaded to Firestore, encrypted on-device before upload |
| Receipt photos | Uploaded to Firebase Storage (JPEG, ≤5 MB per file) |
Sensitive text fields — station names, notes, payment method labels — are encrypted on your device using AES-256-GCM before being sent to Firestore. The encryption key is derived from your Google UID and a per-install random salt stored in your device's EncryptedSharedPreferences. We cannot decrypt your data.
Sign-in is via Google Sign-In only. Transmission requests your email and a sign-in token; it does not access your contacts, calendar, or any other Google account data.
- Firebase Authentication — Google sign-in identity
- Cloud Firestore — encrypted structured data storage
- Firebase Storage — receipt photo storage
- Firebase App Check (Play Integrity) — prevents abuse of backend services
All Firebase services are subject to Google's Privacy Policy.
- Disable sync at any time — Settings → Cloud Sync → toggle off. Your local data is unaffected.
- Delete cloud data — Settings → Account → Sign Out. All your Firestore documents are scheduled for deletion within 24 hours via a TTL policy.
- Export — use the in-app export feature to download a ZIP of your logs and photos.
Transmission is not directed at children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect data from children.
Because your data is stored on your device, you are in direct control of it:
- Access — every log entry is visible in the app.
- Export — use the in-app export feature to download a CSV of your logs at any time.
- Edit / delete — every entry can be edited or deleted from its detail screen.
- Wipe — uninstalling the app or using your phone's "Clear data" option removes all locally stored Transmission data.
If you enable the future cloud feature, you will additionally be able to request export and deletion of any cloud-stored copies from within the app.
- Data is stored in the application-private sandbox provided by the operating system (Android internal storage / iOS app container), which is not readable by other apps on a non-rooted/non-jailbroken device.
- Photos are compressed and stripped of EXIF location metadata before being saved.
- Future cloud backups will be end-to-end encrypted; encryption keys never leave your device.
No system is perfectly secure, but we minimize risk by collecting as little as possible and keeping it on-device.
We may update this policy as the app evolves. When we do:
- The version number and effective date at the top will change.
- Material changes (for example, introducing any new data collection) will be announced inside the app on next launch and will require your acknowledgement before the relevant feature is enabled.
For privacy questions, requests, or concerns, contact:
Email: sharukh7srk@gmail.com
End of policy.