To ensure a smooth and safe experience for players on YouTube, all
Playables must undergo a review process before being publicly launched.
YouTube takes a holistic approach to this review, evaluating developer
compliance with API and other technical restrictions, Trust and Safety,
Privacy, and other policies, alongside a creator's overall history on
YouTube and past Playables performance. YouTube reserves the right to
reject any game that does not adhere to Google's policies, including but
not limited to, the following requirements:
[Accessibility](https://developers.google.com/youtube/gaming/playables/certification/requirements_accessibility) [Design](https://developers.google.com/youtube/gaming/playables/certification/requirements_design) [Internationalization (i18n) and localization (L10n)](https://developers.google.com/youtube/gaming/playables/certification/requirements_i18n_l10n) [Integration](https://developers.google.com/youtube/gaming/playables/certification/requirements_integration) [Monetization](https://developers.google.com/youtube/gaming/playables/certification/requirements_monetization) [Privacy \& Data](https://developers.google.com/youtube/gaming/playables/certification/requirements_privacydata) [Stability and performance](https://developers.google.com/youtube/gaming/playables/certification/requirements_stability) [Trust and safety](https://developers.google.com/youtube/gaming/playables/certification/requirements_trustsafety)

> [!IMPORTANT]
> **Important:** Translated requirements are provided for reference only. Refer to the [English versions of requirements](https://developers.google.com/youtube/gaming/playables/certification/requirements?hl=en) for definitive guidance.

## Contact

Review the contact information on the
[support contact
page](https://developers.google.com/youtube/gaming/playables/support/contact).

## Test

Use the [test
suite](https://developers.google.com/youtube/gaming/playables/reference/test_suite_guide) to validate your integration with the Playables SDK.

## Release

Speak to your Partner Manager for details on this process.

## Definitions

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "MAY" and "EXPECT"
used throughout these documents are to be interpreted as described in [RFC
2119](http://www.ietf.org/rfc/rfc2119.txt). An abridged list is included here for reference:

- **MUST**: This word, or the terms "REQUIRED" or "SHALL", means that the definition is an absolute requirement of the specification. If a Playable cannot meet any of such requirements, it will not be allowed to publish on YouTube.
- **MUST NOT**: This phrase, or the phrase "SHALL NOT", means that the definition is an absolute prohibition of the specification.
- **SHOULD**: This word, or the adjective "RECOMMENDED", means that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Completing those requirements would help Playables get better visibility.
- **SHOULD NOT**: This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
- **MAY**: This word, or the adjective "OPTIONAL", means that an item may or may not be implemented at the discretion of the implementer.
- **EXPECT**: This word is used exclusively to indicate requirements that YouTube EXPECTS to make required (aka MUST) in the subsequent version of these requirements, but which is optional for this document (MAY).