Privacy Policy

DISI Dash

Last Updated: September 10, 2026

Introduction

Thank you for choosing DISI Dash. We are fully committed to protecting your privacy. This Privacy Policy explains how DISI Dash handles data, device permissions, and system interactions on Android phones and automotive head-units.

DISI Dash is a dedicated digital cockpit, telemetry oscilloscope, datalogger, and diagnostic scanner engineered specifically for vehicles powered by the Mazda MZR 2.3 DISI Turbo engine (Mazdaspeed 3 / MPS, Mazdaspeed 6 / MPS, and Mazda CX-7).

Data Safety & Zero Data Collection

We do not collect, store on remote servers, monitor, share, or sell any personal information, driving habits, location coordinates, or vehicle telemetry.

DISI Dash is an offline-first application. The application does not declare or request the Android Internet permission (android.permission.INTERNET). As a result, it is technically impossible for the application to transmit any data over the internet or communicate with external servers.

All diagnostic queries, sensor decodings, PID formulas, Big MAF calibrations, and DTC lookups are executed completely on-device in local memory.

Requested Android Permissions

DISI Dash strictly adheres to the principle of least privilege. We only request permissions necessary to communicate with your vehicle's OBD-II adapter and deliver automotive cockpit features:

  • Bluetooth & Nearby Devices (BLUETOOTH_SCAN, BLUETOOTH_CONNECT, BLUETOOTH, BLUETOOTH_ADMIN): Used solely to scan for, pair with, and maintain a high-speed serial data link to your wireless ELM327, OBDLink (LX/MX/MX+), or vLinker OBD-II adapter. On Android 12+ (API 31+), BLUETOOTH_SCAN includes the neverForLocation flag, guaranteeing to the Android operating system that Bluetooth is never used to derive your physical location.
  • Legacy Location Access (ACCESS_FINE_LOCATION — Android 11 and below only): On Android versions prior to API 31, Android system architecture required location permission to discover nearby Bluetooth devices. DISI Dash uses this legacy permission exclusively for OBD-II adapter discovery on older OS versions; the app never reads, tracks, or records GPS or location data.
  • USB Host (android.hardware.usb.host): Permits connecting to wired USB OBD-II adapters (such as FTDI, Prolific, or CH340 based ELM/OBDLink adapters via USB OTG) on Android head-units and tablets.
  • Foreground Service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_CONNECTED_DEVICE): Powers the background safety supervisor engine, which continuously monitors knock retard and HPFP fuel pressure drops even when navigation apps (e.g. Google Maps, Waze) are in the foreground.
  • Notifications (POST_NOTIFICATIONS): Required on Android 13+ (API 33+) to display the persistent status notification while the foreground safety monitoring service is actively connected to the vehicle.
  • Screen Keep Awake (WAKE_LOCK): Prevents the screen from turning off or sleeping while the cockpit dashboard is actively running on your dashboard or windshield mount.
  • Auto-Launch on Boot (RECEIVE_BOOT_COMPLETED): An optional setting designed for dedicated in-dash Android head-units that automatically launches DISI Dash when the vehicle ignition powers on.

Local Datalogging & File Sharing

DISI Dash includes high-speed WOT pull recording and datalogging capabilities. When you record a pull or datalog:

  • Logs are saved exclusively to local, private application storage on your device in standard CSV format (compatible with Virtual Dyno and MegalogViewer).
  • Logs remain private and inaccessible to other applications unless you explicitly tap "Share CSV" to send the datalog file through the standard Android system share sheet (e.g. via email, cloud drive, or messaging).
  • DISI Dash uses a secure Android FileProvider (com.smartpickle.disidash.fileprovider) with strictly transient, read-only permissions during user-initiated sharing.

Third-Party SDKs & Trackers

DISI Dash contains zero third-party trackers, advertising frameworks, analytical SDKs, or cloud telemetry libraries. We do not use Google Firebase Analytics, Facebook SDK, Crashlytics, or any ad networks. Your driving and vehicle diagnostic experience remains completely private.

Diagnostic & Automotive Safety Disclaimer

DISI Dash queries real-time diagnostic parameters and trouble codes (DTCs) via standard SAE J1979 OBD-II and Mazda CAN protocols. DISI Dash is a passive monitoring, logging, and diagnostic tool: it does not remap, flash, or modify engine calibration maps within your vehicle's Powertrain Control Module (PCM).

Drivers and tuners are solely responsible for ensuring safe vehicle operation, obeying local traffic and motor vehicle regulations, and mounting display devices securely without obstructing visibility.

Changes to this Policy

We may update this Privacy Policy to reflect future features or regulatory requirements. Updates will be published directly on this page and noted in release announcements. Continued use of the application after revisions indicates agreement with the updated terms.

Contact Us

If you have questions, feedback, or concerns regarding our privacy practices or data handling in DISI Dash, please reach out via our Google Play developer profile: SmartPickle on Google Play.