Privacy Policy for Tespit

The party responsible for this app is:

Email: TespitApp@gmail.com

VAT ID: CHE-405.472.785

As the developer, I have no direct access to your vehicle data, VIN, location data, Bluetooth connection, private vehicle key, app settings, or locally stored content. Tespit has no user account of its own, no backend of its own, no cloud database of its own, no ads, and no tracking system.

A lot of data stays local on your iPhone or Android device. Certain features use Apple or Google services, for example StoreKit and Google Play Billing for purchases/subscriptions, MapKit, the Google Maps SDK and Google Routes API for maps/routes, or iTunes Search and the radio-browser.info station directory for cover artwork and station logos. When a route is calculated, the relevant provider may process the origin and destination coordinates needed for that function. In addition, Tesla and Tesla services may process their own data in connection with your vehicle, your Tesla account, the Tesla app, or vehicle systems. I have no direct database access to that data.

The separate app Tespit Social, which comes with Tespit 1.1.15 as an additional app on the App Store and Google Play, has its own privacy policy: https://tespitapp.com/en/datenschutz-social

Tespit is not an official Tesla app. It is not operated, sponsored, reviewed, or officially endorsed by Tesla. All trademarks and names belong to their respective owners.

Depending on how you use the app, the following data may be stored or processed locally on your device:

• Vehicle VIN and vehicle name: for locally setting up and selecting your vehicle.
• Private vehicle key: stored locally and device-bound in the iOS Keychain or Android Keystore.
• Pairing status: to recognize whether a vehicle has already been set up.
• App settings: for example language, layout, units, map style, theme, premium/promo unlock status, and display options.
• Bluetooth and vehicle status while in use: for display on the dashboard.
• Dashboard and Live Activity content: if enabled, to show vehicle information in the app, on the lock screen, or in the relevant system component.

This local data is not transmitted to me as the developer.

With “Trip data”, Tespit can record your trips. Recording is off by default and only runs when you turn it on in the app while the app is running and connected to the vehicle. For each trip it stores:

• Time and vehicle: start and end of the trip, and the name and VIN of the connected vehicle.
• Route: position points about every 2 seconds while driving and every 15 seconds when stationary, each with speed, power, battery level and distance driven from the vehicle telemetry. On iPhone also the altitude from the device's GPS and the outside temperature reported by the vehicle.
• Calculated values such as distance, duration, top speed and estimated consumption.
• Place names of start and destination, and the electricity prices and currency you enter yourself.

Trips are stored only in the app on your device and are excluded from device backups (such as iCloud Backup or Android backup). They are not sent to me, and there is no cloud sync. You can delete single trips or all trips in the app; they are also deleted when you remove the app.

The following services are used for this:

• Place names: to show start and destination with a place name, their coordinates are sent to the operating system's location service (iOS: Apple; Android: the device's geocoder, usually provided by Google).
• Maps: the route is shown with Apple Maps on iOS and with Google Maps on Android. For this, the app loads map tiles of the area you drove through from the respective provider; this also applies to the map in the trip picture.
• Exchange rates (optional): only if you turn on daily exchange rates does the app fetch the European Central Bank's reference rates via api.frankfurter.dev. Only the requested date is sent, no trip data.

Sharing, export and trip picture: a trip only leaves your device when you share or export it yourself – as a picture, PDF or Excel file, to the destination you choose in the share menu. The trip picture after parking is created on the device; its QR code only leads to tespitapp.com and contains no trip data. If you turn on automatic saving, the app adds the picture to your photo library; on iOS it only asks for permission to add photos.

Tespit Social (iPhone only): so that the separate app Tespit Social can show your trips, Tespit places a copy of your finished trips and of your unit, currency and price settings in a protected shared app folder on the device that only apps from the same developer can read. This copy stays on the device, is also excluded from backups and is not transmitted by Tespit. What Tespit Social shares with friends is up to you in that app; the Tespit Social privacy policy applies to it.

Depending on the platform, the app may use Apple, Google, and external services:

