What MapMap collects

1. The principle

MapMap measures its own service, not your users. Everything listed below is derived from traffic our gateway must handle anyway to serve your requests, processed for service improvement. There is no client-side telemetry in production SDK builds, no tracking pixels, and nothing that phones home from inside your application.

2. What we collect (gateway-side)

Usage counters: metered calls per API key, per day, per endpoint: the same numbers that drive your quota, your bill and the usage panel on your account page.

Error classes: counts of response status codes (for example 401, 402, 422, 429) per key and endpoint, so we can see when developers are hitting friction; a storm of 401s is a documentation gap, not a customer to ignore.

Monthly-active-user hashes: when you meter SDK seats via the X-MapMap-User header, we store a salted hash to count distinct users. We cannot reverse it, and we never see who the user is.

Activation events: service milestones on your key, such as the timestamp of your first successful route. We use these to improve onboarding and, for early customers, to say hello.

The demand log: on the hosted API only, one line per metered geospatial request, recording the endpoint, whether it arrived from the API, an agent or an SDK, the territory, the pricing class, the billable units, and, where the request carried coordinates, the origin and destination truncated to a roughly 5 km geohash cell with the time floored to a five-minute bucket. The truncation happens before the line is written, and the line carries no API key, no key id, no account, no IP address and no search text. It is the one collection surface that is not per-customer opt-in, it never runs on a self-hosted deployment, and if you would rather your hosted traffic did not appear even in this form, tell us and we will exclude your key.

Website analytics on mapmap.ai are cookieless and aggregate: page views, docs feedback clicks and playground interactions, never tied to an API key. They run on PostHog in its EU region and on a Plausible instance served from analytics.unified.studio, which is listed with our other processors in the privacy policy.

3. What we never collect

No coordinates tied to identity. Route coordinates are processed to answer the request and are not stored against your identity. Two things are retained and neither is tied to you: the coarse demand log in section 2, which is truncated before it is written and carries no key, account or IP, and the separately documented, consent-gated probe programme, which is off unless you explicitly enable it. Nothing else that carries a location is kept.

No API keys in analytics. Keys are bearer credentials, never analytics identifiers, and never leave the gateway's own auth path.

No transcripts. Agent feedback (see the Agent Feedback Programme) carries only structured fields; never your conversation, prompts or code.

No client-side telemetry from production SDK builds. SDK telemetry is hard-off in shipped apps: anything on an end user's device belongs to you and your privacy policy, not ours to take.

4. Retention

Feedback submissions (agent retros, map-issue reports, docs feedback): 24 months, then deleted.

Usage and error counters: kept with the key while your account is active. Revoked keys and their counters are kept for up to twenty-four months for billing evidence and abuse forensics, then deleted or anonymised, which is the period the privacy policy states. Billing records are kept as long as the law requires.

The demand log and the opt-in probe aggregates: de-identified at the point of collection, and kept for as long as they are useful to the products they feed, as the privacy policy says. There is nothing in either that could be returned to a person.

5. Where it lives

Gateway telemetry and feedback are stored on EU infrastructure. Website analytics run on PostHog's EU region and on the Plausible instance at analytics.unified.studio. Nothing in this document is transferred to ad networks or data brokers; MapMap does not sell data, full stop.

6. Questions

If anything here is unclear, or you want something we hold about your key deleted, email hello@mapmap.ai. You will get an answer from a person.