YouTube API Services - Developer Policies

Note:Complying with the YouTube Developer Policiesprovides guidance and examples to help you ensure that your API clients follow specific portions of the YouTube API ServicesTermsandPolicies(API TOS). The guide offers insight into how YouTube enforces certain aspects of the API TOS, but it does not replace any existing documents.

This document (the "YouTube API Services Policies"or"Policies") sets out the policies that you need to follow when accessing or usingYouTube API Servicesin your service, product, or application. These Policies help you access and useYouTube API Servicesin ways that are consistent with YouTube's interests and that respect and foster the growth of YouTube's community of creators, viewers, content rights holders, and advertisers.

In addition to defining policies, this document explains some of the underlying principles that YouTube followed in creating these Policies. It also offers examples that demonstrate how these Policies would apply in practice.

Please note that this is a legal document and that these Policies are a component of theAgreement,so you must comply with them. YouTube reserves the right to change these Policies, and your continued access to, or use of,YouTube API Servicesconstitutes your agreement to and acceptance of any such changes. Policy changes, like changes to the YouTube API ServicesTerms of Service,will be documented in theTerms of Service Revision History,and you can subscribe to theRSS feedfor that revision history to be notified of any such changes.

I. Terminology and style

This is a legal document that specifies policies about allowed or prohibited actions. As such, it uses certain terms to specifically indicate whether you can or cannot do something. With that in mind, the following terms are used to explain your requirements as related to these Policies:

The termsmustand required refer to absolute requirements.
The termmust notrefers to an absolute prohibition.
The termsshould,should not,recommend,andrecommendedindicate that the statement describes a general best practice. While these terms suggest certain actions or behaviors, they acknowledge that you might decide to follow a different course based on specific aspects of your use case.
The termmayindicates that an action is optional and left entirely to your discretion or, depending on the context in which it is used, to YouTube's discretion.

In addition, theDefinitionssection that concludes this document identifies other terms that have a very specific meaning when used in this document. For your convenience, this document uses a special style for those terms to so that you can easily identify them in context and link to their definitions.

II. Software Development Principles

These principles underlie many of the policies in this document. Even though they might not cover every policy, if you violate or yourAPI Clientsviolate any of these principles, you are likely also violating the terms of theAgreement.That said, if local law requires you to do something other than what is stated in these policies -- for example, to store data for a particular length of time -- you should comply with that law.

Build high-quality applications and maintain them.

Build stable, easy-to-use, feature-richAPI Clientsthat bring significant additional value to the YouTube ecosystem and its users. Promptly updateAPI Clientsas the features offered inYouTube API Serviceschange.
Be honest and transparent.

This principle applies to all facets ofAPI Clientsand the way that they interact with users as well as with YouTube. In keeping with this principle, be clear about who you are and what yourAPI Clientdoes. Don't engage in any deceptive activity or messaging related to your identity, your data collection, storage, sharing, use and deletion practices, actions that yourAPI Clienttakes on users' behalf, or anything else. Be honest and do not mislead or confuse users in the way you use and present data.
Give users control.

Building on the importance of transparency, this principle dictates that users must be aware of and have actively consented to the actions that anAPI Clienttakes on their behalf. It means that users know about and have final authority over any actions theAPI Clienttakes to insert, share, update, or delete their data. It also means that eachAPI Clientmust provide a privacy policy that clearly informs users about the information that theAPI Clientaccesses, collects, stores, shares, and otherwise uses.
Respect users' privacy.

Make sure that your data collection, storage, use, security, and deletion policies and practices protect users. Don't allow unauthorized access to, or use of, user data. Don't store user data indefinitely, and provide a clear, straightforward process for them to delete data in your possession. Finally, don’t, and do not make attempts to, request, collect, or store users' YouTube login credentials.
Be a good citizen.

Don't createAPI Clientsthat encourage or enable people to abuse, threaten, or harass each other. Don't use, distribute, or promote viruses, spyware, malware, or other bad stuff. Don't break the law or encourage or enable others to do so. Hopefully, this is all common sense.

III. General Developer Policies

A. API Client Terms of Use and Privacy Policies

API Clientsmust display a link to YouTube's Terms of Service (https:// youtube /t/terms), and they must also state in their own terms of use that, by using thoseAPI Clients,users are agreeing to be bound by the YouTube Terms of Service.
EachAPI Clientmust require users to agree to a privacy policy before users can access theAPI Client'sfeatures and functionality. The privacy policy must:
1. be prominently displayed and easily accessible to users at all times,
2. notify users that theAPI ClientusesYouTube API Services,
3. reference and link to the Google Privacy Policy at http:// google /policies/privacy,
4. clearly and comprehensively explain to users what user information, includingAPI Datarelating to users, theAPI Clientaccesses, collects, stores and otherwise uses,
5. clearly and comprehensively explain how theAPI Clientuses, processes, and shares the user information described in section (III.A.2.e), including how the information is shared with either internal or external parties,
6. disclose, if it does so, that theAPI Clientallows third parties to serve content, including advertisements,
7. disclose, if it does so, that theAPI Clientstores, accesses or collects (or allows third parties to do so) information directly or indirectly on or from users’ devices, including by placing, accessing or recognizing cookies or similar technology on users' devices or browsers,
8. if theAPI Clientaccesses or usesAuthorized Data,explain that, in addition to theAPI Client'snormal procedure for deleting stored data, users can revoke thatAPI Client'saccess to their data via the Google security settings page athttps://security.google /settings/security/permissions,and
9. if theAPI ClientusesAuthorized Data,explain how users can contact theAPI Clientowner or developer with questions or complaints about theClient'sprivacy practices.

