# Privacy

SEAL APEX has no account, no cloud backend, no analytics and no advertising SDK. Android backup is disabled
(`allowBackup=false` plus data-extraction rules that exclude everything), so settings, addresses and trip history are never copied to a cloud backup.

| Data | Where it goes | Why |
|---|---|---|
| Vehicle signals (speed, SoC, tyres, climate…) | Stays on the head unit | Dashboard, trip statistics |
| Trip and charging history | App-private storage on the head unit (last 30 drives, 12 charges) | Energy screens |
| Location | Rounded to ~1 km for Open-Meteo (weather); precise position to the Overpass API (needed to match the road for speed limits and cameras, only when a live source is active); map tiles from Esri reveal the viewed area | Weather, speed limits, map |
| Notifications from navigation apps | Read in memory to extract the next turn; not stored | HUD and home screen |
| Media metadata | Read in memory from the active MediaSession; not stored | Media card |
| Diagnostics report | Written only when you tap Export, to `Download/SealApex/` | Compatibility checks |
| ADB key (one-tap setup) | App-private storage | Self-connection to the head unit's own ADB |

The diagnostics report masks the VIN (manufacturer prefix + last four characters) and contains no location, account
names, IMEI, phone numbers or Wi-Fi names. The in-app event log never records VIN, location or account data.

No hidden recording: SEAL APEX does not access cameras or microphones.

Network requests use HTTPS and carry a generic `SEAL-APEX/1.0` user agent. Uninstalling the app removes all of its
data.