Smart glasses are moving from novelty to ordinary consumer technology, but their privacy problem is different from the one created by a phone. When someone raises a phone to record, the act is usually visible. Glasses can capture the same room, conversation, face, or private moment while looking much more like something a person simply wears.
That difference is now becoming a product-design and legal issue. Reuters reported on September 22, 2026, and updated its report September 23 that privacy concerns are affecting the emerging market for AI wearables. The report described lawsuits, venue sestrictions, camera-free alternatives, and growing interest in devices that process more data locally or make recording more deliberate and visible.
The renewed attention also makes a pending state investigation worth understanding. On May 20, 2026, the Texas Attorney General announced an investigation into Meta AI Glasses. The announcement raised concerns about recording, privacy representations, access to captured material, and potential collection of facial geometry. It said the state issued a civil investigative demand to determine whether Meta deceptively misrepresented its use of consumer data in violation of Texas law.
An investigation is not a finding of liability. The announcement contains allegations and questions, not a court judgment. As of September 27, 2026, I did not locate an official Texas announcement resolving this specific investigation.
The user is not the only data subject
Traditional consent screens focus on the person who bought the device or opened the app. Smart glasses complicate that model because the people whose voices, faces, homes, workplaces, and behavior enter the system may never see a screen at all. The wearer can accept a privacy policy. A bystander across the room cannot.
This is why a recording light should not be treated as the entire privacy system. Notice is useful only if people can see it, understand it, and respond before collection. A device also needs controls for what is captured, whether information stays local, what reaches a cloud service, how long it remains available, and whether it is used for model improvement or human review.
The Texas announcement specifically discussed an “always enabled” mode and alleged that a visual indicator was not active during that processing. Meta’s position deserves equal clarity: Reuters reported that the company says its recording light cannot be disabled during filming, that the camera is disabled when the light is covered or tampered with, and that it filters identifying information. Meta also said it disagrees with allegations in a separate lawsuit and will contest them.
Those competing claims show why privacy cannot rest on marketing language alone. Terms such as “always enabled,” “recording,” “processing,” and “uploading” need precise technical definitions. People should not have to guess whether a device is waiting for a wake word, analyzing locally, saving a clip, or transmitting data.
Texas law puts facial geometry in a special category
Texas already has a specific biometric privacy statute. The state’s Capture or Use of Biometric Identifier Act, commonly called CUBI, covers retina or iris scans, fingerprints, voiceprints, and records of hand or face geometry. For commercial capture, the Texas Attorney General explains that a person must inform the individual and obtain consent before collecting the biometric identifier.
CUBI also restricts sale, lease, and disclosure, subject to exceptions; requires reasonable care in maintaining and transmitting biometric identifiers; and requires destruction within a reasonable time, no later than one year after the collection purpose expires unless an exception applies. The Attorney General has exclusive enforcement authority and may seek civil penalties of up to $25,000 per violation. The current statutory text is available from the Texas Legislature.
Not every image of a face is necessarily a record of face geometry, and not every camera function automatically triggers CUBI. The important questions include whether the system creates or captures a biometric identifier, whether that happens for a commercial purpose, what notice was provided, and whose consent was obtained. Those are fact-specific legal questions—not conclusions that can be answered from a product name.
The enforcement backdrop is significant. In 2024, Texas announced a separate $1.4 billion settlement with Meta concerning allegations that Facebook’s earlier facial-recognition feature captured Texans’ facial geometry without the authorization required by law. That resolved a different matter involving Facebook photo-tagging technology. It does not resolve the 2026 smart-glasses investigation, but it shows that Texas has used CUBI in major enforcement.
What developers should build before the backlash arrives
Developers of wearable products should begin with a complete data-flow map, not a simplified consumer diagram. Separate sensor activation, temporary buffering, local inference, saved recordings, cloud uploads, human review, derived biometric templates, model training, and third-party sharing. If those actions are collapsed into one vague label, the product team may not understand its own legal and privacy exposure.
Bystander-facing notice also needs to be designed as a real interface. Indicators should be visible from ordinary angles, difficult to defeat, and connected to the actual state of capture and transmission. Products should fail safely when an indicator is blocked or damaged. Audible notices may help in some settings, while physical shutters and camera-free modes can provide stronger assurance than software promises alone.
Data minimization is equally important. If a feature can operate with local processing, the system should not automatically transmit raw audio or video. If a task needs a short buffer, the device should not retain an entire conversation. If facial recognition is unnecessary, the product should not create face-geometry records merely because the hardware makes it possible. Retention schedules should attach to the purpose of collection, and deletion should reach cached copies, derived data, and training pipelines where required.
Consumers and bystanders also need understandable controls and complaint paths. Wearers need clear settings for recording, cloud processing, storage, sharing, and model improvement. Bystanders need a realistic way to report misuse or ask what happens to their data, even without an account.
Privacy will shape whether wearables become normal
The most useful smart glasses may be the ones that make privacy visible. A product can offer convenience without treating everyone nearby as free training data. Clear indicators, local processing, deliberate activation, limited retention, and biometric safeguards are not obstacles to adoption. They are part of what makes adoption possible.
The Texas investigation remains an investigation, but the policy lesson is already clear. Wearable technology changes who becomes a data subject. Developers should design for the person in front of the camera, not only the person behind it.
About Joseph Sides
Joseph Sides is a South Florida-based data privacy advocate, consultant, and entrepreneur whose work focuses on consumer rights, digital transparency, website tracking, meaningful privacy choices, and responsible technology. His public DEV introduction describes a bachelor’s degree in criminology, a minor in business, and training in data analytics. These interests connect questions about how technology operates with questions about what people understand and how organizations remain accountable for their decisions.
The educational purpose of these articles is to make privacy developments easier to follow and their practical implications easier to examine. That means connecting the language of laws and regulatory actions with familiar experiences: visiting a website, choosing an app, responding to a consent request, or trying to delete information. For developers, the discussion also considers how interface choices and data practices shape the choices available to consumers. The aim is informed understanding and thoughtful questions, with attention to both individual rights and responsible product decisions.
Educational Information — Not Legal Advice
This article provides general education and commentary, not legal advice. Joseph writes as a privacy advocate and consultant, not as an attorney. Reading this article does not create an attorney-client relationship, and the discussion is not a substitute for advice from a qualified attorney about your particular circumstances.
Laws, interpretations, applicability, exemptions, and deadlines vary by jurisdiction and can change. A requirement that applies to one organization or activity may apply differently to another. Readers should consult current primary sources and a qualified attorney when evaluating obligations, available rights, or a specific course of action. This article does not promise complete coverage, guaranteed outcomes, or personal legal guidance.
AI Disclosure
Prepared with AI assistance.
Top comments (0)