The following policies will apply to all apps hosted on the Meta Horizon platform.

Apps hosted on the platform may not contain, use, or make available commerce solutions — including for app payment processing, in-app purchases, or in-app advertising — except as specifically provided in this policy, the platform SDK, or otherwise expressly agreed by you and Meta Platforms Technologies in writing. For example, if your app has in-app purchases, and your app is distributed through any Meta Platforms Technologies distribution channel, including the Meta Horizon Store, you must use the Platform In-App Purchases to handle such payment processing. In-app advertising must follow the Advertising policy.

The following exceptions to the above policy are permitted:

Apps hosted on the platform may not run ads unless expressly agreed by you and Meta Platforms Technologies in writing.

Notwithstanding the above, certain apps that fall under our Windows into an existing service and Social Media apps policies are permitted to run ads. Any apps showing ads must comply with applicable laws and advertising standards in the territories in which the ads are delivered, including without limitation that ads must not be deceptive or unfair, and claims must be able to be substantiated. Additionally, all ads must meet the following content, privacy and functionality requirements:

Ads are considered part of an app and must follow all policies applicable to apps, including without limitation the Content Guidelines, App policies found on this page, and Developer Data Use Policy.

Ad content must also meet the following requirements:

Ads must meet format requirements, and must not negatively impact the user experience.

There are a number of laws and regulations across various jurisdictions that apply to advertising to young people of different age groups. Developers are responsible for ensuring that any ads in their apps that are shown to young people comply with those laws and regulations, such as the following:

The digital age of consent varies in different jurisdictions and in different contexts. You should consult with your legal counsel to help determine what obligations and/or age-based restrictions may apply to your app. See also our Developer Data Use Policy for more information on how you can use data Meta provides.

You may use promotional mechanisms (e.g. Keys, promo codes, or other mechanisms) in your app to give a limited number of users an entitlement to your premium application, one-time access to in-app products, items or events, or trials to subscriptions.

The platform is intended to provide quality content designed to operate on supported devices. In order to safeguard the integrity of the platform, and promote a good user experience, apps may enable access to other apps (streamed or otherwise), only if:

Plugins or extensions are allowed as long as they do not require purchase. Apps cannot include purchase of other apps or experiences unless they comply with Meta Quest Payments policy.

Note that you are responsible for the functionality and compliance of all apps, plugins or extensions you offer through your app, including adhering to the policy on Payments, the Content Guidelines, Developer Data Use Policy, and any other applicable terms and policies.

We want users to enjoy their apps within a reliable and trustworthy ecosystem. Our Meta Platforms Technologies system-level features were designed to enhance and streamline the user experience across apps. You must not disable, override or otherwise alter any such system-level features or other system behavior. In addition, your apps must not contain any features, functionalities or other elements that could confuse users regarding the distinction between your app and the Meta Platforms Technologies system (e.g., by mimicking any system-level feature, or introducing any feature that users would reasonably expect to be a system-level feature). Please note that our SDK Agreement also prohibits any such activities.

No trademarks of Meta — including its name, logo, and those of its products or its partners’ products such as “Rift,” “Gear VR,” “Go,” or “Quest” — may appear anywhere in your app. The exceptions are:

The Meta Brand site contains detailed information about how you may use the Meta name and assets.

The Multi-User feature allows a primary user to add other users to their Meta device. Once Multi-User is enabled, the primary account holder can also enable App Sharing to share their app entitlements with those secondary accounts. Secondary account holders will be able to launch the primary user’s apps from their own app libraries on the shared device and have their own identities, achievements, and game saves in the apps.

App Sharing is a platform feature and all submitted apps must support App Sharing, unless otherwise agreed to in writing by Meta Platforms Technologies. For clarity, this policy applies regardless of anything to the contrary in the Distribution Agreement.

Apps may include the following types of streamed content:

If the introduction of streaming may cause customer discomfort, developers should provide a robust warning to users. For more information, see our streaming VRCs for best practices in streaming.

Windows into an existing service are apps whose primary purpose is for users to consume pre-existing, off-platform, non-interactive media content. These apps may be native rectilinear apps, or apps where the content is displayed on one or multiple rectilinear panels within a non-interactive environment or an environment of limited interactivity. Limited interactivity means that any interactive element is peripheral to viewing content on the panel or intended to enhance the viewing experience.

Examples include creating environments such as movie theaters, sports stadiums, multi-panel living rooms.

Social media apps are apps where the primary purpose is consumption of user-generated video or text and where such content is displayed on one or multiple rectilinear panels, within a non-interactive environment or an environment of limited interactivity.

Apps which are paid, include in-app purchases, serve in-app ads or request Platform SDK features may not provide only limited utility or functionality.

Cross-app linking (where a user can travel between two apps directly) made possible with deep linking (Unity, Native, Unreal) and other similar means cannot be monetized, without Meta’s prior written permission.

Any cross-app linking needs to be age appropriate for users in accordance with the age ratings of the experiences, and comply with our policies and applicable laws, including informed user consent for accessing links and compliance with our Developer Data Use policy.

Examples of what is NOT allowed include:

Examples of what is allowed include:

We strongly advise that all developers ensure their app is compatible and functional across all Meta devices in order to provide the best possible experience for their users. This allows users to fully utilize and enjoy their purchases.

However, if you choose to end support for your application on one or more Meta devices, in such a way that users of your app will lose access to its content, or may no longer use essential services that it provides, then you must give Meta and your users a minimum of 180 days’ prior written notice.

This notice must include information about the details of the deprecation, such as the specific device(s) or platform(s) affected and the date of discontinuation. It is important for developers to communicate clearly and effectively with their users.

For users who are not using supported devices, annual subscriptions active at the time of your notice will be canceled. Applicable prorated refunds will be processed for annual subscribers as set out in the Meta Quest Content Refund Policy.