Effective date: July 20, 2022
Information we collect
The personal information that you are asked to provide, and the reasons why you are asked to provide it, will be made clear to you at the point we ask you to provide your personal information.
If you contact us directly, we may receive additional information about you such as your name, email address, phone number, the contents of the message and/or attachments you may send us, and any other information you may choose to provide.
When you register for an Account, we may ask for your contact information, including items such as name, company name, address, email address, and telephone number.
How we use your information
We use the information we collect in various ways, including to:
- Provide, operate, and maintain our website
- Improve, personalize, and expand our website
- Understand and analyze how you use our website
- Develop new products, services, features, and functionality
- Communicate with you, either directly or through one of our partners, including for customer service, to provide you with updates and other information relating to the website, and for marketing and promotional purposes
- Send you emails
- Find and prevent fraud
cleanriver.com follows a standard procedure of using log files. These files log visitors when they visit websites. All hosting companies do this and a part of hosting services’ analytics. The information collected by log files include internet protocol (IP) addresses, browser type, Internet Service Provider (ISP), date and time stamp, referring/exit pages, and possibly the number of clicks. These are not linked to any information that is personally identifiable. The purpose of the information is for analyzing trends, administering the site, tracking users’ movement on the website, and gathering demographic information.
Cookies and Web Beacons
Like any other website, cleanriver.com uses ‘cookies’. These cookies are used to store information including visitors’ preferences, and the pages on the website that the visitor accessed or visited. The information is used to optimize the users’ experience by customizing our web page content based on visitors’ browser type and/or other information.
Advertising Partners Privacy Policies
Note that cleanriver.com has no access to or control over these cookies that are used by third-party advertisers.
Third-Party Privacy Policies
You can choose to disable cookies through your individual browser options. To know more detailed information about cookie management with specific web browsers, it can be found at the browsers’ respective websites.
CCPA Privacy Rights (Do Not Sell My Personal Information)
Under the CCPA, among other rights, California consumers have the right to:
Request that a business that collects a consumer’s personal data disclose the categories and specific pieces of personal data that a business has collected about consumers.
Request that a business delete any personal data about the consumer that a business has collected.
Request that a business that sells a consumer’s personal data, not sell the consumer’s personal data.
If you make a request, we have one month to respond to you. If you would like to exercise any of these rights, please contact us.
GDPR Data Protection Rights
We would like to make sure you are fully aware of all of your data protection rights. Every user is entitled to the following:
The right to access – You have the right to request copies of your personal data. We may charge you a small fee for this service.
The right to rectification – You have the right to request that we correct any information you believe is inaccurate. You also have the right to request that we complete the information you believe is incomplete.
The right to erasure – You have the right to request that we erase your personal data, under certain conditions.
The right to restrict processing – You have the right to request that we restrict the processing of your personal data, under certain conditions.
The right to object to processing – You have the right to object to our processing of your personal data, under certain conditions.
The right to data portability – You have the right to request that we transfer the data that we have collected to another organization, or directly to you, under certain conditions.
If you make a request, we have one month to respond to you. If you would like to exercise any of these rights, please contact us.
Another part of our priority is adding protection for children while using the internet. We encourage parents and guardians to observe, participate in, and/or monitor and guide their online activity.
cleanriver.com does not knowingly collect any Personal Identifiable Information from children under the age of 13. If you think that your child provided this kind of information on our website, we strongly encourage you to contact us immediately and we will do our best efforts to promptly remove such information from our records.
YouTube API Services – Developer Policies
This document (the “YouTube API Services Policies” or “Policies“) sets out the policies that you need to follow when accessing or using YouTube API Services in your service, product, or application. These Policies help you access and use YouTube API Services in 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 the Agreement, so you must comply with them. YouTube reserves the right to change these Policies, and your continued access to, or use of, YouTube API Services constitutes your agreement to and acceptance of any such changes. Policy changes, like changes to the YouTube API Services Terms of Service, will be documented in the Terms of Service Revision History, and you can subscribe to the RSS feed for that revision history to be notified of any such changes.
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 terms must and required refer to absolute requirements.
- The term must not refers to an absolute prohibition.
- The terms should, should not, recommend, and recommended indicate 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 term may indicates 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, the Definitions section 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.
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 your API Clients violate any of these principles, you are likely also violating the terms of the Agreement. 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-rich API Clients that bring significant additional value to the YouTube ecosystem and its users. Promptly update API Clients as the features offered in YouTube API Services change.
- Be honest and transparent.This principle applies to all facets of API Clients and 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 your API Client does. Don’t engage in any deceptive activity or messaging related to your identity, your data collection, storage, sharing, use and deletion practices, actions that your API Client takes on users’ behalf, or anything else. Be honest and do not mislead or confuse users in the way you use and present data.
- 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 create API Clients that 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.
General Developer Policies
- be prominently displayed and easily accessible to users at all times,
- notify users that the API Client uses YouTube API Services,
- clearly and comprehensively explain to users what user information, including API Data relating to users, the API Client accesses, collects, stores and otherwise uses,
- clearly and comprehensively explain how the API Client uses, 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,
- disclose, if it does so, that the API Client allows third parties to serve content, including advertisements,
- disclose, if it does so, that the API Client stores, 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,
- if the API Client accesses or uses Authorized Data, explain that, in addition to the API Client’s normal procedure for deleting stored data, users can revoke that API Client’s access to their data via the Google security settings page at https://security.google.com/settings/security/permissions, and
- if the API Client uses Authorized Data, explain how users can contact the API Client owner or developer with questions or complaints about the Client’s privacy practices.
Maintainability and Deprecation
- API Clients must use the most recent versions of YouTube API Services. This means that you must be able to update API Clients when newer versions of YouTube API Services are released. Non-website API Clients, like mobile apps or installed applications, must be capable of being remotely updated to use the most recent versions of YouTube API Services. You must update your API Clients to the most recent versions of the YouTube API Services within 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 the YouTube API Services, such changes will be documented in the Terms of Service Revision History, and you can subscribe to the RSS feed for that revision history to be notified of any such changes.
- You must promptly update non-deprecated API Clients to use newer versions of YouTube API Services as those versions are released.
- You must update deprecated versions of your API Clients to clearly indicate to users that some functions or features of YouTube API Services might stop working due to the API Clients’ deprecated status.
Implementing YouTube Features
- API Clients must also comply with the Requirements for Minimum Functionality for YouTube API Services (“RMF“). In addition, API Clients must not place any limitations on the YouTube functionality required by the RMF.For example, the RMF states that an API Client that 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 an API Client must not set a shorter maximum length for that field.
- Any API Client feature that initiates a user action related to a YouTube resource must be:
- clearly and unequivocally identifiable as a YouTube action,
- distinct and not mixed with your API Client’s functionality, and
- 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 Clients that perform write operations may suggest parameter or property values, but users must have final control over the data that will be published to YouTube Applications. Similarly, API Clients must 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 Clients that suggest values for text fields, like video titles or descriptions, must incorporate relevant keywords into those values. For example an API Client that suggests video titles should not generate the same default titles for all users.
These examples illustrate how this policy would apply to an API Client that uploads videos to YouTube:
- The API Client may 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, the API Client must not append the recording date, API Client name, or any other text unless the user has explicitly consented to such changes.
- An API Client may provide an option to translate a video title to other languages. However, the API Client must not add any such translations without the user’s consent. In addition, if the API Client’s default 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 Clients must clearly indicate how user-provided data will be used on YouTube.This policy is particularly relevant for API Clients that interface with multiple services and platforms since there may be functional or labeling differences between those services and platforms.
For example, an API Client enables 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 the API Client labels the field “Feedback” in its comment form, it needs to clearly indicate that that value corresponds to the comment text on YouTube.
- API Clients that use search functionality provided by YouTube API Services must not modify or replace the text, images, information, or other content of, the search results returned by those Services.For example, API Clients must not merge or intermix results from sources other than YouTube and present them as YouTube search results.
- An API Client should not limit or reduce the functionality of a YouTube feature unless that limitation is a core aspect (as described in the examples below) of the API Client itself and that YouTube feature is not required by the RMF (“Permitted Feature Limitation“).
- Example 1: Permitted Feature LimitationThe YouTube Data API service allows a video uploader to provide translations of a video’s title. Generally speaking, an API Client that implements this feature should allow uploaders to translate video titles to any language that YouTube supports. However, an API Client that 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.
- Example 2: Non-permitted Feature LimitationA second API Client supports 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 the API Client supports 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 the API Client. Instead, the API Client must offer the full range of languages that YouTube supports.
- API Clients with 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 an API Client could provide that information, and you should choose an appropriate method for your API Client. Within this explanation, an API Client should 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, the API Client could explain that video uploaders can add translations for other languages in the YouTube Creator Studio and provide a link to that functionality.
- API Clients that offer features sourced from multiple services and platforms should offer feature parity to the extent that it exists across those sources, providing user choice. When API Clients include features that are supported on YouTube and on other platforms, API Clients must not consistently present YouTube features in a detrimental way (e.g., by only providing those features from other platforms).For example, suppose an API Client allows users to upload videos to YouTube and three other platforms, and all of those platforms support the ability to upload captions. If the API Client also supports caption uploading, then it must support that feature for YouTube.
Accessing YouTube API Services
- API CredentialsTo access or use some YouTube API Services, you must first use the Google Developers Console (https://console.developers.google.com/) to create API Credentials for your API Project. Those credentials enable Google and YouTube to link API activity to a particular API Project and API Client.
In addition to creating API Credentials, the Developers Console might require you to provide certain other information, such as identification or contact details, before you can access or use the YouTube API Services associated with those credentials. YouTube reserves the right to require you to provide additional information to continue to access or use YouTube API Services.
If you need to create API Credentials to access or use a specific YouTube API service, the documentation for that service explains how to create those credentials. For example, the YouTube Data API service, YouTube Reporting API service, YouTube Analytics API service, and Android Player API service all document steps for creating API 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 an API Client can retrieve, insert, update, or delete on the user’s behalf. Scopes enable API Clients to 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 of YouTube API Services:
- You must not mask or misrepresent your identity or your API Client’s identity when accessing or using YouTube API Services or when creating an API Project or API Credentials.
- You must only use API Credentials assigned to you and to your API Project to access YouTube API Services. Similarly, you must not use any other means to mask or misrepresent your API Client’s access to, or usage of, YouTube API Services.
- If your API Client needs to create API Credentials to access or use YouTube API Services, you must create exactly one (1) API Project for that API Client. Those API Credentials are intended to be used exclusively by the associated API Client, which means that you must not use that one (1) API Project for multiple API Clients.
- You may share your API Credentials with agents operating solely on your behalf and under a written duty of confidentiality. However, you must not share or disclose your API Credentials to any other third party, allow access to or use of your API Credentials by any other third party, or embed your API Credentials in open source projects.
- User Authentication and AuthorizationAuthentication and authorization refer to the process by which users identify themselves and consent to allow an API Client to access certain user-specific data. Some YouTube API Services do 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, an API Client can search for public videos but does not need user authorization to do so. However, an API Client does 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.
- API Clients must 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.
- API Clients must obtain user consent in accordance with the applicable laws and only request access to authorization scopes that they currently use. The access that an API Client requests 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 an API Client access to the first scope, that API Client would be able to retrieve information about the current user’s YouTube channel. However, if a user granted the API Client access to the second scope, the API Client could also upload a video to that channel.
In this scenario, an API Client that 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 the API Client’s developer plans to eventually introduce support for write-based actions, the developer cannot future-proof the API Client by requesting access to the authorization scope for writing data before the Client actually supports features that require that scope.
- API Clients should request access to authorization scopes in context whenever possible. By requesting access to user data in context, via incremental authorization, an API Client enables users to more easily understand why it needs access to that data.
- API Client Identification and Representation
- API Clients must 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;
- API Clients must 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 an API Client requests access to and the consequences of sharing that data.
- API Clients must clearly and comprehensively identify to users the purposes for which they access and use user data. API Clients must not use user data for secondary purposes that are not clearly disclosed to users.Users should not be surprised to learn that an API Client contains hidden features, services, or actions that are inconsistent with the Client’s marketed purposes.
- Every API Client must provide a clearly explained and easy way for users to revoke any authorization consent they have provided to an API Client to access YouTube API Services.When a user revokes consent through this mechanism, the API Client must programmatically revoke that token right away to communicate the change in permissions to Google. For example, an API Client could use a Google API Client Library to revoke the token.
In addition, following revocation of consent through this mechanism, you and your API Clients must delete all Authorized Data that 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.
- Every API Client must provide a clearly explained and easy way for users to revoke any authorization consent they have provided to an API Client to access YouTube API Services.When a user revokes consent through this mechanism, the API Client must programmatically revoke that token right away to communicate the change in permissions to Google. For example, an API Client could use a Google API Client Library to revoke the token.
- Usage and QuotasYouTube may use quotas and place use restrictions to ensure that YouTube API Services are accessed and used as intended and that you and your API Clients do not reduce service quality or limit access for others.
If your API Client reaches the quota limit for a service, you can apply for a quota extension by completing an API Compliance Audit where 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 an additional quota extension.
If YouTube approves the application, you must use the additional quota granted only for the approved use case. If your API Client’s use case changes, to use any allocated quota for the new use case, you must notify YouTube of the change by resubmitting an API Compliance Audit and receive approval for the application.
If YouTube rejects the application, you can file an appeal.
- InactivityYouTube reserves the right to disable or curtail your access to, or use of, specific YouTube API Services if your API Project has been inactive for 90 consecutive days. For example, YouTube could revoke your API Credentials, or reduce (or eliminate) your API Project’s quotas for specific YouTube API Services. If your API Client’s quota 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 the YouTube API Services.
- Contact InformationYouTube’s primary means of contacting you about your API Project or API Client is 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 your API Clients.
- Prohibited AccessYou are prohibited from accessing or attempting to access YouTube API Services via any means if your API Credentials are 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 access YouTube API Services via any means, including by creating or using a proxy to create new Google Accounts, API Credentials or API Projects.
- Undocumented ServicesYou 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.
Handling YouTube Data and Content
- Audiovisual ContentYou and your API Clients must not, and must not encourage, enable, or require others to:
- download, import, backup, cache, or store copies of YouTube audiovisual content without YouTube’s prior written approval,
- make content available for offline playback, or
- use any aspect of the YouTube API Services to facilitate or promote copyright infringement or the exploitation of copyright-infringing materials.
- Data Aggregation
- Do not aggregate API Data except that you may only aggregate API Data relating 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 aggregated API Data must only be viewable by that content owner.
- Do not aggregate API Data or otherwise use API Data or YouTube API Services to 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 an API Client to retrieve API Data on their behalf for their respective viewing. That API Client may separately aggregate API Data retrieved 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. The API Client must not combine API Data from the different content owners.
- Authorized Data UsageThese policies relate to your use of Authorized Data. They are relevant for any API Client that 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 any API Client that enables a user to upload videos, retrieve the user’s list of uploaded videos, create playlists, or comment on videos.
- API Clients must 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.
- API Clients must not display or allow access to Authorized Data to anyone other than the authorizing user or agents expressly approved by that user.
- API Clients must 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.
- API Clients must clearly identify the YouTube channel or content owner that is associated with any request that requires user authorization.
- API Clients must clearly identify any content visibility settings that will be set or modified by any authorized user action. In addition, API Clients must not modify existing content visibility settings unless the authorizing user has expressly instructed the API Clients to do so.For example, in the YouTube Data API service, a video’s privacy status can be set to
unlisted. If an API Client supports video uploads, the Client must clearly display an option for the user to choose one of those values. Similarly, if an API Client supports edits to a video’s metadata, the API Client cannot change a video’s privacy status without the user’s express consent.
- Refreshing, Storing, and Displaying API DataDevelopers 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 YouTube API Data.
- API Clients may 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.
- API Clients may store the following types of Authorized Data for 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:
- data retrieved through the YouTube Analytics API service,
- data provided through the YouTube Reporting API service, or
- 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.)
For example, an API Client may 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. The API Client must also verify, every 30 days, that the video has not been deleted.
To be clear, an API Client must not store statistics retrieved as Non-Authorized Data for more than 30 days. For example, an API Client must not store the subscriber count for a YouTube channel for more than 30 days without authorization from the channel owner.
- API Clients may store all other types of Authorized Data not 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, the API Client must either delete or refresh the stored data.
- API Clients may temporarily store limited amounts of Non-Authorized Data for as long as is necessary for the purposes of the API Client but not longer than 30 calendar days. As in section (III.E.4.c) immediately above, this means that after 30 calendar days, the API Client must either delete or refresh the stored data.
- In all cases, API Clients must use reasonable efforts to ensure that their stored API Data is consistent with the current data available through YouTube API Services. For example, API Clients should reflect metadata changes and viewcount updates as quickly as possible.
- API Clients must display the most updated API Data available in their user-facing presentations, including in user interfaces, although API Clients may display historical API Data provided that it is presented accurately in context of time.
- Your API Clients that 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, your API Client could 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 the API Client does 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 authorized API Client that supports the ability to delete that data.
Similarly, API Clients must 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.
- Your API Clients must not (i) replace API Data with similar, independently calculated data, or (ii) access or use API Data to create new or derived data or metrics. To the extent your API Clients display any information, data or metrics not based on API Data alongside API Data, your API Clients must 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, your API Client must use the number returned in the API Data. You must not substitute a different number to represent likes, such as the number of users of your API Client that liked the video. Similarly, you are not permitted to use the number of likes returned in the API Data to calculate other metrics, such as the percentage of total likes that were made through your API Client or a score that factors in likes, total views, or any other API Data. However, you are permitted, for example, to display the number of likes that were made through your API Client as long as that number is displayed alongside the total likes returned in the API Data and as long as your API Client clearly communicates that the API Client calculates the additional metric independently of YouTube API Data.
- When your API Client loads, 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 Client upon video playback to customize the player on your API 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 to
false. As noted in the YouTube API Services Terms of Service, you and your API Clients must comply with all applicable laws, rules, and regulations, including privacy laws and regulations.
- API Clients must look up the Made For Kids status of each YouTube video that it embeds on its site or app by following the instructions in this guide. For each video that is designated Made For Kids, API Clients must 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 Center for more information on determining content as Made for Kids.
- SecurityYou and your API Client must:
- maintain appropriate administrative, organisational, technical, and physical controls to ensure the privacy, security, and confidentiality of user data and API Data;
- use only industry-standard transport encryption;
- protect API Data and any other data used in your API Client from unauthorized access, use, or disclosure.
You and your API Clients must not, and must not encourage, enable, or require others to, directly or indirectly, scrape YouTube Applications or Google 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.
- YouTube Look and FeelInnovative user experiences and user interface designs are among the most valuable contributions that API Clients can provide to the YouTube community. That said, YouTube’s designers and engineers put a lot of thought into designing YouTube Applications to ensure that those Applications provide a great user experience.
Taking both of those points into account, your API Clients must not change or interfere with user interfaces in YouTube Applications unless you have obtained YouTube’s prior written approval. You can request that approval at this form.
- Any API Client page 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 displaying YouTube Brand Features in accordance with the requirements below and the YouTube Branding Guidelines (https://developers.google.com/youtube/terms/branding-guidelines).In some cases, an API Client might need to display YouTube Brand Features next to multiple individual content elements to make the attribution clear to the viewer. For example, an API Client that 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. The API Client cannot provide one general set of attribution for all search results from various sources.
- 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.
- You and your API Clients must 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. Your API Clients must display applicable YouTube Brand Features and any other YouTube-provided attribution on all types of devices.
- Playback IntegrityPlayback 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 your API 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, and API Clients are prohibited from providing incentives for watching videos as follows:
- API Clients must not charge users to watch content in an embedded YouTube player.
- API Clients must 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 Clients must not require a user to subscribe to a channel or like a video to continue watching YouTube audiovisual content.For clarity, if your API Client’s normal functionality requires a certain action that is not specific to YouTube API Services, such as login or age verification, that functionality is allowed.
- API Clients must not offer or provide incentives, rewards, or other compensation to users for engaging with YouTube Applications (directly or indirectly) by performing actions like viewing content, liking content, sharing content, subscribing to channels, adding comments. For example, API Clients must 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.
Distribution and Commercial Use
In addition, you may distribute and display YouTube audiovisual content and accompanying metadata to users through your API Clients as long as those Clients comply with the Agreement and, specifically, do not engage in any of the prohibited actions listed immediately below.
- Prohibited ActionsFor specific policies in the following list that require YouTube’s prior written approval, you can request that approval at this form.
You and your API Clients must not, and must not encourage, enable, or require others to:
- sell, purchase, lease, lend, convey, redistribute, or sublicense all or any portion of YouTube API Services, including YouTube audiovisual content;
- sell YouTube API Services or access to any components of YouTube API Services unless you obtain YouTube’s prior written approval;
- 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
- sell advertising, sponsorships, or promotions on any page or screen that contains YouTube API Data unless other data, content, or material not obtained from YouTube appears on the same page and offers enough independent value to justify such sales if the YouTube API Data were removed.
- Permitted ActionsAll of the following commercial use cases are permitted subject to your and Your API Clients’ compliance with all other terms of the Agreement, including the prohibited actions detailed in the previous section:
- Selling an API Client;
- Promoting your own business or artistic enterprise by uploading original audiovisual content to YouTube or maintaining channel(s) on YouTube;
- Developing ad-enabled API Clients, such as an ad-enabled blog or website, that use YouTube API Services subject to compliance with all other terms of the Agreement, including the restrictions in section III.G.1.d;
- Placing your own branding in an API Client as long as that branding complies with the YouTube Branding Guidelines and does not interfere with YouTube audiovisual content playback or any YouTube Brand Features;
- Selling or distributing devices that contain or run an API Client;
Monitoring and Audits
YouTube reserves the right to survey, monitor, and/or audit your access to or use of YouTube API Services to ensure quality, to improve YouTube products and services, and to verify your compliance with the Agreement. To that end, YouTube may survey users of your API 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 of YouTube 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 your API Clients, so that YouTube may review those API Clients for compliance with the Agreement.
YouTube may use any technical means to overcome non-compliance with these provisions.
The policies in this section identify additional things that API Clients must 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 your API Clients to 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 your API Clients must not, and must not encourage, enable, or require others to:
- use YouTube API Services to create, offer, or act as a substitute for, or substantially similar service to, any YouTube Applications. API Clients must 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, an API Client must not recreate the browse experience from any YouTube Application without adding significant independent value to that flow.
- misuse YouTube API Services or 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 of YouTube API Services, YouTube Applications, or Google 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 in API Data.
- modify, interfere with, replace, or block advertisements placed or served by YouTube or by YouTube API Services including in API 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, the YouTube 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 of YouTube API Services, YouTube Applications, or Google Applications, including actions that interfere with or disrupt YouTube API Services or 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 to YouTube 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 or YouTube API Services;
- use any technology other than YouTube API Services to access or retrieve API 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 the YouTube API Services;
- modify, translate, create derivative works of, reverse engineer or otherwise attempt to extract the underlying source code from any YouTube API Services or from any software related to those Services;
- use YouTube API Services for 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.
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:
- 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;
- notify Google of the child directed nature of your Child-Directed API Client using the tools provided in here. 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
- not use personalized ads (including remarketing) to target past or current activity by any user of your Child-Directed API Client.
- 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.
- Notwithstanding Section III.D.1.c (API Credentials) above which requires exactly one (1) API Project for 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“).
- 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 Project using the Google Developers Console (https://console.developers.google.com/) (an “Upload Project“) prior to uploading, (B) append mfk110 as 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
- 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.
- 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 Service pursuant 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.
If you are aware of anyone accessing or using YouTube API Services in a manner that is not compliant with these policies or any other part of the Agreement, you may contact the YouTube API Services team to escalate the issue using this form.
“Agreement” means the legal documents defined and referenced in Section 2 (The Agreement) of the YouTube API Services Terms of Service currently located at https://developers.google.com/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 the YouTube 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 the YouTube API Services.
“Google Applications” means Google websites, applications, services, products, pages, and other properties.
“Terms of Service” means the YouTube API Services Terms of Service currently located at https://developers.google.com/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 on https://developers.google.com/youtube or by YouTube, (iii) data, content (including audiovisual content) and information provided to API 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, including https://www.youtube.com, m.youtube.com, mobile applications like the YouTube Gaming application, and so forth, but excluding YouTube API Services.
“YouTube Brand Features” means the trade names, trademarks, service marks, logos, domain names, and other distinctive brand features of YouTube.
Required Minimum Functionality
Required Minimum Functionality (RMF) refers to the features and other functionality that certain tool developers must offer when using the AdWords API. As set forth below, RMF rules are grouped into three categories: Creation Functionality, Management Functionality, and Reporting Functionality. Your compliance with these rules depends on how you use the AdWords API (an “RMF applies” means that RMF applies to you):
|Creation Functionality||Management Functionality||Reporting Functionality|
||RMF applies||RMF applies||RMF applies|
||RMF doesn’t apply||RMF doesn’t apply||RMF applies|
|Internal Use Only
||RMF doesn’t apply||RMF doesn’t apply||RMF doesn’t apply|
If your tool offers very limited and specialized functionality, and could not be used for creating and managing campaigns, ad groups, and ads, it may not qualify as a full-service tool. In this case, the creation and management RMF would not apply. If you’re not sure whether the RMF policy applies to your tool, contact the AdWords API Compliance team. The AdWords API Compliance team will decide whether your tool is full-service or not. Your tool may be reevaluated if the functionality changes significantly.
Note that RMF only applies to tokens with Standard access.
Requirements for Shopping-only,
App Promotion-only and Hotel-only API Tools
If your tool is only designed to create and manage one of the following campaign types, then you are only required to implement the AdWords API creation and management features and reports in the RMF that work with that campaign type.
- Standard Shopping campaigns
- Smart Shopping campaigns
- Mobile App Promotion campaigns
- Hotel campaigns (available only in Google Ads API)
For an updated list of these features please contact the AdWords API Compliance team at https://services.google.com/fb/forms/apicontact/.
Requirements for Reporting-only AdWords API Clients
In order to be compliant with RMF requirements, a Reporting-only AdWords API Client must show Reporting Functionality for each of the levels of the Google Ads hierarchy displayed in its reporting interface. A level of the Google Ads hierarchy means one of Account, Campaign, Ad Group, Ad or Keyword. For example, if a Reporting-only AdWords API Client does show Ad Groups, then it must implement all of the “Ad Group”-level Reporting Functionality that is labeled as “Required” below.
A Reporting-only AdWords API Client may choose not to show specific levels of the Google Ads hierarchy in its reporting interface. For example, if a Reporting-only AdWords API Client does not show any Ad Group performance data in its interface, then it need not implement any of the “Ad Group”-level Reporting RMF.
The above policy also applies to all other report types, though they are not levels of the Google Ads hierarchy. Should you choose to implement any of these reports, you must show all the required fields for each respective report.
In order to be compliant with RMF requirements, AdWords API Client must display all the columns marked required in the Object/Field/Guide column for each report, as default. All other Metric columns must be made available, as an option for users of the AdWords API Client. Google Ads report data should be reasonably prominent and accessible to end users.
If your tool provides a download option, for example a CSV, instead of displaying reporting functionality within the user interface, then the download link must be prominently displayed and intuitively labeled. The downloaded file must contain all of the required reporting fields and be clearly labeled.
Reporting Date Ranges
We recommend that you allow users to filter reporting data by date range. If your tool doesn’t support custom date ranges, then it should at least provide the last 30 days of data for each required reporting field.
Requirements for API Clients providing Creation Functionality or Management Functionality
In order to be compliant with RMF requirements, a Full-Service AdWords API Client must implement all the required creation and management features in the table below and show Reporting Functionality for each of the reports below. Additionally, you must make reasonable effort to ensure that each of the features is easily accessible and functional to end advertisers as measured by the usage of those features.
Requirements for API Clients providing Targeting Idea Service or Traffic Estimation Service
If an AdWords API Client provides any functionality related to TargetingIdeaService or TrafficEstimatorService, it must fully implement the required Creation Functionality, Management Functionality and Reporting Functionality marked “Required” in the table below.
Requirements for Bid Adjustments
All API Clients providing Creation or Management functionality must satisfy the following requirements related to bid adjustments:
- End users must be allowed to input the entire range of allowable values.
- End users must be able to review and edit the bid adjustments before it is set by the AdWords API Client.
- Bid adjustments must be represented only as adjustments to bids, and may not be used to enable or approximate other features, such as targeting or exclusion.
One-Time Extension for Major Updates
In recognition of the fact that API tools may periodically perform extensive technology upgrades, tools that have met all RMF deadlines for at least 2 consecutive years can apply for a 6 month RMF extension in order to implement such upgrades to their platform. If the extension is granted, during the extension period these tools will not be reviewed for compliance with RMF requirements. At the end of the extension period, the tool must be in full compliance with all RMF requirements that were due on or before the last date of the extension period. All RMF requirements due after the end of the extension will remain due on the date specified in the table below.
An API tool may be granted at most one extension every four years (i.e., the second extension must start at least 4 years after the first one ends).
If you would like to apply for an extension for your tool, please request an application form by contacting us at https://services.google.com/fb/forms/apicontact/. Your application must be signed and submitted by an executive (CEO, CTO or Senior VP) of your company. Please note that your application is not guaranteed to be approved.
Unless otherwise specified below, a feature is implemented if and only if all available sub-features and parameters are also implemented. The API Reference documents which parameters and sub-features are available. For example, the feature “Opt in/out of networks” implies support for opting in/out of Google Search, search partners, and the display network. Furthermore, if you implement in your AdWords API Client a feature similar to any feature not required by Google, you must then also implement the similar Google feature in your AdWords API Client. For example, if you implement your own version of “Keyword Ideas” in your AdWords API Client, then you must also implement Google’s “Keyword Ideas” functionality in your AdWords API Client.
To maintain RMF compliance, any new required features must be added by the due date (shown next to each feature as Due: YYYY-MM-DD). Any RMFs with no specified due date are past due. Additionally, we require that you send screenshots and/or mockups of material proposed changes to the AdWords API Client, at least two weeks prior to these changes taking effect, via the Tool Change form. For the sake of clarity, after that two week period has elapsed, you do not need to wait for a response from Google before those material changes take effect.
YouTube Terms of Service
To understand more about how cleanriver.com uses Authorized Data, users can contact Clean River with questions or concerns about our privacy practices at:
Midpoint International Inc.
CleanRiver Recycling Solutions
288 Don Hillock Drive, Aurora, Ontario, Canada L4G 0G9
T: (888) 646-4246 | F: 905-726-9659