Summary of Changes:

View the current version of the Google Play Developer Distribution Agreement

Main Changes implemented on August 29, 2023

• We revised section 3.1 to that subject to a developer accepting the terms of the DDA, Google will allow the developer to use Google Play for their products.
• We revised section 3.5 by deleting the phrases “from time to time’ and “in its sole discretion”.
• We revised section 4.9 by deleting the prohibition on developers using user information outside of Google Play to sell their products.
• We revised Section 5.1 & 6.5 to clarify that (i) the developer grants Google a license upon making their products available on Google Play, (ii) that such license is sublicenseable to 3rd parties for the sole purpose of checking compliance with the DDA and associated policies, and (iii) the authorization/licenses granted under this section cease upon termination of the DDA.
• We revised section 7.1 to state that where prohibited by applicable law, we do not condition promotions or marketing based on a developer launching their app first on Google Play.
• We deleted the phrase ‘in its sole discretion” and added a link to our appeals process policy page to section 8.3.
• We clarified that a developer may terminate the DDA at any time at section 10.2.
• We revised section 12 to clarify that the warranty disclaimers are applicable to the maximum extent permitted by law.

Main changes implemented on 3 October 2022

• We updated the definition of Authorised Provider to clarify that this term refers to a third party non-Google entity authorised by Google to provide services that enable developers to receive payments for Products sold to users via Google Play.
• We updated the term 'Payment Account' to 'Payments Profile', to better describe the service account or profile that enables a Payment Processor to collect and remit payments to the developer.
• We updated the definition of Payment Processor to clarify that this term refers to a Google-affiliated entity providing services that enable developers to receive payments for Products sold via Google Play.
• We updated the definition of Taxes and added a new term 'Transaction Taxes' to provide more clarity about which types of taxes are within the scope of the DDA.
• We updated section 3.2 to make reference to Payments Profile instead of Payment Account.
• We updated section 3.3 to provide that developers grant Google permission to charge, collect and discharge any taxes (such as Telecom and Communications taxes) that developer is responsible for.
• We updated section 3.4 to clarify the mechanism to charge the Service Fee (including any applicable taxes).
• We revised section 3.5 to add new language to support developers that use Play Console to set non-sales taxes on transactions with customers in the United States.
• We revised section 3.6 to require developers that are not United States nor Singapore residents for tax purposes to certify that any services that they provide through their Products will not be performed in the United States or Singapore and to provide written notification (including via email) to Google at least 90 days prior to any change to the certification.
• We revised section 11.1 to add that developers are only monetising their Product on their own behalf and not as an agent or appointee on behalf of another person.
• We revised section 14 to add a requirement for developers to provide Google with a tax indemnity.

Main changes implemented on November 17, 2020

• We updated Section 3.4 of the DDA to link to a help center article with the countries/territories where Google acts as Your agent. 
• We added that taxes may be withheld if Google reasonably determines that it is required under applicable law and that developers must provide tax documentation upon Google’s request (Section 3.6).
• We updated Section 9.3 to incorporate Google’s Controller-to-Controller Data Protection Terms to enable the continued transfer of personal data out of the European Economic Area, Switzerland, and the UK. This was required as a result of a July 2020 decision by the Court of Justice of the EU that invalidated the EU-U.S. Privacy Shield as an approved mechanism for the transfer of personal data.
• We added a new Section 11.4 that requires developers to represent and warrant that the information they provide to Google is current, true, accurate, supportable, and complete.

Main changes implemented on June 12, 2020

• We added to the definition of “Play Console” that the Play Console is available as an app to developers.
• We updated the terms and a support article to remove “for the marketing of” and inserted “to make Your Products available in Google Play” (Section 3.1).
• We added that developers will receive notice of revisions to the “Service Fee” as provided in Section 15 (Section 3.4).
• We deleted wording regarding enforcement actions Google can take when a developer fails to comply with the DDA (Section 4.7).
• We deleted wording regarding Product ratings that is out of date and replaced it with a more detailed description of quality factors that will appear in the developer policies (Section 4.11).
• We deleted the phrase “in its sole discretion” in two places and added examples of what may include an “adverse impact” warranting suspension of a developer or a Product (Section 8.3).
• We updated the terms to (i) add 30 days notice before termination for the reasons specified in Section 10.3 if required under applicable law, (ii) add a right for Google to terminate if there is potential for economic, reputational or security related harm to Google, users, or our partners, (iii) add “Where allowed under applicable law” to Google’s termination for any reason, and (iv) add that, upon termination by Google, developers will lose access to the Play Console and we included a link to a related help article (Section 10.3).
• We added “To the maximum extent permitted by law” to the Disclaimer of Warranties (Section 12.1).
• We added references to specific export control and sanctions regulations to the export law provision (Section 16.5).
• We added that developers may have other ways to resolve disputes with Google as described in the developer policies (Section 16.8).
• We added that the terms are silent on governing law for developers accepting on behalf of a United States city, county or state government entity (Section 16.8).

