Who we are
Teslable is operated by Owlzworks (“we”). This policy explains what we collect when you use the Teslable app and website, why, and what you can do about it. It applies worldwide; the sections for the European Economic Area, California and Korea add the rights those laws give you.
What we collect
Only what a feature needs.
- Account: display name, language and unit preferences, and the date you last used it. You can start without an email; we receive an email address only if you sign in with an email or link one in Settings (so that you can carry on with the same account after changing phones or reinstalling the app). An account without an email is told apart by a random number only.
- Vehicle: VIN, model, software version. You can type the VIN or, if you prefer, sign in to your Tesla account to fetch it: we then ask Tesla once for the list of that account’s cars, read the VIN and keep nothing of the sign-in. We never see your Tesla password.
- Vehicle data: position, speed, state of charge, charging state, tyre pressure, temperatures and odometer, read from the car by your phone over Bluetooth while the app is connected to it (including in the background). These readings, and the drive records, tyre records and parking spot made from them, are kept on your phone only and are not sent to our servers. While Drive Guide is on, the car’s position, speed and heading are passed to Kakao Mobility’s navigation SDK to get the enforcement cameras ahead (see “Who receives it” below). They are lost if you delete the app or change phones, and since we do not hold them we cannot restore them. One exception is an account for which we have switched on the diagnostic log to look into a problem (test accounts): there, positions and the times of prompts during Drive Guide are sent to our servers. The other is a device log you choose to send with feedback (it may contain vehicle and Bluetooth identifiers): that log is sent to our servers. We do not receive vehicle data from Tesla’s servers.
- Things you add: parking spot notes and pillar photos. They are kept on your phone only.
- Ads: the app shows ads through Google AdMob. AdMob may collect an advertising ID and related data to serve and measure ads. Vehicle information (VIN, car position, drive records) is never given to advertisers.
- Ad reward check: to confirm that an ad was watched to the end, the app puts a one-time ticket it got from our server into the ad, and Google sends it back to us. The ticket is a random value; nothing that identifies you, your phone or your car is sent to Google. When the app asks for a ticket, and when it asks for a day pass without an ad, it sends our server a random number made for that app install (install ID), which we use to count passes taken without an ad in a row and stop abuse. On iPhone this number is kept in the device Keychain, so it may stay the same after you delete and reinstall the app.
- Feedback: the category you pick and the message you send, our replies to it, device information (app version and build, platform, OS version, phone model; no vehicle information) and the install ID. We keep it to answer you, and show the replies in the app under Settings → Feedback. The phone’s recent device log (the app log of the last 24 hours, and on Android the system log of the last 6 hours), which may contain vehicle and Bluetooth identifiers, is sent only if you turn on “Also send the device log”; otherwise it never leaves your phone.
- Device: push token, app version, crash and error diagnostics.
- Website: no advertising cookies (this applies to the website only; for ads in the app see “Ads” above and “Who receives it” below). We keep a language preference in your browser.
Why we use it
To run the features you turned on, to check your day pass and show ads, to confirm ad rewards and prevent abuse, to answer your feedback, to send the alerts you asked for, to keep the service secure, and to comply with law.
Who receives it
Processors that run parts of the service under contract:
- Tesla (account sign-in) — only if you choose to fetch the VIN by signing in. One request for the list of your cars, to read the VIN; the sign-in is not kept and no other vehicle data is requested.
- Kakao Mobility (navigation SDK) — the car’s position, speed and heading while Drive Guide is on, to get the enforcement cameras and limits ahead. Nothing that identifies your account or car is sent; installs are told apart by a random value made on the phone. We do not store what Kakao Mobility returns. Republic of Korea.
- Google (Android’s built-in address lookup) — the car’s position each time it has moved 300 m or more while Drive Guide is on, to show the name of the neighbourhood on the drive screen. Nothing that identifies your account or car is sent, and we do not keep the name. United States and other countries.
- Supabase — database and sign-in, hosted in Seoul, Korea (ap-northeast-2).
- Google Cloud (Cloud Run) — API servers in the Seoul region.
- Cloudflare — website and domain.
- Google AdMob — the app shows ads through Google AdMob. AdMob may collect an advertising ID and related data to serve and measure ads. Vehicle information (VIN, car position, drive records) is never given to advertisers. Ad rewards are confirmed with a one-time ticket only. United States and other countries.
- Firebase Cloud Messaging and Apple Push Notification service — delivery of alerts.
- OpenStreetMap tile servers — map content. Tile requests reveal the map area you look at to the tile provider.
Ads and personalised ads
Vehicle information (VIN, car position, drive records) is never given to advertisers. Advertisers may collect device information such as an advertising ID.
- Android: turn personalised ads off under Settings → Google → Ads → Delete advertising ID.
- iPhone: the app asks whether to allow tracking. If you decline, the ads you see are not personalised. You can change it any time under Settings → Teslable.
How long we keep it
Vehicle signals and drive, tyre and parking records are not kept on our servers. They exist on your phone only, where the app removes drive records after 2 years, drive paths after 6 months and tyre records after 90 days. Documents and photos: until you delete them. An account with no email linked: deleted with its data 180 days after it was last used (if a subscription period is still running, after that period ends). Ad tickets: deleted a day after they expire. Feedback (message, category, device information and, if you chose to send it, the device log) and its replies: deleted 30 days after it was sent. The count of passes taken without an ad, kept per install ID: deleted a year after it was last used; if you delete your account, only the install ID and that count remain until then. Account records: while your account exists. When you delete your account, personal data is erased within 7 days except where law requires longer retention.
Your choices
You can change consents, export your data, and delete your account from Settings in the app, or by writing to privacy@teslable.app. Vehicle data collection stops whenever you unlink the car or revoke Bluetooth or location permission; the app then works with what does not need the car.
Security
Traffic is encrypted in transit. Access is logged. No system is perfect; if a breach affects you we will tell you and the relevant authority without undue delay.
European Economic Area and United Kingdom
Legal bases: contract (running the service), legitimate interest (security, product improvement), consent (marketing emails, personalised ads). You have the rights of access, rectification, erasure, restriction, portability and objection, and the right to complain to your supervisory authority. Data is transferred to the United States under standard contractual clauses.
California
We do not sell personal information, and vehicle information is never given to advertisers. Ads in the app are shown by Google AdMob, which may collect an advertising ID and related data. You can turn personalised ads off as described under “Ads and personalised ads” above. You may request to know, delete or correct your information and will not be discriminated against for doing so. Requests: privacy@teslable.app.
Korea (대한민국)
This section is the 개인정보처리방침 required by the Personal Information Protection Act and applies to users in Korea together with the rest of this policy.
- 수집 항목과 목적: 위 “What we collect” 및 “Why we use it” 항목과 같습니다. 필수 항목은 차량 식별 정보이며, 이메일은 이메일로 로그인하거나 설정에서 이메일을 연결한 경우에만 받습니다. 위치정보는 폰이 블루투스로 차와 연결된 동안 위치가 필요한 기능(주행 안내, 주행 기록, 주차 위치 기억 등)을 위해 폰 안에서만 쓰고 회사 서버로 보내지 않습니다.
- 보유 기간: 차량 신호와 주행·타이어·주차 기록은 회사 서버에 보관하지 않음(폰에만 저장). 계정 정보는 회원 탈퇴 시 7일 이내 파기. 이메일을 연결하지 않은 계정은 마지막 이용 뒤 180일이 지나면 파기. 전자상거래법 등 관련 법령이 정한 기록은 해당 기간 보관.
- 제3자 제공 및 처리위탁: 위 “Who receives it” 항목과 같으며, 국외 이전(미국, Google AdMob·FCM·Cloudflare)이 포함됩니다. 이전 항목, 국가, 시기, 방법은 앱 내 설정에서 확인할 수 있습니다.
- 위치정보: 차량 위치의 수집·이용·제공은 별도의 위치정보 이용약관에 따르며, 이용자는 언제든지 수집 동의를 철회할 수 있습니다.
- 이용자 권리: 열람·정정·삭제·처리정지 요구는 앱 설정 또는 privacy@teslable.app 로 하실 수 있습니다. 만 14세 미만은 가입할 수 없습니다.
- 개인정보 보호책임자: Owlzworks 개인정보 보호책임자, privacy@teslable.app.
Children
Teslable is for adults who own or drive a car. We do not knowingly collect data from anyone under 16 (under 14 in Korea).
Changes
We will post changes here and, for material changes, tell you in the app before they take effect.