MapsForDevs — Commercial License Terms (Developer Reference)

This file is a developer-facing summary. The legally binding terms live in your account dashboard and supersede this summary if they conflict.

What you get

Plan	Tile API	Embed widget	Geocoding	Downloads (.mfdmap)
Free	100k tile reqs / mo	Unlimited views (rate-limited per IP)	2.5k reqs / mo	—
Indie ($19/mo)	1M / mo	Unlimited	25k / mo	5 country licenses included
Studio ($79/mo)	5M / mo	Unlimited	100k / mo	30 country licenses included
Scale	Negotiated	Negotiated	Negotiated	Negotiated
Per-country perpetual	n/a	n/a	n/a	$49 / country / version
Per-country yearly	n/a	n/a	n/a	$19 / country / year incl. updates

Quotas reset on calendar month boundaries (UTC+2 / SAST).

What you can do

• Build commercial products on top of our tile API.
• Self-host downloaded .mfdmap archives for use within your own apps.
• Cache tiles you fetched on your own CDN, for up to 90 days from each fetch.
• Display our maps in unlimited end-user browsers / devices, subject to plan quota.
• Modify our public style.json (colours, layer order, fonts) and serve the modified style from your own origin.

What you can't do

• Re-distribute the raw tile bytes / .pbf files / .mfdmap archives to third parties as a generic tile service. (Self-hosting for your own users = fine. Reselling tiles as their own product = not fine.)
• Strip or hide attribution. Both © OpenStreetMap and © MapsForDevs must remain visible on every map view.
• Use a single API key across more than one publicly-accessible product / domain. Issue separate keys per product.
• Bulk-download our entire tile corpus for offline use without buying the country / region licenses. (We have a script that detects this. We will rate-limit and contact you.)

Attribution requirement

© OpenStreetMap contributors · © MapsForDevs

Both clauses, both clickable links, on every map view. See recipes/attribution.md for placement guidance.

For ODbL data (OpenStreetMap), the open database license requires attribution and share-alike for derivative databases. Producing rendered tiles from the database is not a derivative database — your tiles are not subject to share-alike.

API key handling

• mfd_pub_* keys belong in browsers / public bundles. They must be domain-restricted.
• mfd_srv_* keys belong in server-side code only. If exposed in browser code, rotate immediately.
• Keys are shown once at creation. Storage is your responsibility.
• Lost a key? Rotate via the dashboard. Old key works for 24 h grace period.

Data freshness

• Tile API: rebuilt monthly from current OpenStreetMap data.
• Downloads: each .mfdmap is dated; we publish 4-12 refreshes per year per country.
• Geocoding: live against our Nominatim instance; reflects OSM updates within ~24 h.

Service level (SLO)

Plan	Uptime target	Notes
Free	99.0%	Best effort
Indie	99.5%
Studio	99.9%
Scale	99.95% with custom SLA	Contracted

Status page: https://status.mapsfordevs.com

Termination

You can cancel any time. On cancellation:

• Tile API and geocoding stop on the next quota cycle boundary.
• Embed widgets keep working.
• Perpetual country licenses you bought remain valid forever — no termination.
• Yearly country licenses expire at their renewal date.

Privacy & data

• We log tile requests for billing + abuse detection. Logs retained 90 days.
• We don't track end-user identity, geolocation, or session data.
• We don't sell or share request logs with third parties.
• See full privacy policy: https://mapsfordevs.com/privacy

Refunds

• Subscription plans: pro-rata on cancel.
• Per-country perpetual: 30-day money-back if you've not started using it (we check fetch logs).
• Per-country yearly: pro-rata for unused months, minus a 1-month minimum.

Contact

• support@mapsfordevs.com — technical issues, billing
• legal@mapsfordevs.com — license clarifications, custom terms
• abuse@mapsfordevs.com — report misuse of keys / quota theft