Viewing: developers.google.com

[eea-logo.png] Google Maps Platform EEA integration guides

Effective 8 July 2025, new EEA-specific Google Maps Platform Terms of Service (EEA terms) will impact how you build applications and experiences for users if your project is linked to an EEA billing account.

We strongly recommend that you read and understand the announcement, as the details potentially impact your existing and new applications that integrate Google Maps Platform.

This document describes usage and Google Maps Platform functionality changes for the Places API and related services.

The information described in this document reflects the EEA terms governing your use of Google Maps Platform Services as of 8 July 2025, which may change over time. For the most recent and binding terms applicable to you, please see your Google Maps Platform Agreement with Google.

Affected services

All Places API (New and Legacy) methods are affected. The affected services in the Places API (New and Legacy) include the following capabilities: Place Details, Text Search, Nearby Search, Autocomplete, Place Autocomplete, Query Autocomplete, Find Place, Current Place, and Place Photos.

The Places API (New and Legacy) also includes Places API service availability through the Places Javascript API (New and Legacy), the Places SDK for Android (New and Legacy), and the Places SDK for iOS (New and Legacy).

These changes do not apply to the Places UI Kit.

Places API adjustments for EEA customers

These adjustments apply to (a) projects created after 8 July 2025 that are linked to an account with an EEA billing address, and/or to (b) projects that are no longer in the Unmodified State after 8 July 2025.

The following table summarizes the adjustments, delineated in the EEA Service Specific Terms, for each Google Maps Platform service.

Places API Functionality Adjustments	Terms of Service Changes
None	No Use With any Map. Other than latitude, longitude, and place_id, Customer must not use Google Maps Content from the Places API With any Map. Permitted Use. Other than latitude, longitude, and place_id, Customer may only use the Google Maps Content from the Places API as permitted by the Places API EEA Permitted Uses. *For clarity, the restrictions above—No Use With any Map and Permitted Use—do not apply to the Places UI Kit.*

Places API Functionality Adjustments

None

No Use With any Map. Other than latitude, longitude, and place_id, Customer must not use Google Maps Content from the Places API With any Map.

Permitted Use. Other than latitude, longitude, and place_id, Customer may only use the Google Maps Content from the Places API as permitted by the Places API EEA Permitted Uses.

***For clarity, the restrictions above—No Use With any Map and Permitted Use—do not apply to the Places UI Kit.***

Examples of "With any Map" and "without a map"

The EEA terms changes affect how you use Google Maps Content from this service "With any Map." "With any Map" means to display Google Maps Content on, next to, or in a manner that is visually associated with any map, including a Google map, or to link Google Maps Content to any map or link any map to Google Maps Content (unless the specific map being linked to is the source of the applicable Google Maps Content).

For clarity, you may continue to link to the Google Maps Content source links provided by the Service (for example, googleMapsLinks in the Places API).

The following examples are illustrations of what "With any Map" and "without a map" can look like, to help you comply with the terms of your Agreement. The examples are not comprehensive. Ultimately, you are responsible for complying with the terms of your Agreement.

[Blue dot that is used in subsequent examples]

The blue circles in the following examples represent Google Maps Content
from Google Maps Platform Services.

On a map	Next to a map	Visually associated with a map
[A map with a blue dot]	[A map with blue dots next to it]	[A map with a list blue dots separated by text, with a map with blue dots on the other side of the text.]

Linked to a map	Without a map
[A map with a blue dot that links to a map in a new window.]	[A list of blue dots with no map being displayed.]

Alternative integrations

The following integration guidelines and examples are provided to help you visually implement the Places API as it relates to the requirement for no use of Google Maps Content With any Map. As a reminder, your use of Google Maps Content from the Places API must also comply with the Places API EEA Permitted Uses.

You may still use latitude, longitude, and Place ID from the Places API With any Map. This includes linking using only the latitude, longitude, or Place ID to a map as long as other Google Maps Content is not used With any Map.

[with-map-link-to-map.png] [with-map-lat-long.png]

An example of linking to a map using latitude,
longitude, or Place ID, which is still permitted An example of latitude and longitude
on a map, which is still permitted

You may continue to use the Places API Service in permitted situations where the Google Maps Content is not used With any Map.

[without-map.png]

An example of using
Places API Content without a map.

You may use the Places API in combination with Places UI Kit where appropriate for your application.

[with-map-link-to-uikit.png]

An example of linking to a map using Place ID
where Places UI Kit is shown next to the Map

In most other situations, Places UI Kit is available for use With any Map.

Places UI Kit

Google Maps Platform includes Places UI Kit, which lets you build integrations to help your users visualize Places content with any map, or without any map. The Places API Permitted Uses restrictions don't apply to the Places UI Kit.

For example, Places UI Kit lets you display Place Details on a map or render a List of Places from a search next to a map, as illustrated in the following image.

[A list of places next to a map. One marker is selected, and its details are shown on the map.] Note: Places UI Kit elements for Place Details, Place Autocomplete, and Place Search will be generally available in mid-July 2025.

Use the following resources to help you build with Places UI Kit:

Integration guides

Places UI Kit product documentation

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 in order to, for example, limit the risks of mismatched roads.

Note: Use of 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.

What if I have additional questions not covered in this document?

If you have any technical questions not addressed in this document or the General FAQ, you can contact Google Maps Platform 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, reach out using our Contact Sales form.

[with-map-link-to-map.png]	[with-map-lat-long.png]
An example of linking to a map using latitude, longitude, or Place ID, which is still permitted	An example of latitude and longitude on a map, which is still permitted

[without-map.png]
An example of using Places API Content without a map.

[with-map-link-to-uikit.png]
An example of linking to a map using Place ID where Places UI Kit is shown next to the Map

Places API adjustments for European Economic Area (EEA) customers Stay organized with collections Save and categorize content based on your preferences.