B. Maintainability and Deprecation

API Clientsmust use the most recent versions ofYouTube API Services.This means that you must be able to updateAPI Clientswhen newer versions ofYouTube API Servicesare released. Non-websiteAPI Clients,like mobile apps or installed applications, must be capable of being remotely updated to use the most recent versions ofYouTube API Services.You must update yourAPI Clientsto the most recent versions of theYouTube API Serviceswithin a specified time period if required by YouTube from time to time (e.g. for critical updates).
When YouTube intends to make backward incompatible changes to theYouTube API Services,such changes will be documented in theTerms of Service Revision History,and you can subscribe to theRSS feedfor that revision history to be notified of any such changes.
You must promptly update non-deprecatedAPI Clientsto use newer versions ofYouTube API Servicesas those versions are released.
You must update deprecated versions of yourAPI Clientsto clearly indicate to users that some functions or features ofYouTube API Servicesmight stop working due to theAPI Clients'deprecated status.

C. Implementing YouTube Features

API Clientsmust also comply with theRequirements for Minimum Functionality for YouTube API Services( "RMF"). In addition,API Clientsmust not place any limitations on the YouTube functionality required by the RMF.

For example, the RMF states that anAPI Clientthat enables users to upload videos to YouTube must enable those users to set a title for each uploaded video. YouTube's video title field has a maximum length of 100 characters, and anAPI Clientmust not set a shorter maximum length for that field.
AnyAPI Clientfeature that initiates a user action related to a YouTube resource must be:
1. clearly and unequivocally identifiable as a YouTube action,
2. distinct and not mixed with yourAPI Client'sfunctionality, and
3. clearly initiated by the user.
Examples of YouTube resources include videos, channels, playlists, playlist items, and subscriptions. Examples of actions include playing a video, liking a video, adding a video to a playlist, and subscribing to a channel.
API Clientsthat perform write operations may suggest parameter or property values, but users must have final control over the data that will be published toYouTube Applications.Similarly,API Clientsmust not modify user-provided values before sending them to YouTube by truncating, appending, or otherwise altering those values unless the user has explicitly consented to such changes.

API Clientsthat suggest values for text fields, like video titles or descriptions, must incorporate relevant keywords into those values. For example anAPI Clientthat suggests video titles should not generate the same default titles for all users.

These examples illustrate how this policy would apply to anAPI Clientthat uploads videos to YouTube:
1. TheAPI Clientmay suggest a video description or pre-populate the video description. However, it must not add information to the video description after it is submitted by the user and before it is sent without the user's prior consent. For example, theAPI Clientmust not append the recording date,API Clientname, or any other text unless the user has explicitly consented to such changes.
2. AnAPI Clientmay provide an option to translate a video title to other languages. However, theAPI Clientmust not add any such translations without the user's consent. In addition, if theAPI Client'sdefault behavior is to enable the option to translate the video title, it must clearly present to the user an easy way to disable that behavior.
API Clientsmust clearly indicate how user-provided data will be used on YouTube.

This policy is particularly relevant forAPI Clientsthat interface with multiple services and platforms since there may be functional or labeling differences between those services and platforms.

For example, anAPI Clientenables users to add comments about videos to multiple platforms, including YouTube. Each platform uses a different name to refer to the comment text. So, if theAPI Clientlabels the field "Feedback" in its comment form, it needs to clearly indicate that that value corresponds to the comment text on YouTube.
API Clientsthat use search functionality provided byYouTube API Servicesmust not modify or replace the text, images, information, or other content of, the search results returned by those Services.

For example,API Clientsmust not merge or intermix results from sources other than YouTube and present them as YouTube search results.
AnAPI Clientshould not limit or reduce the functionality of a YouTube feature unless that limitation is a core aspect (as described in the examples below) of theAPI Clientitself and that YouTube feature is not required by the RMF ( "Permitted Feature Limitation").
1. Example 1: Permitted Feature Limitation
  
  The YouTube Data API service allows a video uploader to provide translations of a video's title. Generally speaking, anAPI Clientthat implements this feature should allow uploaders to translate video titles to any language that YouTube supports. However, anAPI Clientthat is specifically designed to teach users to speak French and that offers a range of features specific to French translations might be justified in only offering users the option to upload French translations of video titles.
2. Example 2: Non-permitted Feature Limitation
  
  A secondAPI Clientsupports video uploading to YouTube and two other platforms, and all of those platforms allow the uploader to provide translations of the video's title. However, while YouTube supports more than 70 languages, the other two platforms each support half that number, and the three platforms support 25 languages in common. If theAPI Clientsupports only those 25 languages for translation, then that is a non-permitted feature limitation because the limited set of language options is not a core aspect of theAPI Client.Instead, theAPI Clientmust offer the full range of languages that YouTube supports.
API Clientswith Permitted Feature Limitations must explain to users why each limitation is in place and make clear that the limitation is not imposed by YouTube. In many, if not all, cases, there are different ways that anAPI Clientcould provide that information, and you should choose an appropriate method for yourAPI Client.Within this explanation, anAPI Clientshould provide a mechanism for users to access the full feature (such as linking to YouTube Creator Studio or providing an expandable menu within the API Client).

