Free 30-minute AI & automation audit with a senior engineer. You keep the notes. Book yours

DPDP Act Compliance

DPDP Act Compliance Engineering for Apps, Data and Consent

DPDP Act compliance engineering is the work of building the controls that India's Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 require into your actual software: consent capture and records, privacy notices, data-principal rights workflows, retention and erasure, breach intimation and audit logs. MultiGenesys designs and builds these controls into new and existing web, mobile and backend systems, and connects them to the Consent Managers registered with the Data Protection Board. Most Data Fiduciary obligations apply from 13 May 2027, so the engineering work needs to start now.

Regulated healthcare and life-sciences environment

Outcomes

What you get

Ready before 13 May 2027

Notice, consent, security, breach, retention and rights obligations under the DPDP Rules apply from 13 May 2027. We plan the build backwards from that date.

Consent you can prove

Every consent, withdrawal and notice version is recorded with time, purpose and channel, so you can show what a Data Principal agreed to and when.

Rights requests closed on time

Access, correction, erasure, nomination and grievance requests are tracked against deadlines in one queue, instead of across inboxes and spreadsheets.

Evidence for your DPO and auditors

Audit logs, data maps and retention reports give your Data Protection Officer, legal counsel and auditors the records they need without a scramble.

What’s included

DPDP Act Compliance Engineering, end to end

Data inventory and mapping

We map which personal data each system collects, why, where it is stored, who it is shared with and how long it is kept, and turn the map into a maintained register.

Consent capture and records

Itemized notices in plain language, purpose-wise consent, easy withdrawal and a tamper-evident consent ledger exposed through APIs to every app that needs it.

Consent Manager integration

Integration with Consent Managers registered with the Data Protection Board, so Data Principals can give, review and withdraw consent through an interoperable platform.

Rights-request workflows with SLAs

A request portal and back-office queue for access, correction, completion, erasure and nomination requests, with identity checks, deadline tracking and grievance handling within the 90-day ceiling.

Retention and erasure automation

Retention rules per purpose and data class, scheduled erasure jobs, 48-hour pre-erasure notices where the Rules require them, and erasure instructions passed to your processors.

Breach detection and intimation

Logging, alerting and an incident workflow that drafts intimations to affected Data Principals and the Board, tracks the 72-hour detailed report and supports CERT-In reporting.

Children's data and parental consent

Age gating and verifiable parental consent flows for users under 18, plus checks that keep tracking, behavioral monitoring and targeted advertising away from children's data.

Security safeguards and processor controls

Encryption, masking or tokenization, role-based access, one-year log retention, backups, and technical controls and audit evidence for your Data Processors and vendors.

Process

How a DPDP Act Compliance Engineering engagement runs

Clear stages, working software at every step, and the same team from first workshop to production support.

  1. 01

    Step 1

    Assess

    We review your apps, data flows and vendors against the Act and Rules with your legal counsel or DPO, and produce a gap list ranked by risk and effort.

  2. 02

    Step 2

    Map

    We build the data inventory: personal data, purposes, systems, processors, retention periods and cross-border flows, kept as a living register.

  3. 03

    Step 3

    Design

    We design the consent model, notice versions, rights workflows, retention rules and breach runbook, and agree how each control will be evidenced.

  4. 04

    Step 4

    Build and integrate

    We build the consent service, request portal, erasure jobs, audit logging and alerts, and wire them into your web, mobile and backend systems.

  5. 05

    Step 5

    Verify and run

    We test each control end to end, hand over evidence and runbooks, and maintain the controls as your products, vendors and the Rules change.

Why MultiGenesys for DPDP Act Compliance Engineering

DPDP Act compliance is a legal question first and an engineering problem second, and most of the second part lives in code. A privacy notice is only useful if the app records which version a user saw. A right to erasure is only real if a job actually deletes the data from every database, backup policy and processor. We work alongside your legal counsel or Data Protection Officer: they decide what the law requires of your business, and we design, build and evidence the controls in your products. We do not give legal advice.

