Research investigation R0924 / comparison
Three Meta Privacy Boundaries, Not One: What Protects Muse and AI Glasses?
Meta describes three distinct processing paths with different availability and data-flow scopes. A protection described for one path should not be assumed to cover another.
The cutoff is the original September 24, 2026, 15:30 UTC collection snapshot. This is a bounded review of supplied public disclosures, not a survey of every account, device, request, or subsequently released feature.
Version ledger
Frozen public editions
Each edition preserves the records, method, sources, and downloads available at publication time.
The cutoff is the original September 24, 2026, 15:30 UTC collection snapshot. This is a bounded review of supplied public disclosures, not a survey of every account, device, request, or subsequently released feature.
- Dataset ID
- spd:three-meta-privacy-boundaries-not-one-what-protects-muse-and-ai-glasses-c519d504
- Stable URL
- /research/three-meta-privacy-boundaries-not-one-what-protects-muse-and-ai-glasses-c519d504
- Version
- v1
- Coverage
- Live collection
- Records
- 8
- Fields
- 7
- Updated
Measurement technique
How to read this report
- 01Plan an evidence matrix with separate rows for Muse Secure VM, Muse Confidential VM, on-device glasses processing, and planned glasses Private Processing. Record availability, processing boundary, personnel access, keys, approvals, data leaving the boundary, persistent state, verification, and named feature coverage.
- 02Mark each cell documented as current, planned, or unspecified; do not infer feature coverage from workload examples or from another product’s threat model.
- 03Synthesize the saved Meta product, research, and engineering disclosures and the joint partner release. Treat the WhatsApp Private Processing whitepaper as background, not proof of glasses deployment. No new collection or implementation test was performed.
Sources
Evidence
4 publishers supporting 8 records. Expand a publisher to inspect its cited pages.