Home / Adjacent engineering
Beyond DPDP

The engineering around DPDP

Personal data does not stop at consent screens. It flows into AI agents, vector databases, APIs, backups and cloud regions. Each of these carries DPDP duties of its own, and each needs engineering, not just policy. These are the adjacent pieces we build and test, always with the Act in view.

How these connect

One record, many places it can leak from.

Follow the red dot from our drawings. A customer's phone number is collected under a notice, copied into a data warehouse, embedded into a knowledge base, read by an AI agent, sent through an API to a vendor, and saved in tonight's backup. DPDP asks you to protect it, honour the person's rights and delete it everywhere it went. Each page here covers one of those places, how we engineer it, and which part of the law it serves.

Book a scoping call