Privacy Policy and Terms of Service
Effective Date: October 19, 2026 | Version: 2.4
1. Overview and Core Principles
This Privacy Policy applies to the software application «Prometrius Link: OBD2» (also known as PL.OBD2 or Prometrius OBD2), developed by Prometrius Lab (Official IP registration filing No. 2026607449).
Prometrius Link: OBD2 is built on a Local-First Architecture. We do not operate remote telemetry tracking servers. We do not collect, transmit, sell, or monetize any personal data, driving behavior, or vehicle diagnostic metrics.
2. Vehicle Diagnostic Data and VIN Processing
The application interfaces with your vehicle's Electronic Control Units (ECUs) exclusively through user-connected diagnostic hardware (ELM327 or compatible):
- De-identified Vehicle Model Descriptor (WMI + VDS): In compliance with data minimization principles and privacy regulations, the app does not store or transmit the unique vehicle serial number (VIS). From the Mode 09 PID 02 response, only the first 9 characters of the VIN are extracted — comprising the WMI (World Manufacturer Identifier, 3 characters) and VDS (Vehicle Descriptor Section, 6 characters representing body, engine, and transmission variants). The remaining 8 characters containing the individual chassis serial number (VIS) are discarded in memory. These 9 characters represent a non-identifying technical model descriptor and cannot be used to trace a specific vehicle owner.
- Strict Local Storage: Telemetry streams, generated device passports, and communication logs are saved exclusively within the app's sandboxed private storage (
filesDir). All data is permanently destroyed when the user uninstalls the app. File sharing is executed exclusively upon direct user action via the Android Storage Access Framework (SAF) or FileProvider.
3. Explicit Disclosure of Android System Permissions
In accordance with Google Play Developer Policies, here is an explicit justification for each sensitive permission declared in our manifest:
- BLUETOOTH_SCAN (with
android:usesPermissionFlags="neverForLocation") & BLUETOOTH_CONNECT — Required on Android 12+ (API 31+) to discover and establish RFCOMM/GATT connections with ELM327 adapters. TheneverForLocationflag explicitly asserts that Bluetooth hardware scan results are never used to determine physical geographic location. - ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION — Used strictly for: 1) legacy Bluetooth scanning on Android 9–11; 2) reading the hardware MAC address (BSSID) of connected ELM327 Wi-Fi access points on Android 10+. Because standard Wi-Fi adapters share identical factory IP addresses (192.168.0.10:35000), BSSID verification is mathematically required to avoid corrupting vehicle calibration passports. The app never reads, logs, or tracks GPS coordinates.
- FOREGROUND_SERVICE & FOREGROUND_SERVICE_CONNECTED_DEVICE — Required to sustain unbroken real-time serial communication with the vehicle ECU when the app is in the background or when the head unit display turns off.
- WAKE_LOCK — Prevents the mobile CPU from entering low-power sleep mode during high-speed active diagnostic streaming.
- INTERNET — Operates the internal loopback HTTP/WebSocket server (
127.0.0.1) and powers local TCP/UDP streaming to in-car dash displays or private VPN tunnels (Tailscale).
4. Hardware Cryptography and Device Identity
Upon initial launch, the app generates an asymmetric RSA-2048 keypair within the hardware-backed Android KeyStore.
The private key is non-exportable and never leaves the host device's secure hardware element. Only the public key (Public Key PEM) is exported inside the Device Passport to cryptographically sign and encrypt custom polling plans (.plp), ensuring custom plans can only be decrypted and executed by that specific hardware device.
5. Automotive Safety Disclaimer & Limitation of Liability
The application is provided on an "AS IS" and "AS AVAILABLE" basis without warranties of any kind. Interfacing with a vehicle's On-Board Diagnostics (OBD-II) port involves communicating with critical vehicular networks (CAN bus).
Under no circumstances shall Prometrius Lab or its contributors be held liable for any direct, indirect, incidental, or consequential damages, including but not limited to ECU faults, engine/transmission damage, vehicular accidents, personal injury, or traffic violations resulting from the use or misuse of this software.
6. Developer Contact Information
For inquiries, data questions, or support regarding Prometrius Link: OBD2, please contact:
Email: support@prometrius.com
Website: https://prometrius.com