Acceptable use policy

Written to be read. Where a clause has a practical consequence, the consequence is stated rather than implied.

Not permitted

Systematic extraction to build a competing copy of the underlying map, address or place data. Caching for performance is fine; rebuilding the database is not.

Tracking or profiling identifiable individuals without a lawful basis and their knowledge, including covert location monitoring of employees or family members.

Reselling raw responses as a competing location API.

Circumventing rate limits, spend caps or key scoping, including by rotating accounts to extend free allowances.

Use with care

Safety-critical systems — emergency dispatch, autonomous control, aviation and maritime navigation — need independent validation. Location data is an estimate, and we do not warrant it as sufficient on its own for those uses.

High-volume automated decisions about individuals, such as insurance scoring, should account for coverage differences by country rather than treating a data gap as a signal.

Enforcement

We contact the account first except where the activity threatens platform stability or the safety of individuals, in which case we suspend and then contact. Suspensions are explained, and there is a route to appeal at [email protected].

These are commercial terms, not legal advice. They were drafted to be read by the people who have to live with them; have your own counsel read them before you rely on them.