Privacy Policy
Last updated: June 21, 2026. This policy describes how Terssie (“we,” “us,” or “the service”) handles information when you use the Terssie iOS app and related services at terssie.com and api.terssie.com.
Overview
Terssie is a personal Tesla companion application. We designed it so you control vehicle access through your own Tesla account. We do not sell your personal information.
Information we process
Tesla account & vehicle data
When you authorize Terssie through Tesla’s OAuth/Fleet API, we receive and process vehicle data needed to provide features — including battery level, location, lock state, charging status, drive state, trip telemetry, and command responses. Your Tesla account password is never collected by Terssie.
App & device data
- Server URL — stored on your iPhone to reach your backend
- Push notification token — registered with the backend to deliver alerts
- Location — used for approach welcome, home location, and battery guard when you grant permission
- Bluetooth — used locally on your iPhone for Phone Key pairing and door unlatch; BLE keys are stored on-device
Trip & telemetry records
When trip recording is active, the backend stores drive metrics (distance, duration, energy, efficiency, speed events, waypoints, and derived scores) to power Trip History and Grok summaries. Data is associated with your configured backend instance.
AI features (Grok)
If enabled on your backend, vehicle and trip context may be sent to xAI’s Grok API to generate briefings and drive summaries. No Grok requests are made unless your backend operator configures an API key.
How we use information
- Display vehicle status and controls in the app
- Run automation features (sentry, approach welcome, battery guard, in-car delivery)
- Record trips and generate summaries
- Send push notifications you opt into
- Diagnose connectivity issues
Where data is stored
Backend data (settings, device tokens, trip records) is stored on the server you connect to — for example, the hosted service at api.terssie.com or a self-hosted deployment you control. Phone Key material and local app preferences remain on your iPhone.
Sharing & third parties
We share data only as needed to operate the service:
- Tesla — vehicle commands and data through the official Fleet API
- Apple — push notification delivery via APNs
- xAI — optional Grok API calls when configured by the backend
- Infrastructure providers — cloud hosting (e.g., Fly.io) for the production API
We do not sell or rent your personal information to advertisers or data brokers.
Your choices & controls
- Revoke Tesla access at any time from your Tesla account settings
- Disable location, Bluetooth, or notifications in iOS Settings
- Turn off individual features (Approach Welcome, Battery Guard, Proximity Sentry, auto-delivery) in the app
- Contact support@terssie.com to request deletion of backend-stored data where applicable
Retention
Trip history and configuration persist on your backend until deleted or until you stop using the service. OAuth tokens may be refreshed or invalidated when you revoke access. Diagnostic logs are kept only as long as needed for operations.
Security
Connections use HTTPS. Vehicle commands use Tesla’s signed command protocol with a virtual key pair; the public key is published at terssie.com. BLE Phone Key operations are performed locally between your iPhone and vehicle.
Children
Terssie is not directed at children under 13, and we do not knowingly collect information from children.
Changes
We may update this policy from time to time. Material changes will be reflected on this page with an updated date.
Contact
Questions about privacy: support@terssie.com
See also our support page.