Privacy policy

About this policy

This policy describes how the Tesometry beta handles your information. Contact the Tesometry team at support@tesometry.app for support or privacy requests. Support response target: two business days; reports of privacy incidents: within 24 hours.

Information we process

• Account and access: your email address, account identifiers, sign-in requests and sessions. Tesla authorization credentials are stored on the server to maintain the connection. Network addresses may be processed for sign-in rate limiting and service security.
• Vehicle information: vehicle identifiers and available telemetry, including state of charge, odometer, speed, charging state, energy, battery temperatures, current and voltage, software version and other vehicle-state signals configured for the service.
• Derived records: trips, charging sessions, consumption summaries, battery-capacity estimates and vehicle history derived from those signals.
• Location, if separately enabled: vehicle coordinates, trip routes, parked locations and addresses derived from coordinates. Without location permission, Tesometry does not collect location for these features.
• Support correspondence: information you choose to send when asking for help. Please do not send passwords, access tokens or unnecessary location details.

Purposes and permissions

We use this information to provide sign-in, connect your Tesla, show vehicle state and history, operate the service securely, and respond to support and privacy requests. Your data is not sold or used for advertising profiles.

Signing in, authorizing Tesla, enabling telemetry and enabling location are separate steps. Signing in or connecting a Tesla does not by itself start telemetry collection. You can turn telemetry and location off in Settings. Turning a feature off stops new collection for that feature; it does not by itself erase existing history.

Service providers

• Tesla: the Fleet API authorizes access, delivers vehicle telemetry and executes the commands you request, within the permissions you grant.
• Geoapify: coordinates are sent to its reverse-geocoding service to obtain addresses when location is enabled. Loading map tiles sends the requested map area and network request information, such as your IP address, to Geoapify. See Geoapify’s privacy policy.
• Email delivery: our configured email provider processes your email address and sign-in message to deliver login links. Do not forward these links.
• Hosting and storage: service infrastructure processes and stores account and vehicle data; backup and deletion-ledger storage support recovery and deletion enforcement. Authorized operators may access data when needed to operate the service or handle a support request.

These services have their own processing arrangements. We do not promise that every provider processes data only in your country. Contact support for information about the current providers and processing locations.

How long information is kept

• Raw telemetry: the retention worker removes events older than 30 days, measured from receipt.
• Vehicle history: history is retained while collection remains active. The 90-day retention period starts after collection stops or the access period ends. Resuming collection before expiry can reset this deadline. Disconnecting a vehicle deletes its history immediately, as described below. This is not a rolling 90-day limit on active history.
• Account and connection information: kept while needed for the account and connection. Disconnecting the Tesla account or deleting the account triggers the cleanup described below.
• Temporary sign-in records: expire and are removed by the retention worker. Sign-in links expire after 10 minutes; request-rate records are retained for up to one hour before cleanup.
• Deletion records and backups: a minimal deletion marker is retained to prevent a deleted account’s data from returning after a backup restore. Backups are not rewritten instantly when a deletion is requested; deletion markers are applied before a restored service reopens.

Cleanup runs in background workers, so scheduled expiry and physical removal may not occur at exactly the same instant.

Stopping collection and deleting information

Turn telemetry off: new telemetry is rejected locally once the change is applied. Remote disable on the Tesla side is retried until confirmed. Previously collected history follows the retention rules above.

Disconnect a vehicle: new collection for that vehicle stops locally when the request is applied. Remote disable on the Tesla side is retried until confirmed. Its trips, charging sessions, location records, telemetry, command history and snapshots are deleted immediately and cannot be recovered; connecting the same vehicle again starts with empty history. Your Tesla account connection and other vehicles are not affected.

Disconnect Tesla account: new collection stops locally for all your vehicles when the request is applied. Vehicle history, location records and snapshots are removed when disconnect completes, after Tesla confirms remote disable. While disconnect is pending, existing local data has not yet been erased. Your Tesometry email account remains. If you need local account and history deletion without waiting for Tesla, use account deletion.

Delete your account: local sign-in access is revoked, email identities and vehicle history are removed, and collection is stopped. Remote disable and deletion-ledger export may remain pending and are retried. The app may show deletion as pending until those steps finish. Deleted history cannot be recovered through the app.

Your requests and rights

Contact support to request access to your information, correction, a copy, restriction of processing or deletion. You can also delete your account in the app. We may need to verify that the request concerns your account. Where applicable law gives you additional rights, including portability, objection, withdrawal of consent or a complaint to a supervisory authority, those rights remain available. Withdrawing permission does not undo processing that already occurred.

Website and policy updates

The landing and legal pages do not use advertising trackers, third-party fonts or analytics cookies. The language is selected through the page URL or your browser’s language preference. Necessary network requests still reach the hosting service.

The policy date is shown at the top of this page. Review it when deciding whether to continue using the beta, and contact support if an update is unclear.