5 min read

Can We Keep Indian Personal Data On US Or EU Cloud?

The DPDP Act allows businesses to store and process digital personal data outside India by default. Learn how the Section 16 negative list works, how sector laws like RBI mandates override default rules, and how B2B SaaS vendors prove compliance readiness to enterprise clients.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

Last updated:

Can We Keep Indian Personal Data On US Or EU Cloud

Yes. The Digital Personal Data Protection Act, 2023 allows companies to transfer and store digital personal data outside India by default. Section 16(1) states that cross-border transfers are permitted unless the Central Government issues a notification restricting transfers to specific countries. The Act relies on a negative list. The government has not notified any restricted countries. A Data Fiduciary retains the freedom to choose server locations globally until the government publishes a specific restriction.

If a B2B SaaS platform relies on AWS in US-East or Azure in Frankfurt, the company does not need to move that data to a Mumbai data centre just to satisfy the DPDP Act. Organizations can continue using existing global cloud infrastructure today. Privacy leaders managing programs across regimes often look for complex cross-border mechanisms. India does not require standard contractual clauses. The government does not demand binding corporate rules. Companies do not need to perform transfer impact assessments to move data abroad. The DPDP Act simplifies this architecture. A vendor relies entirely on the default permission granted by Section 16.

Foreign cloud storage falls under specific applicability rules. Section 3(a) applies the law to the processing of digital personal data within the territory of India. This applies when the personal data is collected in digital form. It also applies if data is collected in non-digital form and digitised subsequently. The DPDP Act evaluates where the collection takes place. If an Indian retailer collects customer details at a local store in non-digital form and digitises them subsequently, the law applies. The retailer can store this digitised database on an EU cloud server. Section 16 permits this action. The collection happened in India, so the DPDP Act governs the data, but the storage location remains flexible. Data Principals retain their rights to access or erase this data regardless of where the servers physically sit.

Foreign entities hosting data directly evaluate Section 3(b). The Act applies to processing of digital personal data outside the territory of India if that processing is in connection with any activity related to offering of goods or services to Data Principals within the territory of India. A foreign cloud provider selling direct-to-consumer apps in India falls under the DPDP Act. Cloud providers rarely determine the purpose and means of processing. They typically act as Data Processors. The DPDP Act places all regulatory obligations on the Data Fiduciary. If an Indian hospital uses a US-based cloud hosting service, the hospital acts as the Data Fiduciary. The hospital secures consent from patients. The hospital answers to the Data Protection Board if a breach occurs. The US cloud provider simply fulfills the contractual terms set by the Indian hospital. Section 8 dictates that the Data Fiduciary uses a valid contract to engage a Data Processor. The fiduciary remains fully accountable for the data.

Not all cloud data triggers these requirements. Section 3(c) excludes personal data processed by an individual for any personal or domestic purpose. Cloud storage of family photos is exempt. The Act also excludes personal data that is made or caused to be made publicly available by the Data Principal to whom such personal data relates. Data made public by a person under a legal obligation is similarly exempt. Companies exclude these specific categories from DPDP Act transfer restrictions. A blogger posting comments on a public forum makes that data publicly available. The platform hosting the forum processes that public data outside the scope of the Act.

Section 16(2) creates a specific exception for other laws. The DPDP Act states that nothing contained in this section shall restrict the applicability of any law for the time being in force in India. This clause applies to laws providing a higher degree of protection for or restriction on transfer of personal data by a Data Fiduciary outside India. The Reserve Bank of India mandates that payment system data must remain within the country. If a B2B SaaS company sells software to Indian banks, those clients enforce RBI localization requirements. The SaaS provider cannot rely on the DPDP Act default transfer allowance to bypass the RBI mandate. The sector rule controls the data flow. Securities and Exchange Board of India regulations also dictate storage parameters for specific market data. Vendors mapping their infrastructure evaluate both the DPDP Act and these overriding sector mandates.

