What the SDK sends home, and what it makes you build.
Telemetry is a term of your licence, not a setting. It decides what leaves your users' devices, whether you are permitted to stop it, and what your own interface has to carry. Here is what each SDK does by default and what each one asks of you.
How to read this page
The right-hand column quotes or paraphrases published documentation, terms or pricing from Mapbox mobile SDKs, and every row links to the page it came from so you can check it yourself. Where we could not source a claim from Mapbox's own documentation or product terms, the row is not on this page rather than worded more vaguely. Terms change, and quotes name the edition they were read in. If you find a row that has gone stale, tell us and we will correct it.What the SDK sends by default
Nothing. There is no client-side telemetry in production SDK builds and nothing that phones home from inside your application.
A fleet telemetry module exists, is off unless you switch it on, and uploads aggregate road-segment statistics rather than a trajectory. The SDKs never upload GPS positions or routes.
Quoted: “Mapbox Telemetry is a powerful location analytics platform included in this SDK. By default, the SDK sends unidentified location and usage data to Mapbox whenever the host app causes it to be gathered.”
Maps SDK for Android guide, under Telemetry opt out.
Whether you may switch it off
There is nothing to switch off, and no term in the SDK licence obliges you to leave any data flowing to us.
What MapMap does measure is gateway-side and disclosed in full: metered calls, response status classes, salted user-count hashes and activation events, never coordinates tied to an identity.
Quoted: “Customer shall not modify, interfere with or limit the data that a Mobile SDK sends to Mapbox, whether by modifying the Mobile SDK or other means (except for implementing an End User opt-out as required below).”
Mapbox Product Terms (2026-07), clause 2.9.1.
What your own application has to build
No opt-out interface, because there is no default collection for your users to opt out of. Anything your app gathers is yours, and belongs in your privacy policy rather than in ours.
The trust page states the position and the separate disclosure page lists everything the platform collects, so the claim is checkable rather than asserted.
Quoted: “you must provide a telemetry opt-out option elsewhere in your application if you do not plan to use the built-in information button. Custom approaches to this rule must be reviewed and approved by Mapbox.”
Mapbox attribution documentation, which Mapbox Product Terms (2026-07) clause 3.17 names as the binding Attribution Documentation. The Android guide puts it the same way: if you hide the attribution control, you must provide an alternative opt out.
Check the claim rather than take it.
The trust page sets out what the SDKs send and what they cannot send, and the disclosure page lists everything the platform collects server-side. Source access for verification comes with a commercial relationship or an evaluation.
Other comparisons: the full list.