Frequently asked questions

Read the announcement to learn more about Meta Horizon OS.

There are no changes necessary you need to make to support Meta Horizon OS. Software built for Meta Quest already runs on it today. You can continue to build and distribute your titles through the Meta Horizon Store.

Meta Horizon OS is the mixed reality operating system that powers Meta Horizon OS devices. It’s similar to traditional software operating systems but tailored to take advantage of advanced sensors and capabilities needed to deliver mixed reality experiences. Developers create titles using their preferred engine or framework and distribute through the Meta Horizon Store.

Meta Horizon Worlds allows people to easily discover and travel to social worlds and experiences.

The Horizon social layer enables people’s identities, avatars, and friend groups to move with them across virtual spaces on Meta Horizon OS. Some of these rich social features can be integrated into your title now while others will be available in the future. For example, see documentation for Users, Friends, and Relationships ( Unity , Unreal , Native ), and Meta Avatars ( Unity ).

Meta is developing a new spatial app framework to help mobile developers create mixed reality experiences for Meta Horizon OS devices. You’ll be able to use the tools that you’re already familiar with to bring your mobile apps to Meta Horizon OS or to create entirely new mixed reality apps.You can apply for early access here .

The Meta Horizon Store will be the new name for the Meta Quest Store. This Store is the main distribution channel for titles on Quest today and will be available on all Meta Horizon OS devices in the future. If your title was available on the Quest Store, it will be available on the Meta Horizon Store.

We are shifting our model from two independent surfaces, Store and App Lab, to a single, unified, open storefront. This shift will happen in stages, first by making many App Lab titles available in a dedicated section of the Store. If you are currently developing for the Meta Quest Store or App Lab, no changes are required at this time.

In the future, new titles submitted will go directly to the Store and App Lab will no longer be a separate distribution channel. All titles will need to meet basic technical, content, and privacy requirements to publish to the Store. Titles are reviewed at submission and may be re-reviewed as they scale to more people. Like App Lab today, all titles that meet these requirements will be published.

Submission requirements have not changed. The existing Store and App Lab submission processes will continue to operate as we build a unified platform. All titles must still meet the Virtual Reality Check (VRC) guidelines , including our Content Guidelines , Data Use Policy , and App Policies . App Lab titles also must meet our App Lab Policies .

Unless previously approved, you will continue to submit your title to App Lab.

Over time the Meta Horizon Store will integrate all App Lab titles.

Meta will be integrating App Lab titles on the Meta Horizon Store over time, starting with a new dedicated section of the Store containing App Lab titles.

Please contact the store submissions team at submissions@oculus.com referencing the need to suspend distribution of your app.

Whether the goal is to build a business, create a community, test and experiment with new apps, or get feedback on new ideas, you control how your title is distributed. Titles are shareable via a URL and Meta Platform Technologies Keys, and are discoverable through search. Titles are visible in friends activity such as the "Popular With Friends" feed. Meta curates titles to promote across the Meta Horizon Store for placement in banners, shelves, and other highlighted locations.

You can find a wealth of resources to better understand and promote your title in our documentation including analytics , monetization , and engagement .

Parent-managed Meta accounts provide additional protections for preteens ages 10 to 12 (this age may be different depending on the country) to help provide age appropriate and safe experiences for the youngest members of our community. For more information, read the announcement in the Meta Quest blog.

You can find resources and documentation outlining exactly what you need to do by visiting the resource page in the Developer Center and you can check out this video resource .

To meet Meta’s age group self-certification and youth requirements, for each app you must:

Please review the developer documentation and contact Support Center if you have any questions.

To meet Meta’s age group self-certification and youth requirements, for each app you must:

Please review the developer documentation and contact Support Center if you have any questions.

Not all Meta Quest Platform SDK features are available for children ages 10-12 or child-directed apps. See the blocked feature lists and links to relevant API documentation ( Unity | Unreal | Native ).

All apps in the Meta Quest Store must have IARC assigned ratings , which give your users an idea of what type of content your app may have and the audience it is appropriate for.

