Search & fact check with cited sources for What explains the contradiction between Meta's categorical denial in June 2026 that its NameTag facial recognition feature "does not exist" and its CTO Andrew Bosworth's detailed public description of that same system just five weeks lat

Meta's communications VP, Andy Stone, responded by arguing that the feature was not a current reality. According to reporting on Stone's defense, he pointed out that the code was "not enabled" and that Meta had no current plans to activate it . A LinkedIn post from industry analyst Matt Navarra characterized Meta's posture more bluntly: "Meta says that its face-recognition system 'doesn't exist'" . The core of Meta's defense was a semantic argument — that a dormant, unactivated feature buried in code did not qualify as a real "feature" .

The contradiction: Bosworth publicly describes NameTag in detail

Just over five weeks later, around July 8–10, 2026, Meta CTO Andrew "Boz" Bosworth gave interviews in which he explicitly described and defended the same NameTag system .

• On July 8, Bosworth described NameTag as a "local, encrypted feature used to identify people you already know" — not pulling data from a central database .
• He confirmed it would store biometric data on-device and would recognize previously-introduced faces .
• Reports note that Bosworth "defended an unreleased smart glasses feature called NameTag" and used the occasion of new product launches to explain how it would work .

In other words, Meta's CTO gave a detailed, on-the-record description of the very system that the company's communications chief had just weeks earlier denied existed in any meaningful sense.

The sequence of events

How to explain the contradiction

The contradiction is not an accident — it reflects a deliberate two-track communications strategy:

1. Legal/regulatory risk management. Meta faced intense scrutiny. In 2021 it shut down its Facebook facial recognition system and deleted over a billion faceprints after years of lawsuits . In 2024 it paid $1.4 billion to Texas alone to settle biometric privacy claims, on top of a $650 million Illinois settlement . Saying "this doesn't exist" insulates Meta from immediate legal liability and regulatory action.

2. Product development continues internally. The code shipped to 50 million phones was real, sophisticated, and engineered with two deployment variants . Bosworth's later description confirms the company fully intended to build and ship this. The denial was about the feature's activation status, not its existence — a framing that let Meta simultaneously deploy code and disclaim responsibility.

3. Semantic gamesmanship. As multiple analysts observed, Meta's communications team leaned on a narrow definition: a feature "does not exist" if it is not yet user-facing . This allows the company to deny and advance the same feature in the same quarter.

What this reveals about Meta's pattern

NameTag fits a consistent corporate pattern:

• Repeated biometric privacy settlements. Meta has paid nearly $7 billion in combined settlements for facial recognition violations in Illinois ($650M), Texas ($1.4B), and other cases . The EFF has noted this history explicitly: "Meta should already know the privacy risks of face recognition technology, after abandoning related technology and paying nearly $7 billion in settlements" .

• Ship first, disclose later (or not at all). The NameTag code was pushed to 50 million phones over months of updates before anyone outside Meta knew it existed . Researchers at the Electronic Frontier Foundation discovered it only by examining the code .

• Public denial followed by quiet retreat, then reintroduction. On June 5, Meta stripped the code after exposure . But Bosworth's July comments — describing the feature in detail and defending its privacy design — signal that the company has not abandoned the plan. It is waiting for the controversy to subside.

• Minimizing readiness while deploying infrastructure. The pattern mirrors earlier Meta AI rollouts: the company ships the supporting code broadly, denies the feature is imminent when caught, then flips the switch later. NameTag's code was engineered, tested, and distributed. Only the activation flag was missing.

WIRED itself summarized the episode aptly on July 16: "Does a software feature exist if its code has been deployed to the devices of millions of people but they can't use it yet? Not if you work at Meta" .