Holistic DPDP: Scope and Evidence
See how legal review, technology changes, and team processes fit into a DPDP programme. Map the work, assign owners, and review the evidence.
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 Holistic DPDP: Scope and Evidence, 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.
Connecting Legal and Technical Proof
- Start with one customer or employee journey. Record where personal data enters, why it is used, which systems hold it, and who receives it.
- Ask the legal, technology, and operating teams to review the same map. Compare the documented process with what the systems and staff actually do.
- Give each gap an owner, a proposed fix, and evidence needed to check the result. This creates a shared implementation plan.
Common Operational Mistakes
- A notice changes while an older version remains in a form or app.
- Staff export records into folders outside the agreed access controls.
- A vendor receives data through an integration that is missing from the map.
- A retention decision is recorded without a process to carry it out and verify it.
Data Workflows and Evidence
| Work Area | Data or Process | Evidence to Review |
|---|---|---|
| Legal | Notices and vendor terms | Agreed scope, versions, and review decisions |
| Technology | Databases, logs, and integrations | Access settings and change records |
| Marketing | Lead lists and campaign tools | Collection source and preference handling |
| HR | Employee records and payroll | Access, sharing, and retention decisions |
| Support | Requests and support tickets | Intake, verification, and response records |
Retention and Analytics Decisions
- List the purpose and retention decision for each data category. Ask the responsible advisers to check any applicable retention duties before implementation.
- For a withdrawal or deletion request, identify the affected purposes and systems. Record what should stop, what may need to be retained, why, and how the response will be checked.
- Include backups, exports, vendors, and analytics datasets in that review. Record any limits or outstanding work in the final assessment.
This week
- Choose one CRM or email tool. Compare a real data flow with its notice, vendor terms, access settings, and retention process.
- Record one gap, its owner, and the evidence that will show the fix works.
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
How do we link privacy policies to technical systems?
Map each data flow to its purpose, the notice shown, the systems involved, and the people who operate it. Review the policy and system behaviour together, then record any changes and their owners.
What evidence should we prepare for an assessment?
Bring the notices, relevant consent records, access settings, vendor documents, retention decisions, and examples of completed requests. The assessment scope determines which evidence is needed and what remains unverified.
How long does the programme take?
Gap assessment takes four weeks. Implementation takes two to three months, followed by a final assessment.