Privacy Policy
This policy explains what personal data TesHub processes, why, who else gets it, how long we keep it and what your rights are. It covers the TesHub app for iPhone and Android and the website teshub.bg with its dashboard.
In force from 10 November 2026
Who is responsible
The controller of your personal data is Iliyan Konakchiev, the developer of TesHub, a private individual in Bulgaria (Slaveykov housing estate, bl. 78, entr. 2, fl. 3, apt. 6, Burgas, Bulgaria; phone +359 898 357 065). Write to privacy@teshub.bg about anything to do with your data.
TesHub is an independent app. It is not affiliated with Tesla, Inc.
In short
- We don’t sell data, show ads or track you for advertising. The app uses no analytics services and no tracking across other apps or sites; the only usage numbers we keep are how many Tesla requests each account makes. The website uses Google Analytics only if you accept it in the cookie banner.
- Your car’s history is shown only to its owner in Tesla’s account. Drivers the owner added see only how the car is right now.
- Chat messages are stored encrypted on our server, and everything travels over an encrypted connection (HTTPS).
- You can delete your account and your data at any time, from the app.
Your account
Your name, email, password (we keep only a bcrypt hash of it) or your Google or Apple sign-in (its ID and email; with Apple’s “Hide My Email”, the forwarding address Apple gives us), the public keys of the passkeys you add (your face or fingerprint never leaves your phone: it only unlocks the key there), your profile photo, and your car’s model and photo if you choose to show them: the model by your name in the chat and in the discussions (on the website too), the photo on your profile in the app.
Why: so you have an account, can sign in, and others see who they’re talking to. Legal basis: performing our contract with you (Art. 6(1)(b) GDPR).
Chat, discussions and listings
Messages in the general chat and in private chats (text, photos, videos, voice messages, GIFs, reactions, replies, mentions), posts and comments in Discussions, listings (title, description, price, city, photos and the phone number you add), your reports and blocks, and the problems and bugs you report from the Account page (topic, message, the app’s version and your phone’s system).
The general chat is seen by everyone with an account; private chats are shown to their two participants. If a message is reported, administrators can review a copy of that message and its attachments until the report is resolved. While you have a chat open in the app, others see you in the general chat’s “Online now” list (your name, photo and car model). Discussions and listings are public: anyone can read them on the website teshub.bg without an account, and search engines such as Google may index them, with your name and profile photo, the text and the photos. A listing’s phone number is not shown on the website. Photos are resized and their EXIF data, location included, is removed; metadata is removed from videos and voice messages too. When you send a link, our server opens the page to show its title and picture, so that site sees our server’s address, not yours.
Legal basis: our contract with you; moderation is our legitimate interest (Art. 6(1)(f) GDPR) and a legal duty under the EU Digital Services Act.
Your car
You sign in to Tesla on Tesla’s own page: we never see your Tesla password. The tokens Tesla gives the app stay on your phone (iPhone Keychain or Android Keystore). With them the app reads your car’s data from Tesla (VIN, name, model and options, location, battery, charging, climate, locks, tires, alerts, software and more) and sends the commands you tap. Our servers get the access token with each request, to check with Tesla that the car is yours, and don’t keep it. Tesla may use what it receives through TesHub under its own Privacy Notice (tesla.com/legal/privacy).
Telemetry: if you turn it on (the app asks the first time you open Charges or Drives), the car sends our server, while it is awake, its location (about every 10 seconds), speed, gear, odometer, battery and charging, temperatures, doors, windows and locks, Sentry, whether someone is in the driver’s seat, climate, what’s playing, software version and tire warnings. From them we make the history of your charges, drives (with their routes) and parking (with addresses), the car’s notifications and the live dashboard. The foot of the Vehicle tab shows whether it is on (“Telemetry on” or “Telemetry off”). You can stop it at any time in the app (Account → Car → Telemetry): the car stops sending, and what was recorded until then stays until you delete your account.
Car preferences: the battery capacity you enter, charging tags and places, costs and electricity supplier, drive tags, tire rotation and maintenance marks, recent trip destinations and charger filters, and the last car alert you have read are stored encrypted in your account, separately for each VIN. This keeps your settings available across devices and lets the website use the same battery and charging values as the app. A local copy allows offline use; changes sync when connected. These records are deleted with your account.
Automations: if you turn them on, your phone hands our server a refresh token for your Tesla sign-in, so your rules can run while the phone is away. We keep it encrypted (AES-256-GCM) and delete it when you turn automations off or delete your account.
Import from Tessie: your Tessie token is used once for the import and not kept.
Legal basis: our contract with you.
TesHub Pro
You pay through the App Store or Google Play; we never see your card. Subscriptions are handled by RevenueCat, which gets a random customer ID (not your name, email or car), your purchase history and basic device information (model, system version, language). Legal basis: our contract with you.
TesAI and AI drawings
TesAI sends OpenAI your question, the earlier messages of the conversation and a short description of your car (model and year, options, software version and the titles of its release notes, battery %, odometer, tyre pressures, recent alerts) to answer it. AI patterns and backgrounds send OpenAI only the words you type. OpenAI gets a pseudonymous ID, not your name or email, and our requests ask it not to store them, though it may keep them for up to 30 days to fight abuse. Your TesAI conversation is kept only on your phone. On the website TesAI sends only your question and the earlier messages, no car details, and the conversation stays in your browser.
We ask for your permission before the first time, in the app and on the website. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time in the app (Account → AI).
Notifications
For push notifications we keep your device’s token from Apple or Google, its system and language. A notification’s text (for example the sender’s name and the start of a message) passes through Apple Push Notification service or Google’s Firebase Cloud Messaging.
Maps, addresses, routes and weather
To show addresses, routes, heights, weather and charging stations we send coordinates (some rounded) to:
- komoot (Photon): searching places, your car’s address and the town’s name for the weather;
- OpenStreetMap Nominatim: the addresses of your charges, drives and parking;
- OSRM (FOSSGIS): routes for the trip planner;
- Open-Meteo and OpenTopoData: weather and heights;
- Overpass (OpenStreetMap): which charging stations are near the places you charged;
- Google Places: the names and coordinates of a trip’s stops when you send it to the car;
- Apple Maps (iPhone), Google Maps (Android and the site) and OpenFreeMap: the maps in the app and on the site. On Android, Google’s map also sends Google the phone’s crash reports and diagnostics, how the map is moved and zoomed, and an ID of its own, to improve its services.
These services also see the IP address of your phone, your browser or our server. The charging networks’ lists (Eldrive, Fines, Electrip, Voltspot, supercharge.info) are downloaded whole, so they see only an IP address.
Videos, GIFs and news
- YouTube (Google): videos in the chat play from youtube-nocookie.com.
- KLIPY: GIF searches send the words and a random ID of the installation, not your account; GIFs load from KLIPY’s servers.
- News: the app loads each site’s news list (electrek.co, notateslaapp.com, teslarati.com, insideevs.com), which sees only an IP address, shows the titles and summaries, and opens the full article on its site. “Read in Bulgarian” opens the article in Google Translate in your browser, which sees the article’s address and your IP address.
- Recalls are looked up at the US NHTSA by model and year only; “Read in Bulgarian” opens the recall’s public text in Google Translate in your browser.
Security and abuse
We keep how many Tesla requests your account makes a day (to watch the cost of Tesla’s API), the chat’s warnings and bans, and short technical logs on the server, without message contents. Legal basis: our legitimate interest in security and preventing abuse.
Cookies
The website sets the cookies it needs to work: your sign-in (and a note that you’re signed in, for the menu), a short-lived one during the Google sign-in, the theme you pick and your cookie choice. If you use TesAI on the website, the browser’s storage keeps the conversation and your permission for OpenAI.
Only if you click “Accept” in the cookie banner, the website also loads Google Analytics (Google Ireland Ltd.), to count visits and see which pages are read. It sets the _ga cookies (kept up to 2 years) and sends Google the pages you open, the link that brought you, your browser, device and approximate location; Google doesn’t store your IP address and keeps the data for 2 months. It isn’t used for ads: Google signals and ad personalisation are off. Legal basis: your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time with “Cookies” at the bottom of every page; the analytics cookies are then deleted.
What stays on your phone
Much stays only on your phone: recent places in the trip planner, the TesAI conversation and your settings. On the website, the TesAI conversation stays in your browser. Your sign-in tokens are kept in the Keychain (iPhone) or Keystore (Android) and don’t move to another device in a backup.
Who else gets data
We don’t sell data or give it to anyone for advertising. We use providers who process it for us or because you asked for something:
- IONOS SE (Germany; the server is in Europe): our server, with accounts, chat and car data;
- Vercel Inc. (USA; the functions run in Frankfurt): the Tesla sign-in and signing commands for the car;
- Tesla, Inc.: sign-in, car data and commands;
- Apple (Sign in with Apple, notifications, Maps) and Google (Google sign-in, Firebase Cloud Messaging, Maps, Places, YouTube, Translate, and Google Analytics on the website, only with your consent);
- OpenAI (USA): TesAI and AI drawings, only with your permission;
- Brevo (France): the emails we send you (the welcome, a code for a new password);
- RevenueCat (USA): subscriptions;
- KLIPY: GIF search; Tessie (USA): only if you import from it;
- komoot (Germany), the OpenStreetMap Foundation and FOSSGIS (Germany), Open-Meteo (Switzerland), OpenTopoData, OpenFreeMap: maps, addresses and weather (see above);
- public authorities, only when the law obliges us.
Every provider that gets your data must protect it at least as well as this policy does (the same or equal protection), under its contract with us or its own terms, and may use it only for the service it gives.
Some providers are outside the EU. We transfer data to them on the basis of a European Commission adequacy decision (including the EU–US Data Privacy Framework), standard contractual clauses or, where neither applies, because it is needed to do what you asked for (Art. 49(1)(b) GDPR).
How long we keep it
- Your account, discussions and listings: until you delete your account.
- Chat messages: until you delete your account (a private chat for both people when either deletes theirs), and no longer than this: the general chat keeps only its last 5,000 messages, and photos, videos and voice messages in private chats are deleted after 90 days. A reported message stays until we have reviewed it.
- Your car’s history on our server: while TesHub is used with that car. We delete it when you delete your account (unless another TesHub account uses the car), when the car gets a new owner, or after 12 months in which nobody opened it in the app.
- Car notification registrations: an owner’s phone stays registered while the car is recording and expires 14 days after recording pauses; a driver’s phone expires after a day without renewal. Sign-ins expire after 90 days without use.
- Reports and problem reports: as long as the accounts they concern exist.
- When an account with warnings or a ban is deleted: a one-way hash of its email and its Apple and Google IDs, with that ban, for a year or until the ban ends if that is later, so it can’t simply sign up again.
- Database backups: up to 30 days.
- OpenAI: up to 30 days on their side. RevenueCat: we delete your customer record when you delete your account.
- Technical logs: briefly; they are overwritten automatically.
How we protect it
- Everything travels over an encrypted connection (HTTPS/TLS).
- Chat messages, their link previews and problem reports are stored encrypted (AES-256).
- Passwords are hashed with bcrypt and sign-in tokens are stored only as hashes.
- Tokens on your phone are in the Keychain or Keystore; the automations’ Tesla token is encrypted with AES-256-GCM.
- Photos, videos and voice messages are stored on our server under random addresses nobody can guess, and are deleted with your account.
- Access to a car’s data is checked with Tesla, and the number of requests is limited against abuse.
No system is perfectly secure. If we learn of a breach that puts your rights at risk, we will tell you and the Commission for Personal Data Protection as the law requires.
Your rights
Under the GDPR you have the right to access your data and get a copy, to have it corrected or deleted, to restrict its use, to data portability, to object to processing based on our legitimate interest, and to withdraw your consent at any time (without affecting what was done before).
You can do most of it yourself: edit your profile on the Account page, and delete your account there too; on teshub.bg, Account → Download my data gives you a copy of everything your account holds. For anything else write to privacy@teshub.bg; we answer within one month.
You may also complain to the Bulgarian Commission for Personal Data Protection (2 Prof. Tsvetan Lazarov Blvd., 1592 Sofia, www.cpdp.bg) or to the authority of your EU country.
Deleting your account
In the app: Account → Delete account, at the bottom. We delete at once your profile, photos, messages (private chats on both sides), discussions, listings, reports, car links and notification registrations, revoke your Sign in with Apple and delete your RevenueCat customer record. Your car’s history is deleted and the car stops sending us data, unless another TesHub account uses the car. The app tells you when it is done.
An active TesHub Pro subscription doesn’t stop on its own: cancel it in the App Store or Google Play.
You can also delete it on the website (teshub.bg → Profile), or write to privacy@teshub.bg from your account’s email (see teshub.bg/en/delete-account).
Children
TesHub is not for anyone under 16. If we learn an account belongs to a child under 16, we delete it.
Changes
If we change this policy in an important way, we will tell you in the app. The date at the top shows the latest change.