B2B SaaS companies often stall in procurement because they lack compliance documentation for large enterprise clients. Big banks and insurers face regulatory scrutiny. They force vendors to prove readiness. Pointing to a SOC 2 audit rarely satisfies Indian enterprise buyers. Generic global privacy tools frequently miss specific rules. Enterprise clients expect to see precise workflows. They demand verifiable parental consent mechanics. They look for itemised notices in multiple Indian languages. They require an incident response plan that guarantees intimation to affected Data Principals without delay.

The DPDP Rules, 2025 introduce specific timelines. A Data Fiduciary reports a personal data breach to the Board within 72 hours. Enterprise clients audit vendor contracts to ensure the SaaS provider notifies them well before this 72-hour window expires. Indian procurement teams reject generic addendums. They demand distinct clauses covering DPDP Act definitions, specific breach intimation protocols, and clear data erasure mechanisms. A processor failing to report an anomaly to the fiduciary creates a compliance failure for the entire chain. Enterprise agreements allocate this liability directly.

The Central Government dictates commencement under Section 1(2). The Act shall come into force on such date as the Central Government may appoint. Different dates may be appointed for different provisions. Organizations have exactly 194 days until the 13 May 2027 compliance deadline. Enterprise procurement cycles take months to close. Delaying compliance puts revenue at risk. Clients pause contracts to audit their supply chains. A vendor producing a mapped DPDP compliance summary moves through procurement faster. A vendor relying on generic privacy statements faces repeated legal reviews.

Related Questions From B2B SaaS Buyers

Do companies need explicit consent to transfer data abroad? Consent is the primary basis for processing, except where Section 7 legitimate uses apply. A company includes transfer details in the itemised notice. The Act does not require separate consent purely for the act of transferring data to a non-restricted country.

What happens if the US or EU is added to the negative list? A blanket restriction on US or EU cloud providers is highly improbable given current trade relationships. The Central Government issues a notification if it adds a jurisdiction to the restricted list. That document details the compliance timeline to migrate data out of that territory.

Does an existing European privacy program cover these requirements? Mapping multiple regulations requires attention to local deviations. Global frameworks cover broad principles. The DPDP Rules, 2025 mandate distinct mechanics for consent managers, data fiduciary duties, and breach notifications. Vendor-readiness depends on proving compliance with these specific obligations.

What To Do Next

1. Map your data flows. Identify which foreign cloud regions process digital personal data in connection with any activity related to offering goods or services to Data Principals within the territory of India.

2. Check sector rules. Confirm whether enterprise clients operate under RBI or SEBI regulations. These laws impose data localization overrides on top of the DPDP Act baseline.

3. Validate your compliance posture. Global suites often lack the specific evidence trails Indian procurement teams demand. ComplyDP gets B2B SaaS platforms vendor-ready in two weeks so you can close stalled enterprise deals. Scan your current exposure at https://www.complydp.com/audit-preview today.

Sources

Frequently asked questions

Can I store Indian user data on US cloud servers?

Yes. Section 16 of the DPDP Act permits cross-border transfers by default. You can use US or EU cloud infrastructure unless the Central Government formally restricts a specific country via a negative list notification.

Does the DPDP Act require data localization in India?

No, the DPDP Act itself does not mandate data localization. However, if your enterprise clients are governed by stricter sectoral laws like RBI payment regulations, those localization rules override the DPDP Act.

How do cross-border rules affect B2B SaaS procurement?

Enterprise clients audit their supply chain to ensure vendors comply with DPDP requirements. If you cannot produce evidence on demand for Indian consent mechanisms and breach reporting, procurement teams will likely stall the contract.

Is consent required for cross-border data transfer?

Consent is the primary basis for processing, except where Section 7 legitimate uses apply. The transfer itself is part of processing, which must be covered in your itemised notice, but you do not need an isolated consent checkbox just for the transfer.