In the example 1 above, theAPI Clientcould explain that video uploaders can add translations for other languages in the YouTube Creator Studio and provide a link to that functionality.
API Clientsthat offer features sourced from multiple services and platforms should offer feature parity to the extent that it exists across those sources, providing user choice. WhenAPI Clientsinclude features that are supported on YouTube and on other platforms,API Clientsmust not consistently present YouTube features in a detrimental way (e.g., by only providing those features from other platforms).

For example, suppose anAPI Clientallows users to upload videos to YouTube and three other platforms, and all of those platforms support the ability to upload captions. If theAPI Clientalso supports caption uploading, then it must support that feature for YouTube.

D. Accessing YouTube API Services

API Credentials

To access or use someYouTube API Services,you must first use theGoogle Developers Console(https://console.cloud.google /) to createAPI Credentialsfor yourAPI Project.Those credentials enable Google and YouTube to link API activity to a particularAPI ProjectandAPI Client.

In addition to creatingAPI Credentials,the Developers Console might require you to provide certain other information, such as identification or contact details, before you can access or use theYouTube API Servicesassociated with those credentials. YouTube reserves the right to require you to provide additional information to continue to access or useYouTube API Services.

If you need to createAPI Credentialsto access or use a specific YouTube API service, the documentation for that service explains how to create those credentials. For example, theYouTube Data API service,YouTube Reporting API service,YouTube Analytics API service,andAndroid Player API serviceall document steps for creatingAPI Credentials.Those steps generally differ slightly from one API service to another. For example:
- Some services only support authorized API requests, while others support authorized and non-authorized requests.
- Services often support multiple access scopes. Each scope specifies the resources that anAPI Clientcan retrieve, insert, update, or delete on the user's behalf. Scopes enableAPI Clientsto only request access to the resources they need, and scopes also enable users to control the amount of access that they grant to those Clients.
The following policies also apply to access and use ofYouTube API Services:
1. You must not mask or misrepresent your identity or yourAPI Client'sidentity when accessing or usingYouTube API Servicesor when creating anAPI ProjectorAPI Credentials.
2. You must only useAPI Credentialsassigned to you and to yourAPI Projectto accessYouTube API Services.Similarly, you must not use any other means to mask or misrepresent yourAPI Client'saccess to, or usage of,YouTube API Services.
3. If yourAPI Clientneeds to createAPI Credentialsto access or useYouTube API Services,you must create exactly one (1)API Projectfor thatAPI Client.ThoseAPI Credentialsare intended to be used exclusively by the associated API Client, which means that you must not use that one (1)API Projectfor multipleAPI Clients.
4. You may share yourAPI Credentialswith agents operating solely on your behalf and under a written duty of confidentiality. However, you must not share or disclose yourAPI Credentialsto any other third party, allow access to or use of yourAPI Credentialsby any other third party, or embed yourAPI Credentialsin open source projects.
User Authentication and Authorization

Authentication and authorization refer to the process by which users identify themselves and consent to allow anAPI Clientto access certain user-specific data. SomeYouTube API Servicesdo not support access to user-specific data and therefore, do not require any authorization, others require authorization for some requests or data, and still others require authorization for all requests. For example:
- The YouTube IFrame Player API service, which lets you embed videos in a website, does not require authorization just as users do not need to log in to the YouTube website to watch a video.
- The YouTube Data API service requires authorization for some actions. For example, anAPI Clientcan search for public videos but does not need user authorization to do so. However, anAPI Clientdoes need user authorization to upload a video to the user's YouTube channel.
- The YouTube Analytics API service and YouTube Reporting API service require authorization for all actions.
1. Authentication
  1. API Clientsmust not (and must not attempt to) obtain, proxy, request, collect, modify, cache, store, or use any information that the user provides or that YouTube displays to the user during authentication processes, including YouTube user account login credentials like usernames and passwords.
  2. API Clientsmust obtain user consent in accordance with the applicable laws and only request access to authorization scopes that they currently use. The access that anAPI Clientrequests should have a direct and transparent benefit to users of that Client. Do not try to future-proof your access to data by asking for permissions that would enable features that you have not yet built.
    
    For example, the YouTube Data API service supports one authorization scope that grants access to read data and another that grants access to read and write data. If a user granted anAPI Clientaccess to the first scope, thatAPI Clientwould be able to retrieve information about the current user's YouTube channel. However, if a user granted theAPI Clientaccess to the second scope, theAPI Clientcould also upload a video to that channel.
    
    In this scenario, anAPI Clientthat does not support YouTube uploads (or other write-based actions) only needs to request access to the first authorization scope, which is more limited in the privileges it grants. Even if theAPI Client'sdeveloper plans to eventually introduce support for write-based actions, the developer cannot future-proof theAPI Clientby requesting access to the authorization scope for writing data before theClientactually supports features that require that scope.
  3. API Clientsshould request access to authorization scopes in context whenever possible. By requesting access to user data in context, via incremental authorization, anAPI Clientenables users to more easily understand why it needs access to that data.
2. API Client Identification and Representation
  1. API Clientsmust clearly and accurately identify to the user the entity or product that is requesting access to user data and the reason for requesting that access;
  2. API Clientsmust not mislead users when requesting access to data so that users can make an informed decision about whether to grant access to those Clients. Users should be able to readily understand both the value of providing the data that anAPI Clientrequests access to and the consequences of sharing that data.
  3. API Clientsmust clearly and comprehensively identify to users the purposes for which they access and use user data.API Clientsmust not use user data for secondary purposes that are not clearly disclosed to users.
    
    Users should not be surprised to learn that anAPI Clientcontains hidden features, services, or actions that are inconsistent with theClient'smarketed purposes.
3. Revocation
  1. EveryAPI Clientmust provide a clearly explained and easy way for users to revoke any authorization consent they have provided to anAPI Clientto accessYouTube API Services.
    When a user revokes consent through this mechanism, theAPI Clientmust programmatically revoke that token right away to communicate the change in permissions to Google. For example, anAPI Clientcould use a Google API Client Library to revoke the token.
    In addition, following revocation of consent through this mechanism, you and yourAPI Clientsmust delete allAuthorized Datathat was accessed or stored pursuant to that consent. That deletion should happen as soon as possible and must take place within 7 calendar days of the revocation.
  2. As noted in section (III.A.2.i), everyAPI Clientmust include in its Privacy Policy a link to Google's security settings page (https://security.google /settings/security/permissions). When a user revokes consent through that page, you and yourAPI Clientsmust also delete allAPI Datarelated to that user that was accessed or stored pursuant to such consent. To comply with this policy, yourAPI Clientswill need to periodically reconfirm that its authorization tokens are still valid and deleteAPI Dataassociated with users whose authorization tokens cannot be refreshed.
    Based on the requirements defined in section (III.E.4) regarding stored data, all such deletions should happen as soon as possible and must take place within 30 calendar days of that revocation.
Usage and Quotas

YouTube may use quotas and place use restrictions to ensure thatYouTube API Servicesare accessed and used as intended and that you and yourAPI Clientsdo not reduce service quality or limit access for others.

If yourAPI Clientreaches the quota limit for a service, you can apply for a quota extension by completing anAPI Compliance Auditwhere you must specify the use case for which you need the extension. If you have been audited in the past 12 months and have been marked compliant by YouTube API Services team, you can apply for anadditional quota extension.

If YouTube approves the application, you must use the additional quota granted only for the approved use case. If yourAPI Client'suse case changes, to use any allocated quota for the new use case, you must notify YouTube of the change by resubmitting anAPI Compliance Auditand receive approval for the application.

If YouTube rejects the application, you canfile an appeal.
Inactivity

YouTube reserves the right to disable or curtail your access to, or use of, specificYouTube API Servicesif yourAPI Projecthas been inactive for 90 consecutive days. For example, YouTube could revoke yourAPI Credentials,or reduce (or eliminate) yourAPI Project'squotas for specificYouTube API Services.If yourAPI Client'squota is reduced or eliminated, you may reapply for quota or a quota extension, and YouTube will review that application based on YouTube’s determination of your expected use of theYouTube API Services.
Contact Information

YouTube’s primary means of contacting you about yourAPI ProjectorAPI Clientis the email address that is associated with the Google Account that you use to log in to the Google Developers Console. You must comply to any communication that YouTube sends you regarding compliance issues relating to yourAPI Clients.

If users of yourAPI Clienthave questions about your privacy practices, and you do not have a contact address in yourAPI Client'sprivacy policy as discussed in section (A.2.i), YouTube may share your primary email address with those users.
Prohibited Access

You are prohibited from accessing or attempting to accessYouTube API Servicesvia any means if yourAPI Credentialsare suspended, revoked, or terminated, or if the Google Account you used to create those credentials is suspended or terminated, for any reason. In that case, you must not access or attempt to accessYouTube API Servicesvia any means, including by creating or using a proxy to create new Google Accounts,API CredentialsorAPI Projects.
Undocumented Services

You must not use undocumented APIs without express permission. You must access data from YouTube API services only according to the means stipulated in the authorized documentation of that YouTube API service.

You must not reverse engineer undocumented YouTube API services or otherwise attempt to derive the underlying source code of these API services.

E. Handling YouTube Data and Content

Aside from the permissions and rights granted in this section, you and yourAPI Clientshave no further permissions or rights toAPI Data,including to temporarily storedAPI Data.

Audiovisual Content

You and yourAPI Clientsmust not, and must not encourage, enable, or require others to:
1. download, import, backup, cache, or store copies of YouTube audiovisual content without YouTube's prior written approval,
2. make content available for offline playback, or
3. use any aspect of theYouTube API Servicesto facilitate or promote copyright infringement or the exploitation of copyright-infringing materials.
Data Aggregation
1. Do not aggregateAPI Dataexcept that you may only aggregateAPI Datarelating to YouTube channels that are under the same content owner as recognized by YouTube pursuant to content licensing agreement(s) between YouTube and such content owner. Such aggregatedAPI Datamust only be viewable by that content owner.
2. Do not aggregateAPI Dataor otherwise useAPI DataorYouTube API Servicesto gain insights into YouTube's usage, revenue, or any other aspects of YouTube's business.
  
  For example, suppose that two different content owners recognized by YouTube have each authorized anAPI Clientto retrieveAPI Dataon their behalf for their respective viewing. ThatAPI Clientmay separately aggregateAPI Dataretrieved for each content owner's channels provided that such aggregation per content owner does not provide insights into YouTube’s usage, revenue or any other aspects of YouTube’s business. TheAPI Clientmust not combineAPI Datafrom the different content owners.
Authorized Data Usage

These policies relate to your use ofAuthorized Data.They are relevant for anyAPI Clientthat writes data via an API request or retrieves data that can only be accessed via a properly authorized API request. For example, these policies apply to anyAPI Clientthat enables a user to upload videos, retrieve the user's list of uploaded videos, create playlists, or comment on videos.
1. API Clientsmust be honest and transparent about the types of user data and the purposes for which they collect, store, delete, share, safeguard, and otherwise use that data.
2. API Clientsmust not display or allow access toAuthorized Datato anyone other than the authorizing user or agents expressly approved by that user.
3. API Clientsmust only access, collect and useAuthorized Datain accordance with the scope of its privacy policy and user consent obtained in accordance with Section 2.
  
  This means that anAPI Clientmust prompt users to re-accept its privacy policy if theClientstarts to access, collect, or useAPI Datain a way or for purposes that were not covered in the privacy policy that the user originally accepted.
4. API Clientsmust clearly identify any actions that they take to insert, share, update, or delete data or content on the authorizing user's behalf. In addition, the user must expressly consent to those actions prior to their actual execution.
5. API Clientsmust clearly identify the YouTube channel or content owner that is associated with any request that requires user authorization.
6. API Clientsmust clearly identify any content visibility settings that will be set or modified by any authorized user action. In addition,API Clientsmust not modify existing content visibility settings unless the authorizing user has expressly instructed theAPI Clientsto do so.
  
  For example, in the YouTube Data API service, a video's privacy status can be set topublic,private,orunlisted.If anAPI Clientsupports video uploads, theClientmust clearly display an option for the user to choose one of those values. Similarly, if anAPI Clientsupports edits to a video's metadata, theAPI Clientcannot change a video's privacy status without the user's express consent.
Refreshing, Storing, and Displaying API Data

Developers often need to balance the benefits of storing or caching data, such as improved performance or resource usage, with the desire to always retrieve the freshest data, which provides the best user experience possible. With that in mind, the following policies explain your requirements as well as your options in terms of storing, updating, and displaying YouTubeAPI Data.
1. API Clientsmay store authorization tokens for as long as is necessary provided that those tokens are used only for purposes consistent with the specific consent granted by an active user according to the applicable law.
2. API Clientsmay store the following types ofAuthorized Datafor as long as is necessary provided that the data is used for purposes consistent with the specific consent granted by an active user according to the applicable laws:
  1. data retrieved through the YouTube Analytics API service,
  2. data provided through the YouTube Reporting API service, or
  3. statistics provided through other YouTube API services, such as the number of views for a video, the number of channels for a subscriber, or the number of videos in a playlist. (All of those statistics can be retrieved via the YouTube Data API service.)
  Note that even though anAPI Clientmay store this data for more than 30 days, theClientmust still ensure every 30 days that it is still authorized by the user to access that data.
  
  For example, anAPI Clientmay store view counts for a video for more than 30 days, but it must still verify every 30 days that its authorization to access the video uploader's data has not been revoked. TheAPI Clientmust also verify, every 30 days, that the video has not been deleted.
  
  To be clear, anAPI Clientmust not store statistics retrieved asNon-Authorized Datafor more than 30 days. For example, anAPI Clientmust not store the subscriber count for a YouTube channel for more than 30 days without authorization from the channel owner.
3. API Clientsmay store all other types ofAuthorized Datanot identified in section (III.E.4.b) for as long as is necessary for the purposes of the specific consent granted by an active user and for no longer than 30 calendar days. After 30 calendar days, theAPI Clientmust either delete or refresh the stored data.
4. API Clientsmay temporarily store limited amounts ofNon-Authorized Datafor as long as is necessary for the purposes of theAPI Clientbut not longer than 30 calendar days. As in section (III.E.4.c) immediately above, this means that after 30 calendar days, theAPI Clientmust either delete or refresh the stored data.
5. In all cases,API Clientsmust use reasonable efforts to ensure that their storedAPI Datais consistent with the current data available throughYouTube API Services.For example,API Clientsshould reflect metadata changes and viewcount updates as quickly as possible.
6. API Clientsmust display the most updatedAPI Dataavailable in their user-facing presentations, including in user interfaces, althoughAPI Clientsmay display historicalAPI Dataprovided that it is presented accurately in context of time.
7. YourAPI Clientsthat access or use user data must provide a way for a user to request that you delete stored data related to that user. For example, yourAPI Clientcould display a button to delete stored data. If the user indicates that you should delete that data, you must then delete it as soon as possible and within 7 calendar days.
  
  The method for deleting stored data must make clear that deleting the data stored by theAPI Clientdoes not, in any way, affect data stored by YouTube and that to delete data on YouTube, the user needs to use a YouTube Application or an authorizedAPI Clientthat supports the ability to delete that data.
  
  Similarly,API Clientsmust respect any other means by which a user expresses an intent to prevent those Clients from accessing user data related to that user. For example, if a user deletes his account from your API Client, you must also delete any user data you have stored related to that user as soon as possible and within 7 calendar days.
8. YourAPI Clientsmust not (i) replaceAPI Datawith similar, independently calculated data, or (ii) access or useAPI Datato create new or derived data or metrics. To the extent yourAPI Clientsdisplay any information, data or metrics not based onAPI DataalongsideAPI Data,yourAPI Clientsmust include a clear and prominent disclosure there that such information, data and metrics are not from YouTube and are part of your own product.
  
  For example, when displaying the number of likes for a video, yourAPI Clientmust use the number returned in theAPI Data.You must not substitute a different number to represent likes, such as the number of users of yourAPI Clientthat liked the video. Similarly, you are not permitted to use the number of likes returned in theAPI Datato calculate other metrics, such as the percentage of total likes that were made through yourAPI Clientor a score that factors in likes, total views, or any otherAPI Data.However, you are permitted, for example, to display the number of likes that were made through yourAPI Clientas long as that number is displayed alongside the total likes returned in theAPI Dataand as long as yourAPI Clientclearly communicates that theAPI Clientcalculates the additional metric independently of YouTubeAPI Data.
9. When yourAPI Clientloads, it collects and shares some basic user data with YouTube via the YouTube embedded player to render the video thumbnail and title, determine playability and content restrictions, and for fraud and abuse reasons. Additional data is collected and shared by your API Clientupon video playback to customize the player on yourAPI Client and third party sites and apps. Remember that if you enable Autoplay, playback will occur without any user interaction with the player; playback data collection and sharing will therefore occur upon page load. You can limit the data shared with YouTube before a user interacts with the YouTube embedded player by setting Autoplay tofalse.As noted in theYouTube API Services Terms of Service,you and your API Clientsmust comply with all applicable laws, rules, and regulations, including privacy laws and regulations.
10. API Clientsmust look up the Made For Kids status of each YouTube video that it embeds on its site or app by following the instructions inthis guide.For each video that is designated Made For Kids, API Clientsmust turn off tracking and make sure that all data collection with respect to that player is compliant with applicable law(s) including the U.S. Children's Online Privacy (COPPA) and E.U. General Data Protection Regulation (GDPR)). See the YouTube Help Centerfor more information on determining content as Made for Kids.
Security

You and yourAPI Clientmust:
1. maintain appropriate administrative, organisational, technical, and physical controls to ensure the privacy, security, and confidentiality of user data andAPI Data;
2. use only industry-standard transport encryption;
3. protectAPI Dataand any other data used in yourAPI Clientfrom unauthorized access, use, or disclosure.
Scraping

You and yourAPI Clientsmust not, and must not encourage, enable, or require others to, directly or indirectly, scrapeYouTube ApplicationsorGoogle Applications,or obtain scraped YouTube data or content. Public search engines may scrape data only in accordance with YouTube's robots.txt file or with YouTube's prior written permission.

F. User Experience

YouTube Look and Feel

Innovative user experiences and user interface designs are among the most valuable contributions thatAPI Clientscan provide to the YouTube community. That said, YouTube's designers and engineers put a lot of thought into designingYouTube Applicationsto ensure that those Applications provide a great user experience.

Taking both of those points into account, yourAPI Clientsmust not change or interfere with user interfaces inYouTube Applicationsunless you have obtained YouTube's prior written approval. You can request that approval atthis form.
Branding
1. AnyAPI Clientpage or feature that displays YouTube content – including, without limitation, search results, YouTube videos, channels, playlists, thumbnails, and YouTube players – must make clear to the viewer that YouTube is the source of the relevant content by displayingYouTube Brand Featuresin accordance with the requirements below and the YouTube Branding Guidelines (https://developers.google /youtube/terms/branding-guidelines).
  
  In some cases, anAPI Clientmight need to displayYouTube Brand Featuresnext to multiple individual content elements to make the attribution clear to the viewer. For example, anAPI Clientthat displays search results from YouTube and from other sources on the same page needs to clearly identify YouTube as the source of only the search results from YouTube, including text, images, and other information pertaining to YouTube search results. TheAPI Clientcannot provide one general set of attribution for all search results from various sources.
2. Content that does not originate from YouTube must not be shown in a way that suggests that the content is originating from YouTube or in a way that can cause confusion as to the origin of that content.
3. You and yourAPI Clientsmust not, and must not encourage, enable or require others to, directly or indirectly, interfere with or obscure any attribution provided by YouTube, including attribution provided via or shown in embedded YouTube players. YourAPI Clientsmust display applicableYouTube Brand Featuresand any other YouTube-provided attribution on all types of devices.
Playback Integrity

Playback integrity refers to the ability to determine and measure how content and ads are served, how video playback is initiated and implemented, and how users interact with YouTube features in yourAPI Client.Playback integrity is critical to the YouTube platform, as it helps protect creators' interests, including their ability to monetize their content and develop their audience.

YouTube believes that playback integrity is contingent on a user choosing to watch a video, andAPI Clientsare prohibited from providing incentives for watching videos as follows:
1. API Clientsmust not charge users to watch content in an embedded YouTube player.
2. API Clientsmust not otherwise gate access to a video by requiring a user to take an action other than clicking the play button to view or continue playing YouTube audiovisual content. For example,API Clientsmust not require a user to subscribe to a channel or like a video to continue watching YouTube audiovisual content.
  
  For clarity, if yourAPI Client'snormal functionality requires a certain action that is not specific toYouTube API Services,such as login or age verification, that functionality is allowed.
3. API Clientsmust not offer or provide incentives, rewards, or other compensation to users for engaging withYouTube Applications(directly or indirectly) by performing actions like viewing content, liking content, sharing content, subscribing to channels, adding comments. For example,API Clientsmust not offer features or services that trade video views for a fee or that trade video views in return for other YouTube-related or non-YouTube-related actions.

G. Distribution and Commercial Use

You may distribute or sellAPI Clientssubject to the restrictions defined in the "Prohibited Actions" subsection below and, of course, to the other terms of theAgreement.

In addition, you may distribute and display YouTube audiovisual content and accompanying metadata to users through yourAPI Clientsas long as those Clients comply with theAgreementand, specifically, do not engage in any of the prohibited actions listed immediately below.

Prohibited Actions

For specific policies in the following list that require YouTube's prior written approval, you can request that approval atthis form.

You and yourAPI Clientsmust not, and must not encourage, enable, or require others to:
1. sell, purchase, lease, lend, convey, redistribute, or sublicense all or any portion ofYouTube API Services,including YouTube audiovisual content;
2. sellYouTube API Servicesor access to any components ofYouTube API Servicesunless you obtain YouTube's prior written approval;
3. sell advertising, sponsorships, or promotions that are placed on or within YouTube audiovisual content or the YouTube player without YouTube's prior written approval; or
4. sell advertising, sponsorships, or promotions on any page or screen that containsYouTube API Dataunless other data, content, or material not obtained from YouTube appears on the same page and offers enough independent value to justify such sales if theYouTube API Datawere removed.
Permitted Actions

All of the following commercial use cases are permitted subject to your and YourAPI Clients’ compliance with all other terms of theAgreement,including the prohibited actions detailed in the previous section:
1. Selling an API Client;
2. Promoting your own business or artistic enterprise by uploading original audiovisual content to YouTube or maintaining channel(s) on YouTube;
3. Developing ad-enabledAPI Clients,such as an ad-enabled blog or website, that useYouTube API Servicessubject to compliance with all other terms of the Agreement, including the restrictions in section III.G.1.d;
4. Placing your own branding in anAPI Clientas long as that branding complies with theYouTube Branding Guidelinesand does not interfere with YouTube audiovisual content playback or anyYouTube Brand Features;
5. Selling or distributing devices that contain or run an API Client;

H. Monitoring and Audits

YouTube reserves the right to survey, monitor, and/or audit your access to or use ofYouTube API Servicesto ensure quality, to improve YouTube products and services, and to verify your compliance with theAgreement.To that end, YouTube may survey users of yourAPI Clients.

You and those acting on your behalf must:

not interfere with such surveys, monitoring efforts, or audits;
not obscure or conceal from YouTube your access to or use ofYouTube API Services;and
upon request, and within the timeframe stated in that request, provide YouTube with account(s) necessary to access all features or functions of the current, in-production version(s) of yourAPI Clients,so that YouTube may review thoseAPI Clientsfor compliance with theAgreement.

YouTube may use any technical means to overcome non-compliance with these provisions.

I. Additional Prohibitions

The policies in this section identify additional things thatAPI Clientsmust not do. Actions contrary to these policies would be harmful to YouTube, to the YouTube community as a whole, or to individuals or groups of individuals within that community. These policies focus on the need for you and yourAPI Clientsto treat members of the YouTube community honestly and respectfully as well as on your need to respect the integrity of YouTube's services, content, and interests.

You and yourAPI Clientsmust not, and must not encourage, enable, or require others to:

useYouTube API Servicesto create, offer, or act as a substitute for, or substantially similar service to, anyYouTube Applications.API Clientsmust not mimic or replicate YouTube's core user experiences by recreating features or process flows unless they add significant independent value or functionality that improves users' interactions with YouTube. For example, anAPI Clientmust not recreate the browse experience from any YouTube Application without adding significant independent value to that flow.
misuseYouTube API Servicesor engage in abusive behaviors related to those Services. For example, you must not automate or trigger views, uploads, comments, likes, dislikes, or other actions without the user's prior specific and express consent;
interfere, or attempt to interfere, in any way with the proper workings of any aspect ofYouTube API Services,YouTube Applications,orGoogle Applications,including interference or disruption of the servers or networks that provide those Services or Applications;
modify, interfere with, replace, or otherwise disable any functionality, data, or content made available as part of, or in connection with,YouTube API Services.For example, you must not remove, obscure, alter, or disable any links that appear in YouTube players or inAPI Data.
modify, interfere with, replace, or block advertisements placed or served by YouTube or byYouTube API Servicesincluding inAPI Data,YouTube audiovisual content, or YouTube players;
modify, build upon, or block any portion or functionality of a YouTube player;
separate, isolate, or modify the audio or video components of any YouTube audiovisual content made available as part of, or in connection with,YouTube API Services.For example, you must not apply alternate audio tracks to videos;
promote separately the audio or video components of any YouTube audiovisual content made available as part of, or in connection with, theYouTube API Services;
create, include, or promote features that play content, including audio or video components, from a background player, meaning a player that is not displayed in the page, tab, or screen that the user is viewing;
adversely affect the functionality or performance of any aspect ofYouTube API Services,YouTube Applications,orGoogle Applications,including actions that interfere with or disruptYouTube API Servicesor the servers or networks that provide those Services;
confuse, deceive, defraud, mislead, misrepresent, defame, abuse, stalk, threaten, spam, surprise, or harass anyone;
introduce, or attempt to introduce, any viruses, worms, defects, Trojan horses, malware, spyware, adware, or other items of a destructive nature toYouTube API Services,YouTube Applications,Google Applications,or YouTube users and the devices they use to access those services and properties;
circumvent, interfere with, or render ineffective, any geographical restrictions, including IP address-based restrictions imposed by YouTube orYouTube API Services;
use any technology other thanYouTube API Servicesto access or retrieveAPI Data,including to access any portion of any YouTube audiovisual content;
offer an API service that allows users to access any data or functionality directly or indirectly provided by theYouTube API Services;
modify, translate, create derivative works of, reverse engineer or otherwise attempt to extract the underlying source code from anyYouTube API Servicesor from any software related to those Services;
useYouTube API Servicesfor any purpose or activity where the use or failure of those Services could lead to death, personal injury, or environmental damage, such as in the operation of nuclear facilities, air traffic control systems, or life support systems;
infringe copyrights or exploit copyright-infringing materials;
engage in, promote or facilitate unlawful online gambling;
create, display, promote or facilitate disruptive commercial messages or advertisements; or
situate the YouTube player in a nested or hierarchical iframe lineage to circumvent YouTube policies or otherwise obfuscate the source of use.

J. Child-Directed API Clients

If your API Client (or any part thereof) targets or directs itself to children (as defined under applicable law(s) including the U.S. Children's Online Privacy (COPPA) and E.U. General Data Protection Regulation (GDPR)) (referred to herein as a "Child-Directed API Client"), you and your Child-Directed API Client must:
1. ensure that your Child-Directed API Client, including its access to and use of any YouTube API Services, is compliant with COPPA, GDPR, and any other applicable laws or regulations at all times;
2. notify Google of the child directed nature of your Child-Directed API Client using the tools provided inhere. Each Child-Directed API Client notified to Google using such tools or otherwise is referred to herein as a "Known Child-Directed API Client";and
3. not use personalized ads (including remarketing) to target past or current activity by any user of your Child-Directed API Client.
1. For You and Your Child-Directed API Client.You and your Child-Directed API Client will not, and must not attempt to, take any YouTube API Services write-based actions to YouTube websites, applications, services or products via your Child-Directed API Client.
2. Notwithstanding Section III.D.1.c (API Credentials) above which requires exactly one (1) API Projectfor each API Client,you can upload your own videos to your own official YouTube channel(s) via the YouTube Data API Service (not via your Child-Directed API Client or anyone else’s API Client) by creating a new API Project ( "Upload Project").
  1. To upload your own videos to your own official YouTube channel(s) via YouTube Data API Service, you must (A) create one (1) new API Projectusing the Google Developers Console (https://console.developers.google /) (an "Upload Project") prior to uploading, (B) appendmfk110as a prefix in the ID of your Upload Project, and (C) only upload from your non-Child-Directed API Client (not from your Child-Directed API Client or anyone else’s API Client); and
  2. Only you can use the Upload Project, and the Upload Project must only be used to upload your own videos to your own official YouTube channel(s) via the YouTube Data API Service from your non-Child-Directed API Client (not from your Child-Directed API Client or anyone else’s API Client). If you are uploading a Made for Kids video via the YouTube Data API Service from your non-Child-Directed API Client (not from your Child-Directed API Client or anyone else’s API Client), you must designate the YouTube Data API Service Made for Kids parameter as "true". See here for more information on determining if content is Made for Kids.
3. For You and Users of Your Child-Directed API Client.You and your Child-Directed API Client must not enable, encourage or require, users of your Child-Directed API Client to take YouTube API Services write-based actions (such as, but not limited to, uploading content, commenting and creating/sharing playlists). YouTube API Services write-based actions taken by users of Known Child-Directed API Clients will not be implemented on YouTube websites, applications, services and products. This means that, notwithstanding Section 9.1 (Required Notice) of the YouTube API Services Terms of Servicepursuant to which users of your API Client may upload content to their YouTube channels or your YouTube channel(s), uploads from users of Known Child-Directed API Clients will not be implemented on YouTube websites, applications, services and products.
You and your API Client’s access to, or use of, YouTube API Services can be suspended or terminated by YouTube for non-compliance with the YouTube API Services Terms of Service and Policies including non-compliance with this Section III.J.

K. Reporting Noncompliance

If you are aware of anyone accessing or usingYouTube API Servicesin a manner that is not compliant with these policies or any other part of theAgreement,you may contact the YouTube API Services team to escalate the issueusing this form.

IV. Definitions

"Agreement"means the legal documents defined and referenced in Section 2 (The Agreement) of the YouTube API ServicesTerms of Servicecurrently located athttps://developers.google /youtube/terms/api-services-terms-of-service.

"API Client"means a website or software application (including a mobile application) developed by you that accesses or uses theYouTube API Services.

"API Credentials"means the credentials assigned by YouTube or Google via the Google Developer Console that eachAPI Projectauthenticates with to access and use theYouTube API Services.

"API Data"is defined within the definition of"YouTube API Services"later in this Definitions section.

"API Project"means the project created in the Google Developer Console that is required for API Client(s) to access and use theYouTube API Services.

"Authorized Data"meansAPI Datathat an active user expressly authorizes anAPI Clientto access or otherwise use viaUser Credentials.

"Google Applications"means Google websites, applications, services, products, pages, and other properties.

"Non-Authorized Data"meansAPI Dataaccessible by anAPI ClientwithoutUser Credentials.

"Terms of Service"means the YouTube API Services Terms of Service currently located athttps://developers.google /youtube/terms/api-services-terms-of-service.

"User Credentials"means the credentials issued to users that users can authenticate with to permit API Client(s) to perform operations on their behalf that require authorization.

"YouTube API Services"means (i) the YouTube API services (e.g., YouTube Data API service and YouTube Reporting API service) made available by YouTube including those YouTube API services made available on the YouTube Developer Site (as defined below), (ii) documentation, information, materials, sample code and software (including any human-readable programming instructions) relating to YouTube API services that are made available onhttps://developers.google /youtubeor by YouTube, (iii) data, content (including audiovisual content) and information provided toAPI Clients(as defined above) through the YouTube API services (the "API Data"), and (iv) the credentials assigned to you and your API Client(s) by YouTube or Google.

"YouTube Applications"means YouTube websites, applications, services, products, pages, and other properties, includinghttps:// youtube,m.youtube,mobile applications like the YouTube Gaming application, and so forth, but excludingYouTube API Services.

"YouTube Brand Features"means the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of YouTube.