OBD Analyst
Privacy Policy
Effective 13 September 2026 · Last updated 13 September 2026
OBD Analyst Scan Tool does not collect any data.
The app makes no network requests of any kind. There are no servers, no accounts, no analytics, no advertising and no tracking. Everything it records stays in a database on your device and goes nowhere unless you choose to export it yourself.
What the app stores, and where
OBD Analyst records engine data read from your vehicle's OBD-II port, together with readings from your phone's own sensors. All of it is written to local storage on your device. None of it is transmitted.
- Recorded drives and their measurements
- Diagnostic results calculated from those recordings
- Your settings, including the tyre size you have entered
- A diagnostic log of the raw communication with the adapter
Permissions, and why each one is asked for
Bluetooth
Used to read engine data from an ELM327-compatible OBD-II adapter. The app is strictly read-only: it never writes to the vehicle, cannot clear fault codes, and cannot send any command that changes how the car behaves. OBD-II Mode 04, the clear-codes command, is blocked in the source code.
Location
Used to add speed, altitude and road gradient to a recording. The 0–100 km/h time, the grade-corrected power estimate and the speedometer error all depend on it. Location continues in the background only while a recording is running, so that checking a map mid-drive does not interrupt it. It is written to the local database and nowhere else.
Microphone
Used only to measure sound level in decibels. Any temporary audio file created during a measurement is deleted the moment the measurement ends. No audio is stored, played back, listened to, or transmitted.
Motion and fitness
Used to add acceleration and braking intensity to a recording. It is written to the local database and nowhere else.
Sharing and export
You can export a recording as a CSV file or as an HTML report, and you can share the diagnostic log. This only ever happens when you ask for it, and the destination is entirely your choice — the app hands the file to iOS and takes no further part in it. OBD Analyst never uploads anything on its own.
Third parties
There are none. No analytics provider, no crash reporting service, no advertising network, no content delivery network, no remote fonts. Nothing in the app contacts any server.
Crash information, when the app records it, is written to a local file so you can read it and choose whether to share it. It is not sent anywhere automatically.
Children
OBD Analyst is a diagnostic tool for vehicles and is not directed at children. It collects no data from anyone, including children.
Deleting your data
Deleting individual recordings inside the app removes them from the device. Deleting the app removes everything it has stored. Because nothing was ever sent anywhere, there is no copy elsewhere for us to delete and no request you need to make.
Your rights
Data protection law — the GDPR and the KVKK among others — gives you rights of access, correction, deletion and portability over personal data held about you. OBD Analyst holds none: it collects no personal data and operates no service that could hold it. The data on your device is already wholly in your possession, readable by you, exportable by you, and deletable by you.
Changes to this policy
If this policy changes, the revised version will be published at this address with an updated date at the top. Since the app collects no data, any change would be a clarification rather than a change in what happens to information about you.
Contact
Questions about this policy, or about the app: alperunlu.github.io/OBDanalyst/issues