RevScan
OBD-II Diagnostics

Privacy Policy

Effective 21 August 2026 Version 1.0 Applies to com.revscan.app

RevScan reads diagnostic data from your vehicle and shows it to you. It has no servers, no accounts and no analytics. Everything the app records stays on your phone unless you deliberately export or share it.

Stays on your device

  • Vehicle profiles, including a VIN if you enter or read one
  • Live and logged sensor readings
  • Trip logs with GPS coordinates, if you record trips
  • Fault codes, freeze frames and their history
  • Adapter names and addresses you have connected to
  • Dashboards, gauges, custom PIDs, alarms and settings

Never happens

  • No account, sign-in or email address
  • No analytics, crash reporting or advertising SDK
  • No transmission of your data to us or any third party
  • No selling or sharing of data, for any purpose
  • No tracking across apps, sites or devices
  • No background collection when you are not using the app

01 Who this policy is from

RevScan ("the app") is developed and published by Aftab Anwar ("we", "us"), an independent developer. This policy explains what the app does with information on your device. It covers the Android app distributed on Google Play under the package name com.revscan.app, and nothing else.

Because the app has no backend, we do not receive, hold or have any means of accessing your data. The only information we ever see is what you choose to send us yourself — for example, a log attached to a support email.

02 Information the app processes

Vehicle diagnostic data

When you connect an OBD-II adapter, the app requests standard and manufacturer-specific parameters from your vehicle's control units: engine speed, road speed, temperatures, fuel and air measurements, battery and motor data on electric vehicles, diagnostic trouble codes, freeze frames and readiness monitors. If your vehicle reports a Vehicle Identification Number (VIN), or you type one into a vehicle profile, it is stored in the app's local database.

Location

Location is used for one feature: trip recording. While a trip is being recorded, the app samples GPS latitude, longitude, altitude and satellite speed and stores them alongside the vehicle readings so a trip can be drawn on a route sketch and exported as a GPX file. Recording only runs when you start it, and a persistent notification is shown for as long as it does.

On Android 11 and below, the operating system also requires location permission before any app is allowed to scan for Bluetooth devices. That is a platform requirement, not something the app uses your position for.

Bluetooth and Wi-Fi adapters

To find and connect to an OBD adapter, the app lists nearby Bluetooth Classic and Bluetooth Low Energy devices, which means it briefly sees the names and hardware addresses of other Bluetooth devices in range. Only adapters you actually connect to are saved, so that reconnecting is one tap. Discovery results for everything else are discarded when the scan ends.

App configuration

Dashboard layouts, gauge choices, custom PID definitions, alarm thresholds, unit preferences and theme settings are stored locally so the app looks the same next time you open it.

The app does not collect names, email addresses, phone numbers, contacts, photos, calendars, microphone or camera input, installed-app lists, or any advertising or device identifier.

03 Permissions, and why each one exists

Permission Why RevScan asks for it Leaves device
BLUETOOTH_SCAN
BLUETOOTH_CONNECT
Discover nearby OBD adapters and open a serial link to the one you pick. On Android 11 and below the older BLUETOOTH and BLUETOOTH_ADMIN permissions do the same job. No
ACCESS_FINE_LOCATION
ACCESS_COARSE_LOCATION
GPS tagging for trip recording, and the Bluetooth scanning requirement imposed by Android 11 and below. Declined permission disables trip GPS; every other feature still works. No
INTERNET
ACCESS_WIFI_STATE
ACCESS_NETWORK_STATE
Wi-Fi ELM327 adapters expose a plain TCP socket on their own access point, usually at 192.168.0.10. The app opens a socket to the address you configure. It contacts no server, on the internet or otherwise. No
FOREGROUND_SERVICE
…_CONNECTED_DEVICE
…_LOCATION
Keep the adapter link and trip logging alive while the screen is off or another app is in front. Runs only during an active session and always with a visible notification. No
POST_NOTIFICATIONS Show the logging notification and any alarm you have configured, such as a coolant temperature threshold. No
WAKE_LOCK Stop the device sleeping mid-drive while a dashboard or a recording is live. No

Every permission is used only for the feature named. None of them cause data to be sent anywhere.

