Know what you’re connecting.

Permissions you grant

Tesla handles your password and sign-in. Electriplan requests authorization and renewal, vehicle information, and vehicle commands through openid, offline_access, vehicle_device_data and vehicle_cmds. Vehicle information lets Electriplan list your cars, check whether one is online and, only when you ask, read its battery level.

Tesla’s command permission is broader than navigation and can authorize sensitive vehicle controls. This Electriplan integration sends navigation only. It does not request Tesla’s vehicle-location, charging-command, energy or profile permissions. It does not read your car’s location, check on your car in the background or on a schedule, wake it on its own or send destinations without your confirmation.

Battery readings and waking your car

Electriplan can read your car’s battery level so a trip can start from the real charge instead of an estimate. This happens only when you ask in the iPhone app, typically right before a drive. It never happens automatically, on a schedule or in the background.

A reading contains the usable battery percentage and the time of the reading. It may also include Tesla’s nominal battery figure, the charge limit and whether the car is charging, when Tesla provides them. Electriplan asks Tesla for charge information only and never requests the car’s location.

If the car is asleep or out of reach (Tesla reports both the same way), Electriplan tells you and offers to wake it. One confirmation allows one wake attempt: Electriplan sends Tesla a single wake request, then only checks whether the car is awake for up to about a minute. If it does not wake in time, for example because it has no connection, Electriplan stops and says so; it never retries on its own. Waking can take up to a minute, and an awake car may use more power than a sleeping one.

Electriplan’s server returns the reading to your iPhone and does not store it or write it to its application logs. It keeps a usage record (the kind of request, when it ran and whether it worked) to apply usage limits. That record holds no battery figures and no vehicle identifiers.

Your agreement is recorded on your connection as consent version 2026-10-02, with the date you gave it. Connections made earlier keep working for navigation but cannot read the battery until you agree in the app. The service operator can also turn battery reading off, and Electriplan then says it is unavailable. To withdraw, disconnect in Electriplan and revoke Electriplan in your Tesla account.

Data used by the connection

The server stores encrypted Tesla authorization tokens and the vehicle information needed for selection and key checks. The iPhone stores a separate Electriplan session credential in Keychain. A private signing key belongs only in the operator’s protected signing infrastructure; neither that key nor Tesla customer tokens are delivered to the iPhone.

When you confirm a send, Electriplan sends the selected vehicle, trip revision, ordered stop details and your confirmation to its server. It shares the reviewed address with Tesla for a next-stop request, or supported Google Place references for an eligible whole leg. Tesla resolves the shared destination.

Command records retain identifiers, a request fingerprint and the outcome needed to prevent replaying the same request within an Electriplan connection. They do not retain destination text or raw Tesla responses. Service errors use bounded diagnostic codes rather than provider response bodies.

Each exact confirmation can be submitted once. Electriplan keeps up to 60 local send records for recent outcomes, but a fresh review and confirmation can send the same destinations again, including after an accepted or unknown result or through a separate connection. Check navigation in the car before confirming another request.

Retention and deletion

An Electriplan session expires after 30 days. An unfinished sign-in flow expires after 10 minutes; after Tesla returns successfully, its one-time app redemption code expires within one minute. Expired records are removed by the operator’s configured maintenance schedule. Command records remain with the connection so that an old request cannot be sent again after its receipt disappears.

Disconnect with a valid Electriplan session deletes the server connection, stored credentials and associated records. If the session has expired or is no longer recognized, the app can remove its local session but cannot confirm server deletion; expired server records follow the maintenance schedule described above. Revoke Electriplan in Tesla and remove its vehicle key under Locks as well. Deletion cannot recall a command already sent to Tesla.

Encrypted backups may retain deleted data until the operator’s published backup retention expires. Restoration must require fresh authorization; this disclosure does not promise immediate backup erasure.

This Tesla connection does not collect vehicle location telemetry or recordings. Any future feature that uses those data would require a separate design and explicit consent.

Service providers and vehicle confirmation

The intended hosting providers are Vercel and Supabase. Tesla processes the information shared with it under its Privacy Notice.

A provider-accepted or queued response does not prove that your car displays the expected route. Always check the destination and route on the vehicle display before driving.