My T Privacy Policy

Last updated: September 10, 2026

My T is an iPhone app for viewing data from a self-hosted TeslaMate-compatible API or a user-configured Tessie service. This policy explains how My T handles vehicle data, connection details, on-device credentials, optional iCloud synchronization, push notifications, and Live Activities.

1. Purpose of the app

My T connects to a TeslaMate-compatible API that you host or to a Tessie service you explicitly configure. My T is not an official app of Tesla, Inc., TeslaMate, Tessie, or any vehicle manufacturer.

2. Information we do not collect

3. Information stored on the device

To connect to a service you specify, My T may store the following information on your device:

This information is used only to connect to the service you configure. Sensitive credentials are kept in the iOS Keychain. iCloud configuration sync is off by default. If you explicitly enable it, connection configurations and credential copies may synchronize through your private iCloud account to devices signed in to the same Apple Account. The developer cannot read this iCloud content. Drives, charges, GPS history, and TeslaMate database contents are not copied into that configuration backup.

You may also explicitly export a .mytconnection file through the iOS share sheet. The file can contain a server address and connection credentials, so share it only with a trusted device or person. This user-initiated transfer is not routed through the developer’s servers.

4. Source and storage of vehicle data

Vehicle status, trips, charging, location, and statistics come from the TeslaMate-compatible API or Tessie service you configure. Self-hosted data remains in your TeslaMate instance and database. When Tessie is used, its terms and privacy policy also apply. My T reads and displays data supplied by the selected service.

Optional My T Companion runs on your TeslaMate host, reads PostgreSQL in read-only mode, and returns requested data through your own secured endpoint. It does not copy the full vehicle history. To preserve events that iOS cannot reconstruct later, it can keep a bounded Companion-owned parking-event log (up to the newest 50,000 events by default) for observed sleep/wake, plug/charging, security/opening, and climate state boundaries. This remains in the Companion data volume on your own VPS.

5. Network connections

My T connects to the server addresses or data services you configure and, when you choose Friend Together, the dedicated HTTPS sharing address in the invitation you accept. HTTPS, a VPN, Tailscale, or Cloudflare Access is recommended for your own source. User-entered HTTP is supported for local/private networks and temporary public-IP deployments; saving a public HTTP endpoint requires an in-app security warning because traffic and credentials are not encrypted. Developer-operated push services and Friend Together guest connections use HTTPS only.

6. Third-party services

My T uses Apple Maps / MapKit to display maps and calculate driving routes. A route request can send its origin and destination coordinates, including the observed positions of two cars in Together mode, to Apple's mapping service. Map and route processing is subject to Apple's terms and privacy policy. This is separate from the developer-operated push relay.

7. Optional push notifications and Live Activities

If you enable compatible software-update, parked low-battery, or locked-and-empty notifications, or charging and navigation Live Activities, Apple Push Notification service delivery requires a relay operated by the app developer. The relay stores the APNs device token, Live Activity token, and an opaque installation ID required for delivery.

My T Companion sends only the minimum signed event data. Software-update events may include an opaque installation ID, TeslaMate vehicle ID or display name, the observed update type or version, and observation time. Charging events may include session identity, battery percentages, genuine rated-range readings, power, remaining duration, and estimated completion time; missing range values are omitted rather than estimated, and kWh is not sent. Navigation events may include destination/start labels, remaining distance and minutes, ETA, predicted arrival battery, and whether TeslaMate verified the trajectory. A locked-and-empty event may include an opaque installation ID, event ID and time, event type, vehicle ID, and vehicle display name. A low-battery event may include those event identifiers plus the observed battery percentage and episode identifier. Each iPhone stores all-vehicle defaults for its paired TeslaMate server and may optionally store category-specific overrides for an individual server-local car ID. The overridable categories are Lock Screen cards, destination-trip alerts, parked low-battery alerts, software-update alerts, and Lock Secure. Selecting a vehicle in the app does not change notification scope, and sound remains an iPhone-level choice. None of these events sends GPS coordinates, route geometry, VIN, TeslaMate credentials, database passwords, or retained lock/occupancy history to the relay.

