Platform Solutions Requirements

These requirements apply across Meta Horizon platform features rather than to a single feature. Complete them in addition to the steps in the Getting Started Guide.

Verify that the user purchased or obtained your app legitimately. An entitlement check is required when you use platform features. See Entitlement Check.

If your app uses a feature in Table 1 of the Data Use Checkup page, an admin from your team must complete a Data Use Checkup (DUC) to certify that your API access to those features complies with Developer Policies. The app’s access to those features is contingent on a successful review of its DUC by the app review team.

Until one of the events in the next section happens, a DUC you submit during development is approved automatically. Each approved feature is a grant, and automatic approval gives your app provisional access to it; see When to submit a DUC. Test users can call most of these features before DUC approval, because test user accounts are exempt from DUC requirements. The exception is getting the logged-in user: without the User ID or User profile grant, it returns placeholder values or fails, as described in the table below, even for test users.

Request and test every DUC feature your app needs before you submit the app for review. Submitting the app sends its provisionally approved features to manual review. Your app keeps its provisional access to them while that review runs.

After any of these events, a new DUC request goes to manual review, and the feature isn’t available until the review finishes.

Without a grant, a call either fails or succeeds with placeholder values, such as a user ID of 0. A successful call doesn’t prove that your app holds the grant, so check the values it returns. To see what your users see, test with an account that isn’t a test user.

The error code for a failed call varies by call, engine, and OS version. When a call in the table fails, check your app’s Data Use Checkup status in the Developer Dashboard.

The table isn’t complete: a call that isn’t listed can still need a grant.

For more information, see Data Use Checkup.

Apps on Meta Quest 2, Meta Quest 3, and future Meta Quest devices must self-certify their intended age group: Teens and Adults (13+), Mixed Ages, or Children (under 13). The age group you select determines whether you can use platform features. See Age group self-certification and youth requirements.

If you self-certify that your app is intended primarily for children under 13 (ages 10–12), you will not be able to fill out a Data Use Checkup for your app, so you can’t use Data Use Checkup-requiring platform features, such as accessing a user’s ID or friends list, in your app.

Apps that self-certify that they are intended for mixed ages (under 13 or applicable age in user’s region, and 13+) fill out a Data Use Checkup, and use Data Use Checkup-requiring platform features, although some features may behave differently for children under 13.

A Mixed Ages app must also integrate the Get Age Category API to find out the age group of the current user.