DriveSense reads telemetry on-device. Nothing about your vehicle or your driving is sold, shared, or uploaded to us — and this page lists exactly what does leave your phone.
DriveSense (“the app”) is developed and operated by Yusuf Güzel, an independent developer based in Türkiye, acting as the data controller for the limited processing described below. You can reach us at any time at guzelyusuf10@gmail.com.
This policy explains what DriveSense reads from your vehicle, what stays on your device, and the small set of technical data that is sent to third-party service providers so the app can run, be fixed when it breaks, and process subscriptions.
When you connect an ELM327-compatible OBD2 adapter, DriveSense reads standard diagnostic parameters that your vehicle's ECU exposes — for example engine RPM, vehicle speed, coolant and intake temperature, engine load, battery voltage, throttle position, fuel rate and level, oxygen sensor and fuel trim values, diagnostic trouble codes (DTCs), and the vehicle identification number (VIN) and ECU identifiers your vehicle reports.
All of this is processed and stored only on your iPhone. Your vehicle garage, trip sessions, health scores, alert history and calibration profiles are written to the app's local storage on the device. DriveSense has no user accounts, no backend server of its own, and no cloud sync — none of this information is transmitted to us or to any third party.
If you export a session as a CSV file, the file is created on your device and you choose where it goes through the standard iOS share sheet. Once you share it, that destination's own privacy terms apply.
To operate the app we rely on a small number of established service providers. This is the complete list:
| Service | What it receives | Why |
|---|---|---|
| Firebase Analytics |
Which screens are opened and basic app events, plus device model, iOS version, language, region and a Google-generated app instance identifier. | To understand which features are actually used, in aggregate. |
| Firebase Crashlytics |
Only when the app crashes or hits an error: the stack trace, device model, iOS and app version, and recent in-app diagnostic log lines. | To find and fix bugs. |
| Firebase Cloud Messaging |
A device push token, only if you allow notifications. | To deliver notifications you have opted into. |
| RevenueCat | An anonymous app user identifier and your subscription status and transaction receipts from Apple. | To know whether your DriveSense Pro subscription is active, and to restore purchases. |
| Apple | Your purchase, handled entirely inside the App Store. | To take payment and manage the subscription. |
None of these services receive your OBD2 readings, your VIN, your trip history or anything else about your vehicle. Payments are processed by Apple — we never see or receive your card details.
Each provider processes this data under its own terms: Firebase privacy and RevenueCat privacy.
Used solely to discover and communicate with your OBD2 adapter. DriveSense does not use Bluetooth for tracking, proximity beacons or advertising.
Used to deliver alerts you have enabled. You can decline or revoke this at any time in iOS Settings without affecting diagnostics.
DriveSense does not request location access on iOS and does not collect your location. Speed, distance and trip data are derived from the OBD2 port, not from GPS.
Data stored on your device stays there until you remove it. You can delete individual trip sessions or a whole vehicle inside the app, and deleting the app removes all of its local data from your iPhone.
Analytics and crash data held by Google are retained according to Firebase's standard retention periods — crash reports for roughly 90 days, analytics event data for up to 14 months. Subscription records held by RevenueCat and Apple are kept as long as needed for billing, support and legal obligations.
Depending on where you live — including under the GDPR in the EU/UK, the KVKK in Türkiye, and the CCPA/CPRA in California — you have the right to request access to, correction of, deletion of, or a copy of the personal data we hold, to object to or restrict certain processing, and to lodge a complaint with your local data protection authority.
In practice, most DriveSense data never reaches us, so the fastest route is your own device: delete sessions in the app or uninstall it. For the analytics, crash and subscription data described above, email guzelyusuf10@gmail.com and we will action your request, normally within 30 days. We do not sell personal information, so there is nothing to opt out of under the CCPA's “Do Not Sell” right.
DriveSense is a vehicle diagnostic tool intended for licensed drivers and vehicle owners. It is not directed at children under 13, and we do not knowingly collect personal data from them. If you believe a child has provided us with data, contact us and we will delete it.
The service providers listed above operate globally, so the limited technical data described here may be processed on servers outside your country, including in the United States. Those transfers rely on the safeguards each provider maintains, such as the European Commission's Standard Contractual Clauses.
If we change how DriveSense handles data, we will update this page and revise the date below. Material changes will also be noted in the app's release notes. Continuing to use DriveSense after an update means you accept the revised policy.