Last modified: July 19, 2018 | Previous Versions
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.
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 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
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.
2.4 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
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 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
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 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
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 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
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 Temporary caching. Customer may cache limited amounts of Google Maps Content if cache: (a) is only for the purpose of improving Customer Application performance due to network latency, or intermittent connectivity; (b) is secure; (c) is stored for less than 30 consecutive calendar days; (d) is not redistributed; (e) does not prevent Google from accurately calculating Customer's Service usage levels; (f) does not modify attribution in any way; and (g) does not manipulate or aggregate any part of the Google Maps Content or Services.
7. Verification of Customer-Reported Subscriptions
7.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.
8. Commitment Based Pricing and Billing
8.1 Committed Units.
8.1.1 Selection and Commitment. If applicable, Customer may have an option to request Committed Units by making a selection in (i) the Admin Console, or (ii) the Order Form. If Google accepts Customer’s Committed Unit request, then the following provisions will supersede any conflicting "Payment Terms" in the Agreement:
(a) Customer may purchase Committed Units purchases may be made for a Committed Unit Term.
(b) Customer will pay the Fees for those Committed Units whether or not they are used.
(c) Committed Units may include advance Fee payments (if specified in the Price list). Unless otherwise stated in the Price list, any use of the Services beyond the Committed Units selected will be billed at standard Fee rates.
8.1.2 Renewal. Unless otherwise stated in the Admin Console or Order Form, after each Committed Unit Term (if any) ends, Customer’s Committed Unit selection will automatically renew for the same Committed Unit Term at the same quantity throughout the Term until Customer selects in the Admin Console to stop renewing or cancel the renewal (if applicable) or either party notifies the other party to cancel the renewal. A renewal cancellation will take effect after the then-current Committed Unit Term ends.
8.1.3 Cancellation and Expiration. Unless Google agrees otherwise, Committed Unit purchases may not be cancelled or refunded after they are placed but if Google terminates the Agreement (other than for Customer’s material breach) or discontinues providing the Services applicable to the Committed Units, Google will refund Customer any unused prepaid Fees following that termination applicable to those previously purchased Committed Units. If Google allows Customer to cancel a Committed Unit purchase, Google may require Customer to pay a cancellation Fee (as specified in the Price list). Any use of the Services after cancellation or expiration of the Committed Units will be billed at standard Fee rates.
8.1.4 No Resell or Transfer. Unless Google agrees otherwise, Customer may not resell or transfer Committed Units.
9. Definitions
"Committed Purchase(s)" means Customer’s commitment to spend a specified amount for use of the Services over a specified period of time, whether Customer uses those Services or not. A Committed Purchase may be made using the Admin Console or the Order Form (if applicable).
"Committed Units" means a specified quantity of the Services.
"Committed Unit Term" means the period of time (if applicable) within the Term during which Customer may use the Committed Units purchased. The Committed Unit Term (if applicable) will be specified in the Price list.
"Package Purchase" means Customer’s commitment to purchase a specified package of the Services over a specified period of time, whether Customer uses those Services or not. A Package Purchase may be made using the Admin Console or the Order Form (if applicable).
Previous Versions:
To enable APIs or set up billing, we'll guide you through a few tasks:
- Pick product(s) below
- Select a project
- Set up your billing