Putting on smart glasses at a brand demo means the device may track your hand movements, listen to voice commands if the experience uses them, and on some platforms follow where you look, for as long as you're wearing it. In short: a well-run demo should tell you what it tracks before you put the glasses on, process nearly all of it on the device itself, and discard it the moment your session ends. That is a different question from whether the person standing next to you knows there's a camera nearby. This article is about the person who actually wears the device: what data comes from them, what a proper consent step looks like, and what should happen to that data once they hand the glasses back.
For the other half of this topic, how a brand handles everyone nearby who isn't wearing the device and can't tell whether a camera is active, see smart glasses privacy and consent for brand activations. That article covers bystander signage, capture indicators, and the legal side of recording footage in a public space. This one covers the participant sitting or standing right there, glasses on, actively using the thing.
Why participant consent is a different question from bystander consent
A bystander near a smart glasses activation is not wearing anything. They cannot see a lens, cannot hear a shutter, and in most cases have no way to know a camera-equipped device is nearby unless they happen to spot a small capture LED. Their question is entirely passive: am I being recorded without knowing it?
A participant is in the opposite position. They picked the glasses up. A staff member handed them over. They put the device on their own face and started interacting with an experience that responds to their hands, their voice, or their gaze. Nothing about that is ambiguous or accidental, which means their question is active, not passive: what did I just agree to by putting these on? That is a consent question about data collected from them specifically, not about surveillance they didn't choose to be near. Treating both groups the same way, one signage plan for everyone, misses what each group actually needs to know.
What smart glasses actually collect from the person wearing them
None of this is saved video footage of the world around the wearer, which is the bystander concern. It is sensor and interaction data generated by the wearer's own body and voice, used to run the experience in front of them. Four categories cover almost every demo:
Hand-tracking data
The position and movement of your fingers and hands, used to recognize gestures like pinch, point, or grab. Processed frame by frame to drive the interaction, not saved as a recording.
Voice and audio
Microphone input for spoken commands or dictation. Some platforms process this on device; others send audio to a cloud speech service, which should be disclosed if it happens.
Gaze or eye-tracking data
Where you're looking, used on some platforms for selection or to improve rendering. Not every device has this. Treated as more sensitive than hand position because it reveals attention patterns.
Movement and personalization signals
Some AI-driven features draw on movement patterns or session behavior to adapt in real time. This is not face recognition and should never be, but it's still worth asking what it feeds into.
The distinction that matters across all four: is this processed in the moment to make the experience work, then thrown away, or does any of it get saved, tagged to you, or sent somewhere off the device? A participant is entitled to a straight answer to that question before they put the glasses on, not a shrug afterward.
What a proper consent flow at check-in should look like
Most demos do not need a signature. A quick verbal or on-screen consent at check-in, delivered in fifteen to thirty seconds, covers the overwhelming majority of cases. A paper waiver is only appropriate when the demo captures something identifiable and keeps it, such as a take-home photo or clip, or when data is streamed to a third-party service beyond running the experience itself.
Whichever form it takes, the consent moment should say four things plainly:
- What the device tracks while you wear it. Name it specifically: hand movement, voice if applicable, gaze if applicable. Not "sensors" or "technology."
- Whether anything is saved after the session. If the answer is no, say so directly, because that is the reassuring answer most people are hoping for.
- Whether any of it leaves the device. Cloud-processed voice commands are common and fine to use, but a participant should know before they speak, not find out later.
- How to ask questions or opt out. A name and a face, not a QR code to a policy nobody will read mid-demo.
A staff member who can say this in one breath, "this tracks your hand movements to run the experience, nothing is saved, and none of it leaves the glasses," has done the job. A form that asks someone to read three paragraphs of legal text while a queue builds behind them has not, even if it technically discloses more.
What happens to your data after you take the glasses off
On a properly built demo, the answer is straightforward: nothing. Hand-tracking data and voice input are processed in real time to drive the interaction and discarded the instant the session ends or the device resets for the next person. There is no file sitting on a server with your name on it.
That is the target, but it is not automatic, and a brand running the demo should confirm it rather than assume it. Ask the studio or vendor building the experience three direct questions: does any camera frame, audio clip, or gaze sample leave the device during a session; if voice commands are processed in the cloud, what happens to that audio afterward, and for how long does anything, however minor, persist anywhere before it's deleted. If the answer to any of these is "some data is retained," that should be disclosed at check-in, in plain language, not discovered later in a privacy policy.
What a brand should ask its AR studio or vendor before running a public demo
Before a smart glasses demo goes live to the public, someone on the brand side should be able to answer these in writing, the same way they would for bystander consent, but about the wearer's own session data.
| Question to ask | Why it matters |
|---|---|
| What data is generated per session? | Get the specific list: hand-tracking, voice, gaze, other. Not a general description. |
| Is any of it processed off the device? | Cloud voice processing is common; it should be named, not assumed away. |
| Is anything retained after the session ends? | The default answer should be no. If yes, ask for how long and why. |
| Who can explain this to a participant on the spot? | Staff need a plain-language answer ready, not a policy link. |
| Is a waiver actually required, or is verbal consent enough? | Match the consent step to what's genuinely being collected, not the most cautious option by default. |
These questions sit alongside the bystander checklist in smart glasses privacy and consent for brand activations, not instead of it. A demo running in a public space needs both answered: one for the people trying the glasses, one for everyone standing nearby. If you're still working out the wider brief before the first call with a developer, how to brief a smart glasses developer covers where data handling fits into that conversation.
How we handle it on our own demos
Every wearable AR demo the studio runs at events treats participant data the same way: hand-tracking and voice input are processed on device to run the experience, nothing is saved unless the participant explicitly asks for a take-home clip, and the device resets clean between sessions. Staff can explain it in one sentence, because there's only one sentence to explain.
If a participant has to ask twice what happens to their data, the consent step already failed.
Frequently asked questions
Planning a smart glasses demo or activation?
We plan participant data handling and bystander consent into the experience design together, not as an afterthought. Six years running AR and wearable activations for brands.