Pune mixes automotive and industrial manufacturing with a large IT services base and a substantial education sector. Manufacturers in particular tend to assume DPDP is somebody else's problem because they sell to businesses — and then discover personal data in dealer networks, service records, warranty registrations and the plant's own HR systems.
For a B2B manufacturer the personal data is real but scattered: end-customer details captured at dealer level, service and warranty histories tied to named owners, and contractor and workforce records at the plant. None of it sits in the systems a privacy programme would look at first.
Education institutions here face a sharper version of the children's-data question, because a significant portion of their records relate to minors and carry additional obligations.
ProtectComply is built by Exuverse, whose team sits in Noida. We work with organisations across India — remotely for most of a programme, in person when discovery or a workshop genuinely needs it.
Yes. Even where the customer is a business, manufacturers hold personal data through dealer networks, service and warranty records, contractor rosters and their own workforce systems.
Records relating to children attract additional duties, including verifiable parental consent and limits on tracking and targeted advertising, so paediatric or student records must be identifiable as such in your inventory.
Dinkar Singh — Dinkar covers privacy engineering at ProtectComply — discovery, consent propagation and the evidence trail behind them.
Take the free readiness check and find out in 10 minutes.
Start free readiness check →