IARC content ratings are not the same thing as the age group of your app. It is possible for content to be rated as E for everyone while also not meeting any of the FTC's criteria to be considered "directed to children." In that case, that app would certify as Teens and Adults 13+ (General Audience). You should not rely on your app’s IARC rating alone when self-certifying the age group for your app. You can learn more about the definition of "child directed content" by visiting the FTC's COPPA FAQ .

When determining your app’s age group, we recommend that you review the FTC guidelines and consider your app’s subject matter, including visual content, character choices, music, and more. You can also update your app’s age group at any time if your content evolves. For guidance on determining your app’s age group and for age group-specific guidelines, check out our documentation .

The original Meta Quest and Meta Quest Pro devices are for 13+, and do not support users under 13 years old. Age group self-certification is required for apps that will run on Meta Quest 2, Meta Quest 3, and future Meta Quest devices. You can use the device targeting feature to upload a separate build for the original Meta Quest or Quest Pro.

Yes, you can and should update your self-certification if your app’s age group changes. You can do so on the Build Details page under Distribution on App Manager.

All apps in the Meta Quest Store and App Lab must self-certify their app’s age group. If you do not self-certify, your app will face enforcement including Store removal and loss of access to platform features.

The User Age Group APIs are designed for apps that are for mixed ages (under 13 and 13+) to help ensure users are using the appropriate Meta account for their age.

The Get Age Category API provides the age category data of a user so that you can help ensure that your users have access to age-appropriate content and experiences in your app and treat the data of users under 13 appropriately. We'll validate the implementation of the API by monitoring your API analytics, but we will not conduct any additional review of your implementation.

We are not able to provide advice on your responsibilities, the secure storing/handling of data, or other policy/technical subjects related to regulatory compliance. Please consult with your own lawyer, engineer, or policy expert for this matter. You can read more about complying with COPPA at the FTC website .

You can follow the developer documentation (available with Platform SDK 56.0) to get familiar with the Get Age Category API

All apps for mixed ages (under 13 and 13+) must implement one of the Get Age Category API or risk enforcement action up to and including Store removal and loss of access to platform features.

No, implementation of the Get Age Category API is only necessary for apps for mixed ages (under 13 and 13+).

If your app is not built for both users 13+ and children under 13, you are not required to implement the Get Age Category API.

If you choose to implement the Get Age Category API your app will receive age information from Meta. It is your responsibility to ensure that your app is compliant with all applicable laws and regulations based on the age group of the user, including data privacy and age appropriate design code laws and regulations.

Organization Verification is a process that confirms the authenticity of developer organizations publishing or updating apps on the Meta Quest platform. The process can only be completed by an Admin. The process helps ensure that:

Your organization will need to complete either Business Verification or Admin Verification.

You can start verification by navigating to the Organization Verification page via the:

Organization Verification is required for all developer organizations on the Meta Quest platform. Unverified developer organizations will be blocked from publishing or updating apps and completing Data Use Checkup recertification.

Developer verification is part of our continuing efforts to improve and secure our platform. The first step to accomplish this goal is to ensure developers are verified and able to prove they are legitimate entities and/or people.

Any documents or information you submit to verify your organization will be used to detect and prevent impersonation, fraud and other risks. This helps protect you and the rest of the Meta Quest community.

Business Verification is recommended for organizations that are recognized legal business entities. You can complete business verification if you’re an authorized representative who can receive communications and act on behalf of the organization.

Admin Verification is recommended for organizations that are not legal business entities. If you complete Admin Verification, the individual admin is the authorized representative who can receive communications and act on behalf of the organization. In addition, the authorized representative’s admin verification status will be viewable to other admins in the same organization.

Any documents or information you submit to verify your organization will be used to detect and prevent impersonation, fraud and other risks. This helps protect you and the rest of the Meta Quest community.

The documents you submit will be stored for one year. This is applicable for both business documents and personal ID documents.

When you enter your business information, we look up the details in third-party databases. If we are unable to find your business in those databases, you will be asked to submit documents that show your business name, address and tax ID. You may also be asked to submit documentation with your business phone and email if those pieces of information are not included in the databases.

