AI
Meta AI
TLDR: One day after WIRED reported Meta embedded unreleased face recognition in its Smart Glasses app for 50 million phones, Meta removed nearly all NameTag code from Meta AI, including face recognition libraries and stored faceprints. The move impacts user privacy expectations and reopens debate over biometric surveillance and enforcement of state privacy laws.
Key Takeaways:
- WIRED said Meta had embedded NameTag, turning Smart Glasses captures into faceprints stored on device and compared locally to a user database.
- After the report, Meta AI released the same day stripped face recognition libraries, face recognition processing code, and the “Person recognized” alert.
- The cleanup may not erase the core risk, because advocates argue the original decision shows why stronger biometric privacy enforcement is overdue.
Meta’s removal reads like damage control after a code audit, not a sudden conversion. The real question is whether privacy enforcement can keep up with how quickly these experiments sneak in.
Meta’s removal reads like damage control after a code audit, not a sudden conversion. The real question is whether privacy enforcement can keep up with how quickly these experiments sneak in.
Q&A
If the face recognition code was dormant, what still makes it a practical privacy threat?
Even without public activation, the presence of capture and indexing pathways can enable future flips or partial enablement, and it can normalize local biometric retention without clear user expectations.
Why would Meta keep fragments like a debug menu label and a dormant profile link after the removal?
Developers often leave internal scaffolding for testing or future product work; leftover labels can signal planned feature expansion even when the core recognition pipeline is removed.
What could WIRED’s findings change inside the app ecosystem beyond this one update?
It may trigger more code review, app store scrutiny, and regulator attention on embedded biometric components, not just features marketed to users.
How does local storage of faceprints complicate enforcement compared with data sent to servers?
Local retention can still enable tracking on a device and future use during updates, yet oversight is harder because companies can argue the data never left the phone.
What happens next if state privacy bills with private rights of action move forward?
Companies may face higher legal risk that accelerates compliance, because enforcement can move from regulator discretion to direct lawsuits by affected users.
No comments yet. Be the first to share your thoughts!