DPDP Cross-Border Data Transfer Rules
DPDP Section 16 restricts international data transfers to approved jurisdictions. Get expert help today.
Discuss this page with an LLM
DPDP Action Sheet
Use this before your next workflow goes live. It keeps the useful parts visible and turns DPDP into checks your team can actually answer.
For DPDP Cross-Border Data Transfer Rules, the DPDP question is how personal data enters the workflow, where it is stored, which tools touch it, what purpose was explained, and how deletion or withdrawal will work.
1. Lead Forms
Check:
- What data are you collecting?
- Is the purpose clear at the point of collection?
- Is marketing consent separate from service communication?
- Can the user withdraw consent later?
Common mistake: one checkbox that silently covers newsletters, sales calls, partner sharing and remarketing.
2. Email and WhatsApp
Check:
- Who is on the list?
- Where did consent come from?
- Is the list imported from a vendor, event, webinar, scrape or old CRM?
- Can you prove the source of consent?
Common mistake: treating every lead as permanently marketable.
3. Ads and Retargeting
Check:
- Are pixels or ad platforms receiving identifiable user behavior?
- Are audiences built from customer lists?
- Are lookalike or remarketing audiences using personal data?
Common mistake: assuming "the ad platform handles it" means your company has no DPDP responsibility.
4. Website Analytics
Check:
- Which tools run on the site?
- Are IP address, device identifiers, session IDs or form fields being captured?
- Is analytics used only for measurement, or also for profiling and targeting?
Common mistake: installing tools first and asking privacy questions later.
5. Vendor List
Make a quick list:
- CRM
- Email platform
- WhatsApp provider
- Analytics
- Ad pixels
- Form tool
- Landing page builder
- Webinar tool
For each vendor, answer: what data goes there, why, who can access it and how deletion works.
6. This Week's Action
Map one campaign from first click to final follow-up. Mark every place personal data is collected, enriched, shared, uploaded or used for targeting.
If your team cannot answer where the data came from and where it goes next, start with a data flow map before rewriting policy copy.
Book a DPDP clarity callWant all of this handled, end to end? Sanctum is the all-in-one DPDP compliance programme behind this site: legal position, data map, gap analysis, implementation, tooling, training, readiness opinion, and breach cover under one accountable owner. How all-in-one DPDP compliance works or see the Sanctum programme.
Regional Restrictions and Negative Lists
The Indian government maintains a “negative list” of countries where personal data cannot be transferred. Unlike older laws that required specific contract clauses for every country, DPDP focuses on where the data lands. You must verify if your cloud storage regions or offshore processing centers sit within a restricted territory. If a country is blacklisted, no amount of user consent allows the transfer.
Sectoral Overrides for Data Localization
DPDP does not cancel out existing Indian laws that require data to stay within borders. If you operate in banking, insurance, or payments, you must still follow RBI or IRDAI localization rules. Even if DPDP permits a cross-border transfer to a specific country, your industry-specific regulator might still require the primary copy of that data to reside on servers physically located in India.
Cross-Border Workflow Risks
| Workflow Area | Personal Data Involved | DPDP Transfer Risk |
|---|---|---|
| Global SaaS Analytics | User behavior, device IDs, IP addresses | Silent transfer to foreign servers for processing |
| Offshore Tech Support | Customer names, troubleshooting logs | Unauthorized access from a restricted geography |
| Centralized HR Payroll | Employee PAN, bank details, salary info | Storage in a foreign parent company’s database |
| Third-Party Cloud CRM | Lead contact info, purchase history | Hosting data in a region on the government’s negative list |
This week
Map your data’s physical path by checking the “Data Residency” settings in your CRM and cloud storage accounts. Identify the specific country where your primary and backup servers are located to ensure they are not in a restricted region.
Now think about your work. Where does personal data enter your workflows? Where does it sit? Who else touches it?
Frequently asked questions
Does DPDP require me to keep all data inside India?
No, DPDP generally allows data transfers to most countries unless they are specifically blacklisted by the Indian government. However, you must still comply with stricter localization rules if your specific industry regulator, like the RBI, demands it.
Can I transfer data to a foreign vendor if the user says yes?
User consent does not override government restrictions. If the Indian government places a country on the negative list, you cannot send personal data there even if the individual provides explicit permission.
How does DPDP treat remote access by a global team?
DPDP views remote access from outside India as a cross-border transfer. If a team member in another country views personal data stored on an Indian server, that interaction must comply with the same transfer rules as physical data migration.