Google Maps Platform Service Specific Terms

The following terms apply only to the Directions API:

1.1 Use without a Google Map . Customer may use Google Maps Content from the Directions API  in Customer Applications without a corresponding Google Map.

1.2 Attribution Requirements. Customer must provide Google with attribution in accordance with the Documentation if Customer uses Google Maps Content from the Directions API without a corresponding Google Map.

1.3 No use with a non-Google map.  Customer must not use Google Maps Content from the Directions API in conjunction with a non-Google map.

1.4 Caching . Customer can temporarily cache latitude (lat) and longitude (lng) values from the Directions API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Directions API Place ID (place_id) values, in accordance with the  Directions API Policies .

The following terms apply only to the Distance Matrix API:

2.1 Use without a Google Map . Customer may use Google Maps Content from the Distance Matrix API in Customer Applications without a corresponding Google Map.

2.2 Attribution Requirements. Customer must provide Google with attribution, in accordance with the Documentation, if Customer uses Google Maps Content from the Distance Matrix API without a corresponding Google Map.

2.3 No use with a non-Google map.   Customer must not use Google Maps Content from the Distance Matrix API in conjunction with a non-Google map.

The following terms apply only to the Geocoding API:

3.1 Use without a Google Map. Customer may use Google Maps Content from the Geocoding API in Customer Applications without a corresponding Google Map.

3.2 Attribution Requirements. Customer must provide Google with attribution, in accordance with the Documentation, if Customer uses Google Maps Content from the Geocoding API without a corresponding Google Map.

3.3 No use with a non-Google map.  Customer must not use Google Maps Content from the Geocoding API in conjunction with a non-Google map.

3.4 Caching . Customer can temporarily cache latitude (lat) and longitude (lng) values from the Geocoding API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Geocoding API Place ID (place_id) values, in accordance with the  Geocoding API Policies .

The following terms apply only to the Geolocation API:

4.1 Use without a Google Map. Customer may use Google Maps Content from the Geolocation API in Customer Applications without a corresponding Google Map.

4.2 Attribution Requirements. Customer must provide Google with attribution, in accordance with the Documentation, if Customer uses Google Maps Content from the Geolocation API without a corresponding Google Map.

4.3 No use with a non-Google map.  Customer must not use Google Maps Content from the Geolocation API in conjunction with a non-Google map.

4.4 Caching . Customer can temporarily cache latitude (lat) and longitude (lng) values from the Geolocation API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values.

The following terms apply only to the Places API:

5.1 Use without a Google Map. Customer may use Google Maps Content from the Places API in Customer Applications without a corresponding Google Map.

5.2 Attribution Requirements. Customer must provide Google with attribution, in accordance with the Documentation, if Customer uses Google Maps Content from the Places API without a corresponding Google Map.

5.3 No use with a non-Google map.  Customer must not use Google Maps Content from the Places API in conjunction with a non-Google map.

5.4 Caching . Customer can temporarily cache latitude (lat) and longitude (lng) values from the Places API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Places API Place ID (place_id) values, in accordance with the  Places API Policies .

The following terms apply only to the Roads API:

6.1 Use without a Google Map. Customer may use Google Maps Content from the Roads API in Customer Applications without a corresponding Google Map.

6.2 Attribution Requirements. Customer must provide Google with attribution, in accordance with the Documentation, if Customer uses Google Maps Content from the Roads API without a corresponding Google Map.

6.3 No use with a non-Google map.  Customer must not use Google Maps Content from the Roads API in conjunction with a non-Google map.

6.4 Caching . Customer can temporarily cache latitude and longitude values from the Roads API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Roads API Place ID (placeId) values, in accordance with the  Roads API Policies .

The following terms apply only to the Street View Static API:

Customer can cache Street View Static API Panorama ID (pano_id) values, in accordance with the  Street View Static API Policies .

8.1 Google has the ability to independently track Customer’s use of certain Services, but Google relies on Customer to measure its own usage of certain other Services (such as per-Asset Asset Tracking). To verify Customer’s usage of self-measured Services, Google may require the following once per calendar year:

(a) a corporate officer’s certification that Customer has fully complied with the Agreement; and/or

(b) an audit of Customer’s relevant records by a nationally-recognized independent auditor on 30 days prior written notice during Customer’s business hours.

9.1 Google may make available to Customer pre-general availability Google Maps Platform features, services, and software that are not listed at  https://cloud.google.com/maps-platform/terms/maps-services/  or are identified as "Experimental", or "Preview" (collectively, "Pre-GA Offerings"). The terms of the Agreement that are applicable to Services apply to Customer’s use of Pre-GA Offerings. If there is a conflict between this Section 9 (Pre-GA Offerings) and the terms of the Agreement, then this Section 9 will control. The Agreement is amended as follows for Pre-GA Offerings:

