This XML file does not appear to have any style information associated with it. The document tree is shown below.
To clarify these processes and better meet the needs of developers using our API Services, we are adding 3 new forms and a guide.
- Audited Developer Requests Form: Developers who have already passed an API Compliance Audit can fill out and submit this shorter form to request an allocated quota extension.
- Appeals Form: Developers whose API projects have failed a compliance audit (or been denied a quota unit increase) can fill out and submit this form.
- Change of Control Form: Developers, or any party operating an API client on a developer’s behalf, who experience a change 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, audit the new API project’s use case compliance, and validate the developer’s current quota allocation.
Each new form will inform us of your intended usage of YouTube’s API and enable us to better assist you.
More details are available in our new API Compliance Audits guide.
]]>- The new Section III.E.4.i provides additional information about the data collected and sent via the YouTube embedded player. You are responsible for any user data you send to us 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 false.
- The new Section III.E.4.j relates to checking the Made for Kids (MFK) status of content before embedding it on your sites and apps. You are responsible for knowing when videos that you embed on your API Client are made for kids and treating data collected from the embedded player accordingly. As such, you must check the status of content using YouTube Data API Service before embedding it on your API Client via any YouTube embedded players.
The new Finding the MadeForKids status of a video guide explains how to look up 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 page load.
]]>This guidance offers insight into how YouTube enforces certain aspects of the API TOS but does not replace any existing documents. The guide addresses some of the most common questions that developers ask during API compliance audits. We hope that it simplifies your feature development process by helping you understand how we interpret and enforce our policies.
]]>Section III.J (Reporting Noncompliance) of the Developer Policies has been (i) renumbered to Section III.K (Reporting Noncompliance) and (ii) replaced in its entirety with a new Section 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.S. Children's Online Privacy and Protection Act (COPPA), E.U. General Data Protection Regulation (GDPR), and any other applicable laws or regulations, and notifying Google of your Child-Directed API Clients. In addition, Child-Directed API Clients and users of Child-Directed API Clients must not take any YouTube API Services write-based actions to YouTube websites, applications, services or products via Child-Directed API Clients. Access to, or use of, YouTube API Services can be suspended or terminated for non-compliance with the YouTube API Services Terms of Service and Developer Policies including non-compliance with Section III.J.
]]>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 set of Terms has also been removed.
]]>-
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 Developer Policies are now active:
Document Section Form Terms of Service 25.9 Change of control Developer Policies III.D.3 Quota extension Developer Policies III.F.1 UI approval Developer Policies III.G.1 Commercialization approval Developer Policies III.J Report noncompliance -
Developer Policies, section III.E.2.a has been updated to clarify the conditions under which you may aggregate API Data.
-
Developer Policies, section III.G.1.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 Data 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.1.b.
-
Developer Policies, section III.G.2.c has been updated solely to note that the restrictions in section III.G.1, particularly section III.G.1.d, are particularly relevant to that section.
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:
-
The Developer Policies explain policies that you need to follow when accessing or using YouTube API Services in your service, product, or application.
-
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 set a title when uploading a video.
-
The Subject API Services document identifies the Subject API Services discussed in section 14.3 (Special Terms) of the Updated Terms. The new document also explains how that section of the Updated Terms would affect actual deprecation dates for Subject API Services.
-
The Branding Guidelines are not a new document, but they will apply under the Updated Terms just as they apply under the current Terms.
-
This revision history and its accompanying RSS feed.
In addition to these changes, there are a couple of other changes related to the current Terms of Service:
-
Section 7 (Deprecation) has said for a long time that, following a deprecation announcement, Google would use commercially reasonable efforts to maintain YouTube API versions and features identified at https://developers.google.com/youtube/youtube-api-list until the later 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 yet 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 ago as well as to sample implementations that were no longer relevant. The link from the Terms of Service to those guidelines has also been removed.
Comentários
Postar um comentário