Privacy Policy
1. Who we are
TorQ OBD Scanner ("the app", "we", "us") is developed and published by Rajkumar. You can reach us at pbraj.career85@gmail.com.
2. What permissions the app requests
Bluetooth — BLUETOOTH_CONNECT, BLUETOOTH_SCAN
Required to discover paired ELM327 OBD-II adapters and establish a serial (SPP) connection to your vehicle's ECU. The app connects only to the adapter you select. We never scan for, connect to, or transmit data about any other Bluetooth device. No Bluetooth-derived data ever leaves your device.
Location — ACCESS_FINE_LOCATION
Used in two ways:
- Bluetooth scanning (Android 6–11): Android requires location permission to scan for Bluetooth devices. We do not log or use your GPS position for this purpose.
- Trip GPS logging: When you start a trip recording with location enabled, the app reads GPS fixes and stores them locally so the trip detail screen can draw your route. We do not access location in the background unless a trip recording is actively running, and we do not transmit location data to any server.
Notifications — POST_NOTIFICATIONS (Android 13+)
Used for the recording-status notification that appears in the status bar while a trip is being recorded. This is optional — the app functions without it.
3. Data the app stores on your device
| Data type | Stored locally? | Transmitted off-device? |
|---|---|---|
| Bluetooth adapter MAC address & name | Yes — app preferences | No |
| OBD live readings (RPM, speed, etc.) | Streamed in memory only | No |
| Trip metadata (start, end, distance, speed stats) | Yes — SQLite database | No |
| GPS route points during trips | Yes — SQLite database | No |
| Diagnostic trouble code scan history | Yes — SQLite database | No |
| Vehicle profiles you create | Yes — SQLite database | No |
| Dashboard layout & app preferences | Yes — SharedPreferences | No |
| Crash reports | Not collected | No |
| Usage analytics / telemetry | Not collected | No |
| Advertising identifiers | Not used | No |
4. Third-party services and SDKs
The app does not include any third-party advertising SDK, analytics SDK, social-media SDK, or crash-reporting SDK that collects data about you. The only network-capable library bundled is OpenStreetMap tile loading via the flutter_map package, which fetches map tiles from openstreetmap.org when you view a trip route. OpenStreetMap's own privacy policy governs those tile requests (your IP address may be visible to tile servers as with any HTTPS request). No personally identifiable information is sent.
5. Data you choose to export
The app allows you to export trips as CSV or KML files via the Android share sheet. The export only happens when you explicitly tap "Export." Once the file is handed to Android's share sheet, you decide where it goes (email, cloud storage, etc.). We have no visibility into or control over those destinations.
6. Children's privacy
TorQ OBD Scanner is not directed at children under 13. We do not knowingly collect information from anyone.
7. How to delete your data
All data is stored in the app's private storage on your device. To remove it:
- All data at once: Android Settings → Apps → TorQ OBD Scanner → Storage → Clear data. This wipes the SQLite database and all preferences.
- Uninstalling the app removes all data automatically.
- Individual trips can be deleted from inside the Trips tab.
8. Security
All app data is stored in Android's app-private directory, which is not accessible to other apps. Your device's filesystem encryption (if enabled) protects data at rest. We do not transmit data, so there is no network attack surface.
9. Changes to this policy
If we make material changes, the "Last updated" date at the top of this page will change and the app's Play Store "What's new" section for the next release will note the update.
10. Contact
Questions or concerns about this privacy policy: pbraj.career85@gmail.com