Rider privacy
What does a Cybercab record while you're in it?
What a Tesla Cybercab actually records during your ride, how long it is kept, and who can see it, kept separate from what is only hinted in app code.
Undisclosed. Tesla has published no rider-facing recording policy for the Cybercab that we can verify. App code does show one concrete signal: strings that wire the cabin camera to an identity check before Full Self-Driving engages, which for a robotaxi reads as confirming the rider matches who booked the trip. Those are pre-release decompile strings attributed to the app, not a shipped, Tesla-confirmed recording policy. What the Cybercab actually records during a ride, how long it is kept, and who can access it is not disclosed. This page states plainly what is code-hinted, what is a third-party reading, and what is simply unknown.
The plain rider question is simple: while you are in a Tesla Cybercab, what does it record, where does that go, and who can see it. The honest answer today is that Tesla has published no rider-facing recording disclosure we can verify. What exists instead is a small set of dated, attributed signals pulled from decompiles of the Tesla app. One wires the cabin camera to an identity check before Full Self-Driving will engage. Another describes remote-operator controls in the robotaxi app. Those are claimed-tier artifacts, useful but not settled, and they are not the same as a recording policy. Everything past them, whether video or audio is captured, how long anything is retained, whether data leaves the car, and whether you are ever asked to consent, is undisclosed. We treat that absence as the answer, not as a gap to paper over.
What actually exists today
| What people ask about | Status | The reality |
|---|---|---|
| Does a cabin camera check who is in the seat? | Code-hinted | Tesla iOS app code (an app-decompile artifact reported 2026-07-06, attributed to @Tesla_App_iOS) exposes the strings fsdIdentityCheckFailedTitle / showFsdIdentityCheckFailedDialog: a cabin-camera identity gate that must pass before FSD engages, a code hint and not a shipped, Tesla-confirmed policy. |
| Is the ride recorded on video or audio? | Undisclosed | No verified Tesla rider-facing recording disclosure found. Whether video or audio is captured during a ride is not something Tesla has published. |
| Where does in-cabin data go, and is it retained? | Undisclosed | Not disclosed. The 'shadow-mode / trains the neural net' framing is a poster's characterization, never a Tesla statement. |
| Can a remote operator see or intervene? | Code-hinted | Robotaxi-app v26.4.5 strings describe remote-operator voice calls, manual override, and a remote immobilization ('kill switch'). Reported by Tesery and Teslarati, attributed to the app, not confirmed by Tesla. |
| Does identity data leave the car for verification? | Undisclosed | Not disclosed. Whether any identity check runs on-device or sends data out for verification is unstated. |
| Is there a rider consent screen for in-ride data? | None verified | None verified for the Cybercab. By contrast, a v4.59.0 string exposes an in-home consent screen for Optimus, so Tesla ships consent UI elsewhere; none is verified for a Cybercab ride. |
See the reviewed claim in the Tesla Robotaxi claims ledger → (resolved live from the registry, dated 2026-07-06).
How to read the cabin-camera signal
One in-cabin signal is real enough to name, and it is easy to over-read. Here is the honest way to hold it. Treat all of it as claimed-tier: it comes from app code, not from Tesla.
An identity gate before FSD
App-code identity-check strings wire the cabin camera to a check that must pass before Full Self-Driving engages. For a robotaxi, the plain reading is confirming the rider matches who booked the trip.
A third-party 'shadow-mode' guess
Some commentators frame in-cabin cameras as 'shadow mode' that trains the neural net. That is a characterization by posters, not a Tesla statement, and we do not present it as one.
No recording policy
What is recorded, how long it is kept, and who can access it are simply not disclosed. The honest answer to the rider question is that Tesla has published nothing we can verify.
Claimed, not confirmed
Every in-cabin signal here is a dated, attributed app-code artifact. When Tesla publishes a rider recording policy, it becomes a dated line on this page.
What would change this
We track this question so you do not have to. Any one of these moves the answer, and each becomes a dated line on this page the week it happens:
- Tesla publishes a rider-facing recording and data-retention disclosure for the Cybercab or Robotaxi.
- A regulator requires in-cabin recording disclosure for robotaxi riders.
- A new app version ships in-ride strings that confirm what is captured, or adds a rider consent screen.
- In-cabin scrutiny tends to follow real incidents. Right now the verified record holds 5 safety incidents for the Tesla Robotaxi and Cybercab, and every new one is logged the week it lands.
How we know this
Every claim on this page is a dated, attributed artifact, and every absence is stated plainly. The in-cabin signals come from decompiles of the Tesla iOS app, attributed to @Tesla_App_iOS, never presented as a Tesla statement.
If Tesla publishes a recording policy, or if you can show us we got something wrong, our corrections process logs the response on the record.
Common questions
What does a Tesla Cybercab record during your ride?
Is there a camera inside the Cybercab watching riders?
Is my Cybercab ride recorded on video or audio?
Can a remote operator see or take over the Cybercab?
Is there a consent screen before a Cybercab ride?
Keep reading
Track this
Find out the instant Tesla says what it records.
Watch this question and we will tell you the moment Tesla publishes a Cybercab recording policy, a rider consent screen ships, or a new app version reveals what is captured. No car required.
Canonical URL: /home-robots/cybercab-recording · machine-readable mirror: /home-robots/cybercab-recording.md