How To Look At Your Terms Of Service History

This page provides a revision history for the following documents:

YouTube API Services Terms of Service (Americas)
YouTube API Services Terms of Service (APAC)
YouTube API Services Terms of Service (EMEA)
YouTube API Services Terms of Service (Russia)
Branding Guidelines
Developer Policies
Required Minimum Functionality

Subscribe to this changelog.

Note that, in all cases, the legal documents themselves are the authoritative source of information.

July i, 2021

All developers using YouTube's API Services must complete an API Compliance Audit in order to exist granted more the default quota allotment of ten,000 units. To date, both the compliance audit process and requests for additional quota unit allocations accept been conducted by developers filling out and submitting the YouTube API Services - Audit and Quota Extension Form.

To clarify these processes and improve run into the needs of developers using our API Services, nosotros are adding iii new forms and a guide to completing those forms:

Audited Developer Requests Form: Developers who have already passed an API Compliance Inspect tin make full out and submit this shorter class to asking an allocated quota extension.
Appeals Form: Developers whose API projects accept failed a compliance audit (or been denied a quota unit increase) can make full out and submit this form.
Change of Control Course: Developers, or any party operating an API client on a developer'southward behalf, who experience a alter of control (for example, through a stock purchase or sale, merger or other form of corporate transaction) associated with an API project must fill out and submit this form. This enables YouTube's API team to update our records, inspect the new API project'southward use case compliance, and validate the developer's current quota resource allotment.

Each new course volition inform u.s. of your intended usage of YouTube's API and enable the states to amend assist you.

More than details are available in our new API Compliance Audits guide.

October 15, 2020

2 new sections have been added to the Developer Policies:

The new Department III.Eastward.4.i provides additional information about the data nerveless and sent via the YouTube embedded player. You are responsible for any user data you send to usa via any YouTube embedded player before the user has interacted with the player to indicate playback intent. You can limit the data shared with YouTube before a user interacts with the player by setting Autoplay to faux.
The new Section III.E.4.j relates to checking the Fabricated for Kids (MFK) status of content earlier embedding it on your sites and apps. You are responsible for knowing when videos that y'all embed on your API Client are made for kids and treating data collected from the embedded player appropriately. As such, yous must check the status of content using YouTube Information API Service before embedding it on your API Client via any YouTube embedded players.

The new Finding the MadeForKids condition of a video guide explains how to expect upward the MFK status of a video using the YouTube Data API Service.

In conjunction with these changes, a reminder has been added to the Embedded Player Parameter documentation to explain that if you enable Autoplay, playback will occur without any user interaction with the player; playback data collection and sharing will therefore occur upon folio load.

Baronial 27, 2020

The YouTube API Services Terms of Service and the Programmer Policies link, in several places, to a form that you would use to apply for a quota extension, to request YouTube'south approval for a user interface change or other modification, or to notify YouTube of a change of control for your API client. Previously, some of these links pointed to different forms specific to a particular type of request, but they have been updated to all point to the aforementioned grade. For the use cases listed here, please select 'Quota Extension Asking' in the course and include any relevant data in the 'Explain in particular how yous apply YouTube API Services today' input box.

June 30, 2020

The Complying with the YouTube Developer Policies guide begins with a list of policies that developers using YouTube API services must adhere to. The Terms of Service link in that list has been corrected to indicate to the YouTube API Services Terms of Service rather than the YouTube Terms of Service.

June 15, 2020

The new Complying with the YouTube Programmer Policies guide provides guidance and examples to help you ensure that your API clients adhere to specific portions of the YouTube API Services Terms and Policies (API TOS).

This guidance offers insight into how YouTube enforces sure aspects of the API TOS but does not supplant any existing documents. The guide addresses some of the nearly mutual questions that developers ask during API compliance audits. We hope that it simplifies your feature evolution process by helping you understand how we interpret and enforce our policies.

Jan ten, 2020

Section 9.one of the YouTube API Services Terms of Service has been updated to include new requirements for Child-Directed API Clients and non-Child-Directed API Clients too as requirements relating to uploading content to YouTube from Child-Directed API Clients and non-Child-Directed API Clients.

Section Three.J (Reporting Noncompliance) of the Programmer Policies has been (i) renumbered to Section III.K (Reporting Noncompliance) and (ii) replaced in its entirety with a new Department Iii.J (Child-Directed API Clients). The new Section III.J (Child-Directed API Clients) sets forth requirements for Child-Directed API Clients including specific compliance with the U.South. Children'due south Online Privacy and Protection Act (COPPA), Due east.U. General Data Protection Regulation (GDPR), and any other applicative laws or regulations, and notifying Google of your Child-Directed API Clients. In add-on, Child-Directed API Clients and users of Child-Directed API Clients must not take whatsoever YouTube API Services write-based deportment to YouTube websites, applications, services or products via Child-Directed API Clients. Admission to, or use of, YouTube API Services can be suspended or terminated for non-compliance with the YouTube API Services Terms of Service and Programmer Policies including non-compliance with Section Three.J.

