Test whether a glasses app streams audio or video today

Time needed about one to two hours, spread over two sessions

The steps

1. Open the app store listingOn the companion phone, open the app’s page in the official store and read the description and screenshots for explicit statements about server-side processing, live streaming or transcription.You should see: You see explicit wording that the app uploads or streams audio/video, or you see no such statement.
2. Read the privacy policyFrom the store page or the developer site, open the app’s privacy policy and search for mentions of audio/video capture, third-party processors, retention or remote transcription.You should see: The policy either names cloud processing/third parties or fails to address audio/video handling.
3. Check requested permissionsOn the companion phone and on the headset if possible, view the app permissions and note microphone, camera, background network access and location permissions before first run.You should see: You have a list of permissions the app requests and you can record whether background network access is allowed.
4. Prepare an isolated hotspotTurn on a secondary phone or a laptop as a Wi‑Fi hotspot, stop other devices joining, and disable nonessential apps on the hotspot device to reduce noise.You should see: Only your glasses are connected and the hotspot client list shows the glasses as the sole client.
5. Force-stop or disconnect the companion phoneOn the normal companion phone, force-stop or uninstall the companion app and turn Bluetooth off so the phone cannot proxy connections.You should see: The companion phone shows no active connection to the glasses and the companion app is not running.
6. Connect the glasses to the hotspotOn the glasses, connect to the isolated hotspot and confirm the connection in the headset’s network settings and in the hotspot client list.You should see: The glasses report a Wi‑Fi connection to the hotspot and they appear in the hotspot client list.
7. Run the suspicious featureStart the app feature that would use audio or video and perform a 30–60 second session while watching the hotspot outbound counter.You should see: During the session the hotspot outbound data bytes either rise in step with the recording or they remain flat.
8. Observe for delayed uploadsStop the recording and continue watching the hotspot outbound counter for 2–5 minutes to catch deferred uploads.You should see: You either see a delayed outbound spike after stopping or no change in the outbound counter.
9. Repeat with the phone as hotspotTurn the companion phone back on, make it the hotspot, connect only the glasses, and repeat the recording while watching the phone’s hotspot data or per-app data usage.You should see: You can confirm whether the phone observes the same outbound behaviour as the laptop hotspot test.
10. Compare with a baselineUninstall the app and run a quick baseline test on the same hotspot to check for unrelated outbound traffic from the device or system services.You should see: Hotspot outbound bytes remain flat during the baseline test, establishing noise-free behaviour.
11. Document the evidenceSave screenshots of hotspot and companion-app counters with timestamps and note the test conditions, device models and app version before contacting the developer or store.You should see: You have dated screenshots and a short test log describing what you did and what the counters showed.
12. Act on the resultIf you detected streaming, uninstall the app, revoke camera and mic permissions, send the developer a time-stamped query asking where the media is stored and request deletion, and report the app to the store with your evidence.You should see: The app is removed, permissions revoked, and you have documented evidence to send to the developer or store.

How to test app cloud streaming on glasses

Prove whether a glasses app sends audio or video off-device by combining three checks: read the store listing and privacy policy, verify on-device recording indicators and permissions, and run the suspicious feature on a hotspot you control while watching that hotspot’s outbound byte counter. If bytes leave during the session, the app streamed.

Pre-install checklist you must run

Before installation, confirm what the developer says the app does and which permissions it requests. Look for explicit mentions of server-side processing, live streaming, or third-party transcription in the listing and the privacy policy. Missing or vague statements mean you must assume the app may stream until your tests say otherwise.

• Open the app store listing and scan the description and screenshots for words about cloud processing, streaming, or server transcription.
• Open the app’s privacy policy and search for “audio”, “video”, “transcript”, “server” or “cloud”; flag vague or absent policies.
• Check requested permissions on the companion phone and headset: microphone, camera, background network access and location.
• Search our /apps directory for notes and documented local-processing alternatives before you install.

On-device checks you can do without network tools

You can collect quick evidence on the device itself. Use system privacy indicators, try the feature in Airplane Mode where possible, and watch short-term battery or companion-app data counters. These checks indicate whether the camera or mic is active and whether the feature requires network access.

• Look for OS privacy indicators: mic or camera icons, permission banners, or dedicated LEDs; check the device page for model specifics (see /devices/apple-vision-pro).
• Run the feature with Wi‑Fi and Bluetooth off if hardware allows. If it still works, it is local-only; if it fails, the feature needs a network.
• Check the companion app’s per-app data usage or session counters for spikes during your test.
• Note rapid battery drain during recording as a possible sign of network activity, but treat it as supplementary evidence only.

Isolated hotspot test a non-technical proof

Use a phone or laptop you control as a Wi‑Fi hotspot and connect only the glasses. Watch that hotspot’s outbound byte counter while you record. No packet capture is required: if outbound bytes rise in sync with the recording session or shortly after, the app or its cloud received data from the glasses.

