Helixtrip

Legal

Privacy policy

What Helixtrip collects, why, for how long, and how to take it all back.

Last updated: 22 November 2026

1. Who we are

Helixtrip (“we”, “us”) is operated by Pavel Misko, Poland, and is the controller of the personal data described here under the EU General Data Protection Regulation (GDPR). Contact: whitebox.ps@gmail.com.

Helixtrip is an independent service. It is not affiliated with, endorsed by or sponsored by Tesla, Inc. Tesla, Inc. remains a separate controller of your Tesla account and of the data it holds. See Tesla’s own Customer Privacy Notice for that. Tesla may use information submitted to it in accordance with that notice, and if this policy ever conflicts with the notice about Tesla’s own processing, Tesla’s notice applies.

2. In short

  • You sign in on Tesla’s page (auth.tesla.com). We never receive or store your Tesla password.
  • We ask for four permissions and use them for one purpose: wake your car and send it a destination you chose.
  • We do not read your car’s location, driving data, charging data or profile.
  • We do not sell data, show ads, run analytics trackers, profile you or train AI models on your data.
  • You can revoke access and delete your account at any time.

3. Data we process

DataWhyLegal basisKept for
A one-way hash of your account identifier (the pseudonymous “subject” ID from sign-in) and your regionRecognise your account and use the right regional serviceContract (Art. 6(1)(b))Until you delete your account, or 90 days after your last use
Your consent record (version and time) and the list of permissions you grantedShow you what you agreed to and prove consentConsent (Art. 6(1)(a)) and legal obligationUntil you delete your account
OAuth access and refresh tokens (encrypted)Act on your behalf with Tesla’s vehicle servicesContract (Art. 6(1)(b))Access tokens last a few hours. Refresh tokens are replaced on every refresh. All deleted with your account
Vehicle list: VIN, display name, awake/asleep stateShow your cars and address commandsContract (Art. 6(1)(b))Cached while your account exists, refreshed at sign-in
Destinations you send or save: text, and coordinates when availableDeliver them, show history and favoritesContract (Art. 6(1)(b))History 30 days. Favorites until you remove them
Suggestions received through a drop link: the place and an optional sender name typed by the senderLet you approve a destination from someone elseContract (Art. 6(1)(b)). The sender is told this on the link pageUntil you approve or dismiss, at most 14 days
A daily counter of sends per accountFair-use and cost controlLegitimate interest (Art. 6(1)(f))Replaced every day
IP address and browser type in server logsSecurity and debuggingLegitimate interest (Art. 6(1)(f))30 days
Session cookieKeep you signed in on this deviceStrictly necessaryBrowser session, or up to 14 days if you choose to stay signed in

We do not collect precise location from your browser or your car. The coordinates we keep are those of places you choose as destinations. We do not analyse destinations, and we do not use them to infer anything about you, including sensitive information such as health, religion or political views. When you type a place, the text is used to look up matching places (see section 9).

4. Permissions we request

Helixtrip requests only these permissions (OAuth scopes) from Tesla. You see and approve them on Tesla’s sign-in page.

ScopeWhat we use it for
openidSign you in and obtain your account identifier.
offline_accessReceive a refresh token so you do not have to sign in for every destination.
vehicle_device_dataList your cars and check whether each is online, asleep or offline.
vehicle_cmdsWake a sleeping car and send a navigation destination. Tesla groups all commands in this one permission, so it is broader than our use. Our servers only ever call the wake and navigation actions. No other command is implemented.

We deliberately do not request vehicle_location, vehicle_charging_cmds, user_data, or any energy product permissions.

Data obtained from Tesla is used only to provide the feature you asked for. We do not share it with third parties, and we do not use it for advertising, profiling, creditworthiness, insurance or any purpose unrelated to sending destinations to your car.

Before you are sent to Tesla’s sign-in page, Helixtrip shows you what it will process and asks for your explicit consent. We store the version and time of that consent. In the app, Account, then Permissions and consent, shows the permissions we hold and your consent record, lets you download your data, and links to Tesla’s page where you can revoke access. You can withdraw consent at any time by revoking access and deleting your account. Withdrawing does not affect processing that happened before. We will not widen what we process without asking for your consent again.

