# Data localisation for banks in India, Nepal and South Asia: DPDP, RBI and in-country AI

> India's DPDP Act and Rules, notified in November 2025, set a consent- and security-driven privacy regime, while sectoral rules such as the RBI's 2018 payment data direction require payment data to be stored only in India. Nepal's banks, like many in South Asia, prefer to keep banking data in-country. An in-country lakehouse with local AI inference meets both the letter of storage rules and the growing expectation that processing stays local too.

Source: https://datanature.ai/blog/data-localisation-banks-india-nepal-south-asia-dpdp-rbi
Publisher: Dlytica Inc. (DataNature is a Dlytica company)
Updated: 2026-11-05

South Asia's banking sector is digitising fast, and regulators are pairing that growth with clear expectations on where data lives. This guide summarises the main rules in India, how banks in Nepal and the region approach the question, and what that means for data and AI platforms.

## What does India require?

India has no single omnibus localisation law. Two layers apply together:

- **Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025**, notified on 13 November 2025: consent, purpose limitation, security safeguards such as encryption and masking, breach notification, and enhanced duties for Significant Data Fiduciaries. Cross-border transfers are permitted subject to government restrictions.
- **Sectoral rules**, which are stricter: the RBI's 2018 direction on storage of payment system data requires end-to-end payment transaction data to be stored only in India, and other regulators such as SEBI and IRDAI have their own cloud and storage frameworks.

Many banks read this conservatively: keep payment, core banking and customer data in India, and keep the analytics and AI that use it in India too.

## How do banks in Nepal and the region approach it?

Banks in Nepal increasingly expect banking data and the platforms that process it to stay in the country, which rules out many foreign SaaS platforms. Nabil Bank chose DataNature in 2026 for exactly this reason: one governed foundation for analytics and AI, running in Nepal. Sri Lanka and Bangladesh follow similar patterns for regulated financial data. In each case, the safest architecture keeps data, metadata and AI processing in-country.

## What does that mean for a data and AI platform?

| Requirement | What the platform must do |
|---|---|
| Payment and core banking data stored in-country | Storage, backups and replicas in the country |
| Security safeguards under DPDP | Encryption, masking and access controls applied by default |
| Breach readiness | Audit logs of who accessed what, kept in-country |
| AI on personal data | Embeddings, prompts, inference and logs processed locally |
| Regulator access | Lineage and audit evidence available on request |

## How does DataNature run in South Asia?

DataNature deploys in-country: in Nepal on local infrastructure, including telecom private clouds; in India on Indian data centres or your own; and on-premises where required. The whole stack, including the control plane, the Milvus vector store, the AI gateway and audit logs, runs inside the country. Column masks, row filters and PII guardrails are applied in every layer, and StreamHouse supports real-time fraud detection on payment flows without data leaving the country.

## Which use cases are most common?

- Customer 360 and cross-sell for commercial banks
- Real-time wallet and card fraud on the StreamHouse hot path
- Loan document automation with DocuContext
- AML network analysis with the knowledge graph
- Staff-facing Voir agents for branches and contact centres

## Frequently asked questions

### Does the DPDP Act require all data to stay in India?

No. The DPDP framework permits cross-border transfers subject to government restrictions. Sectoral rules, such as the RBI's payment data direction, are stricter for the data they cover.

### Can DataNature run in Nepal?

Yes. DataNature runs in Nepal, including for Nabil Bank, with data, metadata and AI kept in-country.

### Is this legal advice?

No. Confirm your obligations with qualified counsel and your regulator.

## Sources

- [India Briefing: DPDP Rules 2025 notified](https://www.india-briefing.com/news/dpdp-rules-2025-india-data-protection-law-compliance-40769.html)
- [Treelife: data localisation in India, RBI payment data and DPDP Rules](https://treelife.in/compliance/data-localisation-in-india/)
- [DataNature: Nabil Bank onboards DataNature](/blog/nabil-bank-onboards-datanature)
- [DataNature: Nepal region](/regions/nepal)

## How does DataNature Atlas keep this secure and compliant?

Every rule in this article is enforced in one place, inside your jurisdiction. [DataNature Atlas](/platform/atlas) is the platform's governance module:

- **Knows your data**: a catalog with automated PII detection and classification across Bronze, Silver and Gold.
- **Controls access**: role-based grants plus attribute-based policies, row filters and column masks (null, redact, partial, hash, year only).
- **Governs AI**: Voir agents are scoped principals; masks, row filters and PII guardrails apply to every tool call and answer.
- **Proves it**: lineage from source to metric to decision, and an audit log of who or what accessed which data.
- **Stays local**: Atlas runs inside your deployment, so policies, lineage and logs never leave your jurisdiction.

These controls support GDPR, PIPEDA, Quebec Law 25, CCPA, HIPAA and sector rules such as OSFI E-23. Read [DataNature Atlas in depth](/blog/datanature-atlas-governance-rbac-abac-pii-masking) or see [security and compliance](/security).