If you do not have a business phone number, you can complete verification by using a business email. To do so, your email domain must match your website domain and your organization’s legal name must be on your website.

If you are verifying your identity, you will need to upload an identity document such as passport or driver's license.

If you’d like to confirm your connection to your Developer Organization via email, you’ll need to provide your organization’s website when adding your organization’s details.

Typical turnaround time for reviewing a submission is approximately 48 hours. However, becoming verified can take longer if you need to submit additional information.

Yes. Developer organization verification is an additional layer of verification required to publish apps.

If you do not verify your organization or your organization loses verification, you will be blocked from publishing and updating apps and from completing Data Use Checkup recertification.

If you completed the Business Verification process and we weren’t able to verify your business, you can retry verification by submitting more information or go through Admin Verification. In this case, we’ll try to verify your identity. If we can’t confirm your identity with your government ID or two official documents, if could be due to the following:

1. Your photo didn’t meet our requirements. Try submitting your government ID again, and make sure it follows our guidelines:

2. You’ve tried to submit your ID for verification too many times. To move forward with the business verification process, another admin of your organization can submit their ID for verification.

Try requesting another verification code. If you still don’t receive it, then you can troubleshoot phone call issues . If you requested an email code, learn more about how to troubleshoot email deliverability issues .

Yes, although there is no save button, you can exit out and come back later and the verification process will continue where you left off.

As per the updated Virtual Reality Check (VRC) , all multiplayer apps need to have an in-app user reporting flow accessible through the / button. We consider any app with synchronous or asynchronous multiplayer environments a multiplayer app. Developers of multiplayer apps are required to comply with the VRC by adopting one of the two developer tools outlined in the section below.

To comply with these changes, your app must have a form for users to notify you about any conduct and content in your app that does not adhere to the Code of Conduct for Virtual Experiences (CCVE) . This user report form must be accessible to your users via the / button. You can test your implementation by following the steps mentioned here .

To achieve this, you can use either of the following solutions:
1. User Reporting Plugin
2. User Reporting Service

If your app has user-generated content, including synchronous or asynchronous multiplayer environments, then your app is considered a multiplayer app and needs to comply with the updated Virtual Reality Check (VRC) .

Examples of synchronous multiplayer environments include apps where users can directly interact with one another through voice, gestures, or text. Examples of asynchronous multiplayer environments include apps with level editors or apps in which users can upload their own in-app creations for other users to view. Apps with no means of user interaction will not be subject to the updated VRC.

The User Reporting Plugin connects existing reporting flows in your app to the / button, ensuring compliance with the updated Virtual Reality Check (VRC) . Once you connect your existing reporting flow to this Plugin, users can access your reporting flow by pressing the / button and clicking the Report button in the universal menu.

If you have an existing user report flow, you can use the User Reporting Plugin to be compliant with the updated Virtual Reality Check (VRC) . User Reporting Plugin is available as a part of Platform SDK v46 . You can follow the developer documentation to integrate the User Reporting Plugin.

The User Reporting Service helps you create a new end-to-end user reporting flow accessible from the / button, making you compliant with the updated Virtual Reality Check (VRC) . It’s an out-of-the box solution that needs to be enabled in the Developer Dashboard . Once you enable the User Reporting Service in the Developer Dashboard, users on Meta Quest build 50.0 or later can press the / button, then click the Report button in the universal menu to submit a report, which will be sent directly to you.

Anyone can use the User Reporting Service to be compliant with the updated Virtual Reality Check (VRC) . You can enable the User Reporting Service in the Developer Dashboard . As soon as you enable it, you will start receiving user reports within your app from users on Meta Quest build 50.0 or later. You can follow the developer documentation to learn how to customize a reporting flow that meets the needs of your community.

To provide an additional layer of security and privacy, we’re directly encrypting user reports delivered to the developer dashboard. The decryption key is the only way for you to access your encrypted inbox. Meta does not have a copy of your decryption key.

