Privacy
Your data stays on your device. Below is the full breakdown of what the app collects, what goes where, and what we don't touch.
What stays on your device
The following is stored locally and never leaves your phone unless you explicitly export or share it:
- Trip recordings: GPS tracks and OBD telemetry (speed, temps, boost, etc.) captured while a trip is active
- Build log: parts, install notes, and photos you add to your vehicle profile
- Vehicle information: name, model year, color, and VIN (read from your truck's OBD port)
- Backups: parameter snapshots taken before a mod is applied
- App preferences: theme, units, alert cooldown settings
What leaves your device
Crash reports
When the app crashes, an anonymous crash report is sent to Sentry (sentry.io). The report contains:
- Stack trace (the code path that caused the crash)
- Device model and iOS version
- App version and build number
- BLE connection state at the time of the crash (connected or disconnected)
- Truck generation (e.g. Gen 3)
Never included: your identity, VIN, OBD sensor readings, GPS coordinates, trip data, or anything that could identify you. See Sentry's privacy policy for details.
Usage analytics
The app sends a small set of anonymous usage events to PostHog (posthog.com) so a solo developer can tell whether core features actually work in the field. Each install is identified only by a randomly generated ID stored on your device. It is never linked to your Apple ID, your Apple device identifier (IDFV/IDFA), your name, or any personal identifier, and no user profiles are built.
The complete list of events, and the only event-specific data attached to each:
| Event | Sent when | Data attached |
|---|---|---|
app_opened |
The app launches | App version, cold-start flag |
ble_connected |
An OBD adapter connects | Adapter type (real vs. demo) |
ble_connection_failed |
An adapter fails to connect | Error code (e.g. timeout) |
trip_started |
You start recording a trip | Nothing |
trip_stopped |
You stop a trip | Trip length in seconds, and whether OBD data and GPS data were captured (yes/no only) |
mod_applied |
A module change is written | Nothing (never the specific mod or the value written) |
tip_completed |
You leave a tip | Nothing |
tip_restored |
You restore a past purchase | Nothing |
carplay_session_started |
CarPlay connects | Nothing |
Every event also carries a small, non-identifying technical context so the developer can tell which devices a problem affects. This is the same information already sent with crash reports: your device model and manufacturer, iOS version, app version and build, and screen size, along with the analytics SDK version and the anonymous ID above. IP-based location lookup is turned off.
Never logged: your identity, your Apple device identifier (IDFV/IDFA), your VIN, raw OBD sensor readings, GPS coordinates, trip routes, or the specific mods you apply.
See PostHog's privacy policy for how they handle event data.
In-app purchase
Purchase and entitlement status is verified through RevenueCat. RevenueCat receives your App Store receipt and entitlement status. See RevenueCat's privacy policy for details.
Product links
The Build tab contains Amazon product links. These include an Associates referral tag
(chasebaja-20), which means a small commission may apply on qualifying purchases.
A disclosure is shown on screen when these links are present. Amazon's
privacy policy
applies once you leave the app.
Permissions
| Permission | Why |
|---|---|
| Bluetooth | To discover and connect to your OBD-II adapter |
| Location (foreground) | To record a GPS track when you start a trip |
| Location (background) | To continue recording if you switch apps mid-trip |
| Photos / Camera | To add photos to your build log and save build posters to your photo library |
Location is only used during active trip recording. The app does not track your location outside of a trip.
What we don't do
- No advertising networks or ad SDKs
- No advertising or marketing analytics, no user profiling, no session recording — only the anonymous usage counts listed above
- No user accounts or sign-in
- No sale of your data to any third party
- No cross-app or cross-device tracking
Children
Chase Baja is not directed at anyone under 13 and does not knowingly collect data from them.
Changes
Material changes get a new date at the top. Continued use counts as acceptance.
Questions? Open a support request