Google Maps API/Google Earth APIs Terms of Service Updates

As the Google Maps APIs continue to grow and evolve, we periodically review the Google Maps/Google Earth APIs Terms of Service, which define the terms under which we offer these APIs to developers. Today we are posting an update to these terms which contains a number of notable changes. These changes are intended to encourage use of the APIs in mobile applications, and secure the long term future of the APIs as location aware applications become ever more ubiquitous.

Developers are now permitted to use the Static Maps API outside of a web browser, for example to add thumbnail maps to mobile applications, providing the map image is linked to Google Maps. Developers of mobile apps that are sold for a fee through an online store such as the Android Market and Apple App Store no longer require a Google Maps API Premier license. This brings the Terms of the web based Maps APIs into line with the Terms of the Android Maps API and iOS SDK.
 


 

There are also a number of changes that relate to advertising and usage limits. To ensure that we can continue to offer the Maps APIs to developers for free, we now require that any new Maps API applications going forward display any advertising delivered in the maps imagery, unless the site concerned has a Google Maps API Premier license. The opt-out from displaying such advertising that was offered in earlier versions of the Terms will continue to apply to any existing Maps API applications. Information on exercising this right of opt-out will be provided on this blog at least 90 days prior to the launch of any such advertising.

We are also introducing transaction limits on the number of maps that may be generated per day by commercial Maps API web sites or applications. These limits are documented in the Maps API FAQ and will take effect on October 1st 2011. Commercial sites that exceed these limits may be required to purchase additional transactions or a Maps API Premier license. Additional transactions will be offered online at an affordable rate which will be published on or before the 2nd May 2011.

Commercial sites that consistently exceed these limits and do not purchase additional transactions online will be contacted by a Maps API Premier Sales Manager to discuss their licensing options. Not for profit applications and applications deemed in the public interest (as determined by Google at it’s discretion) are not subject to these limits. In addition, Non-profits are also encouraged to check out their eligibility for the Google Earth Outreach program.

In addition to the most notable changes detailed above, there are many other minor changes and clarifications, and we therefore recommend that you read the complete Terms and the Google Maps API FAQ. You can also discuss the Terms with other Maps API developers on the Google Maps API forum. Please note that Google’s Developer Relations team, who monitor the forums, are not able to offer legal advice. However any frequently asked questions or areas of confusion will be clarified in future FAQ and Terms updates.

Maps APIs over SSL now available to all

As public WiFi becomes increasingly ubiquitous, we spend more and more of our time on shared networks. This can expose our personal data to third parties if the sites we access are not secure. Many sites use Google services to store and manage Google data. In response to this, Google is today announcing improved support for SSL (Secure Sockets Layer) across many APIs, and recommending that any application that manages user data switch to using SSL.

We want to ensure that applications using the Google Maps API are free to follow this recommendation. As such we are happy to offer free access to the Maps API v3, Static Maps API, and Maps API Web Services over HTTPS to all developers from today. To load the Maps API v3 over HTTPS, the API must be loaded from the hostname maps-api-ssl.google.com. For the Static Maps API and Web Services, please use maps.googleapis.com.

In addition to offering access over HTTPS, all of the Maps APIs (with the continuing exception of the Places API) will continue to be accessible over HTTP, and we recommend that sites that are using the API purely to display public data, such as store locations, continue to use HTTP for optimal performance.

Please also note that although SSL access is now available to all developers, the terms of the Maps API have not changed. If your site uses SSL because you charge for access to your application, or because your application is not publicly accessible to all users, you must still purchase a Maps API Premier license. For more information on Maps API Premier, please contact the Maps API Premier Sales team.

We hope this change assists in making your users feel safe and secure using your applications. If you have any questions or concerns about this change, please post to the Maps API v3, Static Maps API, or Web Services forum as appropriate for the service you are using.