You’ll soon have the option to generate your decryption key in the developer dashboard and start using the directly encrypted inbox. It’s not required at this time to do so, but it will be starting February 1, 2024.

If you lose your decryption key, you can generate a new key by clicking “Lost your key?” on the User Reporting page under Platform Services. Doing so will also generate a new encrypted User Reporting Inbox. Be mindful and do not generate a new decryption key if you have access to your current key.

If you generate a new key, you won’t be able to open your old encrypted inbox anymore. Old reports will be lost and you won’t be able to read them again.

The details for implementing the User Reporting Plugin are covered here . For engineering support, reach out to our developer forum or support center here .

Note: User Reporting Plugin is not available for Rift and PCVR apps. The User Reporting Service will be the primary reporting tool for Rift and PCVR apps, even if User Reporting Plugin is selected as the primary reporting tool.

Yes. Users will still be able to report under 13 users directly to Meta using this website after the existing Meta Quest platform reporting is phased out. For apps that have their own underage reporting flows, users will continue to be able to report under 13 users directly to developers.

Users can reach out to Meta here , or by clicking “Flag this app” on your app’s product description page on the Meta Quest Store, if they’re experiencing issues with an app.

A Meta account lets you log into your VR devices and view and manage your purchased content in one place. You can set up a Meta account with your email address or Facebook account. If this is your first time creating an account to use a Meta VR product, you can also set up a Meta account with your Instagram account. For more detailed information, check out our developer blog post .

Set up your Meta account from a web browser , the Oculus mobile app or in VR. You can manage your Meta account information at any time under the respective 'Settings' menu once you set up your account.

Yes. If you have previously merged your Facebook account with your Oculus account, you will need to create a Meta account to log into Meta Quest developer surfaces and devices. If you have not merged your Oculus account with your Facebook account, you may continue logging in using your Oculus account until January 1, 2023. You cannot create a new Oculus account.

Yes. Meta accounts, along with Meta Horizon profiles, are replacing Oculus accounts for both developers and users.

No. Information saved in your Meta account includes your payment information, date of birth, email address, phone number and purchased apps. This information isn’t public, but you can choose to share which apps you’ve purchased with your followers or other users via Settings.

No. You can choose to add your Facebook and Instagram accounts to the same Accounts Center as your Meta account to allow for cross-login functionality and connected experiences like finding Instagram followers in VR, but this is not required to use VR or access your device. Your Facebook and Instagram accounts can be added or removed from your Accounts Center at any time. Please Note: if you’re using App Ads , you’ll need to add your Facebook account to the same Accounts Center as your Meta account to continue publishing ads.

Test user accounts are not a requirement, but they can help debug apps, test multiplayer functionality, and more. It’s possible to develop an app without creating a test user account. Test accounts for development can be created in the Developer Dashboard after you set up your Meta account. If you continue using an Oculus account, you will be unable to create new test accounts until you set up your Meta account.

If you created test user accounts prior to setting up a Meta account, you’ll also need to set up a Meta account for each test user account to continue using them, including creating a Meta Horizon profile. To do so, login to your test account and complete the same Meta account set up steps as your primary account. New test accounts that you create after setting up your Meta account will not need to complete these steps.

App entitlements are stored at the Meta account level, and are transferred from Oculus accounts. App entitlements and other durable purchases like subscriptions, content packs and avatar accessories/content only need to be paid for once per account.

No. Only one email address is supported per Meta account. You can create multiple Meta accounts if you so choose, but each account requires a different email address.

You can create multiple Meta accounts, but each one requires a different email address. App entitlements on one Meta account will not be available to other Meta accounts unless you've enabled the App Sharing feature to share apps across accounts on the same Meta Quest or Meta Quest 2 device.

Yes, these account changes apply to all countries.

If you’ve been using Facebook to login to Meta Quest and choose to set up your Meta account with Facebook added to the same Accounts Center, you won’t need to re-verify your account. If you’ve been using Facebook to login to Meta Quest and have previously verified your account using phone verification, but choose not to add your Meta account to the same Accounts Center as your Facebook account, you may need to re-verify your account in order for it to remain valid.

