Privacy

utvtron keeps ride data on your phone by default.

What we store

Sessions, preferences, and optional notes live in this browser's local storage first, always. If you sign in with Google, garage vehicles (names, probe labels, alert thresholds) and finished rides (temp readings, GPS route, impacts) sync to the same Firebase account wrenchtron uses. Recording itself never depends on a connection.. a ride only uploads once you stop it, and stays local if you're offline until the connection comes back. Maintenance history is logged and stored in wrenchtron, not utvtron.

Sensors

Bluetooth is used only to talk to a temperature probe you choose to connect. Location and motion are requested so a ride can log route, speed, and impacts. They are not used when you are not recording.

Map tiles

Viewing a ride with a GPS track loads map imagery from OpenStreetMap / CARTO for that area. Those tile requests go to those providers (they can see the map region, not your session file). Ride recordings stay on this device.

What leaves the device

Nothing is uploaded to utvtron servers — there aren't any for your ride data. If you use Share, the system share sheet may send a generated image to an app you pick. CSV and backup exports only go where you save or send them.

Hosting

The app itself may be served from a static host (for example Vercel). That delivery layer can see normal web request logs (IP, user agent) like any website. It does not receive your session recordings.

Contact

Questions: hello@swantron.com · swantron.com

Last updated August 2026.