Overview
OpenStreetMap (OSM) is a collaborative, open-source mapping platform that provides free map data and tile rendering for website integration. When embedded on a website, OSM maps load tile images from OpenStreetMap's servers, displaying interactive maps without the tracking, cookie setting, or behavioral data collection associated with commercial map services like Google Maps.
What This Script Does
OpenStreetMap embeds operate with a minimal data footprint:
- Map tile loading: Fetches map tile images from
tile.openstreetmap.orgservers based on the map viewport (coordinates, zoom level). Tiles are standard image files rendered in a grid. - Leaflet or OpenLayers: Most OSM implementations use open-source mapping libraries (Leaflet, OpenLayers) loaded from the site's own domain or a CDN for map interactivity — panning, zooming, and marker display.
- Standard HTTP data: Tile requests include standard HTTP headers (IP address, user agent, referrer). OpenStreetMap's tile servers may log this data for operational purposes (abuse prevention, capacity planning).
- No cookies: OpenStreetMap does not set cookies on the website's domain or on its own domain via tile requests.
- No tracking: No behavioral tracking, no user identification, no analytics data collection. OSM serves tiles as static images.
- No JavaScript from OSM: The mapping library (Leaflet) is self-hosted; OSM contributes only the tile images.
Consent & Compliance
OpenStreetMap falls under the functional consent category. Map display serves a functional content purpose with minimal privacy impact.
Under GDPR and ePrivacy, OSM tile loading transmits the visitor's IP address to OpenStreetMap's servers (a third party). Under strict GDPR interpretation, this constitutes personal data processing by a third party. However, the OSM Foundation operates as a non-profit under the GDPR with legitimate interest in serving map data.
Under CCPA/CPRA, the minimal data processed (IP in HTTP logs) serves content delivery. OSM does not sell or share personal information.
Should You Block This Without Consent?
No. OpenStreetMap provides functional map display with no cookies, no tracking, and no behavioral data collection. It is the most privacy-friendly interactive map option available. Blocking it would remove map functionality without meaningful privacy benefit.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
openstreetmap.orgFunctionalFrequently Asked Questions
Do OpenStreetMap embeds need cookie consent?
No. OpenStreetMap does not set cookies, does not run tracking scripts, and does not collect behavioral data. Map tiles are served as static images. While tile requests transmit the visitor's IP address to OSM servers, the OSM Foundation operates as a non-profit and processes this minimally for content delivery only.
What data does an OpenStreetMap embed collect from visitors?
OpenStreetMap's data footprint is minimal. Tile requests include standard HTTP headers — IP address, user agent, and referrer — used for operational purposes like abuse prevention. No cookies are set, no JavaScript is loaded from OSM servers, and no behavioral tracking occurs. The mapping library like Leaflet is typically self-hosted.
How does ConsentStack handle OpenStreetMap tiles?
ConsentStack identifies OpenStreetMap through tile.openstreetmap.org requests and assigns it the functional category. Since OSM sets no cookies and performs no tracking, ConsentStack allows map tiles to load without requiring consent. This makes OSM the most privacy-friendly interactive map option available.
Related Vendors
Manage consent for OpenStreetMap
ConsentStack automatically detects and manages OpenStreetMap trackers so your site stays compliant with global privacy regulations.