(a) Unless otherwise agreed, Google will not charge any Fees for Pre-GA Offerings.

(b) There is limited technical support for the preview Offerings, and the SLAs under the Agreement do not apply to Pre-GA Offerings. Customer’s use of a Pre-GA Offering that is a new feature of an existing Service may impact the performance of that existing Service.

(c) Google may change, discontinue, or suspend Customer’s use of Pre-GA Offerings at any time without notice.

(d) Google may inform you in writing of additional terms and conditions for certain Pre-GA Offerings, which will be deemed a part of the Agreement.

(e) PRE-GA OFFERINGS ARE PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES OR REPRESENTATIONS OF ANY KIND.

(f) Google’s indemnification obligations under the Agreement do not apply to Pre-GA Offerings.

(g) With respect to Pre-GA Offerings, to the maximum extent permitted by applicable law, neither party nor Google’s suppliers will be liable for any amounts in excess of $25,000. The preceding sentence does not amend any (i) limitations on the types of recoverable damages or (ii) exemptions or exclusions from the limitations of liability under the Agreement.

(h) The Deprecation Policy under the terms of the Agreement does not apply to Pre-GA Offerings. 

(i) Customer may provide feedback and suggestions about the Pre-GA Offerings to Google, and Google and its Affiliates may use any feedback or suggestions provided without restriction and without obligation to Customer.

The gaming services consist of the Maps SDK for Unity, Semantic Tile API, and the Playable Locations API ("Gaming Services").

The following terms apply only to the Gaming Services:

10.1 Use Restrictions.

a) Customer can only use the Gaming Services for a Customer Application that is a consumer mobile game application built in Unity.

b) Customer must use content from the Playable Locations API on a map generated by the Maps SDK for Unity.

c) Customer can temporarily cache latitude (lat) and longitude (lng) values from the Playable Locations API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Playable Locations API Place ID (place_id) and Place Type values indefinitely.

10.2 Requirements .

a) Attribution. Customer must provide Google with attribution, in accordance with the requirements described at  https://developers.google.com/maps/documentation/gaming/attribution .

b) Impressions and Invalid Locations. Customer will (i) log impressions from use of the Gaming Services, and (ii) include functions in the Customer Application for End Users to report invalid, or inaccurate, locations within the Gaming Services.

c) Removed locations. At least once per day, Customer will query the Gaming Services to check for locations that have been removed. Customer will remove any locations identified by the Services as "inactive" from the Customer Application.

10.3 Service-Level Agreement.

Google will provide the Services to Customer in accordance with the SLA as described at  https://cloud.google.com/maps-platform/gaming/terms/sla/ .

11.1 Sharing Customer Information . By accessing or using Address Validation API, Customer agrees that Google may share Customer's information (name and address), subject to subsection (2) below. 

11.2 Artificially-Created Addresses .  Google uses services from the United States Postal Service to surface addresses in United States and Puerto Rico. If Customer uses the Address Validation API for addresses in United States and Puerto Rico, then Customer must not make requests with artificially-created addresses. If Customer inputs an artificially-created address, then subject to the Confidentiality section of Customer’s Agreement with Google, Google will :

(i) stop validating addresses for Customer using United States Postal Service services and

(ii) will report Customer’s information (name and address), relevant input address, and aggregated Address Validation API usage data to the United States Postal Service.

11.3 Caching . Customer can temporarily cache the applicable Google Maps Content from the Address Validation API for the applicable Caching Period for the applicable Permitted Purposes, as described in Table 11.3.1 (Caching Permissions). 

Table 11.3.1 (Caching Permissions) 

Downstream transactions means to use the cached Google Maps Content associated with a particular End User’s account to perform a downstream transaction for that End User or to avoid requiring that End User to enter the same information for their next transaction.. 

Correction Requests means to use the cached Google Maps Content associated with an End User’s account to request a correction on an address component (e.g., confirmationLevel, inferred, spellCorrected, replaced, or unexpected) received from the End User.

The following terms apply only to the Routes API:

12.1 Use without a Google Map . Customer may use Google Maps Content from the Routes API in Customer Applications without a corresponding Google Map.

12.2 Attribution Requirements . Customer must provide Google with attribution in accordance with the Documentation if Customer uses Google Maps Content from the Routes API without a corresponding Google Map.

12.3 No use with a non-Google map . Customer must not use Google Maps Content from the Routes API in conjunction with a non-Google map.

12.4 Caching . Customer can temporarily cache latitude (lat) and longitude (lng) values from the Routes API for up to 30 consecutive calendar days, after which Customer must delete the cached latitude and longitude values. Customer can cache Routes API Place ID (place_id) values, in accordance with the Routes API Policies .