**EEA countries, territories, \& regions** Åland Islands, Austria, Azores, Belgium, Bulgaria, Canary Islands, Ceuta \& Melilla, Croatia, Republic of Cyprus, Czechia, Denmark, Estonia, Finland, France, French Guiana, Germany, Greece, Guadeloupe, Hungary, Iceland, Ireland, Italy, Jan Mayen, Latvia, Liechtenstein, Lithuania, Luxembourg, Madeira, Malta, Martinique, Mayotte, Netherlands, Norway, Poland, Portugal, Réunion, Romania, Saint-Martin, Slovakia, Slovenia, Spain, Sweden
> [!NOTE] > **Note:** This page is a point-in-time reference and may contain outdated information. For the most current EEA terms, please consult: > > - [EEA Terms of Service](https://cloud.google.com/terms/maps-platform/eea) > - [EEA Service Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms) As a result of a recent proceeding by Germany's Bundeskartellamt (Federal Cartel Office, or FCO), we're creating Google Maps Platform terms of service specifically for customers in the European Economic Area (EEA) countries and territories. We are updating our terms of service to reflect the result of this proceeding, and we are modifying some Google Maps Platform Services to uphold our standards for Google Maps Content. Because of these changes, you should read and understand everything in this communication. ## Summary Effective **8 July 2025** , the new **EEA-specific Google Maps Platform Terms of Service (EEA ToS)** will impact how you build apps and experiences for users if your project is linked to an EEA billing account. These changes affect how Google Maps Services will function for **new** project integrations, including: - If you want to show Places-related content with a map, you should now use the new Places UI Kit, which works with any map (including third-party maps). The Google Maps Content from the Places API (New and Legacy) may no longer be displayed with any map, including a Google Map. - Certain content from some Google Maps Platform Services will no longer be returned due to our standards for Google Maps Content. - EEA customers may now, where suitable, use Google Maps Platform Services in embedded vehicle systems. They may also use Google Maps Platform Services, where suitable, for real-time navigation with a third-party map, as long as that real-time navigation usage complies with Google's safety requirements. More comprehensive details on these services and terms changes are available in this document and related service-specific integration guides. This document addresses common questions regarding the following: - [Affected customers](https://developers.google.com/maps/comms/eea/faq.md.txt#affected-customers) - [EEA-specific Google Maps Platform Terms of Service](https://cloud.google.com/terms/maps-platform/eea) - [EEA-specific Google Maps Platform Services and Service Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms) - [Your current integration of Google Maps Platform prior to 8 July 2025](https://developers.google.com/maps/comms/eea/faq.md.txt#current-integration) - [Other questions](https://developers.google.com/maps/comms/eea/faq.md.txt#other-questions) If this document has been updated, it will be reflected in the change log at the bottom of this page. ## Affected Customers ### Who is affected by these changes? All projects linked to billing accounts with an address in the EEA ("EEA customers") are affected by these changes starting **8 July 2025**. | Before 8 July 2025 | On or after 8 July 2025 | |---|---| | If your project was created before **8 July 2025** : You can continue your current use of Google Maps Platform Services, as long as you do not [materially modify your integration](https://developers.google.com/maps/comms/eea/faq.md.txt#material-modification) on or after **8 July 2025**. | If your project is created on or after **8 July 2025** , or if you [materially modify your existing integration](https://developers.google.com/maps/comms/eea/faq.md.txt#material-modification) on or after **8 July 2025** , your project will be subject to the EEA-specific [Google Maps Platform ToS](https://cloud.google.com/terms/maps-platform/eea), which incorporates the EEA-Specific [Google Maps Platform Service Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms) and [services modifications](https://developers.google.com/maps/comms/eea/faq.md.txt#sst-updates). | ## EEA-specific Google Maps Platform Terms of Service ### What updates are we making to our Terms of Service? We are introducing an [**EEA ToS**](https://cloud.google.com/terms/maps-platform/eea). This version removes three provisions from the "Restrictions Against Misusing the Services" section of your Agreement: 1. No Re-Creating Google Products or Features 2. No Use with Non-Google Maps 3. No Use in Embedded Vehicle Systems We will remove clauses with the same meaning or effect as the above listed clauses in all other applicable contractual terms that govern your use of Google Maps Platform, including the Google Maps Platform Service Specific Terms. The EEA ToS will also include: - (1) Improved organization through clause rearrangement. - (2) Clarified restrictions on using Google Maps Content for AI/ML by adding a new example. - (3) Added requirements for customers to ensure: (a) authorized third parties uphold the Agreement and (b) responsibility for data misalignment and distinguishing Google content from non-Google content. If you have a negotiated agreement with Google, refer to the question, [How do these updates impact me if I have a negotiated agreement with Google?](https://developers.google.com/maps/comms/eea/faq#negotiated-agreement) ## EEA-specific Google Maps Platform Services and Service Specific Terms ### Will there be any updates to Services and Service Specific Terms? We are modifying some Google Maps Platform Services and Service Specific Terms. These include modified responses for some APIs, changes to permitted uses for certain Services, and the introduction of safety requirements for when our Services are used for real-time navigation or in applications intended for real-time driving. We are removing clauses with the same meaning or effect as the [above listed provisions](https://developers.google.com/maps/comms/eea/faq#tos-updates) from the [EEA-specific Google Maps Platform Service Specific Terms](https://cloud.google.com/terms/maps-platform/eea/maps-service-terms). The Google Maps Platform Services listed below will have new service-specific terms or technical changes. You can refer to the service specific integration guides linked below for additional information. | Services with Technical Changes | Services with New Terms Restrictions | |---|---| | *These APIs behave differently in the EEA region* **Maps** - [Maps Static API](https://developers.google.com/maps/comms/eea/maps-static.md.txt) - [Map Tiles API](https://developers.google.com/maps/comms/eea/map-tiles.md.txt) **Environment** - [Solar API](https://developers.google.com/maps/comms/eea/solar.md.txt) **Mobility** *Technical changes will propagate to your project within 1-3 days after you accept the EEA Terms*. | **Maps** - [Street View Static API](https://developers.google.com/maps/comms/eea/street-view-static.md.txt) **Routes** - [Directions API (Legacy)](https://developers.google.com/maps/comms/eea/directions.md.txt) - [Distance Matrix API (Legacy)](https://developers.google.com/maps/comms/eea/distance-matrix.md.txt) - [Roads API](https://developers.google.com/maps/comms/eea/roads.md.txt) - [Routes API](https://developers.google.com/maps/comms/eea/routes.md.txt) - [Routes Preferred API](https://developers.google.com/maps/comms/eea/routes-preferred.md.txt) **Places** - [Address Validation API](https://developers.google.com/maps/comms/eea/address-validation.md.txt) - [Geocoding API](https://developers.google.com/maps/comms/eea/geocoding.md.txt) - [iOS Geocoder within Maps iOS SDK](https://developers.google.com/maps/comms/eea/ios-geocoder.md.txt) - [Places API (New and Legacy)](https://developers.google.com/maps/comms/eea/places.md.txt) **Mobility** | At this time, only the Services listed above are changing. You will be able to continue using them as is, for unmodified integrations, without the [three ToS provisions](https://developers.google.com/maps/comms/eea/faq#tos-updates). ### Why is Google Maps Platform making these Services and terms changes? #### Standards for Google Maps Content Due to our standards for Google Maps Content, we are making adjustments to some of the Google Maps Platform Services for **new** integrations within your Customer Applications. For example, if the EEA ToS applies to your integration, and you want to display the Places-related content with a map, you should now use the Places UI Kit to display the content instead of Places API (New and Legacy). #### Road safety EEA customers may now use Google Maps Platform Services, where suitable, in embedded vehicle systems. They may also use Google Maps Platform Services, where suitable, for real-time navigation with a third-party map, as long as that real-time navigation usage complies with Google's safety requirements. Due to road safety risks that can arise under these new terms, Google now requires that developers adhere to [safety requirements](https://cloud.google.com/terms/maps-platform/eea-safety-requirements), in order to, for example, limit the risks of mismatched roads. Please note: use of the Google Maps Platform Services in embedded vehicle systems in the EEA occurs at each customer's own discretion and the customer is responsible for compliance with any applicable laws, regulations, industry standards, or other requirements. ### Are any new Services being introduced at this time? We will continue to launch new services. At this time, we are bringing to General Availability the Places UI Kit (Javascript, Android, iOS) to provide map-related visualization use cases for continued support for our developers. This Service can be used with any map, including third-party maps. Refer to the [Places API (New and Legacy) service-specific integration guide](https://developers.google.com/maps/comms/eea/places#uikit) for more information. ## Your current integration of Google Maps Platform prior to 8 July 2025 ### How will these changes impact my current integration of Google Maps Platform Services? To help you with these changes, you may continue using Google Maps Platform in your Customer Application(s) for your current project's Google Maps Platform integrations, with the three ToS provisions waived. Your existing integration is considered in an "unmodified state" as long as it is not materially modified on or after **8 July 2025**. After **8 July 2025**, projects which are created with a billing account in the EEA or moved from a non-EEA billing account to an EEA billing account are not eligible for the unmodified state. You are free to modify your integration and transition your integration out of the unmodified state at any time. If you do so on or after **8 July 2025** , an individual with the full legal authority must accept the [EEA ToS](https://cloud.google.com/terms/maps-platform/eea) in the Console for the project, to continue using our Services. Project Owners and Project Editors have the permissions necessary to accept the EEA ToS. You can update the permissions for individuals on your account in the Console. If you have a negotiated agreement with Google, refer to the question, [How do these updates impact me if I have a negotiated agreement with Google?](https://developers.google.com/maps/comms/eea/faq#negotiated-agreement) ### How do I accept the EEA ToS? As a Project Owner or Project Editor, you can accept the EEA ToS in the following ways: - Accept the EEA ToS on the [Google Maps Platform Support page](https://console.cloud.google.com/google/maps-apis/support) of the Console. - When you perform actions in the Console that will require you to accept the EEA ToS, such as enabling a new Generally Available Google Maps Platform Service or migrating project ownership from a non-EEA billing account to an EEA billing account, the Console will prompt you to accept the EEA ToS. ### Which Terms of Service govern my integration during the unmodified state? As long as your [integration](https://developers.google.com/maps/comms/eea/faq.md.txt#integration) remains in the unmodified state, these [Google Maps Platform Terms of Service](https://cloud.google.com/maps-platform/terms) will continue to apply, with Google waiving the following 3 provisions: - No Re-Creating Google Products or Features - No Use With Non-Google Maps - No Use in Embedded Vehicle Systems Google will also waive clauses with the same meaning or effect as the above listed clauses in all other applicable contractual terms that govern your use of Google Maps Platform, including the Google Maps Platform Service Specific Terms. If you have a negotiated agreement with Google, that agreement will govern your use of Google Maps Platform Services while your integration is in the unmodified state, with Google waiving the three clauses mentioned above and clauses with the same meaning or effect. ### What does an integration in a Customer Application mean? Integration means the use of Google Maps Platform Services within a Customer Application, via a **dedicated project**, to fulfill a distinct end-user purpose or workflow. Each distinct purpose or workflow so fulfilled is a separate integration. For example, if a Customer Application has a store locator that allows users to search for a store near them, and in a separate workflow offers an online store checkout; the store locator integration and the online checkout integration are considered separate integrations within the Customer Application. Google will treat all integrations associated with a project as being in the same state. As a best practice, we recommend that developers use one project per integration. ### How do I transition my integration out of the unmodified state? If you make a material modification to your integration, your integration will transition out of the unmodified state, and you'll need to accept the EEA ToS, as described in [How will these changes impact my current integration of Google Maps Platform Services?](https://developers.google.com/maps/comms/eea/faq.md.txt#affect-current-integration) A material modification occurs when an EEA Customer: (i) uses new functionality of a new or existing General Availability Google Maps Platform Service within an existing integration, or (ii) makes changes to how third party services are used with Google Maps Platform Services within the integration. Google may make updates to this definition and the examples from time to time, and changes to the definition will apply only going forward to subsequent changes that are made. Please refer to the bottom of this page for the change log. #### Examples of material modifications *If you*: - Maintain an existing integration, but update to newer versions of the Services in order to access new functionality. - Maintain the same integration, but enable an additional General Availability Service in the integration. - Maintain the same integration, but query new methods in the Service, or start using new response fields from the Service. - Maintain the same integration, but expand to other platforms (for example, Android). - Have an integration with no map, and start using a Google or third-party map, or replace an existing map. If the addition of functionality to your integration (for example, new platform, new features) is implemented with a new project, that new project will be governed by the EEA ToS and the existing project remains in the "unmodified state." #### Examples that are not material modifications (can stay in "unmodified state") *If you maintain the same integration and*: - Update to a newer version of the Services for security, compatibility, accessibility, or other issue/bug resolution reasons; as long as no new functionality is used. - Make administrative or security updates (for example, setting API quotas, restricting an API key, replacing a restricted API key, or configuring budget alerts). - Change your billing model. - Change visual details of the user interface (for example, color and font). - Move a project to a new billing account. - Expand geographic coverage of the integration without using new functionality. ## Other questions ### Are pricing changes part of these updates? No, pricing is not changing as part of this update. ### Will there be EEA-specific SKUs? No, SKUs will remain the same. ### How do these updates impact me if I have a negotiated agreement with Google? If you have a negotiated agreement with Google, and you materially modify your project's Google Maps Platform integration in your Customer Application, you must adhere to the EEA-specific Google Maps Platform Service Specific Terms, which, starting **8 July 2025**, will be incorporated into your negotiated agreement with Google. ### Why did I receive a notice? You received a notice because you are a project owner, billing administrator, or essential contact associated with a project(s) linked to a billing account with an EEA address. Refer to [Who is affected by these changes?](https://developers.google.com/maps/comms/eea/faq.md.txt#who-is-affected) question for more information on who is affected by these changes. ### I received multiple notices, which one is applicable? You may have received multiple notices if you are associated with multiple billing accounts, where at least one of these accounts has a negotiated agreement with Google. Refer to the notice you received for additional information. If you have additional questions you may [contact us](https://developers.google.com/maps/comms/eea/faq.md.txt#additional-questions). ### How do these updates impact me if I am a Maps Partner? For more information about how these changes might affect you, contact your Partner Development Manager. ### What do I need to do to prepare for these changes? We encourage you to familiarize yourself with all the content in this document and the [service-specific integration guides](https://developers.google.com/maps/comms/eea/faq.md.txt#sst-updates) to ensure new integrations and material modifications to existing integrations comply with the Services and term changes. - Review the list of APIs you are using on your project (with [Usage Reports](https://developers.google.com/maps/reporting-and-monitoring/reporting#usage-rpt) or billing account with [Billing Reports](https://developers.google.com/maps/reporting-and-monitoring/reporting.md.txt#billing-rpt))). - For each of the APIs you are using, check if there are [technical or contractual changes](https://developers.google.com/maps/comms/eea/faq#sst-updates). ### What if I have additional questions not covered in this FAQ? If you have any technical questions not addressed in this or the [service-specific integration guides](https://developers.google.com/maps/comms/eea/faq.md.txt#sst-updates), you can contact [Google Maps Platform Support](https://developers.google.com/maps/support.md.txt?utm_medium=DevSite&utm_content=GMP_Support). If you have a negotiated agreement with Google and have questions about your contract, you can contact your Google Maps Platform representative. If you are unsure who your account representative is, please reach out using our [Contact Sales form](https://mapsplatform.google.com/contact-us/?utm_medium=DevSite&utm_content=Contact_Sales).