Castla mirrors your phone's screen to the web browser that already runs on your car's display. This policy explains what we collect, why we collect it, who processes it for us, how long we keep it, and what you can ask us to do about it.
The most important thing comes first: we never record or store the picture or the sound from your screen. The live stream passes through a media server and is never written to disk. Nobody at Castla can watch it, then or later.
Who we are
Castla is the service described on this website and in the Castla mobile apps. For anything in this policy, write to [email protected].
Castla is an independent product and is not affiliated with Tesla, Inc.
What we collect
Your account
Castla accounts are anonymous and tied to a device, not to a person. When you first open the app we create an account from:
- a device identifier generated by the app
- the platform (iOS or Android)
- the app version
- the device model
We never ask for your first or last name.
You can optionally link an Apple or Google account, so your subscription follows you to a new phone. If you do, we store the account identifier that Apple or Google gives us and the e-mail address attached to it. Nothing else comes from that sign-in.
Your setup answers
If you complete the short questions when you first open the app, we store your answers: your car model, what you plan to use Castla for, when you expect to use it, and your language.
Pairing records
When your phone pairs with the receiver page open on your car screen, we store that the pair exists. This is what lets your phone find the car again without a new QR scan.
Streaming sessions — metadata only
For each mirroring session we store metadata about the session: when it started, when it ended, how long it lasted, whether it succeeded, and the car model.
We do not record, store or have any access to the content of your screen or your audio. The media stream travels through a LiveKit SFU server and is never written to disk. Session metadata tells us that a session happened and whether it worked. It tells us nothing about what was on the screen.
Purchases
Subscriptions are handled through Adapty, which sits in front of the App Store, Google Play and Stripe. We store the transaction identifier, the amount, the currency, the store the purchase came from, the relevant dates, and — for card payments — your Stripe customer identifier.
Your card details never reach us. They are handled entirely by Apple, Google or Stripe.
Notifications
If you allow notifications, we store the Firebase Cloud Messaging token of your device, which is what lets a notification reach that device.
Support
When you contact support we store your request and the messages exchanged in it.
Analytics and diagnostics
- Mixpanel — product analytics: which screens are opened, which features are used, where a flow is abandoned. Our Mixpanel data is processed on Mixpanel's European servers (api-eu.mixpanel.com).
- Adjust — install attribution, so we can tell which campaign or link brought you to Castla. On iOS we ask for your permission first, through Apple's App Tracking Transparency prompt. If you decline, no identifier is shared for tracking.
- Sentry — crash and error reports, so we can find and fix what breaks.
Why we use it
- To run the service. Your account, the pairing records and the live session are what make "open the page in the car, and your phone finds it" work at all.
- To unlock what you paid for. Purchase and subscription records are how the app knows your subscription is active.
- To keep it working. Crash reports and session results tell us when mirroring fails — on which cars, on which platform, after which app version.
- To improve it. Aggregated analytics tell us which features are actually used and where people get stuck.
- To answer you. Support messages are kept so a conversation can continue over several days.
We do not sell your personal data.
Who processes data for us
- LiveKit — carries the live media stream between your phone and your car. Nothing is stored.
- Adapty — subscription management, on top of the stores below.
- Apple App Store, Google Play and Stripe — payment processing. Card details stay with them.
- Mixpanel (European servers) — product analytics.
- Adjust — install attribution.
- Sentry — crash and error reporting.
- Firebase Cloud Messaging — notification delivery.
Our own infrastructure — the LiveKit media server, MongoDB and Redis — is hosted in Germany, at Hetzner.
How long we keep it
- Account, provider links, pairing records, subscription record — for as long as your account exists.
- Streaming session metadata — at most 90 days, after which it is deleted automatically. What remains past that point is a daily count that carries no account identifier.
- Purchase records — kept after an account is deleted, but detached from the account, because tax and accounting rules require a record of the transaction itself.
- Support messages — for as long as needed to handle the request and anything that follows from it.
- Crash reports and analytics — according to the retention settings of Sentry, Mixpanel and Adjust.
Your rights
Depending on where you live, you have the right to ask for access to your data, correction, deletion, restriction of processing, portability, and to object to processing. To exercise any of these, write to [email protected].
Two of them you can exercise directly, without asking anyone:
- Deletion from the app. Delete your account from inside the Castla app.
- Deletion from the web. Sign in with Apple or Google at castla.app/account-delete and delete your account there.
Deleting your account removes your account record, your Apple and Google links, your device records, your pairing records, your notification tokens, your support requests and your subscription record. Purchase records are detached from your account rather than erased, for the accounting reason above. Session metadata is deleted on its own 90-day schedule.
Deleting your Castla account does not cancel a subscription bought through the App Store or Google Play. Those must be cancelled in the store's own subscription settings. See our Terms of Service.
If you believe we have handled your data badly, you can complain to the data protection authority where you live.
Children
Castla is not directed at children. It is a tool for adults who drive: it has no user-generated content, no feed, no profiles and no messaging between users. We do not knowingly collect data from children. If you believe a child has created an account, write to us and we will delete it.
Our separate Child Safety Standards page sets out our position on child sexual abuse and exploitation, and how to report a concern.
Changes to this policy
If this policy changes in a way that matters, we update the date shown at the top of this page and, where the change is significant, tell you in the app.
Contact
Write to [email protected] about anything in this policy.