Overview
HERE Global B.V. is a leading location intelligence company providing mapping data, geocoding, routing, traffic, and location analytics services. Headquartered in the Netherlands and majority-owned by a consortium of automotive manufacturers (BMW, Mercedes-Benz, Audi), HERE powers navigation in vehicles, logistics platforms, and developer applications. The HERE Maps JavaScript API allows website developers to embed interactive maps, store locators, route planners, fleet tracking displays, and geospatial visualizations as alternatives to Google Maps or Mapbox.
What This Script Does
The HERE Maps JavaScript API loads from js.api.here.com and tile CDN domains (maps.ls.hereapi.com, 1.maps.ls.hereapi.com through 4.maps.ls.hereapi.com). API initialization requires an API key embedded in the script call, which authenticates the developer's account for usage billing.
Cookies Set by HERE Maps:
- HERE Maps does not set persistent tracking cookies in standard deployments. The API is primarily a rendering and data API rather than a user-tracking service.
hereMapsAPI_[version]— session-local storage entry (not a cookie) caching tile metadata for performance; cleared when the browser tab closes- If HERE's Traffic or Weather overlays are enabled, additional tile requests include the current viewport bounding box but no user identifier
Network Requests Made by HERE Maps Scripts:
- Map tile requests to
[1-4].maps.ls.hereapi.com/maptile/2.1/maptile/newest/normal.day/[zoom]/[x]/[y]/256/png8?apiKey=[key]— includes the map viewport coordinates (tile x/y/zoom) and the developer's API key; no user identifier is included - Geocoding requests to
geocoder.ls.hereapi.com/6.2/geocode.json?searchtext=[query]&apiKey=[key]— the user's typed location search query is transmitted to HERE's servers for address resolution - Reverse geocoding to
reverse.geocoder.ls.hereapi.com— the user's clicked map coordinates are transmitted to resolve to a street address - Routing requests to
route.ls.hereapi.com/routing/7.2/calculateroute.json— origin and destination coordinates are transmitted; route is computed server-side - Traffic tile requests to
traffic.maps.ls.hereapi.com— real-time traffic data overlay; no user data transmitted beyond viewport coordinates - HERE Platform API calls log usage (request count, API key, endpoint) for billing purposes; logs are retained per HERE's data retention policy
Data Collected by HERE's Servers (Server-Side Logs):
- Requesting IP address (for API authentication and abuse prevention)
- Timestamps of tile/geocoding/routing requests
- Developer API key (identifies the site/application making the request)
- Map viewport coordinates (tile coordinates, zoom level)
- Location search queries typed by the user (for geocoding requests)
- Origin and destination coordinates (for routing requests)
HERE Global B.V. is headquartered in Eindhoven, Netherlands (EU). As an EU-headquartered company, HERE processes data under GDPR directly. HERE's privacy policy covers location query data; users' typed search queries are subject to HERE's data minimization practices and are not retained indefinitely for profiling purposes per HERE's privacy documentation.
Consent & Compliance
HERE Maps is categorized as functional technology. Under GDPR and the ePrivacy Directive, map rendering, geocoding, and routing are services explicitly requested by the user (e.g., searching for a store location or calculating directions). No persistent user-tracking cookies are set. The transmission of location queries and viewport coordinates to HERE's servers is necessary for the map functionality to work. HERE, as an EU-based processor, processes this data under its own GDPR-compliant terms. The developer's API key is an authentication credential, not a user identifier. Site operators should disclose HERE as a third-party data processor in their privacy policy, particularly if geocoding queries could reveal sensitive location information (e.g., users searching for medical facilities).
Should You Block This Without Consent?
No. HERE Maps provides functional map rendering, geocoding, and routing services. It does not set persistent tracking cookies or collect behavioral data for advertising. When used for user-requested features such as store locators, delivery tracking, or directions, it qualifies as a functional service exempt from consent requirements under the ePrivacy Directive.
Consent Categories
Also Known As
Industries
Tracked Domains (1)
here.comEssentialFrequently Asked Questions
Does HERE Maps require consent to load?
No. HERE Maps is classified as functional. It does not set persistent tracking cookies and processes location queries only to return map tiles, geocoded addresses, or routing results explicitly requested by the user. These are strictly necessary operations that qualify for the ePrivacy exemption.
What data does HERE Maps transmit?
HERE Maps transmits tile coordinates and zoom level to map tile CDN domains, location search queries to geocoder.ls.hereapi.com, and route origin/destination to the routing API. All requests include the developer API key for billing authentication. No persistent user identifier is transmitted.
How does ConsentStack categorize HERE Maps?
ConsentStack classifies HERE Maps as functional and permits it to load without consent. Site operators should disclose HERE Global B.V. as a data processor in their privacy policy, particularly if geocoding queries could reveal sensitive locations such as medical facilities. ConsentStack helps surface this in its vendor disclosure tools.
Related Vendors
Manage consent for HERE Global
ConsentStack automatically detects and manages HERE Global trackers so your site stays compliant with global privacy regulations.