To re-verify your account, click here . Learn more about developer verification policy in our documentation . For more FAQs on developer verification, see below .

A Meta Horizon profile is your social presence and how you appear to others. You can customize your username, avatar and other information.

A Meta account lets you login to Meta VR products and manage purchased apps.

A Meta Horizon profile lets you choose how you do and don’t appear to others in VR, so you can connect, explore and share. You will be required to create a Meta Horizon profile when you sign up for a Meta account. For more detailed information, check out our developer blog post .

You create a Meta Horizon profile when you set up your Meta account. You’re required to have a name (what you want people to see when they interact with you like ‘Monique Smith’) and username (your unique identifier in VR like ‘WarriorMama365') to start using your device, and can select your follower and privacy settings too. You can set up your avatar later, but you'll be required to finish this step before entering some multiplayer experiences. You can manage your Meta Horizon profile settings in VR, in the Oculus mobile app, or on the Meta Quest website. For more information, visit our Help Center .

Profile names and usernames are part of your Meta Horizon profile. Your username is your unique identifier in VR (WarriorMama365), while your name is what you want people to see when they interact with you (Monique Smith). You can change your username once every six months and can change your profile name anytime. We encourage you to use profile names as the primary way people are displayed in your app, so users consistently know how to refer to one another. You can still request access to username if this unique identifier is important to your app experience (e.g. for differentiation purposes). You can view the profile name and username for members in your organization by visiting the Members dashboard in the Developer Dashboard .

We’re shifting from a “Friends” model to a “Followers” structure, similar to what we currently offer on Instagram. Your existing Oculus friends will become your followers, with the option to remove or block followers at any time. Users who follow one another will be able to send messages to each other and join the same Party, roster, or in-app multiplayer activities. A person can join a Party with someone they do not follow and who doesn’t follow them if they’re invited by someone they both follow. The Oculus mobile app supports a message request inbox that allows users to send messages to someone who doesn’t follow them. Users who engage with your app are displayed according to their Meta Horizon profile information.

No. Meta accounts retain the existing Platform SDK method of accessing Username and Name, which can be found here .

App Lab is a channel for developers to distribute apps directly to customers safely and securely. App Lab connects customers to apps without requiring store approval or sideloading. App Lab supports both free and paid apps, which are shareable via a URL or Meta Platform Technologies Keys. While App Lab is distinct from the Meta Quest Store and App Lab apps won’t appear in the Store, customers who install apps from App Lab will find them in their Quest library. App Lab apps can also be searched by exact name and found in the “App Lab” section of results.

We’ve taken steps to reduce the technical requirements and Virtual Reality Checks (VRCs) to make submission as simple as possible. In order to promote a safe, secure and positive experience, App Lab apps are required to comply with our App Lab Policies , including our Content Guidelines , Data Use Policy , and App Policies . Apps submitted to App Lab must support App Sharing as explained in our App Lab Policies. Before getting started, please review our App Lab VRCs . Apps are reviewed at submission and may be re-reviewed as they scale to more people.

To start your App Lab submission, follow these steps:

Yes, App Lab shares the same payments and advertising policy as the Meta Quest Store, and a revenue share is paid pursuant to our Distribution Agreement.

See the Meta Horizon Store FAQ .

In the early phase of Quest, we carefully managed the catalog of our store to ensure that it was growing healthily and that our developer community could build sustainable businesses. As we grew we've steadily opened the opportunity, first with the creation of App Lab, and now with the move to a fully open store. Curation helped us make Quest a success, but now it is time to move into the next phase of growth for our platform.

Starting August 5, 2024, we’re moving all content previously shipped in App Lab to be discoverable on the Meta Horizon Store. This also includes all apps under development, apps under review, and all existing App Lab apps.

Read more here about how you can get your App Lab app ready for the Store.

No downtime is expected.

Starting August 5th, we will begin moving apps over in phases, we will send out an email once all of the apps have been moved.

If your app is launching after August 5, 2024, it will be available in the Meta Horizon Store.

If your app is still in early development, follow the steps to prepare your app for Store: review the updated VRCs your app must pass to get onto the Store and update your app Metadata. If you want to launch before your app content is fully finished, you can enable Early Access. Learn more about Getting Your App Ready for Store in our latest blog .

Actions you need to take and the resources available to support your success in the Store:

1. Review Virtual Reality Checks (VRC) to make sure your app meets VRC requirements to ensure better visibility. More information on VRCs can be found below.

2. Go through your app metadata: descriptions, comfort level, keywords, category, genres, and assets to make sure it’s up to date.

3. We will have an “Early Access” label you can enable. This is a good route to set user expectations if your app is still a work in progress. Learn more here .

4. In case of an influx of users, prepare any scalable resources like cloud tools, matchmaking, etc.

5. Consider alternatives to publishing to Store below if you feel that your app is not ready. More details in the blog .

Early Access is a new model developers can leverage to engage early with their community and modify the development of their project based on their feedback. Developers can only select "Early Access" if they have not already published to the Meta Horizon Store. App Lab developers have until August 5 to select Early Access for their app. To opt-in to Early Access, you can visit the Developer Dashboard and navigate to App Submissions > App Metadata > Specs. After publishing to the Store, you will have 30 days to select Early Access within the metadata submission flow. Read more in this blog post .

Yes, if your App Lab app turns on the Early Access flag for the Store, your existing reviews will be retroactively tagged as Early Access reviews.

We’ve updated our VRCs to consolidate the Meta Horizon Store and App Lab requirements into one guide to ensure a smooth and simple process. Updated VRCs your app must pass to get onto the Store include the following:

It is critical that apps meet VRC standards, you can read more about VRC requirements and the latest changes to VRCs here. Not complying with VRCs can result in apps not being discoverable or removed from the platform.

We have updated our VRCs to consolidate the requirements for the Meta Horizon Store and App Lab into one guide, ensuring a smooth and simple process. The updated VRCs that your app must pass to be included in the Store are as follows:

If you would like additional time to finetune your apps, ensure you’re meeting all required VRCs, or want additional time to get user feedback before launching your app on the Store, you can delist it from the Developer Dashboard.

Meta Quest Release Channel features provide a simple and convenient solution for releasing an early version of your app to limited audiences and gather additional user feedback before submitting it for a full launch. Private release channels enable you to invite users via email or URL, and added users will continue to have access to updated versions of your build until they are removed or the release channel is deleted.

Release channel invite URLs can be created in the Developer Dashboard and will be active for 90 days before being disabled unless a new build version is uploaded. To learn more about Release Channel features and invites, visit the documentation.

There are multiple steps involved in the review process, and you should receive notification throughout each stage of the review. If you have concerns about a deadline that you need approved by, we recommend submitting for review four to five weeks in advance.

While it is not a requirement to use the release channels, we recommend that you manage your builds in this way. This is the most effective method of deploying to specific users for testing as well as managing different builds.

Please contact the store submissions team at submissions@oculus.com to request price changes for your app.

Please contact the store submissions team at submissions@oculus.com referencing the need to suspend distribution of your app.

Please see our financial FAQs . If the FAQs don’t answer your question, you can contact payout support here .

Check your player settings and make sure "Virtual Reality Supported" is checked and that "Oculus" is in the list of supported devices.

There are two things you can look into to solve this problem:

Check and make sure that you have added both OVRManager and OVRPlatform script files to your scene.

Right here .

The headset must be on your head for touch haptics to be activated.

Not typically. Depending on the type of projector being used this may be possible. Please see the forum thread here for more information.

Unity's render statistics report a higher FPS than reality because they track all cameras. You should only take into account the Oculus script's FPS reading.

Please see the blog post on optimizing for Gear VR here for a good break down of best practices.

Please see the forum post here regarding setting this up. There are also instructions regarding setting up a basic list of players in text format as well.

The command to set the pixel density in UE4 is 'hmd pd'. You need to detect what phone you're running on and scale it up to increase the quality.

Yes, but not unless you build from source. You can use Wwise and our plugin to render ambisonics and Media Framework to render video.

No. The stereo cubemap won’t line up with 3D content when the user’s head pose has any pitch or roll.

There are two ways to render a portal: rendering to a texture for the content on the other side of the portal and regular render and stencil in the foreground geometry. The second approach is definitely going to work better performance wise on the Gear due to bandwidth limitations.

Here are some helpful links:

We currently do not recommend using HDR on mobile platforms. This is because HDR consumes far more texture bandwidth than the regular pipeline.

In unreal engines 4.13+ there is the ability to use a cubemap overlays to perform this function.

You will need to tick the LeftTexture box in Cubemap Overlays Properties to enable it.

See the documentation here:

Yes. See the following instructions: All the parameters that in blueprint are given to AddLoadingSplashScreen can also be written in the DefaultEngine.ini file of their game (Config/DefaultEngine.ini), as shown:

(most of those parameters are optional)

[Oculus.Splash.Settings]

TexturePath=”path”

DistanceInMeters=translation (vec3)

Rotation=rotation (quaternion)

SizeInMeters=size (vec2)

DeltaRotation=delta (quaternion)

As part of our ongoing efforts to provide a secure platform, all Meta Quest developers need to verify their accounts by providing a payment method and/or phone number. Developers in organizations with bank account information (i.e. published apps) are already in compliance. Accounts that remain unverified may be subject to future actions as described in our policy .

If you’ve set up 2-fac with your Meta account, you’re already in compliance and do not need to verify. To check whether your account is verified, please visit /manage/verify .

If you’ve already added a payment method (excluding Paypal), you’re already in compliance and do not need to verify. To check whether your account is verified, please visit /manage/verify .

Developers in organizations with bank account information (i.e. published apps) are already in compliance. To check whether your account is verified, please visit /manage/verify .

Please verify that your phone carrier and country are supported for SMS two-factor verification by visiting our help page: https://www.facebook.com/help/130694300342171 . If your phone carrier and country are not listed, you are not eligible to use SMS two-factor verification and will need to add a payment method (excluding Paypal).

If you do not verify your developer account, your account will be locked on the Developer Dashboard , which means you cannot make updates to your apps or access information about your apps until you verify your account. You will also lose access to Developer Mode, which means you will not have access to developer capabilities, such as installing apps through non-Store channels. Pre-existing content will still be available but will not be able to update if the developer account is not verified. As we continue to improve our tools, we may apply additional restrictions in the future, including locking your account on other Meta Quest surfaces.

No. Only developers requesting access to those platform features that require oversight, which include User ID, User Profile, Avatars, Deep Linking, Friends, Invites, Matchmaking, In-App Purchase, and Parties.

You will receive a notification via email and also be notified within the Developer Dashboard upon login. If you know your app uses any of the platform features that require oversight, you can proactively complete the checkup. If your app does not use any of the platform features that require oversight, you do not need to complete Data Use Checkup..

You will need to renew your certification on an annual basis, starting from the day the first certification was approved. You will receive a warning 60 days before the certification renewal is due.

If your app is live in the Meta Quest Store, you will have 60 days to complete the Data Use Checkup process once notified. Notifications will be sent via email to the email address associated with your Meta Quest account. If you do not complete Data Use Checkup within the 90-day window, your app will be removed from the Store until the checkup is completed.

Going forward, you will need to renew your certification annually starting from the day your first certification was approved. You will receive a warning 60 days before your certification is due. If you have not completed the certification by that deadline your app will be removed from the Store. If you have still not completed the certification by 30 days after that deadline, your app’s access to Meta Quest Platform features will be revoked.

Meta Quest App Review ensures that your application meets all of our Virtual Reality Checks (VRCs), Content Policy and Publishing Asset Requirements. Data Use Checkup ensures your access to platform features and data use comply with the Developer Data Use Policy.

The Data Protection Assessment (DPA) is an annual requirement for apps that assess certain advanced Meta Quest Platform features, specifically, but not limited to In-App Purchase, Subscriptions, Friends, Deep Linking, and Invites. Features that access a users' most sensitive data come with a higher level of review. In a situation where your app is receiving this level of access, we may request more information.

The DPA questionnaire assesses how developers use, share, and protect User Data and Device User Data (“User Data”) as defined in the Developer Data Use Policy. Completing the DPA helps us offer a safe ecosystem that users can trust.

Note: The Data Protection Assessment is not the same as the Data Use Checkup (DUC). The DUC focuses on certain Meta Quest permissions an app has access to and is an annual process that requires developers to certify that their continued use of user data is in compliance with our Developer Data Use Policy..

No. Not every developer will need to complete a Data Protection Assessment. The Data Protection Assessment is a requirement for all Meta Quest apps accessing advanced Meta Quest Platform features. Advanced Platform Features include, but are not limited to In-App Purchase, Subscriptions, Friends, Deep Linking, and Invites.

The Admin(s) of your developer organization will receive an email from Meta Quest asking you to complete the Data Protection Assessment by a specific deadline.

To complete the DPA, view details of your compliance requirements or track the status of an assessment, please visit the Compliance Dashboard by going to the Org Manager sidebar in the Developer Dashboard. The Compliance Dashboard has a table with each row listing a separate compliance issue. You can filter the table by status, compliance requirement, or app name. For more information, please read the documentation.

Here are the steps to prepare for completing the Data Protection Assessment:

In the email from Meta Quest asking you to complete the Data Protection Assessment, there will be a link to the questionnaire on the Developer Dashboard. You can also find the questionnaire by going to the Developer Dashboard , selecting your app, and then clicking “Data Use Checkup”. If you have an assessment for the app, it will be shown in a banner at the top of the page. Click the button on the banner to navigate to the assessment. Enter your responses and click submit. You do not need to complete the assessment in one sitting. You can save your progress and return to the assessment later so long as you remain within the deadline to submit.

Please refer to our documentation for more detailed information and guidance.

Did you know? Our new Data Protection Assessment video course has tips and resources from Meta experts so you can get clarity on what’s required.

Go to the Developer Dashboard , select your app, and then click “Data Use Checkup”. If you have an assessment for the app, it will be shown in a banner at the top of the page with a button to navigate to the assessment as well as the deadline and your submission status.

Failure to complete the Data Protection Assessment by the deadline will result in applicable apps being removed from the Meta Quest Store or App Lab and revoked access to advanced Platform features, which will potentially impact existing entitlements and app functionality.

As part of our commitment to protecting people’s privacy, we update the Data Protection Assessment to meet current privacy and security policies and industry standards.

Upcoming: In January 2024, we’ll be enhancing the DPA questionnaire to be in line with industry standards regarding personnel security practices, audit logging, and security monitoring. You can start preparing for these upcoming changes by reviewing this resource guide.

The General Data Protection Regulation (GDPR), which goes into effect May 25, 2018, creates consistent data protection rules across Europe. It applies to all companies that process personal data about individuals in the EU, regardless of where the company is based. Processing is defined as anything related to personal data, including how a company handles and manages data, such as collecting, storing, using and destroying data.

Each company is responsible for complying with the GDPR, just as they are responsible for complying with the laws that apply to them today.

Developers must implement and disclose their own complete and accurate privacy policy explaining how they collect, use, and disclose data as required by applicable law. Because each developer has different practices and uses information in different ways, using Oculus's privacy policy would not be appropriate.

Your privacy policy must explain your practices regarding the collection, use and disclosure of data, and we cannot write it for you. We suggest you contact your legal team or seek external counsel

No. We do not “process” data on behalf of our developers under the definition of the GDPR.

No. We do not offer a Data Processing Addendum, because we do not process data on behalf of our developers.

Whether or not your app is compliant depends on many factors that we cannot evaluate for you. It is your responsibility as the developer to make sure that your app complies with the GDPR.

In light of the GDPR, we are offering new tools and information to people who use our services to help them better control their privacy and understand how Oculus uses information. For information about some of the efforts we're taking to make sure we are complying with the GDPR, see our blog post here .