April 4, 2022

Home

Stay organized with collections

Save and categorize content based on your preferences.

Google is committed to
advancing racial equity for Black communities.
See how.

# Google Maps Platform
Service Specific Terms

Last modified: April 4, 2022

This is not the current version of this document and is provided
for archival purposes.
View the current version

Capitalized terms not defined in these Service Specific
Terms have the meaning established in the Agreement. For
the purpose of these Service Specific Terms, if the
order is placed by a Reseller, then the term "Customer"
as used below means Customer and/or Reseller based on
which entity is accessing the applicable Service.

These Service Specific Terms are incorporated into the
agreement under which Google has agreed to provide
Google Maps Platform Service (as described
at https://cloud.google.com/maps-platform/terms/maps-service-terms/)
to Customer (the "Agreement").

1. Directions API

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.

2. Distance Matrix API

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.

3. Geocoding API

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.

4. Geolocation API

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.

5. Places API

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.

6. Roads API

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.

7. Street View Static API

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. Verification of Customer-Reported Subscriptions

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. Pre-GA Offerings

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.

10. Gaming Services

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/.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],[],[],[]]