This document lists requirements that are specific to all applications developed with the Places API, including the Place Autocomplete service that is part of that API. More general information for Google Maps developers may be found in the Google Maps Platform Terms of Service.
Displaying Places API results
You can display Places API results on a Google Map, or without a map. If you want to display Places API results on a map, then these results must be displayed on a Google Map. It is prohibited to use Places API data on a map that is not a Google map.
Displaying attribution
If your application displays data from the Places API on a Google Map, then the Google logo will be included and may not be altered. Applications that display Places API data on the same screen as a Google Map are not required to provide further attribution to Google.
If your application displays data from the Places API on a page or view that does not also display a Google Map, you must show a Powered by Google logo with that data. For example, if your application displays Places API data on one tab, and a Google Map with that data on another tab, the first tab must show the Powered by Google logo.
| For use on a light background | For use on a dark background |
|---|---|
|
|
The Powered by Google logo is not translated into different languages or localized. It's just an image.
The following zip file contains the Powered by Google logo in the correct sizes for desktop, Android and iOS applications. You may not resize or modify these logos in any way.
Download: powered_by_google.zip
If you're using the Places API from a device where the attribution display is not practical, please contact our sales team to discuss licenses appropriate to your use case.
Other attribution requirements
Places API responses may include Listings provider attributions in HTML format that must be displayed to the user as provided. Any links included in the HTML must be preserved. We recommend placing this information below any search results or Place Details information.
Providing terms of use and privacy policy
If you develop a Places API application, you must make available a Terms of Use and a Privacy Policy with your application which meets the guidelines outlined in section 3.2.2(a) of the Google Maps Platform Terms of Service:
- Your Terms of Use and Privacy Policy must be publicly available.
- You must explicitly state in your application's Terms of Use that by using your application, users are bound by Google’s Terms of Service.
- You must notify users in your Privacy Policy that you are using the Google Maps API(s) and incorporate by reference the Google Privacy Policy.
The recommended place to make available your Terms of Use and Privacy Policy depends upon your application's platform:
Mobile applications
If developing a mobile app it is recommended that you provide a link to your Terms of Use and Privacy Policy on your application's download page in the relevant application store and in an application settings menu.
Web applications
If developing a web application it is recommended that you provide a link to your Terms of Use and Privacy Policy in the footer of your website.
Pre-Fetching, Caching, or Storage of Content
Applications using the Places API are bound by the Google Maps Platform Terms of Service. Section 3.2.3(a) and (b) of the terms states that you must not pre-fetch, index, store, or cache any Content except under the limited conditions stated in the terms.
Note that the place ID, used to uniquely identify a place, is
exempt from the caching restriction. You can therefore store place ID values
indefinitely. The place ID is returned in the place_id field in
Places API responses.