April 22, 2024

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 22, 2024

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. Address Validation API

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

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

10.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 10.3.1 (Caching
Permissions).

Table 10.3.1 (Caching Permissions)

**Google Maps Content**

**Caching Period**

**Permitted Purposes**

   - formattedAddress

   - postalAddress

   - addressComponent: componentName

   - USPS Data standardizedAddress

30 consecutive calendar days, after which
Customer must (1) delete the cached Google Maps
Content or (2) replace with End User data provided
through End User confirmation or correction

Downstream transactions

   - addressComponent: confirmationLevel, inferred,
spellCorrected, replaced, unexpected

30 consecutive calendar days, after which
Customer must (1) delete the cached Google Maps
Content or (2) replace with End User data provided
through End User confirmation or correction

Correction Requests

   - Location: latitude values, longitude values

30 consecutive calendar days, after which
Customer must delete the cached Google Maps
Content

Any

   - placeId

Indefinitely

In accordance with the

Address Validation API Policies

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

11. Routes API

The following terms apply only to the Routes API:

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

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

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

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

12. Maps Datasets API (Pre-GA Offering)

The following term applies only to the Maps Datasets API:

*12.1 No Personal Data***. **Customer will not
provide to Google any Personal Data via the Maps Datasets
API.

13. Aerial View API

The following term applies to the Aerial View API:

13.1 *Caching. *Customer may cache Aerial View API
Video IDs, in accordance with

Aerial View API Policies.

14. Solar API

The following terms apply only to the Solar API:

*14.1 Acceptable Use****. ***Customer can
use the Solar API only (a) to determine the feasibility of
installing energy systems for a particular address or
geographic area, (b) to design or install an energy
system, or (c) for a Downstream Transaction. A “Downstream
Transaction” means (i) the design of an energy system
requested by a user for a particular address, (ii) the
preparation and delivery of a commercial proposal for an
energy system that is requested by a user for a particular
address, or (iii) the preparation and delivery of
marketing materials for an energy system where a user has
opted-in to receiving such materials.

*14.2 Attribution Requirements. *If Customer uses
data or displays imagery from the Solar API, Customer must
include this attribution “Source: Includes solar data from
Google” on or next to the data or imagery used, or with
attribution to other third parties.

14.3 *Caching*. Customer can temporarily cache the
“Building Insights” and “Data Layers” from the Solar API
(“Solar Data”) for up to 30 consecutive calendar days,
after which Customer must delete the cached Solar Data.
The deletion obligation does not apply to Solar Data
incorporated into fixed media (e.g. energy system design,
feasibility study, commercial proposal, marketing
materials) for use in a Downstream Transaction.

15. Air Quality API

The following terms apply only to the Air Quality API:

15.1 *Acceptable Use*: Customer can use the data
retrieved from Air Quality API in (a) air quality based
routing solutions developed by Customer and (b) Customer
environmental risk indices and correlational research.

15.2 *Attribution Requirements*: If Customer uses
data or displays imagery from the Air Quality API,
Customer must include this attribution “Source: Includes
air quality data from Google” on or next to the data or
imagery used, or with attribution to other third parties.

15.3 *Caching*. Customer can temporarily cache the
applicable Google Maps Content from the Air Quality API
for the applicable Caching Period, as described in Table
15.3.1 (Caching Permissions).

Table 15.3.1 (Caching Permissions)

**Google Maps Content**
**Caching Period**

   - Current conditions values

One hour, after which Customer must delete the
cached Google Maps Content.

   - Historic values for a specific location and
given time range

Until the Agreement is terminated.

   - Hourly forecast values

One hour, after which Customer must delete the
cached Google Maps Content.

16. Pollen API

The following terms apply only to the Pollen API:

16.1 *Acceptable Use. *Customer can use the data
retrieved from Pollen API in (a) pollen based routing
solutions developed by Customer and (b) Customer
environmental risk indices, insights, and
forecasts*.*

16.2 *Attribution Requirements. *If Customer uses
data or displays imagery from the Pollen API, Customer
must include this attribution “Source: Includes pollen
data from Google” on or next to the data or imagery used,
or with attribution to other third parties.

16.3 *Caching. *Customer can temporarily cache the
applicable Google Maps Content from the Pollen API for the
applicable Caching Period, as described in Table 16.3.1
(Caching Permissions).

Table 16.3.1 (Caching Permissions)

**Google Maps Content**

**Caching Period**

   - Today's Forecast values

365 consecutive calendar days , after which
Customer must delete the cached Google Maps
Content

   - Forecasts values

24 hours, after which Customer must delete the
cached Google Maps Content

   - Heatmap values

24 hours, after which Customer must delete the
cached Google Maps Content

[[["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"]],[],[],[]]