Google introduced Google Maps Platform Terms of Service specifically for customers in the European Economic Area (EEA), effective July 8, 2025.

These changes primarily affect Google Cloud projects connected to a billing account with an EEA billing address. They do not apply simply because:

The determining factor is generally the billing address associated with the Google Maps Platform project used by the locator.

For affected EEA Google projects, Google has introduced new rules governing how information obtained from the Google Places API may be displayed with a map.

Google Places information can include:

Under the EEA terms, most of this Google-supplied content generally cannot be displayed on, next to, or visually associated with a map unless it is presented through an approved Google service such as Places UI Kit.

Latitude, longitude, and Google Place IDs may still be used with a map under the applicable terms.

RP Promap is primarily designed to display location information supplied and controlled by the merchant—not to create a permanent database by copying information from Google Maps.

Your Promap locations normally contain information that you enter or import, such as:

Because this is merchant-provided information, it can generally continue to appear in your store list, map markers, information windows, and location details.

RP Promap may use Google Maps Platform for supporting functions such as:

RP Promap separates these supporting map functions from the merchant’s location database wherever possible. The locator can therefore use coordinates to locate and sort stores while displaying the location information supplied directly by the merchant.

RP Promap should not be used to scrape, copy, or bulk-import Google Maps listings into a permanent location database.

Merchants should not copy Google-provided ratings, reviews, photographs, hours, or other Places content into Promap unless they independently own that information or have permission to use it.

You remain responsible for ensuring that the location content you upload to RP Promap is accurate and that you have the necessary rights to use it.

In most cases, you do not need to make any immediate changes. Rose Perl manages the technical map integration and reviews changes that may affect how Google services are used.

You should still make sure that all location information entered into Promap comes from your business, an authorized distributor, your dealers, or another source you are permitted to use.

Review the billing address associated with your Google Cloud billing account.

If the billing address is outside the EEA, these EEA-specific terms generally do not apply to that project.

If the billing address is within the EEA:

Google may allow certain integrations established before July 8, 2025 to continue in an “unmodified state.” Adding a new Google service, method, response field, platform, or feature may cause an integration to leave that state. Contact Google or your legal advisor if you rely on this status.

To help determine the correct configuration, Rose Perl Support may ask:

We do not need your Google password or payment-card information. Never send those details to Rose Perl Support.

Storefront visitors do not need to accept the Google Maps Platform EEA business terms or change their Google billing settings.

Visitors may be asked by their browser to allow location access if the locator’s Auto Detect Location feature is enabled.

If you are visiting a store locator:

The browser, device, network, and personal privacy settings determine whether location access is available. RP Promap cannot override a visitor’s browser permissions.

The locator should remain usable through manual search when location permission is denied.

When automatic location detection is enabled, the visitor’s browser controls the permission request. Visitors must be informed why their location is being requested and must be able to deny or revoke access.

Merchants should ensure that their privacy policy explains:

The website should also reference:

Most merchants using their own location information should see little or no change.

You should still be able to:

Features that display live Google Places information—such as Google reviews, ratings, photos, or Google-sourced business details—may require modification, removal, or implementation through Google Places UI Kit for affected EEA projects.

Not necessarily. Applicability is generally based on the billing address connected to the Google Maps Platform project, not the locations displayed on the map.

Not by itself. A visitor’s physical location does not normally determine which Google Maps Platform agreement governs the project.

Generally, yes. The key distinction is whether the information belongs to you or was obtained from Google Places.

RP Promap can use address autocomplete to help visitors search for nearby locations. For affected EEA integrations, the application should minimize the Google information it retains or displays and use coordinates or Place IDs wherever appropriate.

Do not assume that Google Maps or Places content can be copied merely because you manage the business listing. Enter information from your own business records or an independently authorized source. Contact Google or your legal advisor if you are uncertain about the rights attached to specific content.

Affected EEA projects may need to remove this information from the custom locator interface or display it through Google Places UI Kit. Contact Rose Perl Support before enabling this type of integration.

Yes, provided the visitor grants browser permission and the feature is configured appropriately. Visitors who decline can search manually.

Google states that these EEA terms did not themselves introduce pricing changes or EEA-specific SKUs. Normal Google Maps Platform usage charges still apply.

Contact Rose Perl Support and provide:

Do not send your Google password, billing card, secret API credentials, or other sensitive account information.

Rose Perl can help review the technical Promap configuration and identify features that may require adjustment. Questions about the legal interpretation of Google’s terms should be reviewed with Google or your legal advisor.

This article provides general product and technical information and is not legal advice. Google may update its terms and guidance. Refer to your Google Maps Platform agreement for the requirements applicable to your project.