Using smart glasses in camera-restricted places safely

Time needed about 90 minutes, spread over two sessions

The steps

1. Open the companion app and locate privacy controlsOn your phone, open the glasses' companion app and find any sections labelled Privacy, Sensors or Settings that control camera, microphone or streaming.You should see: The companion app shows toggles or labels for camera, microphone or live view indicating they can be turned off.
2. Revoke camera and microphone permissions in phone settingsOpen your phone's Settings > Apps > select the companion app > Permissions, and remove Camera and Microphone permissions.You should see: The Permissions screen shows Camera and Microphone as 'Denied' or 'Not allowed'.
3. Disable background network access and streamingIn the companion app or phone settings, turn off background data, live view, remote streaming and any auto‑upload feature; then force‑stop the companion app.You should see: The companion app shows streaming or live view as off and the phone's App info indicates Background data is disabled or the app is not running.
4. Apply a clear physical lens cover or bandAttach a visible fabric band or purpose lens cover to each outward lens so it is obvious from a few metres that the cameras are blocked.You should see: The lenses appear fully covered from the front and a staff member can see the cover without touching the glasses.
5. Take verification screenshots and a short videoCapture three screenshots: the companion app privacy screen showing sensors off, the phone Permissions screen showing Camera and Microphone denied, and a photo of the covered glasses; then record a 10‑second video toggling the companion app state off.You should see: You have three image files and one short video saved in a folder labeled 'compliance packet'.
6. Save the one‑page proof and script to your phoneCreate a one‑page PDF or note that summarises your name, device model, accessibility need, sensors disabled and vendor support link; save it to Files or Photos and memorise a 20‑second script.You should see: The PDF or note opens quickly from your phone without internet and you can read the 20‑second script smoothly.
7. Test captions while in compliance modeWith companion‑app sensors and OS permissions disabled and the physical cover applied, confirm that captions run as you need; enable only Bluetooth if the caption solution requires it.You should see: Captions appear on the glasses or a paired phone/device while camera and network streaming remain off.
8. Practice the verification routine and save it as a habitRehearse switching to School Mode, opening the compliance packet and delivering the 20‑second script; time yourself until you can complete it under 60 seconds.You should see: You can switch modes, present the packet and speak the script in under a minute without searching for files.

How to use smart glasses in camera‑restricted places

If you need live captions in a no‑camera venue, prepare a single 'School Mode' on your phone that disables cameras, microphones and streaming, applies a visible lens cover and saves verification screenshots. Present that packet at entry; if access is denied, switch to a phone‑based or staff‑run captions fallback.

This playbook works with modern consumer smart glasses. The checklist below shows what staff usually ask to verify and how to build, test and present the proof.

• Prepare a single profile that turns off camera, mic and streaming and saves verification images
• Make verification obvious: visible cover, app privacy screen, and OS permission pages
• Have a tested fallback so the user still gets captions if access is refused

Which sensors and apps count as recording devices and why they matter

Treat outward cameras, microphones used by captioning apps, and any live‑streaming or remote‑access service as recording devices. Depth or IR sensors may look like cameras. You must be able to show these three categories are disabled or isolated so staff can verify the device poses no recording risk.

For practical checks, focus on three categories you can disable and prove: the outward camera(s), the microphone(s) used by captioning or recording apps, and any streaming or remote‑access service on the companion app or phone.

• Camera — captures images or video and is the primary concern.
• Microphone — captures speech and ambient sound.
• Streaming/service — sends audio or video off the device and turns local sensors into a recording risk.

Concrete steps to disable or isolate cameras and microphones on common platforms

Before you reach the venue: revoke app camera and microphone permissions, disable companion‑app streaming and background access, and apply a physical lens cover. Document each change with screenshots. Do these steps in that order so staff can see OS‑level permissions denied as well as the in‑app privacy state and the physical cover.

Use the companion app to toggle sensors off, then confirm the phone's Settings > Apps permissions show Camera and Microphone denied. If available, disable live view or streaming and force‑stop the companion app. Finish by attaching a visible lens cover so the cameras are clearly blocked.

• In the companion app: find privacy or sensor controls and toggle camera and mic off.
• On Android/iOS: open Settings > Apps > [companion app] > Permissions and remove Camera and Microphone.
• Turn off live view/streaming and force‑stop the companion app; disable background data if needed.
• Apply a visible lens cover or band so the cameras look intentionally blocked from a few metres.

How to create and test a single compliance‑ready profile you can activate before entry

Create a named profile on your phone that combines companion‑app toggles, OS permission changes, a physical cover and saved verification images. Test the sequence from normal mode: switch to the profile, capture screenshots of the companion app, the OS Permissions page and a photo of the covered glasses, then save them in a labeled folder.

Practice the switch until you can activate the profile and open the proof images in under a minute. Keep one short video of you toggling the settings off; staff find a live toggle or video more persuasive than still images alone.

