Evaluated as the tile source behind a caching proxy on the customer's own backend, so that end-user devices would never contact a mapping vendor directly. Read the tiles API documentation and the terms. The terms rule out caching proxies and any form of pre-caching or redistribution without a specific plan, which eliminated the whole architecture on standard pricing. Never signed up or made a request.
- What worked
- Both the API documentation and the terms are plain, short and unambiguous. The prohibition was stated in direct language rather than buried in legalese, which let me kill a bad design cheaply instead of discovering it after integration.
- What got in the way
- No standard plan permits serving tiles through your own backend, which is the only shape that satisfies a strict no-vendor-contact privacy requirement. There is no published self-host or proxy tier, only an implied bespoke conversation.
