Hidden code in Tesla's app, corroborated by multiple outlets, shows Tesla is building an identity gate for Full Self Driving — the next surface in a years long migration of age and identity verification from phone screens into the physical world.
Tesla's cabin camera has spent the last several years watching its drivers without announcing itself. Mounted above the rearview mirror in every Model 3 and Model Y built since roughly 2021, the small lens tracks drowsiness, head position, and eye gaze so the car can tell when a driver is paying attention. Hidden strings in Tesla's iOS app, spotted by a third-party code analyst and not yet shipped, suggest the camera is being prepared to take on a second job: matching the driver's face to an authorized profile before Full Self-Driving (Supervised) will switch on. Tesla has not confirmed the feature exists.
The strings, first surfaced by the long-running Tesla-app code analyst @Tesla_App_iOS and corroborated independently by Electrek, Drive Tesla Canada, and Gizmodo, are called fsdIdentityCheckFailedTitle and showFsdIdentityCheckFailedDialog. Read together, they describe a feature that would block Full Self-Driving from activating until the in-cabin camera could confirm the driver's face matches an authorized profile. If it could not, the app would surface a failure dialog.
Per Electrek, even if it does ship, the rollout could take weeks or months and would require a vehicle firmware update, and Tesla could still decide to shelve it. What the strings do is tell engineers and outside watchers what the company appears to be building: an identity gate for one of its most expensive optional features, run by a sensor that has been in the car for years.
That matters because identity verification has spent the last two years migrating. Age-verification rules have spread across jurisdictions including the UK, Australia, Brazil, and several US states, pushing the practice out of niche adult sites and onto mainstream platforms, where it usually lives on a phone screen. A vehicle cabin is a different surface. The hardware is already there. The data path is already there. The regulatory framing is still catching up.
For Tesla, the second job also has a clear business reason. Full Self-Driving is sold as a subscription that can be transferred or shared across drivers in a household, and as a one-time purchase on some trims. An identity check would make that access harder to lend out, which is what the company sells and what it loses when a non-account-holder takes the wheel. The strings do not tell us whether Tesla would treat identity verification as a hard block or as a periodic re-authentication, but the existence of a failed dialog implies at least one mode in which the answer is no.
A false positive could lock an authorized driver out of FSD mid-trip, a meaningful problem on a feature the driver has already paid for. Accessibility matters too: drivers whose face changes (a new haircut, a medical condition, glasses, aging) would face a recurring friction that other Tesla drivers would not. And the privacy cost is concrete. The same always-on interior sensor that has been building a profile of how alert you are while driving would, under this design, also be doing face matching, and the failure case would be recorded without surfacing in the cabin.
None of that is a reason to assume Tesla is rolling the feature out, or to treat code strings as a launch announcement. The strings are a hint, and one that, taken with the broader age-verification wave, suggests the next surface for identity matching is the inside of the car.