Passing the Most Commonly Failed VRCs

Privacy.1 addresses the most basic requirements for your policy: that it applies to your business and to your app, and that users can freely access it. To avoid delays and interruptions, make sure your privacy policy meets these criteria:

First, as obvious as it sounds, the link you provide must be live and remain live as long as your app is on the Store. Consider a monitoring tool that regularly checks the status of your page and alerts you if it goes down.

Second, your website must have a proper HTTPS connection. Make sure your website and privacy policy page are secured with a valid SSL certificate.

Third, the link you submit must include a privacy policy. We see this issue often. Do not link to a page hosted by a third-party site such as Discord.

Fourth, your privacy policy must be publicly available. Make sure users are not required to enter any data or log in to view it.

Finally, your privacy policy must be specific to your organization and your app. Don't copy the policy of a similar app or link to anyone else's privacy policy. The privacy policy must mention this specific app, or your submission will fail.

Remember, this isn't the only VRC your privacy policy must satisfy. Review all required privacy VRCs and evaluate your privacy policy before you submit your app. These proactive steps will help get your app live faster and set you up for long-term success.

Privacy.4 is all about making sure your privacy policy provides a clear process for users to request their data be deleted. Most often, apps fail this VRC because the clause is either missing altogether or does not adequately protect users' rights.

To pass Privacy.4, start by confirming your policy includes a dedicated deletion clause. Then, make sure that section satisfies these four criteria:

First, you must provide your users with clear instructions for making a deletion request. Include the specific steps they need to take. Whether it's submitting a request via email, filling out a form, or using an in-app feature, the process should be easy to follow.

Second, inform your users of any exceptions to the data deletion process. For example, you may need to keep certain records or data for compliance purposes. If this applies to your app, clearly communicate those exceptions in your privacy policy.

Third, do not include any language that suggests your deletion clause only applies to users with certain characteristics. Apps often fail this VRC because their privacy policy suggests that only users in certain geographic regions, like California or the EU, can request deletion. Make sure your policy clearly states that all users can submit a deletion request.

Fourth, and finally, you cannot charge your users to delete their data. Make sure your deletion clause does not state or imply that users must pay a fee for deletion.

The bottom line is you must allow users to request their data be deleted, and your privacy policy must give them a clear blueprint to do so.

The VRCs in the Publishing category relate to what you provide for your app's Product Detail Page. We evaluate these details as a part of app review. Many apps fail Publishing.1, which requires you to provide a valid URL to your app's website. Here's what you need to do to pass this VRC.

First things first, the URL you provide must link to a live website. Apps often fail Publishing.1 because the site throws an error. Consider setting up a monitoring tool that regularly checks the status of your page and alerts you if it goes down.

Second, your website must be secure. Apps often fail this VRC because users are alerted that the URL may not be safe or private. Before you submit, make sure your website is protected with a valid SSL certificate.

Third, keep in mind that “valid” doesn't just mean live or secure. The majority of apps fail this VRC because the URL is hosted by a third party like Discord. Provide a link to a functional website URL that is publicly accessible and clearly applies to your organization and this specific app.

Fourth, and finally, make sure the content on the page adheres to Meta's Content Guidelines. If you haven't already, review the Content Guidelines to verify your website is compliant.

Providing the URL for your app is a quick and simple step, so it may be easy to overlook this VRC. Taking time to ensure the link meets these requirements before you submit will help you clear the review process faster.

To pass Functional.3, your app shouldn't crash, hang, or leave users stuck at any point. That includes the very beginning of the experience.

If your app requires a login, you must provide instructions for a user to create an account. Those instructions must be easy to find wherever accounts are created, and always discoverable in VR.

Next, your app cannot have any progression blockers. At a high level, users should be able to progress through the game's timeline or from one level to another. So, a user's inputs should elicit appropriate responses. For example, if a user turns a door knob, the door should open.

The bottom line is, it shouldn't be difficult for a user to move through your app. Before you submit, play through your app and make sure you can progress through the content for at least 45 minutes.

While we do see progression issues, developers actually fail this VRC most often because they don't provide test credentials. That effectively leaves our reviewers “stuck.” If your app requires a login, include test credentials so we can begin the testing process.

When you define your app's metadata, you'll indicate whether the play mode for your app is sitting, standing, or roomscale. This helps users understand the physical space and requirements necessary to use your app, so the play mode you select must be accurate.

Beyond accuracy, you should consider your selection from an accessibility point of view. Many users choose apps based on physical differences. Apps often fail Tracking.1 because progression requires a greater range of motion than the play mode implies.

To meet the requirements for sitting, your app should be completely playable while a player is seated in stationary furniture, like a couch or fixed-position chair. Make sure your app never requires a player to stand, lift off the seat to reach down to the ground, or pivot more than 90 degrees to the left or right.

Even though it may be the chair you use for testing, a gaming chair with wheels and a swivel isn’t a good benchmark for meeting the sitting requirement. Test your app using a stationary chair and confirm that the app never requires you to leave the seated position.

To comply with the standing mode, your app must be completely playable from a fixed standing position. The app can require limited motion, like turning around or reaching. But users shouldn't have to take more than two steps in any direction within the play area.

And finally, to comply with roomscale requirements, your app must be completely usable within a play area measuring 6 and a half feet by 6 and a half feet or greater. Roomscale ensures users have enough physical space to progress in your app, and implies an unlimited range of motion within that space.

If you're unsure which mode most accurately reflects your experience, go with the mode that has fewer limitations. Standing even once in an experience designated for “sitting” may not seem like a big deal, until a user is physically incapable of doing so. Setting the right expectations helps avoid user frustration, and contributes to the success of your app.