Privacy Policy — Lap Vision

Last updated: 2026-05-20

Lap Vision is a track-day telemetry app developed by EtunersKZ. This Privacy Policy describes what data the app collects, how it is used, and what control users have over it.

1. Data we collect

• GPS location (latitude, longitude, altitude, speed, bearing, accuracy) — used to record lap timing, vehicle trajectory, and analytical metrics during a recording session. Collected while a session is active. To prevent loss of lap data when the screen is off or another app comes to the foreground (e.g., music control, incoming call), GPS recording continues in the background for the duration of the active session. Background collection stops automatically when the user ends the session. Outside of an active session, the app does not collect location.
• Accelerometer and gyroscope data from the device IMU — used to derive G-force, vehicle dynamics, and analytical insights for the recorded lap.
• Bluetooth scan results and device identifiers — used solely to discover and connect to compatible external devices: GPS receivers (Dragy DRG70, RaceBox) and the optional LapVision-CAN adapter (ESP32). Bluetooth scanning is not used to derive user location for any other purpose. The neverForLocation flag is set in our Android manifest.
• Vehicle CAN-bus telemetry (optional, only if the user connects the LapVision-CAN adapter) — engine RPM, throttle position, boost pressure, coolant temperature, transmission state, brake pressure, and similar engine/drivetrain channels read from the vehicle's diagnostic CAN bus. Used to overlay engine data on lap analysis. Diagnostic Trouble Codes (DTCs) read by the user through the Diagnostics module are also processed only on the device.
• Optional driver profile — name and photo, stored locally only if the user enters them. Used to display the user's identity in replay screens and exports.
• Session metadata — start time, lap times, sector times, track name, and other recorded telemetry.

2. How data is stored

All data is stored locally on the user's device in a SQLite database and shared_preferences storage. Lap Vision does not transmit user data to any remote servers operated by us. There is no cloud sync, no analytics, no advertising SDK, and no third-party data sharing.

3. Network usage

The app communicates with the following third-party services for map rendering only:

• Google Static Map tiles (mt0–mt3.google.com) — for satellite imagery in the 3D Replay view. Standard HTTP request includes the user's IP address as required by the protocol. No additional user data is sent.
• OpenStreetMap, Esri ArcGIS World Imagery — alternative tile sources, used when the user explicitly switches to them.

Tile requests follow standard map-tile protocols and do not include identifying telemetry data.

4. Data export and sharing

The user may export sessions as CSV files (RaceChrono v3 compatible format). Exported files contain telemetry data and are saved to device storage or shared via system share sheet at the user's explicit action. The user controls whether and to whom such files are shared.

5. Permissions required

Android:

• ACCESS_FINE_LOCATION — GPS position for lap timing.
• ACCESS_BACKGROUND_LOCATION — to continue recording GPS during an active session when the screen is off or another app is in the foreground. Requested only when a session needs background access; the user can deny it and the app will work in foreground-only mode.
• BLUETOOTH_SCAN, BLUETOOTH_CONNECT — to connect to external GPS devices (Dragy, RaceBox) and the LapVision-CAN adapter. The neverForLocation flag is set in the Android manifest, so Bluetooth scan results are not used to derive user location.
• WAKE_LOCK — to keep the screen on during recording.
• INTERNET — to load map tiles.

iOS:

• NSLocationWhenInUseUsageDescription — GPS position for lap timing while the app is in use.
• NSLocationAlwaysAndWhenInUseUsageDescription — to continue recording GPS during an active session when the screen is off or another app is in the foreground. The app does not collect location outside of an active session.
• NSBluetoothAlwaysUsageDescription — to connect to external GPS devices and the LapVision-CAN adapter.
• NSMotionUsageDescription — accelerometer and gyroscope for vehicle dynamics.
• NSPhotoLibraryUsageDescription / NSPhotoLibraryAddUsageDescription — to pick a car photo for the share card and to save generated share cards.
• NSCameraUsageDescription — to take a photo of the user's car for the share card, when chosen by the user.

Background location is used exclusively during an active recording session and stops when the user ends the session. The app does not track location for any other purpose.

6. Children's privacy

Lap Vision is intended for adult motorsport enthusiasts. The app does not knowingly collect data from children under 13.

7. User control

Users can delete recorded sessions at any time from the Sessions screen. Uninstalling the app removes all locally stored data. Driver profile (name, photo) can be removed in Settings.

8. Changes to this policy

If we change this Privacy Policy, we will update the "Last updated" date above and notify users via an in-app message before the change takes effect.

9. Contact

Questions or concerns about this Privacy Policy: vwclubkz@gmail.com