The DPDP Rules are phasing in through 2026 and 2027. Organisational compliance is mandatory by 13 May 2027.

What this means for you

Home / Engagement

How the work runs, from first call to handover.

The work runs as a sequence of steps, scoped at the outset. How many steps apply and how deep each one goes, depends on your business, what you tools you run, and what infrastructure you already have for compliance. We make these decisions with you, keeping your business needs at the centre.

Scope is agreed before the start

You know which steps apply, what each produces and what we need from your team before any invoice exists.

Decisions stay with you

Where a choice is genuinely open, we write up the options and the risks. Your leadership decides and we record it.

Steps can run in parallel

Drafting often begins while discovery finishes in a quieter corner. The sequence helps you guide the work.

Before any assessment work, we establish that we can act for you, write down what we are doing, and name the people on your side who will own each part of it. Engagements that skip this step stall halfway through because nobody is clear who decides.

This is also where we flag anything that would change the shape of the work, such as a group structure, a parent company abroad, or an existing adviser already handling part of the picture.

What you receive

Conflict and matter check

A short note confirming we can act for you, covering your group entities, funders, major vendors and any connected parties.

Engagement letter and scope

Which steps apply, what each produces, what we need from you, the fee for each, and how changes to scope get agreed.

Governance charter

Named owners for each area: who signs off decisions, who handles complaints, who runs the systems, and who we contact when something is unclear.

Kick off plan

The interview schedule, the systems we will need access to, and the dates each step is expected to close.

This is the step that does the real work. We interview the people who actually use each system, not only the people who own them, because the gap between the two is where unrecorded data usually lives. Sales keeps a personal spreadsheet. Support runs a WhatsApp group. Someone built a form in 2022 that still collects responses.

By the end of it you have a written record of every activity in the business that touches personal data, which almost no small or medium business has before starting.

What you receive

Record of processing activities

One row per activity: what data, about whom, for what purpose, from where, who receives it, where it is stored, how long it is kept and who owns it.

Data flow diagrams

Diagrams showing how data moves through your business, from the moment it is collected to the moment it should be deleted.

Vendor and tool register

Every third party that receives personal data from you, what they receive, and what your contract with them currently says about it.

This step tells you what your current arrangements actually achieve. We take each activity from the map and work out whether the way you collect, use and share that data is genuinely supported by what customers were told and what they agreed to.

Most of the uncomfortable findings surface here. A consent box that covers three unrelated things; a notice that does not mention the vendor who receives the data, and so on. We write down what is actually true, with the reasoning, so the fixes that follow are aimed at something real.

What you receive

Activity by activity analysis

Each processing activity assessed against what currently supports it, with the reasoning recorded so your team can follow it later.

Consent quality review

What your consent mechanisms actually capture, whether they are bundled, whether anyone can withdraw, and what records exist of who agreed to what.

Records about children

Where your business holds data about anyone under eighteen, what permission exists, and what needs to change. Prepared where this applies to you.

Marketing and profiling review

How your lists were built, what your advertising tools collect, and whether what you tell people matches what the tools actually do.

This is the largest step, and it is where most of the value sits. We write the documents your business needs, built from your own data map rather than from a template.

Not every item below applies to every client. A business with no customers under eighteen does not need to address verifiable parental consent. The scope agreed at the start decides what gets drafted.

What you receive

Rewritten privacy notice

Built from your actual processing record, consistent with every notice you use, in English and one further language where you need it.

Internal data protection policy

How your own team handles personal data: access, sharing, devices, exports, corrections and what to do when someone asks a question.

Rights and grievance procedure

How a request to see, correct or delete data gets received, checked, actioned and logged, with response templates and timelines.

Vendor contract terms and checklist

Data protection terms to add to each your vendor agreements, plus a checklist for assessing the next vendor before you sign.

Breach response plan

Who does what in the first hours, what gets recorded and communicated, with communication material tailored to you.

Retention policy

How long each category of data is kept, what triggers deletion, how deletion happens and who is responsible for running it.

Documents on their own change nothing. Someone has to build the consent screen, configure the deletion job, close the old access and update the website. This step turns the drafted material into a list of tasks your developers or vendors can actually pick up.

We stay available while that happens, reviewing each item as it goes live rather than discovering at the end that the consent screen records the wrong thing.

What you receive

Implementation tracker

Ticket level tasks for consent capture, logging, deletion, access changes and notices, each with an owner and a deadline.