June 18, 2019

The link to the class that you would apply to apply for a quota extension, which appears in department D.3 of the Developer Policies, has been updated.

Dec 18, 2017

Section Three.E.4.h of the Developer Policies has been updated to clarify that in add-on to not replacing API Information with independently calculated data, yous also must not access or use API Data to create new or derived data or metrics. In addition, the updated policy explains a requirement on API Clients to clearly disembalm that any information, information, or metrics that are not based on API Data but that display alongside API Data are non from YouTube and are part of your own product.

February x, 2017

The updated YouTube API Services Terms of Service and related documents such equally the Developer Policies, which were originally published on Baronial 11, 2016, at present collectively constitute the effective set of Terms for YouTube API Services. The electric current set of Terms was originally published 180 days before it would become effective to ensure developers had sufficient fourth dimension to review and comply with the updated set of Terms.

The Terms and related documents, such as the Developer Policies, have been updated so that they no longer mention old and new sets of Terms. To avoid confusion, the prior fix of Terms has likewise been removed.

January 27, 2017

The following changes have been made to the YouTube API Services Terms of Service and Developer Policies that are scheduled to get into consequence on February 10, 2017.

Section 23 of the YouTube API Services Terms of Service has been updated. The changes limit the length of time and circumstances when the non-assert provision in the Terms is applicable.

The following forms linked from the Terms and Programmer Policies are now agile:

Document	Section	Class
Terms of Service	25.9	Change of control
Developer Policies	3.D.3	Quota extension
Developer Policies	III.F.1	UI approval
Developer Policies	3.M.1	Commercialization approving
Developer Policies	Iii.J	Written report noncompliance

Developer Policies, section III.East.2.a has been updated to analyze the conditions under which you may aggregate API Data.
Developer Policies, department 3.G.i.d has been updated so that the provision applies to YouTube API Data rather than YouTube audiovisual content. As noted in the Terms, YouTube API Information includes YouTube audiovisual content.
Developer Policies, section III.G.1.d has also been updated to not mention subscriptions, which are already covered under the restrictions in section III.G.ane.b.
Developer Policies, section III.Grand.2.c has been updated solely to note that the restrictions in section III.G.1, especially section 3.Thou.1.d, are particularly relevant to that department.

Baronial 11, 2016

The newly published YouTube API Services Terms of Service (the "Updated Terms") provides a rich set of updates to the current Terms of Service. In addition to the Updated Terms, which will go into effect as of February ten, 2017, this update includes several supporting documents that explain YouTube policies to aid guide developers who are integrating YouTube API Services into their API Clients.

This update includes the following documents. All documents are in English unless otherwise noted.

The Updated Terms. Versions are available for the following regions and countries:
- Americas
- APAC
- EMEA - translations are also published in Dutch, French, German, and Spanish
- Russia (Russian)
The Developer Policies explain policies that you demand to follow when accessing or using YouTube API Services in your service, product, or awarding.
The Required Minimum Functionality defines minimum functional requirements for API Clients that implement or provide access to specific features of YouTube API Services. For example, API Clients that enable video uploads to YouTube must enable users to gear up a championship when uploading a video.
The Bailiwick API Services certificate identifies the Discipline API Services discussed in section 14.3 (Special Terms) of the Updated Terms. The new document as well explains how that department of the Updated Terms would affect bodily deprecation dates for Bailiwick API Services.
The Branding Guidelines are not a new document, but they will utilise under the Updated Terms simply equally they apply nether the electric current Terms.
This revision history and its accompanying RSS feed.

The following changes were made to a previous version of the Terms of Service.

In add-on to these changes, there are a couple of other changes related to the electric current Terms of Service:

Section vii (Deprecation) has said for a long time that, following a deprecation announcement, Google would employ commercially reasonable efforts to maintain YouTube API versions and features identified at https://developers.google.com/youtube/youtube-api-list until the after of (i) one year after the announcement or (ii) April 20, 2015. The text has been updated to remove the reference to the April 2015 date since any deprecation announcements even so to occur are certain to be after that date.
We have removed the set of Monetization Guidelines that talked about guidelines for building commercial applications. Those guidelines, which were originally written in 2008, contained references to features that were deprecated years agone as well every bit to sample implementations that were no longer relevant. The link from the Terms of Service to those guidelines has also been removed.