This section lists requirements that are specific to all applications developed with the Google Places API Web Service, 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 APIs Terms of Service.
If your application displays Google Places API Web Service data on a map, that map must be provided by Google.
If your application displays Google Places API Web Service data 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 a list of places on one tab, and a Google Map with those places on another tab, the first tab must show the "Powered by Google" logo.
|For use on a white background||For use on any non-white background|
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.
If your application uses the Zagat logo, consult the Zagat Branding and Attribution guidelines.
Google Places API Web Service 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.
Pre-Fetching, Caching, or Storage of Content
Applications using the Google Places API Web Service are bound by the Google Maps APIs Terms of Service. Section 10.5.d of the terms states that you must not pre-fetch, cache, index, or store 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
Google Places API Web Service responses.