6. How data is kept

  • Stored data, including history and favorites, is encrypted at rest with AES-256-GCM, and tokens are additionally bound to your account. The key is held in a secrets manager or in the server environment, never in the data file or in source code.
  • Tokens are decrypted in memory only for the moment of an API call.
  • Refresh tokens are single-use. We store the replacement at once and discard the old one.
  • If Tesla reports that access was revoked or the password was reset, we delete the stored tokens and ask you to sign in again.
  • Tokens are never written to logs or sent to your browser. Your browser holds only an opaque session cookie.

7. What we never do

  • We never store your Tesla password or two-factor codes.
  • We never unlock, start, or drive your car, we never read where it is, and we never send anything to it that you did not choose.
  • We never use data from your account for anything other than the feature you asked for.
  • We never sell, rent or share your data for marketing.
  • We never use third-party advertising or analytics cookies or pixels.

8. Retention

History is deleted after 30 days and server logs after 30 days. If you do not use Helixtrip for 90 days, we delete your tokens and account data. If you delete your account, everything in the table above is erased immediately, except encrypted backups, which expire within 35 days. In any case we delete or update personal data obtained through your car account within 30 days when we no longer need it for the feature, when we stop operating Helixtrip, when you ask, when Tesla asks us to, or when the law requires it.

9. Who else sees data

RecipientRoleWhat they receive
Tesla, Inc. (sign-in and vehicle services)Independent controllerYour sign-in, the requests we send and the destination, as needed to deliver them. Tesla may also collect information about how our application uses its services. Governed by Tesla’s Customer Privacy Notice.
Hosting provider in the EU/EEAProcessorStored data described above, encrypted where stated.
Geocoding service (self-hosted open-source Photon with OpenStreetMap data, on our EU servers)Our own systemThe text you type in the search box, without your account identifier.

We disclose data to authorities only when the law requires it. Accounts in Europe use Tesla’s Europe, Middle East and Africa region, and accounts in North America and Asia-Pacific use the North America region. Our servers are located in the EU/EEA. Where your data moves to a country outside the EEA (for example when a US account is served), the transfer is necessary to perform the service you requested (Art. 49(1)(b) GDPR).

10. Your rights

Under the GDPR you may request access to your data, correction, erasure, restriction, portability and object to processing based on legitimate interests. Email whitebox.ps@gmail.com. We answer within one month. You can delete your history, favorites and entire account yourself in the app, and download your data from Account, Permissions and consent. Tesla does not answer requests about data we hold. Send them to us.

You may complain to the supervisory authority. In Poland this is the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl, or to the authority in your own country.

11. Revoke access or delete your account

  1. Revoke at Tesla. Open auth.tesla.com/user/revoke/consent and remove Helixtrip. This invalidates our tokens immediately. You can also review third-party apps in the Tesla mobile app under Security & Privacy.
  2. Remove the virtual key (if you added one). On the car’s touchscreen, open Controls, then Locks, and delete the Helixtrip key.
  3. Delete your Helixtrip data. In the app choose Delete account and data, or email whitebox.ps@gmail.com from an address you can verify.

12. Cookies

Helixtrip sets one first-party cookie, ht_session, which keeps you signed in. It is strictly necessary and is marked HttpOnly, Secure and SameSite=Lax. We do not use analytics, advertising or social media cookies, and we load no third-party scripts, fonts or trackers. The demo stores sample history in your browser’s local storage only.

13. Security

All traffic uses HTTPS. Tokens are encrypted at rest. Access to production systems is limited and logged. Requests are rate-limited. If a breach affects your data, we will notify the authority within 72 hours where required and inform you without undue delay if there is a high risk to you. If we suspect a security incident involving data obtained through your car account, we will tell Tesla without delay and cooperate with it. Report vulnerabilities to whitebox.ps@gmail.com.

14. Children

Helixtrip is for people who hold a Tesla account and are at least 16 years old. We do not knowingly process data of children.

15. Changes

If we change what data we collect or why, we will update this page and the date above, and tell signed-in users in the app before the change applies.

16. Contact

Pavel Misko, operator of Helixtrip. Privacy, support and security reports: whitebox.ps@gmail.com