One-Stop DPDP: Scope and Ownership
Compare a one-stop DPDP programme by scope, responsibilities, and evidence. See what to agree across legal review, implementation, and ongoing support.
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 One-Stop DPDP: Scope and Ownership, 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.
Reducing Coordination Work
- A one-stop programme gives the buyer one place to coordinate the agreed legal, technology, and operating work.
- The scope should identify who provides each part, who makes decisions, and how dependencies are resolved.
- Compare providers using the work and evidence they will deliver. Record the actions your own team still needs to complete.
The Contact Plan for Incidents
- Agree who receives an incident report and who can reach the relevant systems and vendors.
- Document who assesses the facts, who approves decisions, and who handles communications or notifications when required.
- If ongoing incident support is part of the engagement, define its hours, response expectations, and limits. Test the contact route before relying on it.
Working Through Retention Dependencies
- Map live records, exports, vendor copies, and backups. Ask the responsible advisers to review the retention needs and any exceptions.
- Agree how each system will apply the decision and how restored backups will be handled.
- Record technical limits and the evidence needed to check the result. A proposed deletion method needs review against the actual system and duties involved.
Consolidated Compliance Workflows
| Work Area | Records Involved | Scope Question |
|---|---|---|
| Preference handling | User reference, notice, preferences | Who checks connected systems? |
| Incident response | Access logs and incident records | Who gathers evidence and approves actions? |
| Vendor review | Data flows and service terms | Who resolves gaps with the vendor? |
| Data mapping | Systems, fields, and purposes | Who maintains the map after changes? |
| Data requests | Request and response records | Who coordinates the full response? |
This week
- List the current owners of legal review, data mapping, implementation, and support.
- Identify one handover where responsibility is unclear. Add an owner, a decision route, and a review point to the scope.
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
What should a one-stop DPDP contract make clear?
It should identify the entities, systems, work, deliverables, responsibilities, dependencies, and review points included. Ask how legal advice, implementation, tooling, and support are provided and which costs or services need separate agreement.
Who is the accountable programme owner?
The programme owner coordinates delivery and escalation across the agreed work. Your business supplies the internal decision-makers and access needed. Confirm any statutory roles and legal responsibilities separately with your advisers.
Does the programme include breach support?
Check the written scope. If ongoing breach support is included, agree the contacts, availability, evidence access, decision rights, and response responsibilities before an incident.
How long does the programme take?
Gap assessment takes four weeks. Implementation takes two to three months, followed by a final assessment.