Draft — pending legal review, not yet in force

This text is a working draft published for transparency. It has not been reviewed by counsel, may change before launch, and does not yet form part of any agreement with you. Items in [square brackets] are still to be confirmed.

API and SDK terms

Draft of 19 November 2026

These terms add to the terms of service and apply when you use the MilsatMaps APIs, the SDKs (including the script-tag build and the @milsat/maps package), and the tools for AI agents. If they conflict with the terms of service, these terms win for the APIs and SDKs.

1. Keys

  • Public keys (pk_…) are meant to be seen in web pages and apps. Restrict each one to the websites or apps that use it in the console.
  • Secret keys (sk_…) must stay on your servers. Never put one in a web page, an app bundle or a public repository.
  • You are responsible for requests made with your keys. Rotate or revoke a key as soon as you think it has leaked.
  • Test keys are for development only and must not serve your production users.

2. Limits

Usage counts against your project's monthly allowance and, on paid plans, its spending cap, as described on the pricing page. We also apply rate limits to keep the Service fair and stable. Do not try to get around limits, for example by spreading traffic over several free projects.

3. Attribution

Wherever you show a map or data from the Service you must keep the attribution visible and legible:

  • “© OpenStreetMap contributors”, linked to openstreetmap.org/copyright;
  • “Milsat” for Milsat data; and
  • the imagery provider's credit when satellite imagery is shown.

The SDK's map control shows these for you; do not hide or obscure it. Where you use data without a map, follow Attribution and data.

4. OpenStreetMap data and the ODbL

OpenStreetMap data is licensed under the Open Database Licence. If you build and publicly use a database derived from it, the ODbL's share-alike terms apply to that database. These terms do not take away any right the ODbL gives you over OpenStreetMap data.

5. Milsat data: caching and storage

  • You may cache responses temporarily to improve performance, for up to [30] days, and must refresh them after that [period to be confirmed].
  • You may store place identifiers indefinitely and use them to look places up again.
  • You must not extract Milsat data in bulk, build your own database from it, or resell or redistribute it, without a separate written agreement: contact us.
  • Postcode and other data supplied to us by third parties may carry further conditions, which we will tell you about in the documentation [to be confirmed].

6. Prohibited uses

  • Tracking or monitoring identifiable people without their knowledge and a lawful basis.
  • Safety-critical uses (such as emergency dispatch or the navigation of aircraft or vessels) where an error in map data could cause harm, unless we agree otherwise in writing.
  • Building a product that substitutes for MilsatMaps from its data or responses.
  • Training machine-learning models on Milsat data, other than letting an AI agent call the Service's tools to answer a user's request.
  • Scraping the console or website, or reverse engineering the Service beyond what the law allows.

7. Your users' data

You are the controller of personal data your application sends to the APIs, such as search text and locations. Tell your users about it in your own privacy notice and have a lawful basis for it. We process it only to answer requests, meter usage and keep the Service secure, as described in our privacy policy [data processing terms to be confirmed].

8. Changes and deprecation

We version the APIs and the SDK. We will give at least [90] days' notice before removing or making a breaking change to a generally available API version, except where a change is needed urgently for security or legal reasons. Beta features may change without notice.

9. Suspension

We may suspend a key or project at once if it puts the Service, other customers or the public at risk, or breaks these terms, and will tell you why when we can.