PhoneToCar

PhoneToCar privacy policy

Version 12 · 19 November 2026

1. The short version

  1. What your car shows goes from your phone to your car over your hotspot or Wi-Fi, not over the internet. It reaches us only if you send a problem report: a report includes a picture of your screen, unless you remove it.
  2. No accounts and no ads. PhoneToCar sends us a problem report only when you tap Send report. Our website counts visits with Cloudflare Web Analytics, without cookies, but not for visitors in the EU or the wider European Economic Area (section 8). PhoneToCar never sends us your location or your speed. We don't sell your information or share it for advertising.
  3. We get information only as described below.

2. Who we are

PhoneToCar is made by Alexander Ostrikov ("we", "us"), a private individual, not a company. We are responsible for the information described here (the "controller"). On Google Play the developer is shown as SuperSova. Contact: support@phoneto.app.

3. On your phone

  1. While PhoneToCar is casting, anyone on your phone's hotspot or tethering who opens its address, or on other Wi-Fi once you allow their browser, can see the screen PhoneToCar casts, including any personal information on it, and control it: in Mirror phone, your phone's own screen; in Additional screen, the car's screen and the apps on it. Keep your hotspot's password private, use a hotspot only you and your car use, and stop casting when others are on the network.
  2. Accessibility: only to do on your phone the taps and swipes you make on the car's screen, and, in Mirror phone while casting, for the drive lock: to see which app is open and to control the phone's keyboard while the drive lock limits typing. It doesn't read your screen, what you type or your notifications. An app's name reaches us only in a declaration (section 6) or a report you send (section 4).
  3. Location: for the drive lock, only while PhoneToCar is casting (including when PhoneToCar isn't open on your phone's screen), to tell whether the car is moving. Your location and speed stay on the phone and are never sent to us, not even in problem reports. A declaration records only what the drive lock concluded (section 6.3). A screen picture in a report can still show a map; you can remove it. With location allowed, PhoneToCar also keeps your Wi-Fi network's hardware address on your phone, to recognise the Wi-Fi where you allowed wireless debugging.
  4. VPN: only while PhoneToCar casts, and only to give your phone an address that the car's browser can open. None of your internet traffic goes through it, it connects to no server, and it reads and collects nothing. Android allows one VPN at a time, so while PhoneToCar's VPN is on, any other VPN on your phone is off.
  5. Wireless and USB debugging (Additional screen): to start a helper that works only on your phone, with Android's shell (debugging) rights, which are stronger than an ordinary app's. With them, PhoneToCar can change some protected Android settings. It uses this to turn wireless and USB debugging on and off, turn on your hotspot and keep the screen awake while casting, and puts the screen settings back afterwards. It isn't used to give PhoneToCar Accessibility or location permission, or to turn Location on. The drive lock also uses the helper, on the phone, to see which app is open on the car's screen (or in front, in Mirror phone; without the helper, Accessibility tells it), whether an app asked for the keyboard, how often each side's picture changes, and, while casting with no screen of PhoneToCar's in use, to start its location (only if you allowed it, item 3.3). After a restart, when the phone is on Wi-Fi, PhoneToCar can turn on wireless debugging for a moment to start the helper again. If USB debugging is turned off, PhoneToCar asks before turning it on again, unless you chose otherwise in its settings. On some phones, it first switches it on for a moment to check whether a setting turned it off.
  6. Also: screen sharing, for Mirror phone; Bluetooth, only for "Start with my car"; local network, so the car and the setup can reach your phone; and notifications. PhoneToCar doesn't use the microphone.
  7. Your settings, cars, chosen apps, drive days, purchase state and acceptance of the Terms are kept on your phone, not in Android's cloud backup. They come to us only in a problem report you send (for your acceptance, declarations and purchases, see sections 6 and 7).
  8. Apps and the picture: PhoneToCar reads the names and Android categories of the apps on your phone, to show Choose apps and to apply the drive lock. To spot video, it measures on the phone how much the car's picture changes and checks which apps are playing video; it doesn't look at what the picture shows. These stay on the phone, except app names in a declaration (section 6) or in a report you send.

