Home Google Maps Platform Google Maps Platform Service Specific Terms Stay organized with collections Save and categorize content based on your preferences. Last modified: October 15, 2018 | Previous Versions 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. ## 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. Previous Versions: - July 19, 2018 - May 1, 2018 Enable Google Maps Platform 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 Maps Features included: - Maps - Streetview APIs included: - Maps JavaScript API - Maps Static API - Street View API - Maps SDK for Android - Maps SDK for iOS Build customized map experiences that bring the real world to your users. Routes Features included: - Directions - Distance Matrix - Roads APIs included: - Directions API - Distance Matrix API - Roads API - Maps JavaScript API Give your users the best way to get from A to Z. Places Features included: - Place Details - Current Place - Find Place - Geocoding - Geolocation - Time Zone APIs included: - Places Library, Maps JavaScript API - Places API - Geocoding API - Geolocation API - Time Zone API - Elevation API Help users discover the world with rich details. Cancel Continue Continue Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates. [[["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"]],[],[],[]]