04 Where the data is kept

All records live in a private SQLite database and preference store inside the app's own storage area, which Android isolates from other apps. Exports you create — CSV and GPX trip files — are written to the app's dedicated folder in external storage, where a file manager can reach them so you can move or share them yourself.

Nothing is uploaded. The app makes no outbound network request other than the local TCP connection to a Wi-Fi OBD adapter you have configured.

Android backup

RevScan participates in Android's standard backup system, so the database and settings can be restored when you set up a new phone. This means a copy may be held in your own Google account backup, or transferred directly to your new device, under Google's terms and encrypted with your device credentials. Because trip records can include GPS coordinates, they are included in that copy. You can turn this off at any time in Android Settings → Google → Backup, or by disabling backup for RevScan specifically. We never have access to those backups.

05 How long it is kept, and deleting it

Data is kept until you delete it. There is no expiry and no automatic upload before deletion, because there is nowhere for it to go.

06 Sharing with others

There is no automatic sharing. If you export a trip and send the file to a mechanic, a forum or a cloud drive, that transfer is yours and this policy stops at the point the file leaves the app. Exported CSV and GPX files can contain precise GPS coordinates and, therefore, where you have been — worth a glance before you post one publicly.

We disclose information to no one. The only circumstance in which we could produce your data is one that cannot arise, since we never hold it.

07 Third-party components

RevScan is built with Google's AndroidX and Jetpack Compose libraries and the Kotlin standard library. These are compiled into the app and do not phone home. The app bundles no advertising network, no analytics SDK, no crash reporter, no social login and no tag manager.

Google Play itself collects information about installs, updates and crashes under Google's own privacy policy. That is a function of the store, not of the app, and we receive only aggregate, anonymous statistics from the Play Console.

08 Security

Data is protected by Android's application sandbox and by your device's own encryption, which is on by default on modern Android versions. Keeping a screen lock enabled is the single most effective thing you can do to protect what the app has recorded.

The link between the app and an OBD adapter is a Bluetooth or local Wi-Fi connection defined by the adapter, not by us. Inexpensive ELM327 adapters commonly ship with a fixed PIN or an open Wi-Fi access point and offer no meaningful transport security. Anyone within radio range of such an adapter can potentially talk to it, whether or not this app is installed. Unplug the adapter when you are not using it.

09 Children

RevScan is a vehicle maintenance tool intended for adults and is not directed at children. It collects no personal information from anyone, and therefore none from children under 13, or under the age of digital consent in your jurisdiction.

10 Your rights

Privacy laws including the GDPR, the UK GDPR, the CCPA/CPRA and India's DPDP Act give you rights to access, correct, export and erase personal data held about you, and to object to its sale or sharing.

Those rights are satisfied directly and immediately in the app: the data is on your device, you can read all of it in the app, edit it, export it as CSV or GPX, and delete any part or all of it. We hold no copy to produce, correct or erase, and we have never sold or shared personal information, so there is nothing to opt out of. If you would like this confirmed in writing, ask us at the address below.

11 Changes to this policy

If a future version of RevScan handles data differently, this page will be updated before that version is released and the effective date at the top will change. A change that would meaningfully expand what the app collects will also be announced in the app's release notes on Google Play. The current version of this policy is always the one published at this address.

A Appendix — Google Play Data safety

For transparency, this is how RevScan is declared in the Data safety section of its Play Store listing.

Data type Collected Shared Notes
Location (approximate and precise) Not collected Not shared Accessed on device for trip recording. Never leaves the device, so it is not "collected" as Play defines the term.
Personal info, contacts, messages, photos, audio Not collected Not shared Never accessed.
App activity and diagnostics Not collected Not shared No analytics or crash-reporting SDK is present.
Device or other identifiers Not collected Not shared Bluetooth adapter addresses you connect to are stored locally and never transmitted.
Files created by you (CSV, GPX exports) Not collected Not shared Written to the app's own folder. Any onward sharing is an action you take.

Play treats data as “collected” only when it is transferred off the device. RevScan transfers none.

Data is encrypted in transit where transit exists: the only connection the app makes is to your OBD adapter, whose security is a property of that adapter. Deletion is available in the app, as described in section 5.