DPDP Guide for Customer Data Platforms
Manage identity resolution, event streams, and audience sync while complying with India's DPDP Act for customer data platforms.
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 Guide for Customer Data Platforms, 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.
Identity Resolution and Purpose Limitation
Customer Data Platforms (CDPs) merge data from websites, apps, and CRM systems to create a unified profile. Under DPDP, you cannot stitch data for a new purpose without a clear notice. If you collected an email address for a newsletter, you cannot use it to link a user’s offline store visits unless the original notice explained this identity resolution step. Every data point in a profile must be tied to a valid consent or a specific legitimate use.
Downstream Sync and Consent Management
When a CDP syncs an audience segment to an ad platform or email tool, the CDP is the central control point. DPDP requires you to ensure that every downstream tool follows the user’s current consent preferences. If a user withdraws consent in your mobile app, your CDP must automatically remove that user from all synced marketing lists. You are responsible for ensuring that external vendors do not continue processing data after a user has opted out.
| Workflow Area | Personal Data Involved | DPDP Risk |
|---|---|---|
| Identity Resolution | Email, Phone, Device ID, CRUID | High |
| Event Tracking | Clickstreams, IP Address, Location | Medium |
| Audience Segmentation | Behavioral traits, purchase history | High |
| Downstream Sync | PII exported to AdTech/MarTech | Very High |
| Profile Enrichment | Third-party data append | High |
Retention and Event Stream Expiration
DPDP requires data deletion once the specific purpose for processing is met. CDPs often store historical event logs for years to build long-term behavioral models. You must set automated expiration dates for these event streams. If a user profile has been inactive for a period longer than necessary for your business purpose, the Act requires the deletion of that profile and all associated event data.
This week
Map every destination in your CDP. List every external tool receiving data via downstream sync. Confirm that your “delete” or “opt-out” signals are successfully reaching these tools and removing the users from their active databases.
Need help applying this to your business? Review the consulting scope and bring the systems, teams, and data flows involved to your first call. If you already have a gap assessment, see implementation support.
Frequently asked questions
Does DPDP apply to anonymous device IDs in a CDP?
Yes. If an ID can be linked to a specific person through identity resolution, it is personal data. You must manage consent for these IDs just like names or phone numbers.
How do we handle consent for historical data in the CDP?
You must check if the original consent covers your current processing. If the purpose has changed, you need to issue a fresh notice to those users before continuing.
Can we sync CDP audiences to international marketing tools?
Yes, provided the Indian government has not restricted transfers to that country. You must ensure the receiving tool follows the data processing instructions in your contract.