App Privacy
Meta Wallet App Privacy Label support matrix.
The App Store privacy label must match the exact submitted app build, SDKs, account features, analytics, wallet functionality, and regional availability.
Build-specific disclosure required
This public matrix is a reviewer and operator aid. The final App Store Connect answers must be completed from the submitted binary, server-side feature flags, SDK inventory, and enabled regions.
Expected data categories to evaluate
- Contact Info
- Email address, phone number, and support contact content when account or support workflows are enabled.
- Identifiers
- User ID, account ID, device identifiers, wallet addresses, Defi Oracle Meta (Chain 138) network identifiers, and public ledger references where used by the submitted build.
- Diagnostics
- Crash logs, performance data, app version, device model, operating system, and security events when diagnostics are enabled.
- Financial Info
- Only disclose if the submitted build enables payments, balances, Defi Oracle Meta (Chain 138) wallet transactions, on-ramp, off-ramp, card, banking, or regulated financial features.
- Sensitive Info
- Only disclose if identity verification, sanctions screening, eligibility checks, regulated recovery, or similar workflows are enabled.
- Usage Data
- Only disclose if analytics, event telemetry, product interaction, or app activity measurement is enabled.
Tracking position
Meta Wallet must not disclose "no tracking" in App Store Connect unless the submitted build and all third-party SDKs do not track users across apps or websites owned by other companies. Any tracking use requires the appropriate App Tracking Transparency flow and App Store privacy disclosure.
SDK inventory
The review package should include every third-party SDK, network endpoint class, crash reporter, analytics provider, identity provider, blockchain infrastructure provider, payment processor, and customer-support processor used by the submitted build.