Privacy Policy

1. Scope

This policy explains how the LiveTa iOS app and this website handle information. LiveTa is an independent client for your self-hosted TeslaMate service and is not affiliated with or endorsed by Tesla, Inc. or the TeslaMate project. Operator: Bolin Group Inc, California, United States. Contact: [email protected].

2. Our privacy approach

You control your vehicle data. For core vehicle features, the app connects directly to your configured LiveTa Connector and reads your TeslaMate data. Full routes, trips and charging histories are not centrally uploaded to the developer by default. Optional galleries, push relays, support communications and third-party network services process the information described below; this is not a claim that every feature bypasses third parties. The app does not request your Tesla password or send vehicle control commands.

3. Information processed by the app

To display vehicle status and history, the app reads vehicle identifiers, locations, routes, driving status, charging, energy and parking records from your connector. Server addresses, device credentials and connection settings establish and authenticate the connection. Preferences, caches, manually entered fees, notes, places, pricing rules and merged records support viewing and managing records. These core records are processed on your device or services you manage. Additional transfers for galleries, notifications and support are described below.

3A. Optional station photos and public sharing

When you view a station gallery, your configured LiveTa API sends the station name, coordinates, available station identifiers and a pseudonymous user identifier derived one way from your pairing credential to the gallery. These support station matching, submission status and blocking rules. The identifier is pseudonymous, not anonymous. This does not give the gallery your raw pairing credential, database password or full trip history. Opening a gallery can cause these requests even if you never upload a photo.

Uploading is optional. After selecting or taking each photo, you must actively confirm that you have the right to share it and agree to make the photo and station location public, then confirm upload. The consent switch starts off and the server also checks public-sharing consent. Camera access requires system permission; the system photo picker provides only selected photos. Images are re-encoded and original metadata removed before upload, but visible content can still reveal faces, plates or places. Obscure unrelated personal information first.

The gallery processes photos, associated stations and coordinates, pseudonymous uploader identifiers, submission times, consent status, moderation status, report reasons, blocking relationships and moderation actions. The shared gallery operated by Bolin Group Inc uses Cloudflare Workers, D1, private R2 storage and Images to process and deliver content. Protected original storage does not make published photos private. Other gallery operators explain their own processing.

Ordinary submissions become public after approval; authorized administrators may publish immediately on submission. Others may view, save and share public photos. Available controls let you remove your own submissions, report photos and block uploaders. Submissions are associated with your current pairing identity. Remove photos you no longer wish to share before unpairing. Unpairing or clearing local caches does not delete public photos. If you lose the original pairing identity, contact [email protected] for help with content we manage. Removing a photo ends permission for further public display, without affecting prior lawful processing or necessary reporting, security and legal records.

Public photos remain until removed or the display service ends. Pending submissions, reports and moderation records remain as needed for review, appeals, security and applicable law. Removal does not automatically erase other users’ copies, delivered caches or legally required records. Posting is not required for core vehicle-data features.

Server-verified identity linking can preserve your gallery submission identity across Tailscale and Cloudflare connections. Linking does not grant gallery Owner privileges: the server verifies Owner status, and record sync does not change it.

4. Local storage and connection security

Device pairing credentials are stored in the iOS Keychain. Connection settings, local edits and caches are stored on your device. The connector stores a hash of the device credential; database credentials remain on your server. Use a protected network connection and secure your connector, remote access and backups. No storage or transmission method can guarantee absolute security.

4A. Optional remote notifications and network access

In a push-enabled build, after opt-in and system authorization, the app may register an APNs token, vehicle identifier, preferences and push environment with your configured connector. The connector and any configured relay process these to send notifications, delivered by Apple through APNs. Messages may contain vehicle status, events or places. Availability depends on the build, permissions, server and push setup. Tokens are not used for advertising.

Turn off notifications in the app or iOS Settings and manage registrations on your server. Unpairing or revocation requires connectivity or administrator action. Delivered notifications are managed by the device and system settings. Cloudflare Tunnel + Access proxies requests when selected. Access credentials stay in the Keychain per server address; Tunnel tokens should not be put on your phone.

5. Optional phone location

Phone-trip location is off by default and is used only after you enable it and grant system permission. It supports local phone-trip information. LiveTa does not upload these phone coordinates to the developer or your connector. You can disable location in the app or iOS Settings. This does not prevent the app from reading existing vehicle-location records on your own server. Third-party processing for maps, searches and directions is described below.

6. Apple Maps and other services

Native maps, address searches and route planning use Apple Maps. Apple may process searches, locations and device information needed to provide these features, as described in its Maps privacy notice. Your TeslaMate installation, connector, proxy, VPN or hosting provider may also process connection information and logs. Their administrators control configuration, retention and security.

7. Live Activities and Lock Screen