• Create a hotspot on a secondary phone or a laptop and ensure no other clients are connected.
• Open the hotspot client list or the OS network monitor and note the outbound bytes before you start.
• Run the suspected feature for 30–60 seconds and watch the hotspot’s outbound bytes during the session.
• Continue watching for 2–5 minutes after stopping to catch deferred uploads.

How to tell whether the phone or the glasses are streaming

Separate phone and glasses traffic with two quick tests: run the feature with the companion phone powered off or its companion app force-stopped, then run the feature again with the phone acting as the isolated hotspot. Comparing those results tells you whether the glasses upload directly or the phone proxies the data.

• Test A — phone disconnected: force-stop or uninstall the companion app and disable Bluetooth, then run the feature on the glasses. If the hotspot still shows outbound bytes, the glasses streamed independently.
• Test B — phone as hotspot: make the companion phone the only network for the glasses and watch the phone’s hotspot or per-app data counters.
• If the feature fails when the phone is disconnected, the glasses rely on the companion phone for processing; treat any subsequent traffic as jointly generated.

Device-specific notes and common gotchas

Manufacturers expose recording status and permission flows differently. Check the device page before testing and expect quirks: some models show an LED, others hide indicators in the companion app, and Android-based headsets use varied permission dialogs. Use the isolated hotspot when indicators are missing or unclear.

• Ray‑Ban Meta: some models show a front LED or companion-app recording status; compare behavior on our Ray‑Ban Meta device page at /devices/ray-ban-meta.
• Apple Vision Pro: visionOS enforces visible privacy indicators and permission flows; still run the hotspot test because companion services can relay data. See /devices/apple-vision-pro.
• Android XR and vendor-based glasses: status icons and permission banners vary; check system permission logs and run the hotspot test. See /devices/android-xr.
• Deferred sync: many apps upload after a session ends. Watch hotspot or router logs for a few minutes after you stop recording.

What to do if you detect streaming

If your tests show outbound bytes tied to recording, act immediately: remove the app, revoke camera and mic permissions, document the evidence, and contact the developer and the store. Don’t assume uninstall removes copies already uploaded to third-party servers.

• Remove the app from the headset and the companion phone, and revoke microphone and camera permissions at the OS level.
• Take screenshots of hotspot or router counters with timestamps and keep logs as evidence.
• Send the developer a short, time-stamped message asking where the audio/video is stored and how to delete it, and report the app to the store with your evidence.
• Switch to documented local-processing alternatives listed on our /apps page.

How this testing fails in practice, and why

These tests are pragmatic but have known failure modes: background phone syncs can mask results, some apps defer uploads, and vendor telemetry or OS services can create unrelated outbound traffic. Learn the common failure sequences so you can establish a baseline and repeat tests to rule out noise.

• Companion-phone noise: leaving the phone connected to cellular produces background syncs that mask the glasses’ traffic. Disable cellular or use a clean laptop hotspot.
• Deferred uploads: apps may queue recordings and send them after you stop. Watch the outbound counter for several minutes after the session.
• Vendor telemetry and OS updates: system services can contact cloud servers. Run a baseline test with the app uninstalled to identify unrelated traffic.
• Missing indicators: when devices lack visible LEDs or clear UI cues, rely on the isolated hotspot or router logs.

What to do next and where to verify claims

Run the permission and hotspot tests now, then confirm the app’s claimed behaviour on our app directory or the device page before you keep using it. If the app fails your tests, follow the removal, documentation and reporting steps and repeat tests after updates.

• Find local-processing alternatives and documented apps on our /apps page.
• Check device-specific guidance at /devices/ray-ban-meta and /devices/apple-vision-pro.
• If you need UI-specific steps for a model, open that device’s page for screenshots and recent notes.

Where this usually goes wrong

• Outbound traffic appears only when the companion phone is nearbyThe phone is proxying uploads or performing heavy processing and sending data itself.Force-stop the companion app, disable Bluetooth, and repeat the hotspot test with the phone disconnected to isolate the glasses.
• No traffic during recording but a spike appears laterThe app queues recordings and uploads after the session ends (deferred upload).Extend observation for several minutes after stopping and capture timestamps and screenshots; treat deferred uploads as streaming.
• Hotspot outbound counters are noisy or unreliableThe hotspot device is running background syncs or other network activity.Use a clean laptop hotspot, stop background apps, or reboot the hotspot device before testing.
• Device has no visible recording indicatorSome glasses models do not expose an LED or clear UI indicator for camera or mic use.Rely on the isolated hotspot and router logs instead of indicators and check the device page for model-specific quirks.

The checklist

• Open the app store listing
• Read the privacy policy
• Check requested permissions
• Prepare an isolated hotspot
• Force-stop or disconnect the companion phone
• Connect the glasses to the hotspot
• Run the suspicious feature
• Observe for delayed uploads
• Repeat with the phone as hotspot
• Compare with a baseline
• Document the evidence
• Act on the result

Frequently asked questions