Meta executives claimed that a controversial facial recognition feature didn’t “exist.” Fast forward a few weeks later, and they’re describing the feature in public — and in detail.
In June, a Wired investigation revealed that Meta had quietly infused unreleased facial recognition tech into its “AI Glasses,” the tech giant’s chatbot and camera-equipped smart glasses. While the feature, dubbed NameTag, was inaccessible to consumers, it was designed to register faces encountered by Meta glasses wearers “into unique biometric signatures, commonly known as faceprints, and check each one against faceprints stored on the user’s phone,” according to the magazine.
It’s safe to say that Meta executives were furious after Wired published its investigation. After all, the company has a long track record of data privacy violations. The revelation that its “pervert glasses,” as some have taken to calling Meta’s controversial smart glasses, could soon be using facial recognition tech — not unlike the eyewear being used by Immigration and Customs Enforcement (ICE) agents — fueled an existing PR disaster.
Andy Stone, the tech giant’s spokesperson and VP of communications, declared on X that Wired’s reporting was “intellectually dishonest” and “advocacy-driven click bait.” What’s more, according to Stone, NameTag was fully nonexistent.
“Here’s a thing: Wired reports Meta didn’t answer several questions about how this will work,” Stone added in a follow-up post. “How could we? The feature doesn’t exist!”
In response to Stone, another Meta executive, chief technology officer Andrew “Boz” Bosworth, jumped in.
“Incredibly misleading from Wired,” he wrote. “Absolutely dishonest.”
Yet despite company leaders reassuring us that the feature doesn’t exist, Bosworth discussed it in detail during an interview with The Atlantic CEO and podcaster Nick Thompson. Bosworth’s comments in the interview, which was published last week, seemingly contradicted his fellow executives, revealing that the feature did indeed exist.
NameTag, Bosworth told Thompson, would be “encrypted locally to your device,” and would catalog people who smart glasses wearers “met in person, with your glasses on, who introduced themselves, or you said, ‘okay, this is David, remember this person.'”
This information is “only available to you, when you are wearing your glasses,” Bosworth added. He emphasized that the data captured by NameTag wouldn’t be stored in a centralized database.
“This is a person you’ve met before. Here’s their name. They’re right in front of you. That’s… what we call a NameTags feature,” said Bosworth. “I think people get confused because they hear face recognition and they think, ‘oh, there’s a central face database that everyone’s being scanned constantly into.’ It’s not that.”
In addition to supporting blind or low-vision smart glasses wearers, said Bosworth, NameTag could solve what Meta calls “the cocktail party problem,” saving wearers from any awkwardness that may arise when encountering people at parties who they’re sure they’ve met before, but can’t quite place.
“It’s a very universally human problem,” Bosworth said. “Nearly every human I talk to, no matter what their status of their vision or their memory, understands that this is a problem that would help them feel more comfortable in social situations if they had it.”
To be clear, Wired never suggested that the facial recognition feature it uncovered was being used to build a “central face database” by way of Meta’s smart glasses. Indeed, in line with what Bosworth said in the podcast appearance, Wired reported that “code discreetly added to Meta’s AI app over multiple updates this year shows that the feature, internally called ‘NameTag,’ identifies people captured by the glasses’ camera and, when activated, alerts the wearer when it recognizes someone.” The story also repeatedly noted that the feature was unreleased and inaccessible to glasses wearers.
When journalists and others called out the contradiction between Meta’s past and recent statements, Stone — the comms executive who said that Wired couldn’t answer questions about the feature because it “doesn’t exist” — jumped back in the comments section.
“We have said for months we’re exploring such features, even as nothing has shipped to consumers,” the spokesperson said in response to a post by The Intercept journalist Sam Biddle. “No secret there despite the conspiratorial thinking.”
There’s a big difference between a feature not existing and a feature that exists — if still unfinished — and has yet to be released. Meta appears to be arguing that if a feature remains inaccessible to consumers, it’s technically nonexistent, even if the company has gone as far as to issue multiple updates inserting code for the feature into products that are already in consumers’ hands. (Meta quietly deleted the NameTag code after its existence was made public.)
During the podcast interview, Bosworth took care to emphasize that Meta is considering the privacy implications of a facial recognition-powered feature like NameTag. He noted that it’s likely illegal in states like Illinois and Texas, and that it “has to be done in a way that people feel comfortable.”
Meanwhile, Meta continues to fight an ongoing consumer harm lawsuit, prompted by an investigation by a pair of Swedish newspapers. The publications found that Meta collected recordings by smart glasses wearers and passed them along to human data labelers, despite promising consumers that their recordings would be stored only on their devices.
“Designed for privacy,” reads a webpage for Meta’s smart glasses, “controlled by you.”
More on Meta’s smart glasses: Meta Furious Over Bombshell Smart Glasses Revelation
Facts Only
* Meta executives claimed a facial recognition feature did not exist.
* A Wired investigation revealed unreleased facial recognition technology was infused into Meta’s "AI Glasses."
* The feature, named NameTag, was designed to register faces encountered by wearers into biometric signatures ("faceprints").
* NameTag checked these faceprints against those stored on the user's phone.
* Spokesperson Andy Stone stated that NameTag did not exist and reported were "intellectually dishonest."
* Chief Technology Officer Andrew Bosworth discussed NameTag in an interview, detailing its local encryption and function.
* Bosworth stated NameTag would catalog people met in person with the glasses on who introduced themselves or were recognized.
* Bosworth asserted that data was only available to the wearer when wearing the glasses.
* The feature was intended to help smart glasses wearers manage social encounters.
* Wired reported internal code identified faces and alerted wearers upon recognition.
* Meta reportedly deleted the NameTag code after public revelation.
Executive Summary
Full Take
The narrative presents a fundamental tension between corporate denial and internal disclosure regarding advanced technology deployment, highlighting the strategic disconnect between official statements and operational realities. The contradiction exposed suggests that asserting non-existence serves a function distinct from factual truth—it functions as a control mechanism to manage public perception, especially concerning features with significant privacy implications. The feature's existence, detailed by Bosworth, focuses on local processing and immediate utility, positioning the technology as solving a social problem rather than creating a centralized surveillance infrastructure, which Meta attempts to frame the narrative around. This divergence points toward a pattern where companies employ semantic framing—claiming absence versus admitting evolution—to manage liability while simultaneously moving forward with implemented functionality. The fact that the system was internally developed and subsequently deleted suggests an attempt at retroactive containment following public exposure, rather than a genuine cessation of development. The implication for user agency centers on whether internal operational decisions supersede public accountability, particularly when features perceived as invasive are selectively revealed based on the audience's receptivity to risk.
Bridge Questions: If features that are technically implemented but unreleased remain inaccessible, what is the ethical responsibility regarding their gradual introduction? How does the calculated deletion of code affect trust more than the initial revelation of existence? What governance structures are necessary to reconcile internal development practices with external public assurances of privacy?
