Maps API with India data residency: what each provider actually offers (2026)
- Back to blog Ola Maps is the only major maps API that stores data in India by default. Mappls, Google Maps, Mapbox, and maps.guru do not offer India data residency as a standard tier — and for edge-hosted providers the reason is structural, not a product gap. We are maps.guru, we run on Cloudflare, and we do not offer India data residency today. This post explains what the rules actually require, which providers meet them, and why "runs in India" and "stored in India" are different claims.

## The short version
ProviderIndia data residencyWhat that means in practice
Ola MapsYes — India-only stackTiles and queries stay in India; India-only coverage
MapplsIndia-built, not publishedIndian company, residency terms via sales engagement
Google MapsNo standard India tierGlobal infrastructure; India-specific serving for content
MapboxNoUS/global infrastructure
maps.guruNoCloudflare edge — see the structural reason below

If India data residency is a hard contractual requirement, Ola Maps is the answer today and we will say so rather than pretend otherwise.

## What actually requires data residency
Three separate regimes get conflated. Only one of them is a general residency mandate, and it does not apply to most map data.

### DPDP Act 2023 — a blocklist, not a residency mandate
The Digital Personal Data Protection Act 2023 does not impose general data localisation. Section 16(1) permits transfer of personal data outside India except to countries the Central Government restricts by notification. It is a negative-list model — transfer is allowed by default.
This is a meaningful liberalisation from the earlier draft bills, which did contemplate broad localisation. Advice written before 2023 frequently still assumes the stricter regime.
The Act also only governs personal data. A vector map tile of Bengaluru contains no personal data. A geocoding request containing a customer's delivery address usually does.

### RBI payment-data localisation — narrow, and strict
RBI's April 2018 directive on Storage of Payment System Data requires that the entire payment data lifecycle be stored only in India. This is a genuine hard localisation requirement, but its scope is payment system data — not map tiles, not geocoding.
It becomes relevant to maps only if you are embedding location into payment records — a fintech storing merchant coordinates inside transaction data, for example.

### Geospatial Guidelines 2021 — accuracy-gated
The 2021 Geospatial Guidelines impose residency based on spatial accuracy, not on data category. Clause ix:
Digital Maps/Geospatial Data of spatial accuracy/value up to the threshold value can be uploaded to the cloud but those with accuracy finer than the threshold value shall only be stored and processed on a domestic cloud or on servers physically located within territory of India.
The threshold is one metre horizontal, three metres vertical (clause iv(a)(1)). Standard basemap tiles and locality-resolution geocoding sit above it, so this clause does not apply to them. Survey-grade capture — drone photogrammetry, LIDAR, CORS-corrected GNSS — sits below it, and then residency is mandatory.
See our India map boundary compliance guide for the boundary requirements in the same Guidelines.

## Why edge providers structurally cannot offer India residency
This is the part that is rarely explained, and it is why our answer is no.
maps.guru runs on Cloudflare Workers, R2, and D1. Cloudflare's Data Localization Suite splits into two capabilities that sound similar and are not:
Regional Services — India is supported. Cloudflare can restrict which data centres decrypt and service HTTPS traffic, and India is an available region: "Cloudflare will only use data centers that are physically located within India to decrypt and service HTTPS traffic."
Storage jurisdictions — India is not supported. R2 Jurisdictional Restrictions support exactly two jurisdictions: eu and fedramp. D1 jurisdictions support the same two. D1 offers a location hint — apac for Asia-Pacific — but Cloudflare documents hints as best-effort placement, not a residency guarantee, and apac is a region, not India.
So on Cloudflare today you can guarantee where traffic is processed but not where objects are stored, for any jurisdiction other than the EU or FedRAMP. Any provider building on this stack that claims India data residency is either running separate Indian infrastructure or overstating what the platform provides.
The same structural limit applies to most edge-first providers. It is a real trade-off of the architecture that makes edge delivery fast and cheap.

