Terms of service

1. Who these terms bind, and how they are accepted

The MapMap hosted API, the self-serve console and every API key issued through them are operated by MapMap AI Ltd, a company registered in England and Wales (“MapMap”, “we”). These terms govern their use. You accept them by ticking the acceptance box on the signup page, or by sending accept_tos: true in a POST /v1/keys request.

Acceptance through the API binds the person or organisation on whose behalf the request is made. If an automated system or AI agent sends the request, the principal who operates or instructed that system is bound exactly as if they had accepted in person. If you accept on behalf of an employer or client, you confirm you have authority to bind them.

2. The service and prepaid usage

The service provides routing, ADR compliance checks, route optimisation, analysis (isochrones, matrices, map matching), vector tiles and map styles, and offline territory downloads over HTTP, metered per API key. The free tier, plan volumes, per-call rates and the monthly download allowance are published at /pricing and in machine-readable form at /pricing.json.

Paid usage is prepaid or covered by an active monthly plan. There is no post-paid overage: when included volume and prepaid credit are exhausted, requests are refused with an HTTP 402 or 429 status until you top up, subscribe or the month rolls over. Credit is drawn per call at the published rates and is non-transferable. Except where required by law, prepaid credit and part-month subscription fees are non-refundable.

3. Your keys and your account

API keys are shown once at issuance and stored by us only as cryptographic hashes. You are responsible for keeping keys secret and for all usage made with them, whether or not you authorised it. If a key leaks, revoke it or contact us without delay.

You must provide a working email address you control. It is the identity of record for your keys, your ledger and your plan.

4. Fair and lawful use

You must not attempt to circumvent metering, quotas, rate limits or issuance limits; probe, scan or disrupt the service; resell raw access to the API without agreement; or use the service for anything unlawful. Navigation output is an aid, not a substitute for driver judgement or legal compliance: the driver and operator remain responsible for observing signage, vehicle limits and the applicable dangerous-goods regulations.

We may apply reasonable technical limits (including the published issuance and key caps) to protect the service for everyone.

5. Data attribution

Routing and map data derive from OpenStreetMap, made available under the Open Database Licence (ODbL). Anything you render or republish from the service must credit “© OpenStreetMap contributors” with a link to openstreetmap.org/copyright. Territory packages carry their own attribution manifests.

6. No warranty

The service is provided as is and as available. We do not warrant that it will be uninterrupted, error-free or that routes, restrictions or compliance decisions are complete or correct for every road, vehicle or load. To the fullest extent permitted by law, all implied warranties and conditions are excluded.

7. Limitation of liability

Nothing in these terms excludes liability that cannot be excluded by law, including for death or personal injury caused by negligence, or for fraud.

Subject to that, we are not liable for loss of profit, revenue, data or goodwill, or for any indirect or consequential loss; and our total aggregate liability arising out of or in connection with the service in any twelve-month period is limited to the amounts you paid for the service in that period, or one hundred pounds sterling if greater.

8. Suspension and termination

You may stop using the service at any time; cancelling a subscription returns your keys to the free tier at the end of the paid period. We may suspend or revoke keys, or terminate access, for breach of these terms, non-payment, abuse, or where required by law. Where practicable we will give notice. Sections 5 to 10 survive termination.

9. Aggregated and de-identified data

Some features let you contribute operational data, at your option. For example, a fleet operator may enable the SDK’s aggregation module, which shares de-identified road-segment statistics with us and never your GPS positions or routes; the module is off by default and cannot upload a trajectory (see the privacy policy and /trust).

One collection surface is not optional: calls to the hosted API are recorded in a de-identified demand log, described in section 1 of the privacy policy. It is coarsened before it is written (coordinates to roughly 5 km cells, times to five-minute buckets) and carries no key, account, IP address or search text, so it is not personal data and cannot be linked to you. It does not apply to self-hosted deployments. If you would prefer your hosted traffic excluded, ask us and we will exclude your key.

Whether or not you enable any such feature, you grant MapMap a perpetual, irrevocable, worldwide, royalty-free right to create, use and commercialise Aggregated Data (data derived from your use of the service that has been aggregated and/or de-identified so that neither you nor any individual is identified or reasonably identifiable), including after these terms end. Aggregated Data is not your confidential information and is not personal data. We do not sell personal data. Where we process personal data on your behalf (for example, a fleet’s driver data), a separate data processing agreement governs that processing.

10. Changes, notices and governing law

We may update these terms; material changes will be posted on this page with a revised date, and continued use after the change takes effect is acceptance of the updated terms. Notices to you may be sent to the email of record.

These terms, and any dispute or claim arising out of them, are governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.