When enabled, Live Activities may display vehicle status, places or navigation information on your Lock Screen and Dynamic Island. Anyone able to see your screen may see this information. You can disable Live Activities in the app or iOS Settings.

8. Analytics, advertising and support

The current app does not integrate third-party advertising or behavioral analytics SDKs or collect vehicle data through a developer-operated analytics service. Apple may process diagnostics and app usage information according to your system privacy settings and its policies.

During TestFlight testing, Apple processes test-device, usage and crash information under its testing-service rules and makes relevant diagnostics and feedback, screenshots and contact information you submit available to the developer. Feedback can contain information visible on your screen. Review and obscure unrelated personal information before submitting it. See TestFlight information and terms.

If you contact support, we process the email address, issue description and attachments you provide to respond, troubleshoot and handle necessary follow-up. Emails to [email protected] may be forwarded through Cloudflare Email Routing to a mailbox we manage with Microsoft Outlook. Cloudflare and Microsoft process addresses, message content, attachments and technical information for routing, delivery, storage and security under their policies and service configuration. Do not send database passwords, real pairing QR codes or unnecessary full vehicle histories.

9. Retention and deletion

Local caches follow the app cache settings and can be cleared. Local edits remain until you delete them or remove the relevant app data. Settings provide separate controls to clear caches, delete local edits and unpair. Unpairing removes the local credential and attempts to revoke it on the connector; revoke it on your server if the device is offline. Do not rely on uninstalling the app to revoke access: Keychain items, external exports and system backups may remain. Clearing app data does not delete original TeslaMate records. Manage self-hosted data on your server. Support communications are retained only as needed to resolve the issue and meet applicable legal requirements.

10. Exports, backups and sharing

You can choose to export CSV files or JSON backups. These may contain vehicle history, locations, costs and notes. You choose where to save or send them. File services, sharing destinations and other apps process shared information under their own policies. Deleting app data does not delete these external copies.

With supported app and API versions, Settings lets you manually upload or restore personal-record snapshots, including fees, notes, places, pricing and tire settings, merged records, and supported notification preferences and inbox records. Snapshots stay on your configured API, not a developer-hosted vehicle backup, and are limited to the same API instance and vehicle. Other paired phones authorized for that vehicle can read uploaded snapshots; share your backend only with people you trust. Device push tokens and notification enablement permissions are not transferred. Owner privileges remain server-verified and are not granted by record sync. Clearing local data or unpairing does not delete server snapshots; contact the relevant server administrator for removal.

11. This website

This website is hosted on Cloudflare Pages and uses system fonts, without Google Fonts, registration forms, advertising trackers or custom behavioral analytics scripts. Cloudflare may process IP addresses, request times, URLs, browser request headers and technical logs for delivery, security and troubleshooting. Its policies and actual configuration govern processing and retention. This website does not request Tesla credentials, database passwords or real pairing QR codes. If analytics or other collection is enabled later, we will update this policy and obtain consent where required.

This website does not use advertising cookies or sell or share personal information for cross-site behavioral profiling. This remains the case whether or not a browser sends Do Not Track or Global Privacy Control signals. Cloudflare may use necessary security cookies depending on its configuration. If our practices change, we will update this notice and provide choices where required.

12. Your choices and rights

You can manage location, notification and Live Activity permissions, export supported records, clear caches, delete local edits, unpair and manage your own server data. Applicable law may also provide rights of access, correction, deletion, restriction, portability, objection or complaint. The developer cannot access or delete your self-hosted vehicle records for you. For photos, support information and other personal information we manage, contact [email protected].

Where GDPR or similar law applies: station and pseudonymous identifiers needed to respond to gallery-viewing and related service requests are processed to provide the requested service; public photo sharing is based on your active consent, which you can withdraw by removing the photo or contacting us; support enquiries rely on responding to your request, pre-contractual steps or legitimate interests in resolving issues; necessary anti-abuse, moderation and dispute records rely on legitimate interests in service security and rights protection or applicable legal obligations. Withdrawal does not affect earlier lawful processing. You may object to processing based on legitimate interests and complain to a competent supervisory authority.

The operator is in California, United States. Cloudflare, Apple, Microsoft and services you choose may process information in the United States or other countries. Transfer mechanisms and applicable safeguards depend on the services and laws involved; contact us about arrangements for processing we control. Administrators of services you manage or choose explain their own arrangements.

13. Children

LiveTa is intended for users who can manage self-hosted vehicle data services. It is not directed at children, and we do not knowingly collect personal information from children. Contact us if you believe a child has provided personal information to us.

14. Policy updates

We may update this policy as features and data practices change and will revise the date on this page. Material changes will be communicated through the website or app. Where additional permission is required, we will request it before the relevant processing begins.

15. Contact

Operator: Bolin Group Inc, California, United States. Privacy and support email: [email protected]. Describe your request without including passwords, pairing credentials or unrelated vehicle histories.