4. Problem reports

  1. A report is sent only when you tap Send report in "Report a problem". It holds what you write; a picture of your screen, which can show other apps (you can remove it); pictures you add, saved again without hidden details such as a photo's location; your phone's maker, model and Android version; and PhoneToCar's version, state and recent logs.
  2. The logs can include your car's Bluetooth name, the car browser's version, your phone's certificate name and how getting its certificate went (never the secret in item 5.3), your trial and purchase state, the names of apps open on the car's screen or in front on your phone, and the private network addresses your phone and car use on your hotspot or Wi-Fi, which show how they connect. They hold no hardware addresses (such as Wi-Fi or Bluetooth addresses), no internet addresses, and no location or speed. PhoneToCar does not read your contacts, messages or files (except pictures you add). A screen picture can still show a map, and Sentry works out a city and country from your internet address (section 4.3).
  3. Sentry (Functional Software, Inc.) stores reports for us in the United States, and deletes them after 30 days. When a report arrives, Sentry works out the city and country from your internet (IP) address and stores them with it, but not the address itself. It emails us the report's title (your first line) and details such as the phone model.
  4. We use reports only to fix problems. We delete one sooner if you ask (say roughly when you sent it), and the email notices once we no longer need them.

5. The car's certificate

  1. So that the car's browser can open your phone at a secure (HTTPS) address, PhoneToCar registers with our service at api.phoneto.app, gets a random name such as 5dtef, and gets and renews a certificate for it. This starts at the end of Additional screen's setup, or the first time you cast or your car connects by Bluetooth, whichever comes first. Certificates come from Let's Encrypt or, when Let's Encrypt has no room, from ZeroSSL for a phone that passed the check in item 5.5.
  2. Your phone sends our service the PhoneToCar version, technical settings, and a one-time code that proves the name is your phone's. Like any web request, it also carries your internet address and your phone's model and Android version. The code is in a public DNS record for up to 15 minutes, and Cloudflare's audit log keeps that record's name and time for 18 months.
  3. Our service keeps the name for good, so a name is never given twice. It also keeps a hash (a scrambled form) of a secret that only your phone keeps, the version, its certificate settings (which certificate authority it uses, and whether it is a developer build) and two dates, until you ask us to delete them (section 10.3). To limit misuse, it keeps a hash of your internet address for 1 day, and the times certificates were asked for, for up to 7 days.
  4. Let's Encrypt, or ZeroSSL, receives the name, your phone's public key and internet address. ZeroSSL's certificates are issued by Sectigo, which gets the name and the public key. Every certificate is published in public Certificate Transparency logs, where it can't be removed. Private keys never leave your phone; the name says nothing about you. Reinstalling or clearing PhoneToCar's data gives your phone a new name.
  5. When PhoneToCar from Google Play asks for your phone's first certificate, it also sends our service a one-time Google Play Integrity token, made from your certificate name in a way that doesn't show the name to Google. Our service may send the token to Google, which tells it whether PhoneToCar came from Google Play and whether your phone passes Google's checks. Our service gets no device identifier. It keeps only whether the check passed, with your certificate name, until you ask us to delete it (section 10.3). It uses this only to keep the limited number of new certificates for PhoneToCar on real phones, not for scripts. Without Google Play, or if the check fails, your phone still gets a certificate when there is room.

