Distribute and grow

App policies

Updated: Dec 9, 2025

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

1.1. Payments

1.1.1. 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.

1.1.2. The following exceptions to the above policy are permitted:

Bulk IAP or Subscription Licenses: Developers may sell licenses for prepaid in-app functionality off-platform only when selling such licenses in bulk to business customers (such as companies or educational institutions).

Windows into an Existing Service: Apps that are Windows into an existing service may sell access off-platform for their pre-existing, off-platform subscription content.

Physical goods and services: Sale of physical goods and services consumed outside of your app is allowed only if you have obtained express agreement from Meta Platform Technologies in writing. Developers must use purchase methods other than Platform In-App Purchases to collect payment for physical goods and services.

1.2. Promotional mechanisms

1.2.1. 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.

Per the Content Guidelines, these mechanisms must not facilitate or promote online gambling, online real money gambling, or online lotteries (such as being a prize in sweepstakes that require payment of some kind).

These mechanisms must not be offered in exchange for, or as a reward for, a user review, and you are not permitted to give away physical goods in connection with any promotional mechanism.

You must administer these mechanisms fairly and in accordance with all applicable laws and regulations. You must not disadvantage users of the Meta platform through these mechanisms. For example, if your content is sold at a lower price elsewhere, you must make a comparable offer to users of the Meta platform.

Meta will not assist you in the administration of your promotional mechanisms. We may take action if we find that your use of promotional mechanisms does not comply with this policy, including revoking your access to promotional mechanisms provided by Meta (e.g. Keys).

2.1. Advertising

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

2.1.2. 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:

General requirements

2.1.3. 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.

2.1.4. Ad content must also meet the following requirements

Ad content must be age-appropriate. Ads and their associated offers (for example, the ad is promoting the download of another app) must be appropriate for the content rating of your app.

Ads must not contain sexually explicit content (even if not rising to the level of pornography) even if such content may otherwise be allowed under our Content Guidelines.

Ads must not promote unsafe substances (including recreational drugs), weapons, ammunition or explosives, tobacco and related products, alcohol, online gambling, or CBD and related products.

Ads should not portray adults or children in unsafe situations or condone unsafe behavior.

Ads must not imitate or impersonate system features or services or interfere with the main function of the app or normal system/device operation.

Ads must include proper disclosures and cannot be disguised as editorial content. The disclosure requirements can vary by jurisdiction.

Format requirements

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

Only in-stream ads (pre/mid/post-roll), overlay, banner, or interstitial ads are allowed. Ads that are not intended to pause content in the app (e.g., banner ads) cannot disrupt the user experience by taking up more than 40% of the panel containing the content. Ads that pop up in the environment (outside of the panel the app is running in) are not allowed.

Ads cannot be stereoscopic, head-tracked or immersive.

Apps which contain a link must use the default external browser when opening that link.

Ads should be easily identifiable and not blur the line between advertising and non-advertising.

Advertising to users under 18

2.1.6. 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:

Ads must only promote age-appropriate content and products.

Ads must not exploit the immaturity, credulity, or lack of experience of young people, including without limitation in connection with the use of premiums, loyalty programs, sweepstakes and contests.

Ads must not apply pressure or imply peer status or other unsubstantiated benefits.

Ads must not promote unhealthy foods (“HFSS” – High Fat / Salt / Sugar content).

Ads must not contain direct exhortations to purchase, or have parents purchase the products (“Buy this now!” / “Tell your parents to buy this now!”).

Apps may not use data provided by Meta from users under the age of 13 or under the digital age of consent (whichever is higher) to target or customize ads. Notwithstanding the foregoing, apps may use necessary data such as age and coarse location data to identify such users for the purpose of ensuring that the ads shown to such users, if any, comply with appropriate laws and regulations.

2.1.7. 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.

3.1. Store within a store

3.1.1. 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:

The content has already been purchased by the user and the app is merely enabling access to that content, or

The content is delivered from a local source connected via a local network.

3.1.2. 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.

3.1.3. 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.

3.2. Streaming

3.2.1. Apps may include the following types of streamed content:

Rectilinear, video or non-immersive content, regardless of the streaming source

Stereoscopic, head-tracked or immersive content streamed from a local source connected via a local network tethered to a user’s PC, either by a wired or wireless connection

Stereoscopic, head-tracked or immersive content streamed from virtual devices or cloud sources is allowed only if you have obtained express agreement from Meta Platform Technologies in writing.

3.2.2. 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.

3.3. Cross-app linking

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

3.3.2. 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.

3.3.3. Examples of what is NOT allowed include:

Agreements or understandings between developers to exchange anything of value to promote apps via deep links. A thing of value, includes but is not limited to, data, fiat or digital currencies, in-game tokens, points, coins or other exchangeable goods, or in-kind transfers.

Per-user, time-spent, or other engagement-based agreements or understandings paid out to the originating app for directing user traffic.

Intentionally using linking to manipulate app distribution on Meta’s surfaces or circumvent any Meta policies, including Meta’s Payments policy or Developer Data Use Policy.

3.3.4. Examples of what is allowed include:

