DPDP & Data Protection
Turn data-protection obligations into operating responsibilities
India’s Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025 follow a phased commencement schedule — the engagement maps requirements to the dates and notifications applicable to you at the time.
The business problem
Where DPDP pressure usually comes from
-
Obligations on a phased schedule
The DPDP Act, 2023 and DPDP Rules, 2025 commence in phases, and it isn’t always clear which requirements apply to the organization, and from when.
-
Personal data no one can fully locate
Data sits across systems, vendors, and teams. If it can’t be located, consent can’t be honored reliably and deletion can’t actually be executed.
-
A privacy notice standing in for a program
A notice has been published, but consent withdrawal, data-principal requests, processor oversight, and retention still depend on processes that haven’t been built.
-
Ownership shared by everyone and held by no one
Engineering, product, HR, procurement, and customer support all touch personal data, but responsibility for the obligations isn’t assigned to any of them.
Overview
What DPDP readiness is meant to achieve
Compliance isn’t a privacy notice. If personal data can’t be located, ownership is unclear, or deletion can’t actually be executed, policy alone won’t resolve the exposure — notices, consent, individual requests, processor oversight, safeguards, and retention all depend on processes and systems working together, and on clear ownership across the functions that actually touch personal data: engineering, product, HR, procurement, and customer support.
Secalyx starts with the data, not the policy: a factual processing inventory — categories, purposes, systems, vendors, flows — that supports every later decision about notices, consent, retention, security, and data-principal rights. Collection is limited to data needed for the stated purpose, and every processing activity is traced back to a documented basis.
Secalyx provides operational and security advisory support and works alongside your legal counsel, who confirms legal positions and regulatory obligations.
Scope
What the engagement covers
Scope, responsibilities, timeline, and expected outputs are agreed in writing before work begins.
Processing inventory
Categories of personal data, sources, purposes, systems, and third parties involved, with collection limited to data needed for the stated purpose.
Rights and consent operations
Notices, consent mechanisms, consent withdrawal handling, and data-principal request procedures.
Processor and transfer governance
Contracts, due diligence, security expectations, and oversight of parties processing personal data on your behalf, including cross-border transfer decisions where applicable.
Retention, deletion, and security safeguards
A retention and deletion control plan based on schedules approved by the organization and its legal counsel, backed by access control, encryption, and monitoring for personal data specifically.
Operational ownership
Assigning responsibility for data-protection obligations across engineering, product, HR, procurement, and customer-facing teams, so the program doesn’t rely on one function.
Process
Where DPDP obligations attach
Personal data creates a different obligation at each stage of its life, and a different owner within the organization — this is where DPDP requirements attach to your actual data flow and to the teams that run it.
-
01
Collect
notice, consent, purpose-limited collection
-
02
Use
purpose limitation, access control
-
03
Share
processor terms, third-party oversight
-
04
Protect
security safeguards, breach response
-
05
Respond
data-principal requests, grievances
-
06
Retain & Delete
approved schedules, verified disposal
Deliverables
What you receive — and why it remains usable
Outputs
- DPDP operational-readiness assessment
- Personal-data inventory and flow map
- Notice and consent-control requirements, including consent withdrawal handling
- Data-principal request and grievance workflow
- Processor and third-party governance requirements
- Retention and deletion control plan based on schedules approved by the organization and its legal counsel
- Breach response procedure
- Evidence register
- Ownership and accountability matrix across functions
How Secalyx works
- Technical, operational, and contractual gaps considered together, not fixed in isolation.
- Findings prioritized by data sensitivity and volume, not a uniform checklist.
- Program built to remain usable as vendors and processing purposes change.
- Legal interpretations confirmed by your qualified counsel.
- Ownership assigned by function, not left as a shared responsibility no one actually holds.
Questions
Frequently asked questions
What does DPDP readiness involve?
Building a factual inventory of personal data — categories, purposes, systems, vendors, and flows — and then the notices, consent, retention, security, and data-principal rights processes that rely on it.
Who confirms the legal position?
Your qualified legal counsel confirms legal interpretations and regulatory obligations. Secalyx provides the operational and security advisory work that puts them into practice.
Does this help with GDPR as well?
Many of the same controls — data inventory, purpose limitation, retention, and security — support both. Where GDPR applies, its specific obligations are mapped alongside the DPDP Act, 2023.
How do we start?
Book a consultation and share the customer question or obligation behind the work. Scope, responsibilities, timeline, and expected outputs are agreed in writing before work begins.
Need to turn DPDP obligations into an operating plan?
Tell us the requirement, deadline, or pressure you are dealing with.