Short version. Tesstats has no developer operated account or analytics backend. The app connects to services you choose. Vehicle data stays on your devices and your server unless you choose to export it or use another service.
1. Who this policy covers
This policy covers the Tesstats app and this website. Tesstats is an independent application. It is not a Tesla service and it is not part of the TeslaMate project.
2. Data handled by the app
Tesstats can display data from the server that you configure. This may include vehicle status, location, trips, charging sessions, battery history, climate state, tire pressure, costs, and route context.
The app can also use device data when you allow it. This may include location, motion, Bluetooth, and notification permission. Driver Display can use iPhone location and motion for a fresher speed estimate. Optional Bluetooth mode can read supported vehicle telemetry while the display is active.
Where data is stored
- Server credentials are stored in the Apple Keychain
- Cached vehicle data and app settings are stored on your device
- Trip tags are stored on your device
- Encrypted backups are created only when you choose to create one
What the project does not collect
- No Tesstats account is created
- No advertising identifier is collected
- No analytics or tracking service is built into the app
- No vehicle history is sent to a Tesstats developer server
- No vehicle control command is sent by Tesstats
3. Data on this website
This site is a static website hosted by GitHub Pages. It does not use advertising scripts, analytics scripts, contact forms, or marketing cookies.
GitHub may process basic connection data when it serves the site. This can include an IP address, browser details, and request logs. That processing is controlled by GitHub. You can read the GitHub Privacy Statement.
4. Services you choose to use
Tesstats can connect to a TeslaMate server, an MQTT broker, TeslaMateApi, and an optional notification service. You choose and control those addresses. Their operators decide how they handle data.
If you run the optional push service, Apple Push Notification service processes a device token and notification delivery data. The operator of that push service is responsible for its setup and data handling.
Links to Tesla, TeslaMate, Apple, AltStore, and GitHub open services with their own privacy rules. Review those rules before using those services.
5. Your choices and control
You can remove saved server settings, clear app data, delete exports, revoke device permissions, and uninstall the app at any time. You can also delete data from the TeslaMate server that you operate.
Because the Tesstats project does not receive your vehicle data, the maintainers usually have no personal vehicle record to access or delete. Requests about data stored by Tesla or TeslaMate must go to the service that holds it.
6. Security
Tesstats uses encrypted MQTT connections by default. It expects HTTPS for history data unless you clearly allow local HTTP. Credentials stay in Keychain. No system can promise perfect security, so you are responsible for protecting your server, network, passwords, and backups.
7. Children
Tesstats is a vehicle data tool and is not directed to children. The project does not knowingly collect personal data from children.
8. Changes to this policy
This policy may change when the app or its data handling changes. The effective date at the top will be updated. Material changes will be described in the project release notes when practical.
9. Contact
For a privacy question about Tesstats, open an issue in the Tesstats issue tracker on GitHub. Do not include passwords, server addresses, exact vehicle locations, API keys, or other secrets.