# API privacy notice

This notice explains what happens to your personal data when you use the Mapit API with a personal key or a connected app. It adds to Mapit's [Privacy Policy](https://mapit.me/en/privacy-policy/) and the data protection section of the [General Terms and Conditions](https://mapit.me/en/terms-and-conditions/), which cover everything else.

Effective 17 November 2026. Last updated 18 November 2026.

## 1. Who is responsible

The controller is the Mapit company named in your contract: in Spain, Mapit IoT, S.L., calle Casp 172, 4B, 08013 Barcelona, NIF B-66716291. You can reach Mapit's data protection officer at [gdpr@mapit.me](mailto:gdpr@mapit.me).

## 2. What the API returns

The API only returns data from your own account, and only to a key or app you created or approved. It returns the same data the Mapit app shows you:

| Data | Who can read it |
| --- | --- |
| Your name, email, language and time zone | Every key and connection |
| Your vehicles: name, model, plate, kilometres, subscription status and end date | Every key and connection |
| Last reported position, battery and device status, with the time they were recorded | Only if you ticked **location** |
| Trips: start and end times, distance, duration, average and top speed, the route on a map, and ride statistics | Only if you ticked **route history** |

The API never returns payment details, and it does not show Mapit's internal account, device or vehicle numbers. It uses codes that work only for your account.

## 3. Apps you connect

- When you connect an app, such as Home Assistant or an AI assistant, Mapit sends it the data you allowed. From then on, that app's provider decides what to do with it. It is their own controller, and their privacy policy applies, not Mapit's.
- Disconnecting an app stops new data from reaching it. It does not delete data the app already received. Ask the app's provider for that.
- You can see and disconnect your apps and keys at any time at [login.mapit.me/connections](https://login.mapit.me/connections).

## 4. What Mapit records when you use the API

### Your keys and connections

For each key or connection Mapit keeps: your account, the name you gave the key or the app's name, the permissions, when it was created, when it ends, and whether it was deleted. Keys and tokens are stored only as a one-way fingerprint (a hash), so Mapit cannot read them back.

### Request logs

For each request Mapit records one line with:

- the kind of request (for example "vehicle status"), not the full address;
- the answer code (for example 200 or 429) and how long it took;
- the kind of client: personal key, Home Assistant, Claude, ChatGPT, a program on your own computer or another app;
- your Mapit account number (not for requests from AI assistants) and a short code that tells your keys and connections apart.

The log does not contain the address you called, its parameters, your key or token, or the data returned. Mapit uses these logs to run the service, find faults and stop abuse.

### Sign-in

When you sign in to manage keys or connect an app, the sign-in page passes your email and password to Amazon Cognito, the system that checks Mapit passwords. The password is never stored or logged. To stop password guessing, Mapit counts failed attempts for a short time (see the [Limits](https://developers.mapit.me/limits.md) page), keyed on a fingerprint of your IP address. Mapit also records each step of connecting an app (sign-in succeeded or failed, the permissions asked for and granted, the connection made, renewed or removed) with the kind of app, but not your account, email or IP address.

### Usage analytics

Mapit uses PostHog, hosted in the EU, to count how many people use the API. It receives only these events, linked to your Mapit account number and not to your name or email:

- an app was connected (the kind of app, its name and the permissions);
- you opened the page to connect an app (the kind of app and the permissions it asked for);
- a personal key was created (the permissions; never the key or its name);
- a new key or connection was used for the first time (the kind of app, the kind of request and how long after it was made);
- once a day for each kind of app you use (Home Assistant, a personal key, Claude, ChatGPT, a program on your computer or another app): the kinds of request it made that day, such as "vehicle status" or the name of an AI tool, and the name and version of the client software, such as `HomeAssistant/2026.8.2`. It is sent when the app next calls on a later day;
- each request an AI assistant makes through the MCP connection (the tool's name, how long it took, whether it failed and how, the assistant's name and model, a conversation code, and the names, not the values, of what it asked for).

PostHog does not receive your IP address, your location, your trips or any other data the API returns. Location lookup from IP is turned off.

## 5. Why Mapit does this

- To give you the API you asked for: performance of your contract with Mapit.
- Request logs, limits and security checks: to keep the service and your data safe and stop abuse. This is in Mapit's legitimate interest in running a secure service.
- Usage analytics: to learn how the API is used and improve it. This is in Mapit's legitimate interest in understanding and improving the API. You can object at any time by writing to [gdpr@mapit.me](mailto:gdpr@mapit.me).

## 6. How long Mapit keeps it

| Data | Kept for |
| --- | --- |
| Request logs | One month, then deleted automatically. |
| Key and connection records | Until the key or connection would have ended (the [Limits](https://developers.mapit.me/limits.md) page says how long keys last), even if you delete it sooner, then deleted automatically. Backups of these records are kept for up to 35 more days. |
| Sign-in session | As short as the [Limits](https://developers.mapit.me/limits.md) page says. |
| Usage analytics in PostHog | No more than 12 months. |
| Daily usage summary (the last day of use, until it is sent to PostHog) | Up to 400 days after the last call. |

Your account, vehicle, location and trip data are kept as the [Privacy Policy](https://mapit.me/en/privacy-policy/) says. Using the API does not change that.

## 7. Who processes it for Mapit

| Provider | What for | Where |
| --- | --- | --- |
| Amazon Web Services | Runs the API, sign-in, storage and logs | Ireland (EU), region eu-west-1 |
| Amazon CloudFront and AWS WAF | Deliver requests and block abuse. They do not keep request logs for Mapit. | Servers near you in Europe or North America |
| PostHog | Usage analytics | EU |

Some of these providers handle data outside the European Economic Area: CloudFront servers in North America, and the US parent companies of AWS and PostHog. Mapit uses only providers that rely on the safeguards the GDPR requires for such transfers, such as the European Commission's standard contractual clauses or an adequacy decision. You can ask [gdpr@mapit.me](mailto:gdpr@mapit.me) for details.

## 8. Your rights

You have the rights listed in the General Terms: access, correction, deletion, restriction, objection, portability, and not being subject to automated decisions. To use them, write to [gdpr@mapit.me](mailto:gdpr@mapit.me).

You can complain to a data protection authority: in Spain the AEPD ([www.aepd.es](https://www.aepd.es/)), in Portugal the CNPD ([www.cnpd.pt](https://www.cnpd.pt/)). You do not need to contact Mapit first.

## 9. Changes

If what the API records changes, Mapit will update this notice and its date before the change.
