Google's new glasses blur faces before Gemini sees them. For other apps, it's a rulebook
Google has banned facial recognition on its $395 camera glasses. Its own developer documents don't show anything in the software that would actually stop an app from doing it.
Meta's Ray-Bans picked up a nickname that no marketing department wants: "perv glasses". In 2024, Harvard students wired a pair to a face search engine and identified strangers on the street. So when Google opened preorders on Thursday for its own camera glasses, built by Samsung with frames from Warby Parker and Gentle Monster, it made a point of saying what the glasses refuse to look at.
The answer is your face. And everyone else's.
What Gemini doesn't get to see
Shahram Izadi, the Google vice president who runs Android XR, laid out the design in a company post. When a wearer asks Gemini about what's in front of them (translate this menu, what building is that), any faces in the frame are blurred before the image goes to Google's servers. That includes the wearer. Look in a mirror and ask Gemini a question, and it gets a picture of someone with no face.
"With this in mind, we set out to design the glasses so that personal help doesn't come at the expense of anyone's privacy," Izadi wrote, as quoted by Android Police.
Google says images captured for Gemini queries are not saved to Gemini's history and are not used for AI training or ad targeting. It told 9to5Google that the blurring happens locally on the paired phone and that the images are deleted straight after processing, Biometric Update reports.
The hardware has some manners too. A front-facing light comes on when the glasses record. Cover or disable it and the camera stops recording, Google says. Ordinary video clips are capped at 90 seconds, and there is a physical switch to turn the whole thing off.
For outside developers, the rules are blunt. Apps distributed through the Play Store may not use the cameras for real-time facial recognition or for live-streaming, and they may not tamper with the recording light.
That is a real line in the sand. Meta has acknowledged exploring facial recognition for its glasses, though it says nothing has shipped. Google has put in writing that its platform won't allow it.
A rule and a lock are different things
Now the fine print, which Biometric Update went through.
Google's developer documentation shows how an approved third-party app can get at the glasses' camera through a companion Android phone, using the standard CameraX interfaces. One of those is called ImageAnalysis. It exists so apps can run computer vision on a live feed.
An app has to ask permission to use the camera. But permission to see and a ban on recognising are two separate mechanisms, and the documents only describe the first as something the system enforces. Biometric Update found no operating-system control that would stop an authorised app from analysing the feed to work out who someone is. The documents also don't establish that Gemini's face blurring applies to anyone's app but Google's.
So the prohibition, as published, is a policy. Break it and you presumably get thrown out of the Play Store. For apps installed from somewhere other than the Play Store, the documents don't say how the rule would be enforced at all.
The outlet was careful about what this does and doesn't show: "These unanswered questions do not demonstrate that unauthorized facial recognition can operate on the glasses." What they show is that nobody outside Google can currently confirm the ban is more than a clause in a developer agreement.
Android Police noticed the same softness from a different angle. Google hasn't said whether the blurring is foolproof or whether some unblurred frames could still reach its servers.
The light that stays off
There is a second gap, and it is the one a bystander would care about.
The recording light is the glasses' way of telling the room that a camera is on. But Google's published requirements for that light cover photos and videos saved to the gallery. According to Biometric Update, Gemini can analyse the wearer's surroundings through the camera without the outward-facing indicator lighting up.
Google's reasoning is easy to guess. The faces are blurred and the image is deleted, so in its view nothing is being recorded. From the other side of the lens it looks different. A stranger's glasses are pointing a 12-megapixel camera at you and sending the frame off for analysis, and nothing tells you.
Meta's glasses have drawn fire for the same behaviour. Senators Edward Markey and Ron Wyden questioned Meta on October 29 about camera-based AI features that run without a visible signal. About two weeks earlier, the European Data Protection Board recommended that AI camera processing on wearables be made noticeable to people nearby.
Also worth knowing: the blurring covers Gemini queries. Ordinary photos and videos taken with the glasses are saved with every face intact, same as a phone.
Who wants the feature Google banned
The demand for face-identifying glasses is not hypothetical, and it is not limited to creeps. The Department of Homeland Security's fiscal 2027 budget includes a $7.5 million plan for biometric smart glasses that would let immigration officers identify people in real time. Ten Democratic senators asked DHS in May to drop it.
Google's rules forbid that kind of use on its platform. Whether they would hold against a government customer, or against software that never goes near the Play Store, is one more thing the documentation leaves open.
The glasses start at $395 and ship in the United States and South Korea on December 10. They work with Pixel and Galaxy phones and with iPhones. By Christmas there will be a lot more cameras at eye level, and the promise that they can't tell who you are will be tested by people with more motivation than a tech blogger reading the developer docs.
Sources: Android Police, Biometric Update.
More from the feed
A carpenter's missing hand now talks to his robot arm through a sensor under his skin
Phantom Neuro has put its muscle-reading implant into its first two patients in Melbourne. One went home three hours after surgery.