Google Maps Configuration
How to configure Google Maps and properly map these configurations within the customer panel to ensure users are clearly informed about the use of this Third Party Provider (TPP). The tables below outline how embedding Google Maps on your website affects the privacy risks for users.
When embedding Google Maps onto your website, Google offers very limited configuration options.
You must make sure:
- That user consent is collected before Google Maps starts tracking (through blocking of the iframe and use of contextual consent)
- That you enter into a valid Joint Controller Agreement with Google.
Privacy relevant configurations (Parameters)
This table shows features which are enabled or disabled within Google Maps. Use this overview to ensure your Google Maps setup and Consenter Manager settings stay consistent.
Each row represents a feature that can be disabled or enabled in various ways when configuring your TPP for your website. The left-hand column describes the feature, while the right-hand column provides guidance on where to find it in the Consenter Manager and how to configure it to accurately reflect your TPP setup.
Some functions or data categories may be named differently between TPPs or in our overview due to the lack of standardization. As the data controller, you are responsible for informing users in a clear and comprehensible manner. This guide supports you by offering uniform, established terminology that helps users understand how their personal data is processed, thereby fostering trust in your brand.
| Parameters | ➡️ TPP Config High risk (consent) | ➡️ Consenter Manager Config What to indicate in Consenter Manager when embedding Google Maps on your website |
|---|---|---|
| Consent | Yes (ideally contextual consent) | Select Google Maps as data recipient. |
| Joint controller agreement | Yes, Google acts as Joint Controller regarding the processing of data for the data provision, but as independent controller for further data processing. | Select respective legal role of data recipient (Controller). |
| Tracking method | Cross session, cross domain, cross device (with User ID) | Select respective tracking method: Google may be able to track users with fingerprinting techniques and potentially also across devices, if they are logged into their account. |
| Identifier | IP address, device identifier, probabilistic identifiers, direct Identifiers | 1. Select respective data categories: The identifiers used by Google may vary depending on your users, e.g. whether they are logged into their Google account). You should therefore select all possible identifiers in Consenter Manager. |
| User ID features | Yes (if user is logged in to Google account) | 1. Select respective data categories: - Authentication-derived identifiers - Direct identifiers - User profile 2. Select personalization model Profile based personalization |
| Retention Period | 18 months | Indicate maximum storage duration |
| Processing location | USA (Adequacy Decision) | Indicate respective storage location Google is certified under EU-U.S. Data Privacy Framework (DPF). |
Data categories
This table details the categories of data collected by Google Maps. Use this overview to ensure your Google Maps setup and Consenter Manager settings stay consistent.
Each row represents a data category that can be disabled or enabled in various ways when configuring your TPP for your website. The left-hand column describes the data category, while the right-hand column provides guidance on where to find it in the Consenter Manager and how to configure it to accurately reflect your TPP setup.
Some functions or data categories may be named differently between TPPs or in our overview due to the lack of standardization. As the data controller, you are responsible for informing users in a clear and comprehensible manner. This guide supports you by offering uniform, established terminology that helps users understand how their personal data is processed, thereby fostering trust in your brand.
| Data categories | ➡️ TPP Config Low risk (no consent) | ➡️ Consenter Manager Config What to indicate in Consenter Manager when embedding Google Maps on your website |
|---|---|---|
| IP Address | Yes (plain) | Select respective data category |
| Technical data - Device characteristics - Browser/OS data etc. | Yes | Select data category: Device characteristics |
| Aggregated site statistics | Yes | Select data category: Aggregated site statistics |
| Geo-location info | Precise location data (if Browser-Localization is enabled on user device) | Select data category: - Precise location data - Non-precise location data |
| e-Commerce Activity | No | - |
| Device identifiers | Yes | Select respective data category |
| Probabilistic identifiers | Yes | Select respective data category |
| Authentication-derived identifiers | Yes (if user is signed into Google) | Select respective data category |
| Direct identifiers | Yes (if user is signed into Google) | Select respective data category |
| User provided data | No | - |
| Special categories of personal data | No | - |
| Privacy choices | Yes (With Google's consent mode) | Select respective data category |
| User's profiles | Yes | Select respective data category |
Last updated on