Making exclusive content, features, or discounts available to users via deep links.

Static paid brand placements.

3.4.1. 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.

3.4.2. 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.

4.1. Windows into an existing service

4.1.1. 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.

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

These apps are allowed to run ads in standardized formats (e.g., pre/mid/post roll, brand cards, overlays, etc.) and are subject to requirements set out in the Advertising policy.

These apps may not charge additional fees to users to access limited Virtual or Augmented Reality interactivity, elements, or content.

All purchases must follow the Payments policy.

4.2.1. 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.

These apps are allowed to run ads in standardized formats (e.g., pre/mid/post roll, brand cards, overlays, etc.) and are subject to requirements set out in the Advertising policy.

All purchases must follow the Payments policy.

4.3. Limited functionality apps

4.3.1. 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.

4.4. Apps that override system behavior

4.4.1. 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.

4.5. Video container apps

4.5.1. Collections of unique, high-quality 360 videos are welcome, especially if they’re interactive. If your app is primarily video, consider integrating spatialized audio. We generally do not accept apps that only present a small number of 2D videos, nor apps that are a wrapper for a single 360 video.

4.5.2. For single 360 videos, consider publishing to Meta Platforms Technologies Video. Meta Platforms Technologies Video features high quality content that demonstrates the immersion of VR in engaging short 360 videos. Visit the Meta Platforms Technologies Creators Portal for more details on how to publish to Meta Platforms Technologies Video.

4.6. VPN and password manager apps

4.6.1. VPN and password manager apps are not permitted on the Horizon platform without Meta’s prior written permission. Only VPN apps that have a valid App Defense Alliance security certification are eligible for consideration. Meta reserves the right to conduct security audits of such apps at any time.

5.1. Comfort ratings

5.1.1. Comfort is very important to us. Comfort is a subjective, variable, and individual experience. However, we want to communicate to users as best we can about what they can generally expect from a VR app. You must assign your app one of three comfort ratings: Comfortable, Moderate, or Intense. You can get a sense for how these are applied by looking through the Meta Horizon Store catalog.

“Comfortable” experiences generally avoid camera movement, player motion, or disorienting content and effects. Generally, apps that have fixed camera position will be classified this way.

“Moderate” experiences, on the other hand, might have more camera and player motion.

“Intense” experiences usually incorporate first person camera motion, acceleration, or significant camera movement and player motion.

5.1.2. In general, pay a lot of attention to comfort in the user’s VR experience. Investing in comfort is worth it. Even “Moderate” and “Intense” apps should strive to be as comfortable as possible.

5.2. Content ratings

5.2.1. All apps must be rated by the International Age Rating Coalition (IARC). All apps that will be released in South Korea must also be rated by the Game Rating and Administrator Committee (GRAC). You can obtain ratings directly through the Developer Dashboard, in the Submission Info > Content Ratings section.

IARC

5.2.2. IARC and its member rating authorities provide ratings designed to inform consumers and reflect cultural differences around the world. Once the ratings process is completed, the IARC provides age ratings that help users make age-appropriate choices. During the submission process, you will be redirected from the developer dashboard to the IARC website to complete a questionnaire about the content in your app. There is no fee to you to request a rating, and results are provided instantaneously. By requesting an IARC rating, you understand and accept that Meta Platforms Technologies will disclose your app name, organization name, and contact email to IARC for purposes of obtaining a rating.

GRAC

5.2.3. Meta Platforms Technologies is an authorized GRAC self-rating authority, which means games that receive an IARC certificate through Meta Platforms Technologies also receive a GRAC rating automatically.

6.1. Restricted use of Meta name and logos

6.1.1. 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:

References to Meta hardware or services, (e.g., in a “Quit to Quest Home?” dialog box or similar UI).

Models or meshes supplied to you by Meta explicitly for inclusion in your app, (e.g., controller models with the Meta logo).

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

6.2. Pre-launch listings

6.2.1. Pre-Launch Listings must comply with all policies for Store marketing materials guidelines. Pre-order listings can be created up to 90 days before launch, with an option to enable discounted sale pricing once during the pre-order period. Coming Soon listings can be created up to 180 days before launch, except as expressly authorized by Meta Platforms Technologies to you in writing.

6.2.2. Once your pre-launch listing has been created, you must not change your release date within 2 weeks of your originally communicated release date. Any changes to your release date within 2 weeks of your originally published release date may result in your listing being excluded from any featured pages in the Meta Horizon Store. All users with pre-orders will be notified by Meta if your app is changing within 2 weeks of the current date or delayed for greater than 90 days.

6.2.3. If at 2 days prior to your intended app release date, you do not have a Meta-approved full release with a scheduled date, order fulfillment for your pre-orders will be paused until a new launch date is provided.

6.2.4. If your project is canceled, all user pre-orders will be canceled and to the extent necessary, refunds processed as set out in the Meta Quest Content Refund Policy.

6.2.5. For more information, see Pre-Launch Listings and Sales.

6.3. Ending support

6.3.1. 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.

6.3.2. 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.

6.3.3. 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.

6.3.4. 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.