Privacy Policy
Last updated: 23 August 2026
The short version: WattLoft is self-hosted software. Your car's data lives in a database on the machine of whoever runs the installation — not on our servers, because there are none. This website collects nothing beyond what serving a web page inherently requires, and the software phones no one home.
1Scope
This policy covers two different things, and keeps them separate throughout:
- The website — the pages at wattloft.com (this site).
- The software — the open-source WattLoft application people install and run on their own hardware, including the installation reachable at connect.wattloft.com.
Each installation of the software is controlled by the person who operates it (the “operator”), who acts as the data controller for everything that installation stores. The WattLoft project has no access to any installation, including its database, accounts or vehicle data.
2This website
- No analytics. No tracking scripts, advertising pixels, or fingerprinting of any kind.
- No cookies. The site sets none.
- No accounts. You can't sign up on wattloft.com itself; the “Sign in” button takes you to a software installation, covered by section 3.
- Hosting. Pages are delivered through Cloudflare's network, which processes connection metadata (IP address, user agent, requested URL) to serve and secure the site, per Cloudflare's privacy policy. We do not receive or retain these logs.
- Email. If you write to [email protected], we see your address and message, use them only to respond, and delete them when the conversation is done.
3The software
A WattLoft installation stores, in a SQLite database on the operator's machine:
Vehicle data
- Telemetry read from Tesla's Fleet API: state of charge, rated range, temperatures, tire pressures, odometer, firmware version and similar readings.
- Location data: the car's position over time, reconstructed into drives with start and end points, and charging locations.
- Charging sessions (energy, cost where Tesla reports it, place) and battery-health measurements derived from charging.
Account data
- Email address, optional display name, role, and a salted scrypt password hash — never the password itself.
- A session cookie (
ts_session) that keeps you signed in to that installation. It identifies your session only; it is not used for tracking.
Tesla credentials
- Signing in to Tesla happens on Tesla's own pages (OAuth). The software never sees a Tesla password — it stores only the tokens Tesla issues, locally, and uses them solely to read vehicle data and send the commands you ask for.
4Operators and members
If you operate an installation, you are responsible for the data it collects: who gets accounts, how long history is kept (retention is configurable and history can be wiped in Settings), and whether people whose driving is recorded know about it. In many places, recording the location of a car someone else drives requires their consent — tell the people you share cars with.
If you have an account on someone else's installation (for example a family member's), the operator controls that machine and the data on it. Account questions, exports and deletion requests go to them. For the installation at connect.wattloft.com, the operator is reachable at [email protected].
5Third parties the software talks to
- Tesla Fleet API — the source of all vehicle data and the channel for commands, under Tesla's terms and privacy notices. The operator's own developer credentials are used.
- Cloudflare Tunnel — carries encrypted traffic between browsers and the installation, so no router ports are opened.
- Map tiles (OpenStreetMap-based providers) — map imagery for drives and charging locations. Tiles are requested by the installation's server and cached there, so your browser never contacts the tile provider directly.
- Nominatim (OpenStreetMap) — reverse geocoding, turning coordinates into place names for drives and charges, requested by the server.
6Security
- All traffic between your browser and an installation is encrypted (HTTPS via Cloudflare; certificates are managed automatically).
- Passwords are stored as salted scrypt hashes; sessions use signed (HMAC) cookies.
- Sign-in and sign-up endpoints are rate-limited.
- Because the software is self-hosted, physical and OS-level security of the machine is the operator's responsibility — as are backups.
7Your rights
Depending on where you live (for example under the GDPR or similar laws), you may have rights to access, correct, export or erase personal data. Because each installation is operated independently, exercise these rights with its operator — the software makes this easy for them:
- Accounts can be removed entirely, taking their settings and access with them.
- All history can be deleted from Settings, or by deleting the database file.
- The database is a single SQLite file — exporting your data is copying a file.
8Children
Neither the website nor the software is directed at children under 16, and neither knowingly collects data about them. Accounts are created by installation operators or with their permission.
9Changes
If this policy changes, the new version is published here with an updated date. A material change will be noted prominently on this page. Continued use of the website after a change means the current version applies.
10Contact
Questions about this policy, the website, or the installation at connect.wattloft.com: