Data residency narrative (India retail)

This page explains typical placement of workloads; authoritative POP for a SKU is what you consent to at checkout and on product pages—not this summary alone.

Hosting payload (sites, DBs, mailboxes)

Retail KVM and shared footprints target India-advertised POPs. Cross-border mirrors or DR copies, if enabled for your tier, surface in SKU text or concierge tickets—not buried only in prose here.

Flows that inherently cross borders

• Payment orchestration acquiring via Indian gateways still involves card-network hops
• Optional chat widgets/CDN probes may egress metadata to jurisdictions of those vendors (register)
• Authoritative invoicing artefacts live in authenticated billing tooling — correlate with GST discussion in India DPA appendix

Buyer action

If your regulator demands single-region persistence with no discretionary subprocessors, start with framework routing before assuming retail cart checkout satisfies the clause.