Open Street Maps (OSM) Configuration
How to embed Open Street Maps (OSM) on your website 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 OSM on your website affects the privacy risks for users.
When embedding Open Street Maps (OSM) onto your website, you do not have to collect user's consent, if the processing can be deemed strictly necessary for the provision of the website and may thus be based on Art. 5 (3) ePrivacy Directive.
You may still select OSM as data recipient in Consenter Manager in order to inform your users about the data processing or collect their consent nevertheless in order to stay on the safe side (legally). However, you only need to block OSM before obtaining informed consent from your users (e.g. through contextual consent in the iframe), if you think user consent is required in your specific case.
Privacy relevant configurations (Parameters)
This table shows features which are enabled or disabled within Open Street Maps (OSM). Use this overview to ensure your OSM 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 Low Risk (no consent) | ➡️ TPP Config Low Risk (Consent) | ➡️ Consenter Manager Config What to indicate in Consenter Manager when embedding OSM on your website |
|---|---|---|---|
| Consent | No | Yes (ideally contextual consent) | Select OSM as data recipient. |
| Joint controller agreement | No | No (Controllership) - OSM acts as independent controller | Select: Independent Controller as legal role of data recipient |
| Tracking method | No tracking | First party, single session | Select respective tracking method. |
| Identifier | - | Device identifiers | Select respective data category |
| Retention Period | Purpose fulfillment | Purpose fulfillment | Select respective retention period |
| Processing location | Self hosted (EU) | United Kingdom (Adequacy decision) | Indicate respective storage location |
Data categories
This table details the categories of data collected by Open Street Maps (OSM). Use this overview to ensure your OSM 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) | ➡️ TPP Config Low risk (Consent) | ➡️ Consenter Manager Config What to indicate in Consenter Manager when embedding OSM on your website |
|---|---|---|---|
| IP Address | Yes (plain) | Yes (plain) | Select respective data category. |
| Technical data - Device characteristics - Browser/OS data etc. | Yes | Yes | Select data category: Device characteristics. |
| Aggregated site statistics | No | Yes | Select data category: Aggregated site statistics |
| Geo-location info | Precise location data (if Browser-Localization is enabled on user device) | 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 | No | - |
| Device identifiers | No | Yes | Select respective data category. |
| Probabilistic identifiers | No | No | - |
| Authentication-derived identifiers | No | No | - |
| Direct identifiers | No | No | - |
| User provided data | No | No | - |
| Special categories of personal data | No | No | - |
| Privacy choices | No | No | - |
| User's profiles | Yes | No | - |
For technical integration guides (code implementation), see
Open Street Maps Integration Guide →
Last updated on