Set up your bannerConfigure Your ToolsMaps

HERE

How to configure HERE at different risk levels and map it in the Consenter Manager.

This work is licensed under CC BY-SA 4.0

Typical processing purposes: Unlock additional website features

Overview

This guide explains how to implement different privacy configurations for HERE maps and location services on a website and how to reflect them in the Consenter Manager.

  1. Configure the third-party service.
  2. Map the selected configuration in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The configurations are comparative examples, not guarantees of legal compliance. Verify that the guide matches your product edition, implementation, and current provider documentation.

At a glance

Scope. HERE Maps API for JavaScript and HERE Location Services (HERE Technologies).

What the service does in this scope. When location-based services are used (e.g. search, routing or map data requests), location data is sent to HERE to serve the content. HERE Location Services Self-Hosted provides on-premises location services, including map rendering tiles for client-side rendering with the Maps API for JavaScript, giving customers control over their user data.

Configurations included.

ConfigurationSummary
Configuration A — Lower riskHERE Location Services Self-Hosted; tiles and search served from your own infrastructure.
Configuration B — Medium riskHERE cloud Maps API for JavaScript; loaded after Consenter consent or click-to-load.

Configuration A. With self-hosting, requests stay on your infrastructure; map it as self-hosted. Whether a Consenter entry is needed depends on whether the self-hosted setup stores anything on the device; verify.

Step 1 — Configure HERE

#Configuration areaWhere to configure itConfiguration A — Lower riskConfiguration B — Medium risk
1Processing purposesOperator decisionUnlock additional website featuresUnlock additional website features
2HostingHERE contractSelf-hostedHERE cloud
3LoadingConsenter script blocking / click-to-loadPer verificationAfter consent
4Location searchOnly on user actionUser-initiatedUser-initiated

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldConfiguration A — Lower riskConfiguration B — Medium risk
Processing purposesUnlock additional website featuresUnlock additional website features
Tracking methodNo trackingThird party tracking (single session, cross-website)
IdentifierNo identifierIP address
Data categoriesNon-precise location data (if searched)IP address, Device characteristics, Non-precise location data
Legal role of data recipientSelf-hostedProcessor
Personalisation modelNo personalisationNo personalisation
Maximum storage durationPer your server logsPer HERE privacy policy
Processing locationYour infrastructurePer HERE contract; check the DPA for US sub-processors

How is this guide?

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Need Help?

Last updated on

On this page