• Name the profile clearly (for example 'School Mode') and save the checklist in your phone notes.
• Take three screenshots: companion app privacy screen, OS permissions showing Camera/Microphone denied, and a photo of the cover in place.
• Record a 10‑second video toggling the companion‑app sensors off to show the transition.

Make the device status obvious to staff so they can verify it quickly

Show staff visible signals they can confirm from a few metres: a bright fabric band or rigid lens cover, a companion‑app privacy screen, and the phone OS permissions page. If the glasses have a capture LED, use it to show the camera turning off. Staff rely on what they can see, not your explanation.

If a model has no LED, the physical cover and a live app screen are the primary proof. Make the cover look deliberate and tamper‑evident so staff accept it without handling the glasses.

• Use a visible fabric band or a removable rigid lens cover that clearly blocks the lenses.
• Open the companion app privacy screen and the phone Permissions page for staff to view.
• If present, demonstrate the capture LED switching off when you disable the camera.

What short documentation and scripts to carry and show security or staff

Carry a single‑page PDF that names you, the device model (for example Ray‑Ban Meta), the accessibility need and the sensors you disabled, plus two verification screenshots. Keep it offline in Files or Photos and memorise a 20‑second script you can read while the staff reviews the packet.

The one‑page proof should list the device model, the function you need (live captions), the exact sensors disabled and a vendor support link. Show the companion app privacy screenshot and the phone permissions screenshot alongside the physical cover photo.

• One‑page proof: name + device model + purpose + bullets of sensors disabled + two screenshots.
• Short script: a 20‑second line stating you need captions, that cameras/mics are off, and you have documentation.
• Keep the vendor support link bookmarked (see /devices/ray-ban-meta) so staff can confirm technical details.

When venues must provide accommodations and how to handle refusals

Schools and employers commonly have obligations to provide reasonable accommodations, but venue rules can limit devices for safety or privacy. Present your proof packet, ask for the accessibility contact, and request an alternative that delivers the same captions — phone app or staff device — before escalating to the accessibility coordinator or HR.

If staff refuse an onsite solution, offer two fast fallbacks: a phone captions app you already set up, or captions on a staff device. Record the interaction (names and time) and follow up with the accessibility office if you exhaust onsite options.

• Always open with the one‑page proof and the compliance profile active.
• If denied, offer two fast fallbacks: a phone captions app or a staff device running captions.
• If the venue insists on an absolute ban, note names and times and escalate to the accessibility coordinator.

Why this fails in practice and what to do about it

Most failures come from skipping the verification test. Staff will ask to see specific screens; mismatched screenshots, a partially covered lens, or an active background stream turn the interaction adversarial. Rehearse the routine, refresh screenshots after updates, and include a short video of you toggling settings off.

Specific fixes: update screenshots after firmware or app updates, use a two‑point cover so both lenses are obviously blocked, and test captions with Bluetooth on but data and camera off if required.

• Refresh screenshots monthly and after updates so staff see a matching UI.
• Use a cover or band that clearly blocks both lenses; a small sticker can be missed.
• Test captions in the compliance state and record the exact steps that keep them working.

What to do next: prepare your one‑tap profile and proof packet

Set aside an hour to build and test a 'School Mode' profile: toggle companion‑app sensors off, revoke OS permissions, attach the cover, save three screenshots and a short video showing the state, then store them in a 'compliance packet' folder in Files or Photos. Rehearse the script once with someone.

After you make the packet, practise switching modes and presenting the proof until you can do it in under a minute. Bookmark relevant support pages such as /devices/ray-ban-meta and our live captions app list so you can produce vendor details quickly.

• Build and name a single profile on your phone called 'School Mode'.
• Save screenshots and a short video to a folder titled 'compliance packet'.
• Practice activation and the 20‑second script until it takes under a minute.

Where this usually goes wrong

• Staff ask to see proof but your screenshots don't match the current app UIA companion app or firmware update changed the screens after you saved the screenshots.Refresh the screenshots immediately and keep one short video showing you toggling the settings off; update screenshots after updates.
• Captions stop working when you activate compliance modeYou disabled Bluetooth or local processing that the captions depend on while trying to remove network access.Test caption behaviour in airplane mode with Bluetooth on and record the exact steps that keep captions working; save that as part of the profile.
• Security refuses to accept a fabric band as proof the camera is coveredThe cover looks informal or could be removed easily, and staff want an obvious tamper‑resistant signal.Use a removable rigid lens cover or a brightly coloured tamper‑evident tie; offer to demonstrate you cannot remove it without taking the glasses off.
• The companion app restarts streaming after a phone updateApp auto‑restart and background permission were reenabled by an update.After an update, re‑run the checklist: revoke permissions, disable background data, force‑stop the app and retake screenshots before entering any restricted venue.

The checklist

• Open the companion app and locate privacy controls
• Revoke camera and microphone permissions in phone settings
• Disable background network access and streaming
• Apply a clear physical lens cover or band
• Take verification screenshots and a short video
• Save the one‑page proof and script to your phone
• Test captions while in compliance mode
• Practice the verification routine and save it as a habit

Frequently asked questions