meta-wearables-privacy-publishing

Draw the data flow from glasses or phone source through processing, network, storage, and deletion, then record purpose, consent, retention, and access for each data class. Verify every iOS permission and usage description against actual code paths before release.

You need accurate Info.plist usage descriptions, a privacy manifest file, and App Store privacy details that match real collection behavior. Camera and microphone access should follow a clear user action with explanation, not launch-time requests.

Yes, it includes review against the official Meta Wearables terms and acceptable use policy, refreshed from the developer documentation. Material legal uncertainty is escalated to the product owner or counsel since the review is not legal advice.

Only when the exact implementation and source establish that data stays on device. A valid callback, Developer Mode registration, attestation result, or release-channel membership is not proof of local processing or physical capability.

The audit stops before publishing if any source, permission, consent, retention, terms, or physical-device gate is unresolved. It cannot guarantee App Store approval, Meta endorsement, or legal compliance, and credentials and callback payloads must stay redacted.