Mapbox
Developer platform · mapbox.com · last read 2026-11-09
At a glance
- Is Mapbox GDPR compliant?
- No tool is GDPR compliant on its own: compliance depends on what you process with it and how. What follows is what Mapbox itself publishes, each answer linked to its source and the date we read it.
- Does Mapbox have a SOC 2 report?
- Mapbox states SOC 2 Type 2 on its own page, but does not say there how to get a report. Mapbox also publishes a SOC 3 report. We read this on 2026-11-09. Source and date
- Where does Mapbox store EU customer data?
- The vendor states that no EU location is offered. Source and date
- Who are Mapbox's subprocessors?
- Mapbox lists 15 third-party subprocessors; 15 of them name at least one processing country outside the EEA. We last read the list on 2026-11-09. Source and date
The same questions for any vendor, and the rule behind each: the vendor due diligence checklist.
Identity
| Legal entity | Mapbox, Inc. |
|---|---|
| HQ | — |
| Parent company | — |
| Ultimate ownership | — |
| EU contracting entity | — |
| LEI | — |
| US CLOUD Act reach | Not determined from the sources read |
| Source | mapbox.com · 2026-11-09 |
Data location
| Region | EU data location | Minimum plan | Source | Observed |
|---|---|---|---|---|
| EU | No EU location | — | mapbox.com | 2026-11-09 |
EU: The document answers "No" to whether Mapbox can limit its geographic processing to Europe. Its products and services store and serve source data from an AWS primary region in the US.
The same question for every vendor: where SaaS vendors store EU data.
Mapbox's subprocessor list names AWS and Google for hosting or infrastructure. Which SaaS vendors run on which cloud, and the sovereign offerings of each: sovereign clouds.
Subprocessor chain
15 third parties · 8 of the vendor's own group companies · 15 with a country outside the EEA · all read 2026-11-09
| Subprocessor | Country | Purpose |
|---|---|---|
| Amazon Web Services (“AWS”) | US | Hosting provider |
| Astronomer | US | data orchestration platform provider |
| Atlassian | US | Project management tool, code development, and bug tracking |
| Cloudfront on AWS | US, MX, CA, EU, IL, ZA, KE, JP, AU, NZ, HK, ID, PH, SG, KR, TW, TH, VN, IN | Content delivery network (“CDN”) |
| Fivetran | US | Data aggregation service |
| Github | US | Code development, testing, and ticketing system |
| Google Firebase | US | Backend cloud computing services and application development platforms |
| MixPanel | US | User analytics provider for Straightaway |
| Mode Analytics | US | Data analytics provider |
| Observe Cloud | US | Data visibility & analytics provider |
| Panther Labs | US | Web server and platform infrastructure log aggregator |
| Snowflake | US | Service provider for data analytics and processing |
| Tableau Software | US | Business intelligence and data visualization provider |
| Twilio (Segment.io) | US | Data aggregation service |
| Zendesk | US | Service provider of customer support tools |
Mapbox's own group companies listed as subprocessors (8)
| Company | Country | Purpose |
|---|---|---|
| Mapbox GmbH | DE | — |
| Mapbox International, LLC | US | — |
| Mapbox Japan G.K. | JP | — |
| Mapbox Oy | FI | — |
| Mapbox Poland sp. Zo.o | PL | — |
| Mapbox Technologies Canada, Inc. | CA | — |
| Mapbox UK Ltd. | GB | — |
| MapData OOO | BY | — |
The count outside the EEA is arithmetic over the country column, not a judgement about lawfulness. A transfer outside the EEA can be perfectly lawful; whether this one is depends on your use, not on the vendor.
Every subprocessor in the registry, and which vendors name it: subprocessors.
Processing terms
No data processing agreement read yet.
These terms side by side for every vendor: data processing agreements compared. What vendors give you for a transfer impact assessment: transfer impact assessments.
Assurance
Does Mapbox have a SOC 2 report?
Mapbox states SOC 2 Type 2 on its own page, but does not say there how to get a report. Mapbox also publishes a SOC 3 report. We read this on 2026-11-09.
Of the 114 vendors in this registry whose own pages mention SOC 2, 57 say the report is available on request, 1 links to the report itself, and 56 state it without saying how to get it. The type is the one the vendor names.
| Scheme | Status | Scope | Source | Observed |
|---|---|---|---|---|
| ISO 9001 · ISO9001 | Claimed | Global Quality Standard | mapbox.com | 2026-11-09 |
| SOC 2 (Type II) · SOC2T2 | Claimed | Security, Availability, and Confidentiality Report | mapbox.com | 2026-11-09 |
| SOC 3 · SOC3 | Certificate published | General Control Report | mapbox.com | 2026-11-09 |
| TISAX | Claimed | Automotive Industry Standard | mapbox.com | 2026-11-09 |
Claimed means the vendor asserts the scheme on its own page and offers nothing further. Available on request means the report or certificate exists but sits behind a request, a login or an NDA. Neither is a certificate we have seen. That is a distinction an auditor makes, so we make it too.
SecNumCloud, C5, ENS and HDS for every vendor, with the pages for ISO standards, SOC 2 and TISAX: certifications compared.
Official registers
- ACN qualified cloud (Italy): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
- DORA critical ICT third-party providers (ESAs): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
- ENS certificates of conformity (CCN, Spain): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
- EU Cloud Code of Conduct (GDPR Art. 40): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
- FedRAMP Marketplace (US): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
- SecNumCloud qualified services (ANSSI, France): checked 2026-11-09, no entry under Mapbox; Mapbox, Inc.
What the authority publishes, not what the vendor claims. An entry covers the offering it names and nothing else: a FedRAMP authorisation for a government edition says nothing about the commercial service. No entry is not a finding about security - most vendors never apply - and an entry filed under a name not listed above would not have been found.
Support window
Not yet collected. This row will say not declared only once we have read a lifecycle or security page and found no period stated — see support windows.
Vulnerability reporting: no security.txt at the well-known path (read 2026-11-09)
How other vendors publish theirs: security.txt across the registry.
Documents
| Document | Disclosure | Transcription | HTTP | Observed |
|---|---|---|---|---|
| certifications | Public | full | 200 | 2026-11-09 |
| residency | Public | full | 200 | 2026-11-09 |
| subprocessors | Public | full | 200 | 2026-11-09 |
History
Nothing has moved since we started watching this vendor on 2026-11-09. Changes appear here only after a human has reviewed them.
Every reviewed change across the registry, newest first: vendor changes.