## What "India-hosted" actually buys you
Two things get bundled under "data residency" and only one is a compliance property:
Latency. India-hosted vendors typically serve Indian users in roughly 50–100 ms; EU-hosted vendors closer to 150–300 ms. This is a performance argument, and a good one for real-time tracking or delivery ETAs. It is not a legal argument. Edge providers with Indian points of presence often win on latency without storing anything in India.
- Legal residency. Where data is stored and processed for regulatory purposes. This is what an auditor or a bank's vendor-risk team is asking about, and a CDN PoP in Mumbai does not satisfy it.When a vendor says "India-first" or "served from India," ask which of the two they mean.

## Choosing
SituationRecommendation
Contractual India residency requirementOla Maps — India-only stack
Regulated fintech touching payment-system dataOla Maps or self-hosted on Indian cloud
Capturing sub-metre survey dataSelf-host in India; residency is mandatory
Want low India latency, no residency clauseAny edge provider with Indian PoPs, including us
India + international coverage, transparent INR pricingmaps.guru, LocationIQ

## Self-hosting is a legitimate answer
If residency is genuinely mandatory and you want to stay off a single vendor, the open-source path is real: PMTiles archives on Indian object storage, served by a tile server, rendered by MapLibre GL JS. That is architecturally what we run — the difference is which country the bucket sits in. See our Google Maps to MapLibre migration guide for the client-side portion.

## Where we stand
We do not offer India data residency, and on our current infrastructure we cannot honestly claim it. What we do offer is INR billing, Indian company ownership, edge delivery with Indian points of presence, and transparent flat pricing with no sales calls — see pricing.
If residency is your gating requirement, use Ola Maps. If it is latency you actually care about, benchmark us against them from an Indian network before deciding.

## FAQ

### Which maps API offers India data residency?
Ola Maps is the only major maps API offering India data residency as a standard property — its infrastructure is India-only. Mappls is an Indian company but does not publish residency terms outside a sales engagement. Google Maps, Mapbox, and maps.guru do not offer India residency as a standard tier.

### Does the DPDP Act require storing map data in India?
No. The Digital Personal Data Protection Act 2023 does not impose general data localisation. Section 16(1) permits transfer of personal data outside India except to countries the Central Government restricts by notification — a negative-list model rather than a residency mandate. The Act also applies only to personal data, which map tiles are not.

### Do RBI rules require map data to stay in India?
Only if the map data forms part of payment system data. RBI's April 2018 directive requires the entire payment data lifecycle to be stored only in India, but its scope is payment system data. Map tiles and general geocoding fall outside it unless you embed location inside payment records.

### Can a Cloudflare-hosted service offer India data residency?
Not for storage today. Cloudflare's Regional Services supports India for HTTPS traffic processing, but R2 and D1 Jurisdictional Restrictions support only the eu and fedramp jurisdictions. D1's apac location hint is a best-effort placement hint covering Asia-Pacific, not a guarantee and not India-specific.

### Is India-hosted the same as low latency in India?
No. India-hosted usually means roughly 50–100 ms for Indian users versus 150–300 ms from EU infrastructure, but an edge provider with Indian points of presence can match that latency while storing data elsewhere. Latency is a performance property; residency is a legal one.

### When does the one-metre accuracy threshold apply?
Clause iv(a)(1) of the 2021 Geospatial Guidelines sets the threshold at one metre horizontal and three metres vertical. Data finer than that must be stored and processed on a domestic cloud or on servers inside India, and may only be created or owned by Indian Entities. Standard basemap tiles and locality-level geocoding are coarser than the threshold, so it does not apply to them.

## Sources

- Digital Personal Data Protection Act 2023 (MeitY)
- RBI — Storage of Payment System Data (April 2018)
- Survey of India — Geospatial Data Guidelines (2021)
- Cloudflare Data Localization Suite — region support
- Cloudflare R2 — data location and jurisdictions
- Cloudflare D1 — data location
- Ola Maps pricing
- Mappls API hubThis post is engineering guidance, not legal advice. If residency is a compliance requirement, take Indian counsel.

## Ready to build with
beautiful basemaps?
Join developers worldwide who trust maps.guru for their mapping needs. Start free, no credit card required.
Get started free Get started free
Contact us
Free forever plan
5-minute setup
No credit card