The alert-sound selection, imported sound filenames, and imported audio remain on the iPhone and are not sent to Companion or the relay.

The relay retains APNs/Live Activity tokens, an opaque installation ID, and locale until you disable the feature or for up to 365 days after inactivity. Vehicle-event content is processed only for immediate APNs delivery and is not persisted. Low-battery acknowledgement and the explicit four-hour snooze state remain on your VPS, scoped to the responding iPhone, vehicle, and battery episode; the relay does not store them. Delivery audit records retain only installation ID, event type, outcome, and timestamp for up to 90 days; they do not retain vehicle names or IDs, destinations, battery values, software versions, or content summaries. To provide anonymous vehicle-count and enrollment-time statistics, Companion first derives a non-reversible vehicle alias on your server from a local-only random namespace and TeslaMate's local car ID. The relay retains only that alias and its first/last seen timestamps for up to 365 days and does not store the alias together with an installation ID. This statistic contains no raw car ID, vehicle name, VIN, server address, location, route, telemetry, software version, or notification content. These device identifiers and usage records are used only for app functionality—not advertising, analytics, or cross-app tracking.

8. Optional Together and Friend Together sharing

These features are included in My T 6.01, awaiting App Store review as of September 10, 2026. Same-server Together compares cars in a source you already have permission to access. Friend Together is an optional, separately enabled feature for two owners whose cars use different TeslaMate servers. Each participating server needs compatible Companion support and a dedicated HTTPS sharing address; installing the app or pairing notifications does not enable sharing.

Each owner selects a car, a display alias, the recipient and a duration of 1, 2, 4 or 8 hours. Location sharing includes precise coordinates, observed speed, heading, vehicle state and observation times. Navigation (destination coordinates and available route/arrival information), battery percentage/rated range, and the observed trajectory since consent are separately selectable. An invitation alone does not release vehicle data: the owner confirms the requesting device and confirmation code. Mutual sharing requires a separate approval in each direction.

The recipient's iPhone requests only the permitted observations directly from your Companion sharing endpoint. The invitation reveals that endpoint and the chosen vehicle alias/model; it does not include Tesla manufacturer credentials, your full TeslaMate connection credentials, VIN, other cars or unrestricted trip history. Friend Together does not send positions or trajectories to the developer's push relay, and does not add background or Lock Screen sharing. Apple Maps may process route endpoints as described in section 6.

Device-bound credentials and sharing-session metadata are stored on the participating phones; the device private key stays in that phone's Keychain. Companion keeps bounded permission, expiry, device-public-key and token-hash records on the owner's server, not a new shared GPS-history archive. Data access ends when the server confirms revocation, the recipient leaves, or the grant expires. If the server cannot be reached, My T reports that stopping is not yet confirmed; local dismissal or deleting the app is not remote revocation. A Companion restart ends active sharing and requires a new invitation.

Precise locations, destinations and trajectories can reveal home, work or other private places even without an address label. Share only with people you trust and obtain the permission of people whose journeys you disclose. Stopping sharing prevents further authorized reads; it cannot erase information the recipient has already seen, saved or captured. Manage or stop each sharing direction in the app before removing a connection or uninstalling.

9. Data deletion

You can remove or change connections, delete iCloud backups, and unregister the push relay by disabling enhanced services. My T sends an authenticated unregister request; if the relay is temporarily unreachable, the signed pairing remains only on this iPhone so the app can retry deletion the next time it runs. Inactive relay installations are automatically deleted after no more than 365 days; anonymous vehicle aliases are also deleted no more than 365 days after they were last seen. Uninstalling removes on-device app data but does not automatically delete existing iCloud backups. Data held by TeslaMate, Tessie, or another configured service must be managed through that service.

10. Contact

For privacy questions or ordinary support, use the My T support page or open a support request on GitHub. Do not include credentials, precise vehicle locations, VINs, or private server addresses.

← Back to My T