Main changes implemented on November 5, 2019

• We updated the terms to allow application security partners to review Products for compliance with developer policies (Section 5.1).
• We updated the terms to help us better market and promote Your Products within Google Play and on Devices (Sections 5.1, 6.2, and 6.3).
• We changed the defined term “Transaction Fee” to “Service Fee” to better reflect the range of services that Google provides to developers covered by the fee (Section 3.4).

Main changes implemented on April 15, 2019

• We updated the terms to reflect where Google is acting either as Your agent or as a marketplace service provider depending on the country where You distribute your Product(s) and that Google will market Your Product(s) subject to Your control and direction (Sections 2.1, 3.1, 5 and 11.2).
• We changed the terms to describe that Google will deduct the amount of withholding taxes from payments if Google is required by applicable law to withhold taxes, or if Google is notified by the Payment Processor or the Authorized Provider that they are required by applicable law to withhold taxes (Section 3.6).
• We improved wording and organization throughout for clarity and readability.
• We updated the DDA and relevant support articles to accomplish the above changes and to clarify there are no changes to our approach if the United Kingdom ceases to be part of the European Economic Area in the future.

Main changes implemented on February 26, 2018

• We updated the terms to describe that, as Your agent, Google is acting as merchant of record for sales to users in the EEA (Section 3.3).
• We changed the terms to describe that Google will determine and remit the taxes for sales in the EEA. And with notice to You, Google may also determine and remit taxes for sales in other countries or territories (Section 3.4).
• We added a provision permitting Google to run promotional activities within certain parameters, such as no impact on amounts payable to developers (Section 7).
• We clarified that data collected or used will be in accordance with Google’s privacy policy and that data can be used in the aggregate to improve Google Play, related products and services, and the user and Developer experience across Google products and services (Section 9).
• We improved wording and organization throughout for clarity and readability.

Main changes implemented on May 17, 2017

• We updated the terms to subtract the developer share of all refunds from developer payouts (Section 3.7).
• We made changes to make it clear that the DDA covers the existing and new services provided to developers through Google Play (replaced definition of "Store" with new definition of “Google Play” throughout).

Main changes implemented on July 2, 2016

• We've updated the terms to support the launch for Google Play Family Library, which allows users to share paid apps with family members (Section 5.4)
• Clarified that the DDA governs all tools and features in the Developer Console (Definitions, Section 11, Section 13)
• Clarified that Google may evaluate your apps for compliance with the Developer Program Policies and the DDA (Section 5.1)
• Clarified that the DDA supersedes any conflicting terms in your End User License Agreement (Section 5.4)

Main changes implemented on May 5, 2015

• Update to allow applicable Google entities to distribute apps and games on Google Play based on the countries where your product(s) is available for download and purchase (Section 3.3)
• We've clarified that Google will only need to be notified of a change of control (e.g. acquisition, merger, etc.) by your business. (section 15.6).

Main changes implemented on September 25, 2014

• Update to requirements regarding the level of support that developers must provide to their users, including a minimum defined service level and requirements for accurate contact information (section 3.6).
• New language introduced to support the distribution of apps and games from the Google entity most appropriate to the user's location, and to comply with changes to international tax regulations (section 3). Please see this page for details.
• We've updated Section 4.5 to provide additional clarity around the distribution of third-party apps on Google Play to maintain a secure ecosystem.
• Expansion of the marketing opportunities developers have available when Google promotes their apps (developers may manage this setting via controls in the developer console). See sections 5.1 and 6.2.
• We've added language supporting the removal of installed apps from devices where the apps could pose serious harm or an identified security risk to devices or data. (Section 7.2).
• The agreement amendment procedure has been updated to be less disruptive to developers and consistent with industry standards, allowing us to bring new product features to users and developers more quickly. (Section 14).