Set up your bannerConfigure Your ToolsMaps

Mapbox

How to configure Mapbox 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 reflect Mapbox GL JS in the Consenter Manager. The sources do not document a supported way to switch off Mapbox GL JS telemetry, so this guide uses a single fixed-behaviour table.

  1. Implement the service as described below.
  2. Map the implementation in the Consenter Manager.
  3. Update your privacy policy to reflect the actual implementation.

The mapping is an example, not a guarantee of legal compliance. Verify it against your implementation and current provider documentation.

At a glance

Scope. Interactive maps rendered with Mapbox GL JS and Mapbox tiles. Mapbox, Inc. is a US company.

What the service does in this scope. Mapbox GL JS uses browser localStorage keys prefixed mapbox.eventData to store telemetry data, including a randomly generated ID sent with telemetry events to Mapbox to calculate aggregate usage statistics. Mapbox applies anonymisation procedures, such as clipping traces, for telemetry that sends location data, and relies on its DPA with the 2021 SCCs for transfers to the US.

No configuration without prior consent. The localStorage ID is device access under § 25 TDDDG and is not needed to display the map. Load the map after Consenter consent, or show a click-to-load placeholder.

Step 1 — Implement Mapbox

Configuration areaFixed behaviour / required action
Processing purposesUnlock additional website features
LoadingConsenter script blocking / click-to-load for the map
Telemetry storagemapbox.eventData* in localStorage
ContractMapbox DPA with SCCs

Step 2 — Map the configuration in the Consenter Manager

Consenter Manager fieldValue to selectBasis and conditions
Processing purposesUnlock additional website featuresMap display
Tracking methodFirst party tracking (cross-session)localStorage ID on your origin
IdentifierDevice identifiersRandom telemetry ID
Data categoriesAggregated site statistics, Device characteristics, Device identifiers, IP addressTelemetry and tile requests
Legal role of data recipientProcessorPer Mapbox DPA; verify the role for telemetry
Personalisation modelNo personalisation—
Maximum storage durationUntil storage is clearedlocalStorage has no expiry
Processing locationUnited StatesUS enterprise; the US CLOUD Act

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