Consent and verification flow specification

Exactly what each screen asks, what gets stored when someone agrees, and what happens when they change their mind.

Tool selection

Where a tool is genuinely needed, a shortlist with the trade offs. If your existing setup is enough, we record it.

Custom tools

We build specific tools to address your business needs to achieve compliance goals.

The last step tests whether any of this work holds. We train the people who access personal data, then run the new processes against realistic situations.

How to deal with a deletion request? What happens when a laptop is lost on a Friday evening? What fails gets fixed or recorded as an open item with a date.

What you receive

Training materials and attendance record

A short session for all staff and deeper sessions for the people handling requests, data exports or vendor relationships.

Assurance and test report

Results of the breach exercise, the test requests and the withdrawal test, with anything that failed written down and assigned.

Close out report

What was done, what risk remains, what is still open, and an index pointing to every document produced during the engagement.

Review calendar

What to check and when, so the work stays current after we step away.

A stronger foundation that achieves DPDP compliance

End to end or modular, your choice. All the steps listed above can run as a single engagement or stand alone as independent modules. The first conversation establishes what you need, and the engagement letter records that.

Critical for compliance

Breach response

Something goes wrong eventually. A laptop is left in a cab, a vendor emails a spreadsheet to the wrong address, or an old server turns out to have been reachable for a month. Most of the damage comes from the hours afterwards, when nobody is certain on what to do.

We build the plan before you need it, as part of Compliance Support. It names the people who act in the first hours, and fixes what gets recorded at each point. We draft the notification letter templates specific to your business and we run one practice exercise with your team against a scenario drawn from your own systems.

What you receive
Breach response planWho is called first, who decides, who speaks to affected people and who files the notification, with a named substitute for every role.
First hours checklistOne page for whoever takes the call: what to contain, what to preserve, what not to delete, and what to write down while it is still fresh.
Notification templates specific to youAn e-mail to the affected people and the notification to the Data Protection Board of India, drafted to ensure that you have processes in place for a bad day.
Incident registerA record of every incident, including the ones that turn out to be nothing, carrying the assessment that decided whether it had to be reported.
Practice exercise and findingsOne run through a realistic scenario with your team, and a short note on where it stalled and what we changed because of it.
Critical for compliance

Data Subject Rights Requests

The law allows people to ask to see their data, correct it, or have it deleted. Your own staff can ask about their personal data that you have collected, and so can a parent on behalf of their child. Every request starts a clock, and a request that sits unaddressed in an inbox for weeks is a cause of action for Data Protection Board of India to pull you up.

We build the route that receives them. It is drafted during Compliance Support and tested during Implementation support, so that by handover a request arriving at your published address reaches a named owner, gets checked against identity, gets actioned across every system holding a copy, and gets answered inside the timeline.

What you receive
Request handling procedureThe route from arrival to answer: where requests land, who owns them, how you confirm the person is who they say they are, and what to do when you cannot.
Response templatesA prepared reply for each kind of request, including the ones you are entitled to refuse, with the reason written in language the person will understand.
Request registerA log of what was asked, what you did and when. This is what you produce if anyone asks whether you actually answer people.
Deletion mapWhere each category of data really lives, including backups, exports and vendor systems, so erasure reaches every copy rather than the first one you find.
End to end testWe submit live requests as a member of the public before handover, then record how long each one took and where it got stuck.
Added where needed

Modules that attach to the engagement.

Some businesses need more than the core sequence. These attach to the relevant step rather than running separately, and each is agreed before it starts.

Optional

Periodic review

A set number of hours each month for escalations, new tools, new activities and a scheduled check that what we built is still being followed.

Optional

Plain language explainers

A short notice and script written for the people whose data you hold, including customers, parents or members, rather than for their lawyers.

Optional

Full impact assessments

A detailed evaluation of a product with a complete data risk assessment covering who could be harmed, what reduces that, and what alternatives exist.

Optional

Training the trainers

A facilitator guide and two sessions with your internal trainers, so you can run induction for new staff without bringing us back each time.

Optional

Data sharing programme

Where you share data with partners, sponsors or group companies, a sharing agreement, a due diligence checklist and rules on what may be shared.

Optional

Extended assurance testing

Unannounced test requests submitted as a member of the public, sampling of your consent records, and testing if a vendor can actually return your data.

Next

Find out which of these steps your business needs.

A thirty minute call is enough to tell. You leave knowing the three gaps that matter most, whether or not you engage us.