Our platforms already handle sensitive personal data this way. FinAIQ isolates tenants with PostgreSQL row-level security and keeps audit history tables, soft deletes and role- and folder-level permissions across 79 data entities, while validating GSTIN and PAN details. Sikka Exchange runs document-and-selfie KYC through a purpose-built review console with audit logs and webhook logs. FlexySure captures digital KYC with document upload and national-ID verification, stored on AWS S3.

The timing matters. As of November 2026, the Data Protection Board provisions and Consent Manager registration are in force, and the main Data Fiduciary obligations follow on 13 May 2027. Retrofitting consent, retention and rights workflows into live systems takes longer than most teams expect, especially across backend services, mobile apps and third-party processors. If you are planning the work, start a conversation and we will help you scope it.

Technologies we use

  • Java / Spring Boot
  • Node.js / TypeScript
  • Python
  • PostgreSQL (row-level security)
  • React / Angular
  • Flutter / React Native
  • Keycloak / OAuth2 / JWT
  • Apache Kafka / RabbitMQ
  • Elasticsearch / OpenSearch
  • Prometheus / Grafana / Loki
  • AWS / Azure / Google Cloud
  • Terraform
  • Kubernetes

Engagement models

Work with us the way that suits you

How we work

Dedicated product team

A stable, cross-functional team — engineers, design, QA, DevOps — that owns your roadmap quarter after quarter.

Fixed-scope delivery

A defined build with milestones, demos and a hard definition of done.

Embedded engineers

Senior engineers inside your team, in your tools and your stand-ups, with no hand-over boundary.

Working standards

What you can expect on every project

Engineering standards

Reviewed, version-controlled code

Every change goes through pull requests and peer review in your repository, with a clean history you own.

Automated testing in CI/CD

Unit, integration and API tests run in the pipeline on every change, so regressions are caught before release.

Security by default

Least-privilege access, secrets management, OWASP-aligned checks and environment separation from day one.

Production-ready by default

Idempotent APIs, audit trails, monitoring, alerting, backups and documented runbooks ship with every platform.

Frequently asked questions

Still unsure? Ask us directly — we reply within one business day.

When does the DPDP Act come into force?

In phases. The DPDP Rules, 2025 were notified on 13 November 2025, and the Data Protection Board provisions took effect that day. Consent Manager registration (Rule 4) started on 13 November 2026. The main Data Fiduciary obligations, including notice, consent, security safeguards, breach intimation, retention, children's data, Significant Data Fiduciary duties, Data Principal rights and the penalty provisions, apply from 13 May 2027. MeitY has discussed shortening this runway, so check the latest Gazette notifications.

What are the penalties under the DPDP Act?

The Act's Schedule sets maximum penalties per breach: up to ₹250 crore for failing to take reasonable security safeguards, up to ₹200 crore for failing to notify a personal data breach or meet children's data obligations, up to ₹150 crore for Significant Data Fiduciary obligations, and up to ₹50 crore for other breaches of the Act or Rules.

How quickly must a personal data breach be reported under the DPDP Rules?

Rule 7 requires a Data Fiduciary to inform each affected Data Principal and the Data Protection Board without delay, and to send the Board a detailed report within 72 hours of becoming aware of the breach, unless the Board allows longer. CERT-In's separate six-hour cyber incident reporting direction also still applies.

What does DPDP compliance software need to do?

At minimum it should record consent with the notice shown, let users withdraw consent as easily as they gave it, handle access, correction, erasure, nomination and grievance requests, erase data when the purpose ends, retain logs for at least one year, and support breach intimation. Most organizations need these controls built into their existing apps, not a separate tool alone.

Do we need a Consent Manager?

Not necessarily. A Data Principal may give, manage and withdraw consent through a Consent Manager registered with the Data Protection Board, so your systems should be able to accept consent from one. Many Data Fiduciaries will run their own consent capture as well. We build for both.

Do you provide legal advice on the DPDP Act?

No. We are an engineering partner. We work alongside your legal counsel or Data Protection Officer, who interpret the law for your business, and we build and evidence the technical controls they specify.

Tell us what you’re building. We’ll show you how we’d ship it.

Share a few lines about your project. A senior engineer — not a salesperson — replies within one business day.

Free AI audit Let’s talk