Read supported OBD-II data
Connect a BLE ELM327-style adapter, view supported standard sensor values, read stored trouble codes, and inspect connection diagnostics.
OBD2 Radar brings supported live OBD-II readings together with maintenance records, EV charging history, diagnostic codes, and ownership costs in one iPhone app.
Live readings require a compatible BLE OBD-II adapter and vary by vehicle.
Use the live connection when your vehicle supports it. Keep service and cost records useful even when you are offline.
Connect a BLE ELM327-style adapter, view supported standard sensor values, read stored trouble codes, and inspect connection diagnostics.
Save vehicles, scan a VIN, log service, review estimated maintenance intervals, and export a vehicle history PDF.
Manually log charging sessions, record expenses and subscriptions, review charts, and export cost data as CSV.
OBD2 Radar asks your vehicle which standard diagnostic values it supports before showing live readings.
Use a compatible BLE OBD-II adapter in the vehicle’s diagnostic port. Classic Bluetooth and Wi-Fi adapters require different connection methods.
Put the vehicle in ignition-on or READY mode. Open the OBD2 tab, scan, and select the adapter.
Supported standard PIDs appear in the app. Generic OBD-II may not expose EV traction-battery charge, range, temperature, or State of Health.
For questions, connection problems, or privacy requests, email the support address below.
Tell us what you were trying to do and what happened.
If an adapter connects but no values appear, please include:
Please avoid sending a full VIN or personal documents unless needed to resolve your request.
The Bluetooth link may be working while the vehicle’s ECU is not responding to standard OBD-II commands. Check that the car is in READY/ignition-on mode, the adapter supports BLE ELM commands, and the Connection Diagnostics panel shows a reply.
Charging sessions in the EV tab are manually entered. Most EV traction-battery values require manufacturer-specific diagnostics and are not available through generic OBD-II.
No account is needed. Saved garage records, cost tools, and the diagnostic-code guide work locally. A compatible adapter and vehicle are needed for live readings.
This policy covers the OBD2 Radar iOS app. It does not describe any separate data practices of your WordPress host, theme, or plugins.
OBD2 Radar is designed around records kept on your device. The current app does not require an account and does not include a developer-operated cloud sync service, advertising SDK, or third-party analytics SDK.
You may enter a vehicle name, VIN, odometer, maintenance and inspection history, diagnostic codes, charging sessions, expenses, subscriptions, notes, and receipt photos. The app stores these records locally on your device using Apple’s app storage. We do not receive these in-app records through a developer-operated server in the current version.
If you choose to connect a compatible BLE OBD-II adapter, the app uses Bluetooth to discover the adapter and request supported standard diagnostic values and trouble codes. Responses are processed on your device. The app does not send these responses to us. Availability of values depends on the vehicle and adapter.
With your permission, the app can use the camera to scan a VIN or receipt and can access a photo you select for an expense record. Text recognition runs on the device using Apple frameworks. A receipt photo you attach may be saved with the local expense record. The app does not upload scans or photos to us.
The reminders feature may request notification and when-in-use location permission. In the current version, reminders are scheduled locally; the app does not send location to us or maintain a location history. You can change permissions in iOS Settings. If you add the widget, a small summary such as vehicle name, estimated oil life where applicable, inspection timing, and issue count is shared locally between the app and widget through an Apple App Group.
When you choose to export a PDF or CSV, copy diagnostics, or use the iOS share sheet, you decide where that information goes. The destination app or service may have its own privacy practices. Your device backup settings may also cause locally stored app data to be backed up by Apple; we do not operate that backup service.
If you email support@sukheshcs.com, we receive your email address and the information you include so we can respond. Please do not send sensitive vehicle or personal information unless it is necessary for your support request. Support correspondence is handled through our email service rather than through the app.
The current app does not use data for advertising tracking or sell your in-app records. Records remain on your device until you delete them where the app provides a delete control or remove the app. Device backups may remain according to your Apple settings. You can ask us about a support email or request its deletion by contacting the support address above.
If the app’s data practices change, this policy will be updated with a new date. For privacy questions, contact support@sukheshcs.com.