DPDP compliance
Applicability and Significant Data Fiduciary testing, data discovery and records of processing, consent and notice re-architecture, retention schedules, breach response, data principal rights operations.
DPDP servicesProtectHQ scopes, audits, remediates and then operates compliance programmes across several regulated disciplines. Engagements are taken one standard at a time, or combined, as the obligation requires.
Consent Manager registration under Rule 4 and the First Schedule, and the Data Protection Board's powers.
Notice, consent, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties.
Different regulators, different evidence, one recurring failure: a gap report nobody can act on. We stay through remediation and the first year of operation. Each practice is engaged on its own or alongside the others.
Applicability and Significant Data Fiduciary testing, data discovery and records of processing, consent and notice re-architecture, retention schedules, breach response, data principal rights operations.
DPDP servicesAI inventory and use-case triage, Annex A control design, AI impact assessments, risk treatment, internal audit and certification readiness through Stage 1 and Stage 2.
AI governance servicesEntitlement baselining, effective licence position, publisher audit defence, remediation and true-up negotiation support, then a run-state that keeps the position current.
SAM servicesCommissioned separately, the same evidence is gathered more than once by more than one team. Commissioned together, a single inventory and control set answers every auditor. This is an argument for combining them, not a condition of engaging us.
Four phases, applied identically whichever standard is in scope. Each concludes with a deliverable you can put in front of a regulator, a board or a publisher's auditor.
What is in, what is out, and on what evidence. Systems, entities, data flows, contracts, licence estate. Written down and signed off before anyone starts testing.
Control-by-control testing against the statute or the standard, with sampling, interviews and artefacts. Findings rated by exposure, not by how awkward they are to raise.
We draft the notices, build the registers, rewrite the clauses, configure the workflow and sit with your engineers. Owners and dates against every finding.
Rights requests, breach drills, licence reconciliation, control monitoring, management review packs. Either we run it for a term or we train the team that will.
Three practices carry their own method pages. Others we deliver on request, or map alongside an engagement already under way. The register below is maintained as the practice grows.
| Standard or framework | How we take it | What an engagement covers |
|---|
Nothing here is sold as a bundle. A single-standard engagement is complete in itself, and most clients begin with one. Combining them changes what you pay for evidence, not whether we will take the work.
Forty-five minutes, no deck. Tell us what you process, where it sits and what you have already committed to. You will leave with a view of what is genuinely in scope and what it takes to close it.
Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025
The Rules turned principles into dated obligations. Most organisations do not yet know which of them apply, to which systems, or who owns the answer.
This practice is engaged on its own. Clients who also carry ISO/IEC 42001 or software licensing obligations can combine them, but nothing here requires it.
Book a scoping callThe DPDP Act, 2023 set the principles. The DPDP Rules, 2025, notified on 14 November 2025, supplied the mechanics and the calendar. Consent Manager registration and the Board's powers commence a year after notification; the operational obligations — notice, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties — commence eighteen months after, on 13 May 2027.
Consent has to be free, specific, informed and as easy to withdraw as it was to give — which is an architecture problem, not a banner problem. Retention needs schedules with deletion that actually fires. Breach reporting needs a clock that starts before anyone has decided whether it is a breach. And every obligation has to survive an auditor asking for the evidence.
Every system that touches personal data, found and written down — including the ones that never reached the architecture diagram. Scope is signed off before anyone starts testing.
Clause by clause against the Act and the Rules, evidenced from live systems rather than from policy documents. Findings rated by regulatory exposure, with the penalty basis stated.
Consent, notices, retention and breach response rebuilt until they work in production. Every finding closed against evidence, never against an assurance that it has been handled.
Rights requests answered inside statutory timelines, drift caught as systems change, and a board pack that states your position honestly enough to rely on.
The Rules were notified in November 2025 with commencement staged across eighteen months. Two dates matter.
The Rules are made. Nothing commences yet, but the obligations are now fully specified and can be designed against.
Consent Manager registration under Rule 4 and the First Schedule, and the Data Protection Board's powers.
Notice, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties.
Every phase ends with something you can put in front of a regulator, a board or an auditor.
| Phase | Principal deliverable | Who it is for |
|---|---|---|
| Scoping | Scope statement, data inventory, processing record, flow maps | Your programme owner |
| Audit | Gap register against the Act and Rules, with evidence and exposure rating | Risk committee and counsel |
| Remediation | Working controls, documents, contracts and runbooks — not recommendations | Engineering and operations |
| Run | Operating rights desk, drills, re-audit and management reporting | The board, and the Board |
Scope, sequence and fees are agreed in writing before the audit begins.
Each stage carries its own obligation, and two things cut across all of them: a rights request can arrive at any point, and a breach does not wait for you to be ready.
Of the twenty-three rules, most of the operational weight falls in the final tranche — which is also the one organisations tend to treat as distant.
Procedural rules took effect on publication and the Consent Manager framework follows at twelve months, but notice, consent, security, breach reporting, retention, children's data, transfers and Significant Data Fiduciary duties all commence together at eighteen months. That final tranche is where the engineering sits, which is why a programme begun when the deadline feels close has already lost the time it needed.
Your obligations are narrower but not absent, and they arrive through your contracts as much as through the statute. Fiduciaries are pushing security, breach-notification and deletion commitments down to processors now. We scope processor engagements against both the Rules and the contracts you are being asked to sign.
Because consent re-architecture and retention with real deletion are engineering programmes with release cycles attached, not documents. The organisations that will be comfortable in May 2027 began in 2026. The November 2026 Consent Manager commencement also needs the same underlying artefacts: purpose taxonomy, consent records, withdrawal propagation.
Yes. We are tool-agnostic and sell no licences. If you already run a consent or privacy platform we configure against it and tell you honestly which obligations it does not cover.
No. We give assessments, controls and evidence. Where a position needs a legal opinion we frame the question and work with your counsel on the answer.
Most DPDP programmes stall because scope was assumed rather than tested. Start where it matters.
AI governance · ISO/IEC 42001:2023
ISO/IEC 42001 is the first certifiable management system standard for artificial intelligence. It asks what you use AI for, who is accountable for it, and what happens when a system behaves outside its intended purpose.
This practice is engaged on its own. Where DPDP or licensing work is already under way, the control sets are mapped across rather than rebuilt.
Book a scoping callThe familiar management-system shape — context, leadership, planning, support, operation, performance evaluation, improvement — wrapped around AI-specific obligations. Annex A sets out control objectives covering AI policy, internal organisation, resources, impact assessment, lifecycle, data, information for interested parties, use of AI systems and third-party relationships.
Certification follows an independent two-stage audit: a review of the documented system, then an audit of that system operating. Our role is to make both uneventful.
An AIMS does not stand alone. Training data pulls in DPDP. Model hosting pulls in your cloud and security controls. Vendor models pull in third-party risk. If you already run ISO/IEC 27001, most of the governance machinery exists and should be extended rather than duplicated.
We build one control set with multiple mappings, so the same evidence answers the privacy auditor and the AIMS auditor.
Every AI system located, including the ones procurement never saw, and your role for each — developer, provider or deployer — since the obligations differ. A certificate scope you can defend.
Assessed against every clause and every Annex A control objective, with a statement of applicability justified line by line and mapped to the ISO 27001 controls you already run.
Policy, impact assessments, lifecycle gates and human oversight built so a Stage 1 reviewer can follow them without a guide — and so a model can actually be switched off.
Internal audit and management review on the standard's cadence, new use cases assessed inside your release process, and surveillance audits that hold no surprises.
The constraint is rarely effort. It is elapsed time: a certification body needs to see the system operating, not just documented.
A certificate names a boundary. Drawn tightly, the audit stays finite; drawn around the phrase "all AI", it commits you to inventorying every spreadsheet someone calls a model.
Every exclusion needs a stated reason, because a weak one widens the scope mid-audit. Governing a system and certifying it are different commitments: plenty of AI belongs in your inventory without belonging inside the certificate.
You may. Deployers carry obligations around intended use, oversight, monitoring and supplier management. Whether you certify is a commercial decision, usually driven by customers asking. Whether you govern it is not optional once the system touches customers or employment decisions.
For an organisation with an existing ISO/IEC 27001 system and a contained scope, six to nine months is realistic. Starting from no management system, nine to fifteen. The constraint is almost always evidence of the system operating, which takes elapsed time rather than effort.
Preparation and certification are deliberately separate, and should stay that way. We prepare the management system, run the internal audit and support you through both audit stages; the certificate itself follows an independent audit.
The scope statement decides the cost of everything after it. We will help you set one you can actually defend.
Software asset management — ISO/IEC 19770 aligned
Most organisations first establish their licence position inside the response window of a publisher's audit letter. That is the most expensive moment at which to begin.
This practice is engaged on its own, and frequently is — a licence position needs no privacy or AI programme alongside it.
Book a scoping callRarely from deliberate under-licensing. It comes from virtualisation and clustering rules, indirect and digital access, processor-based metrics on hardware nobody re-counted after a refresh, editions upgraded by a feature toggle, contractors left in a directory group, and perpetual estates drifting into subscription terms at renewal.
An entitlement baseline that is maintained rather than rebuilt, discovery that reconciles against it on a schedule, a request-to-deploy path that cannot be bypassed, and a licence position you can produce in a week because it is never more than a month old.
Publishers ranked by spend and by audit likelihood, entitlement sources gathered from contracts rather than portals, and an honest account of what your discovery tooling cannot see.
An effective licence position per publisher with every metric rule and assumption written out, including the virtualisation, indirect access and sub-capacity analysis that creates most exposure.
Reclaim, re-edition and re-host first, then re-run the position — so you negotiate against the corrected number rather than the frightening one in the first draft.
A licence position never more than a month old, deployment controls that cannot be bypassed, and a renewal calendar you arrive at already prepared.
The first number is almost never the final number. Technical remediation comes before any conversation with the publisher.
The expensive mistakes are made in the first fortnight, usually by being helpful too quickly.
No, but the order of work changes. Scope control and data handling come first, the internal position second, and nothing goes to the publisher until you know what it says. Call before you respond.
Eventually, for scale. Not to get a first position. Tools report what they are fed; the entitlement baseline and the metric interpretation are the hard parts, and both are human work. We will tell you when a tool is worth buying and we take nothing from the vendor if you do.
Yes. SaaS waste and licence tier mismatch is usually the quickest money back, and bring-your-own-licence into cloud is where the most unpleasant surprises live.
Start with one publisher. If the number comes back clean, you have lost very little.
How engagements run
Advisory work commonly concludes at the findings report, which is where the work properly begins. These four phases are structured so each is incomplete without the next — and so you may conclude the engagement after any one of them.
Everything expensive downstream is decided here: what is in, what is out, and on what grounds.
You leave with a signed-off scope, an inventory with owners, and a fixed price for the audit — a proposal you are free to take to someone else.
Control by control against the statute or the standard, evidenced from live systems — including an honest note on what we could not test.
You leave with a findings register rated by exposure, root causes rather than symptoms, and a remediation plan sequenced by dependency.
We do the work beside your team rather than supervising it, and close each finding against evidence rather than against an assurance.
You leave with working controls, the artefacts that prove they work, and a closure report mapping every original finding to what changed.
Compliance decays: systems change, people leave, a new product ships with a new data flow. This phase keeps the position current enough for your board to state it honestly.
You leave with an operating calendar, monthly reporting, drills on schedule, and a handover pack written from day one so you can take the work in-house whenever you want to.
They are not four separate projects with four kick-offs. Each one starts before the last has finished, because the handover is where programmes usually lose a month.
A clean audit describes one day. What happens to that position over the following year is the part nobody budgets for.
Nothing deliberate causes the decline. A system is replaced, an integration is added, someone leaves and takes the only knowledge of a manual step with them, a product ships with a data flow that was never mapped.
The run phase is not monitoring for its own sake. It is the difference between a board that can state its position and a board that is repeating what a consultant told it a year ago.
Illustrative shape, not measured data. The pattern is consistent across engagements; the slope is not something anyone can honestly put a number on.
A single named lead in the working sessions, a one-page written status each week, and findings raised the week they are found rather than held for the report. Where your policy requires it, we work inside your systems and your evidence never leaves them.
A sponsor who can settle a scope question in a day, access to the people who operate the systems rather than only those who own them, and whatever contracts and records exist — however messy, since reconstructing them is part of the job. Above all, permission to write down what we find.
A gap report that nobody can act on is an expensive way to document a problem you already suspected.
About
ProtectHQ delivers data protection, AI management system and software asset assurance work for organisations operating in India. It is the professional services practice of KIPIT Consulting Services (OPC) Private Limited.
DPDP, ISO/IEC 42001 and software asset management appear unrelated until you deliver them. Each turns on establishing what you actually hold, evidencing it, closing the distance between the documented state and the real one, and keeping it closed as the organisation changes underneath you. The statute differs; the discipline does not.
It is also why the practice extends to adjacent standards without changing method. The frameworks we currently work in are listed on the home page.
Senior practitioners on the work, and engagements sized so the lead is present throughout. We decline work rather than staff it with people learning the standard on a client programme.
There is no junior bench and no account manager between you and the practitioner testing your controls.
A deadline, an audit letter, a customer questionnaire you cannot answer. Any of those is a fine place to start.
Contact
Forty-five minutes with the practitioner who would run the engagement.
contact@protecthq.in
KIPIT Consulting Services (OPC) Private Limited
F. No. GAL-122, New Town Heights
Sector 86, Narsinghpur
Gurgaon, Haryana 122004, India
CIN U62090HR2024OPC122269
The practitioners
Senior practitioners deliver every engagement, and the person who scopes it is the person who tests your controls.
Buyers of assurance services assess the people before the firm. This page is therefore specific about experience held and the qualifications supporting it.
Works across DPDP compliance and AI governance — applicability and scope at one end, and at the other the control evidence an auditor will actually ask to see. Twenty years in banking and fintech security, so controls are designed for organisations already carrying regulatory scrutiny rather than retrofitted to them afterwards. Also builds the assessment frameworks and audit toolkits the practice runs its engagements from.
Works on the parts of an engagement where something has already gone wrong, or is about to: breach detection and response, security safeguards testing, and the reply when a regulator or a software publisher writes. Twenty years inside global technology companies, which is where the licensing and audit-defence knowledge behind the software asset work comes from. An investigator's eye on assurance — what someone would go looking for, not only what a checklist asks.
Both are reachable at contact@protecthq.in.
A specialist practice is not a volume one. Very large parallel estates take longer with us than with a global bench, certification and legal opinions sit with the bodies and counsel properly responsible for them, and our calendar is a real constraint on start dates.
Stated here rather than discovered at kick-off.
Describe what you are facing and the engagement lead for that practice takes the call. There is no qualification layer to clear first.
Privacy and data handling
We ask organisations to be precise about personal data. The same standard applies to us.
ProtectHQ is the professional services practice of KIPIT Consulting Services (OPC) Private Limited ("we", "us"), CIN U62090HR2024OPC122269, registered at F. No. GAL-122, New Town Heights, Sector 86, Narsinghpur, Gurgaon, Haryana 122004, India. Questions about this page, or about personal data we hold, go to contact@protecthq.in.
Our role depends on the data involved. For personal data we collect about our own contacts, prospects and clients, we act as a Data Fiduciary and determine the purposes of processing. For personal data we encounter inside a client engagement, we act as a Data Processor on that client's documented instructions, under the engagement letter and the data processing terms attached to it. We do not use client personal data for our own purposes, and we do not use it to train models.
When you write to us or book a call, we hold your name, organisation, contact details and whatever you choose to tell us about your situation. We use it to respond, to prepare a proposal and to maintain our client and prospect records. The lawful basis is the consent you give by making contact, and, once an engagement starts, the legitimate uses associated with performing it.
Everything we learn on an engagement is confidential, including the fact of the engagement itself unless you agree otherwise. We do not name clients in marketing, proposals or case studies without written permission. Every member of the team is bound by individual confidentiality undertakings that survive the engagement.
If personal data we process for you is compromised, we will notify you without undue delay and in any case within 24 hours of becoming aware, with what we know, what we are doing, and what you need to decide. Where we are the Data Fiduciary, we will notify affected individuals and the Data Protection Board as the Rules require.
Where we hold personal data about you as a Data Fiduciary, you may ask for a summary of it, ask us to correct or complete it, ask us to erase it where we have no continuing need, nominate another person to exercise your rights, and withdraw consent at any time. Write to contact@protecthq.in and we will respond within 48 hours.
Where your personal data reached us through a client engagement, we are a processor and cannot act on a request directly. Contact that organisation, or tell us and we will route the request to them.
If you are not satisfied with how we have handled a request or a complaint, write to our grievance officer at contact@protecthq.in. If the matter remains unresolved, you may approach the Data Protection Board of India.
We will update this page as our practices or the law change, and the date below will move. Material changes affecting an active engagement are communicated directly, not by a website edit.
Last updated 27 October 2026. This page describes our practices; it is not legal advice.
Terms of service
These terms cover the use of this website and the general basis on which we provide professional services.
This website and the ProtectHQ practice are operated by KIPIT Consulting Services (OPC) Private Limited, CIN U62090HR2024OPC122269, registered at F. No. GAL-122, New Town Heights, Sector 86, Narsinghpur, Gurgaon, Haryana 122004, India. "We" and "us" mean that company. "You" means a visitor to this site or a client engaging us.
Nothing on this website is an offer capable of acceptance. Our services are provided only under a signed engagement letter or statement of work, which sets out scope, deliverables, fees, timelines and responsibilities. Where anything on this site conflicts with that document, the engagement letter prevails.
Our work depends on the completeness and accuracy of what you give us. You agree to provide timely access to relevant people, systems, contracts and records, and to tell us about anything that materially affects the engagement. We are not responsible for conclusions that prove wrong because material information was not disclosed to us.
Fees, milestones, the invoicing schedule, payment terms and any charge for late payment are set out in the engagement letter for each engagement. Taxes are charged in addition at the applicable rate, and out-of-pocket expenses are charged at cost with prior approval.
On full payment, you own the deliverables prepared specifically for you and may use them freely within your organisation. We retain ownership of our methods, templates, frameworks, tooling and general know-how, including anything we developed before the engagement or independently of it, and we may continue to use the skills and experience gained. Our deliverables may not be distributed outside your organisation, or relied upon by a third party, without our written consent.
Each party will keep the other's confidential information confidential and use it only for the engagement. Our handling of personal data, security measures, sub-processors and retention are described on our privacy and data handling page and in the data processing terms attached to the engagement letter.
We check for conflicts before accepting an engagement and will tell you if one arises during it. We may work for organisations in the same sector, including competitors, provided confidentiality is maintained and no conflict exists. Where we have prepared a management system, we will not later purport to provide independent third-party certification of it.
Our aggregate liability arising out of or in connection with an engagement is limited to the amount set out in the engagement letter for that engagement, except for liability that cannot be excluded by law, including fraud and wilful misconduct. Neither party is liable for indirect or consequential loss, or for loss of profit, revenue, goodwill or anticipated savings.
Either party may terminate an engagement on 15 days written notice. You remain liable for fees for work performed and commitments reasonably incurred up to termination. On termination we will hand over work product completed to that point and deal with your material as the privacy page describes.
The content here is provided for general information. It describes regulatory regimes in general terms and may become out of date as law, standards and guidance change. It is not advice, and you should not act on it without taking advice on your own situation. We do not warrant that the site will be uninterrupted or error free. The site's content, design and marks are ours and may not be reproduced without permission.
Where we link to other sites, we do so for convenience. We do not control them and are not responsible for their content or their handling of your data.
We may update these terms. The version in force for an engagement is the one in effect when the engagement letter was signed, unless both parties agree otherwise in writing.
These terms and any engagement are governed by the laws of India, and the courts at Gurgaon have exclusive jurisdiction, subject to any dispute resolution clause agreed in the engagement letter.
Questions about these terms: contact@protecthq.in.
Last updated 27 October 2026.