6. Your acceptance and declarations

  1. When you tick the box and tap I agree, PhoneToCar keeps on your phone which version of the Terms of Use you accepted, and when.
  2. It also sends our service a record of your acceptance: a random install ID made by the app, the Terms version, a SHA-256 fingerprint of the Terms text you were shown, its language, the PhoneToCar version, and the time by your phone's clock. Our service adds the time it received the record. The install ID isn't made from anything about your phone or you, and we don't link it to your certificate name, except in a deletion request you send us (section 10.3). But it stays the same until you reinstall PhoneToCar or clear its data, so it ties together every acceptance and declaration from that install, for as long as we keep them (item 5).
  3. Each time someone taps "I'm not the driver" or "I'm parked: unlock" on the car's screen, or turns "Allowed while driving" on or off for an app on the phone (Terms of Use, section 4), PhoneToCar sends our service a record of that declaration: the install ID, the app or apps it was for (in Mirror phone without Additional screen's helper, only the kind of app as the drive lock sorts it, such as navigation, audio, video or games, not its name; or that it wasn't known), the time by your phone's clock, the Terms version with its fingerprint and language, the PhoneToCar version, which words were shown, where it was made (the car's screen or the phone, not your location), and what the drive lock concluded then, as a category only, such as stopped, moving or unknown. Our service adds the time it received the record.
  4. Our service doesn't store your internet address, or any form of it, with these records.
  5. We keep these records to prove what you accepted and declared, if there is ever a dispute (our legitimate interests, section 10). We also count the declarations, together, to see how the drive lock's buttons are used and to improve it. Acceptance records are kept in our service's database at Cloudflare, in backups in Cloudflare R2 storage and in a private offline copy, for 6 years after your latest acceptance from that install. Declaration records are kept in the database for 90 days, and in the R2 backups and the offline copy for 6 years after your latest declaration from that install. We chose 6 years because it is a usual time limit for claims about a contract, and we review it every year. The R2 backups are set so that they can't be routinely deleted or changed during those 6 years; the account owner can change that setting. We use the backups only to restore our service, or where a legal claim needs them. The offline copy is on a computer we control, in the country where we are based. We keep records longer only while a legal claim that needs them is under way.

7. Purchase

  1. Google Play takes the payment; we never see your payment details. PhoneToCar keeps on your phone only whether you bought it (or a payment is pending) and the price last shown. Google Play's billing library in PhoneToCar also tells Google whether its requests succeed. In Play Console, Google shows us each order's number, date, product, price, phone model and the buyer's country (in some countries also city and postcode), and lets us search orders by the buyer's email, for refunds and taxes.

8. Our web pages and email

  1. car.phoneto.app, the address you open in the car, is a small page that sends the car's browser on to your phone. It, our website phoneto.app and our service run at Cloudflare, which receives the internet address, browser type and time of each request to them, and answers lookups of your phone's name. Our web pages, car.phoneto.app included, use Cloudflare Web Analytics to count visits and see how fast pages load, but not for visitors in the EU or the wider European Economic Area (EEA), or whose country isn't known. For other visitors, a small script on each page sends Cloudflare the page's address (without the part after "?"), the site you came from, your browser, operating system and type of device, your country, and how long the page took to load. It uses no cookies or other storage on your device, and Cloudflare says it doesn't use it to track people across websites or over time. We see only totals. Cloudflare keeps the detailed records for 7 days and a sample of them after that; we can see the last six months. You can stop it at any time with "Don't count my visits" on this page: your browser then keeps that choice in a cookie for 400 days (renewed on each visit), and nothing else, and the script isn't added for you. Content blockers usually stop the script too. The analytics aren't in the app, and aren't on the page your phone shows the car. Our pages don't respond to "Do Not Track" signals.
  2. If you write to support@phoneto.app, we get your email address and message, and use them only to answer you. Cloudflare forwards it to our Gmail (Google). We keep emails while we need them to help you.

9. Who receives information

  1. Only these services, plus the public records in section 5 and the legal cases at the end of this item: Sentry (reports), Cloudflare (web pages and their analytics, our service, email, backups), Google (Google Play, Play Integrity, Gmail), Let's Encrypt, ZeroSSL and Sectigo (certificates). Sentry and Cloudflare process information for us, under their data-processing terms, and ZeroSSL processes it for us, as its privacy policy says. Google (Google Play, Play Integrity, Gmail), Let's Encrypt and Sectigo handle it under their own terms and privacy policies. Google Play also gives us install numbers, crash reports from phones that share them with Google, and reviews you post. We may also give information, including your acceptance and declaration records, to courts, authorities, lawyers, insurers and other parties to a legal claim, where needed to establish, exercise or defend legal claims, or when the law requires it. These records can be used in a dispute with you or with someone else, for example after a crash.
  2. Sentry (which stores reports) and Let's Encrypt are in the United States. Cloudflare and Google run on worldwide networks, including in the United States and the EU. Sentry, Cloudflare and Google take part in the EU-U.S. Data Privacy Framework and its UK extension. Let's Encrypt doesn't. ZeroSSL is in the EU; it hosts with Amazon Web Services and may move information outside the EEA, including to the United States, with the safeguards its privacy policy names. Sectigo, which issues ZeroSSL's certificates, is in the United Kingdom and may pass information outside the EU to validate and issue certificates. Your phone connects to Let's Encrypt or ZeroSSL directly, at your request, to get your certificate, and sends it only what it needs: your internet address, the name and your phone's public key. Where sending it to Let's Encrypt, or Sectigo's issuing it, counts as a transfer, we rely on it being necessary for the service you asked for (GDPR Art. 49(1)(b)).

10. Legal bases, your rights

  1. Problem reports: your consent, which you can withdraw by asking us to delete your report. Reports are optional.
  2. The certificate and the purchase: to provide what you asked for. Order details in Play Console: also to keep the records tax law requires, for as long as it requires. Hashed addresses, the certificate's Play Integrity check (section 5.5), your acceptance and declaration records, our web pages and emails: our legitimate interests in protecting our service, proving what you accepted and declared, improving the drive lock and defending legal claims, running our web pages, counting visits to our website from outside the EU and the EEA and how fast it loads (Cloudflare Web Analytics; you can stop it with "Don't count my visits", section 8), and answering you. Accepting the Terms is needed to use PhoneToCar, and a declaration is part of each confirmation you make to the drive lock. Location for the drive lock: our legitimate interest in reducing driver distraction. Android asks for your permission first; that permission isn't the legal basis, and you can refuse it or object. Your location and speed never leave your phone.
  3. You can ask us for a copy of your information, to correct or delete it, to limit or object to its use, or to receive it in a portable form: write to support@phoneto.app. To ask us to delete your information, use Settings › About › Delete my data in PhoneToCar. It writes an email to us with your install ID, your certificate name, and a short code that shows the request comes from your phone, so nobody else can delete your phone's registration. Only that email links your install ID to your certificate name. Delete your data explains what we delete and what we keep. We answer within one month, and if we refuse, we say why. We can't find your certificate name or acceptance and declaration records from your name or email alone. Even if you ask us to delete them, we keep your acceptance and declaration records for the time in section 6, because we need them to establish, exercise or defend legal claims, and our reply says so.
  4. You can also complain to the data protection authority where you live or work.
  5. You can object at any time to our use of your information based on our legitimate interests. We then stop, unless we have compelling legitimate grounds, or need it for legal claims.
  6. We don't sell your information or share it for cross-context advertising. Where a privacy law gives you rights to know, access, correct or delete your information, or to use an authorised agent, write to us. We won't treat you differently for using them.

11. Safety, children, changes

  1. Everything PhoneToCar sends to us and to the services above is encrypted (HTTPS). Keys and secrets made on your phone stay in PhoneToCar's private storage, not backed up. Our service stores your phone's secret only as a hash. When we delete something from our service, a copy can stay in its database's restore history at Cloudflare for up to 30 days, and in our offline copy (section 6.5), which keeps weekly copies of the database, for up to 8 weeks.
  2. PhoneToCar is only for adults (Terms of Use, section 2). We don't knowingly receive children's information.
  3. We post changes here, with a new version number and date.