REGION:ap-south-3·
DataDack CloudDataDackcloud
Back to all articles

Understanding Indian DPDP Act Compliance for Cloud & SaaS Workloads

What the DPDP Act asks of a cloud workload, and what hosting in Noida actually covers. Consent and retention stay with the application. Residency is the part the region provides.

DataDack Compliance & Security

DataDack Compliance & Security

Legal, security, and cloud compliance engineering team at DataDack.

April 9, 20263 min read
Understanding Indian DPDP Act Compliance for Cloud & SaaS Workloads

Understanding the DPDP Act for a workload in India

The Digital Personal Data Protection Act, 2023 governs how an organisation collects, processes, stores and protects the personal data of people in India. It covers consent, purpose limitation, security safeguards and cross-border transfer. Hosting in India does not, by itself, make an application compliant. It removes the residency question from the review.

The longer note is the DPDP page. This essay is the version a buyer can read before that page.

What stays yours

You are the data fiduciary for the product you run. That means:

  • Collect personal data with clear consent, and use it for the purpose you stated.
  • Keep it only as long as that purpose needs, and be able to show the safeguards.
  • Honour the rights of the person the data is about, including erasure when the Act requires it.

None of those is a setting in the console. They live in the application.

What the region covers

Compute and storage on DataDack run in Noida (ap-south-3), in Yotta NM1 & CtrlS, Noida Tier-IV. There is no cross-border replication, so a disk, a snapshot and a backup of personal data stay inside Indian borders by default. The region is a single place, which is what makes a residency answer short: there is no second country to account for.

Around that, the platform includes:

  • Always-on L3/L4 DDoS protection on the address.
  • Private VPC networking, so the database does not have to sit on a public subnet. Traffic between subnets in the VPC is ₹0/GB.
  • Encryption at rest, and tenant isolation between accounts.

Tenant bandwidth is 1 Gbps shared. That is a capacity fact, not a compliance one. It does not change where the bytes are stored.

What this is not

An older version of this post claimed a private fibre path that never touches a foreign relay, and storage APIs that track consent and erase data on demand. Those are not product features. Do not design a control around them.

SOC 2 Type II is in progress. A security-posture pack for procurement is available on request from the contact page. A Business Associate Agreement is available on request for enterprise plans.

A practical split

QuestionWho answers it
Where is the disk?Noida. DPDP page
Who can reach the database?Your VPC and security groups. VPC
Did the user consent?Your application
How long do you keep a row?Your application
Can you show the safeguards?The region, plus the documentation you request

If the review is really about a regulated deployment — BFSI, healthcare, public sector — start from the enterprise use case and the DPDP page, not from a blog sentence.

From this article

The post explained it.The console runs it.

Nothing in the article is a different price or a different credit. ₹1,000 in free credit on signup is the signup offer, applied in the console.

  1. 01One credit, the same as the homepage
  2. 02Rates mentioned here are catalogue rates
  3. 03Noida is the region you land in
Noida liveap-south-3
₹1,000free credit on signup
No credit card required • Instant access
  • Instant API & web console access
  • No card required for sandbox
  • 30-minute architecture assist