• StoreKit (iOS) and Google Play Billing (Android): to handle in-app purchases, subscriptions, restoring purchases, and purchase status.
• MapKit (iOS), the Google Maps SDK, and Google Routes API (iOS and Android): for map, location, route, and navigation features. When the optional Google services are selected, Google may process the location coordinates, IP address, device/app identifiers, and SDK usage, crash, performance, and other technical diagnostic data needed to provide and improve the service.
• Privacy for Google services: Google's processing is governed by the Google Privacy Policy (https://policies.google.com/privacy) and Google Maps Additional Terms (https://maps.google.com/help/terms_maps/). The Tespit developer can see only aggregate API usage and billing metrics, not individual location, map, or route data.
• iTunes Search: to look up cover artwork for music, podcasts and audiobooks by title, artist, or album on both iOS and Android.
• radio-browser.info: to look up station logos while radio is playing (for example TuneIn, FM or DAB+) on both iOS and Android. Only the station or title name reported by the vehicle is sent. radio-browser.info is a free, open directory of radio stations (https://www.radio-browser.info).
• GitHub (iOS and Android, only with speed camera warnings enabled): The speed camera data comes from OpenStreetMap (© OpenStreetMap contributors, ODbL) and is stored as a file in the public repository https://github.com/gena3ekiller/tespit-map-data. Tespit downloads a small control file there at most once a day and, if new data is available, the file itself, and only in countries where the feature is permitted. As with every download, GitHub (GitHub, Inc., USA) receives your IP address and technical connection data. Tespit does not transmit any location, trip or vehicle data; the app calculates the warnings on your device, and the file is only stored there (not in the backup, deleted when switched off). The privacy statement of GitHub applies to the processing by GitHub (https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement).
• Apple diagnostics: crash and diagnostic data may be provided to me via Apple if you've agreed to share it with developers.
• App Store Connect: Apple may show me aggregated information such as downloads, sales, revenue, subscriptions, and general app statistics.
• Google Play Console: Google may show me aggregated information such as downloads, sales, revenue, subscriptions, and general app statistics.

These services are processed by Apple, Google, or the relevant external provider depending on the platform. I don't see raw data such as your current location beyond the information needed for a route you requested, your vehicle connection, private key, or locally stored app settings.

If you use a Tesla vehicle, the Tesla app, a Tesla account, or Tesla vehicle services, Tesla may process its own data independently of Tespit. Depending on your Tesla settings and usage, this may include vehicle data, diagnostic data, location/route information, app and account data, security data, software/service data, or vehicle system data.

Tespit does not operate a backend for this and does not forward this Tesla data to me as the developer. I have no access to your Tesla account, your Tesla app, Tesla servers, your Tesla vehicle history, or data that Tesla processes directly from the vehicle or via Tesla services.

Tesla's own privacy information applies to this processing. You can review data sharing and privacy options in your Tesla account, the Tesla app, or the vehicle, to the extent Tesla offers these settings.

Bluetooth is used to establish a local connection to the supported vehicle. The connection is used for the dashboard display and pairing. On Android, the app uses the BLUETOOTH_SCAN and BLUETOOTH_CONNECT permissions; scanning is declared not to be used for deriving location. The private keys remain local in the iOS Keychain or Android Keystore. I, as the developer, cannot access these keys.

Location data is used for map, route, and dashboard features. The app only requests location while it is in use and does not use location in the background. When a route is calculated, origin and destination coordinates may be sent to the Apple or Google service providing that function. Dashboard speed is read exclusively from Tesla vehicle telemetry, not from the device GPS. Your location is not transmitted to any backend of my own.

After you initiate the action, the app may let you paste text from the clipboard via a button, for example the VIN, on iOS or Android. It can also open the Tesla app via a deep link. No data is transmitted to me as a result.

If you contact support via email, I process the information you voluntarily send, for example your email address, description of the issue, screenshots, or technical details. Please don't send private vehicle keys, credentials, or other sensitive information.

As of now, the app does not use any ad network, tracking system, Firebase Analytics, or an analytics backend of its own. Personal data is not sold. The separately operated website tespitapp.com is explained in the following section.

This information concerns the website tespitapp.com, not the Tespit app. The website uses its own data-minimising first-party event counter. It stores only aggregated counters for allowed events and a few limited dimensions.

• No cookies, user IDs, session IDs, or fingerprinting.
• The event-counter logic does not store IP addresses, email addresses, or personal vehicle data.
• Supabase is used solely as the technical database infrastructure for aggregated website counters.

The website is provided through Lovable infrastructure. If Lovable makes general or aggregated website statistics available at platform level, these may additionally be available. This notice makes no absolute statement about which technical raw data the hosting or platform infrastructure processes internally.

For the Android notice, the website stores locally in the browser under the key tespit-android-status-notice-v2 whether the notice has already been dismissed. This value is used solely for the user interface, is not a user or session ID, and is not transmitted to Supabase through the event counter.

Depending on applicable law, you may request access, correction, deletion, or restriction of processing. For any requests, please use the email address listed above. In many cases, you can delete locally stored app data simply by removing the app from your device.

This privacy policy may be updated as features, services, or legal requirements change.

Email: TespitApp@gmail.com

VAT ID: CHE-405.472.785

Responsible for content, operation, and support of the Tespit app: Esat Arslan.

© 2026 Esat Arslan. All rights reserved.