An IT services company meets the DPDP Act from two sides. It is a Data Fiduciary for its own employees, candidates and customer contacts. And it is a Data Processor for every client whose systems or data it touches — which means clients will start asking for proof well before the Board does. This checklist covers both.
Know what you hold
- 1. A register of personal data. Each system, what personal data it holds, whose it is, why you have it and who can see it. Include client environments you can access.
- 2. A classification. Mark what is sensitive in practice — identity documents, bank details, health information, children’s data — so the stronger controls go where they matter.
- 3. A retention period for each kind of data, and a way to delete it when the period ends.
Protect it
- 4. Access by role, with two-factor sign-in, and a record of joiners, movers and leavers.
- 5. Encryption in transit and at rest, and masking where full values are not needed.
- 6. Logs kept for at least one year on every system holding personal data, with someone reviewing them.
- 7. Backups, and a restore test with a date on it.
Be able to respond
- 8. An incident routine that produces the two notices the law requires — to the Board and to affected people — with a detailed report inside 72 hours. Rehearse it once.
- 9. A named contact and a grievance channel that answers within 90 days, published where people can find it.
- 10. A way to handle requests for access, correction and erasure, tracked to a deadline.
Control the chain
- 11. Vendor contracts with security, breach-notice and erasure clauses, and a register showing each vendor was checked and is rechecked.
- 12. For your clients: a standard processor addendum you are willing to sign, and the evidence to back it — certificates, policies, training records, audit reports.
What clients will ask you for
Expect a questionnaire. The common questions are where the data is stored, who can access it, how quickly you would report a breach, whether staff are trained, whether you use sub-contractors, and what independent assurance you hold. Each of the twelve items above answers one of them. A company that can send the evidence the same day wins the renewal over one that needs three weeks.
What this list does not cover
Notice and consent. If you collect personal data directly from the public — through a website, an app or a form — you also need plain-language notices and a consent mechanism that can be withdrawn as easily as it was given, and a parental-consent process if any users are children. That is a product and legal design task of its own, and it sits in the customer-facing application, not in your back office.
How long it takes
For a company of fifty to five hundred people with reasonable security already in place, the twelve items are three to five months of part-time work, most of it in the register and the vendor contracts. Starting in the first quarter of 2027 is cutting it fine.
- How do I start preparing for the DPDP Act?
- Begin with a register of the personal data you hold and where it is. Every other obligation — security, breach reporting, retention, vendor control — depends on it.
- Is an IT services company a Data Fiduciary or a Data Processor?
- Usually both: a fiduciary for its own employee and customer-contact data, and a processor for client data it handles on their behalf.
- Do we need a Data Protection Officer?
- The Act requires a Data Protection Officer only for Significant Data Fiduciaries notified by the Government. Every Data Fiduciary must publish the contact details of a person who can answer questions about processing.
- How long does DPDP readiness take?
- Typically three to five months for a mid-sized company that already has basic security controls.
This is a working summary for people who have to act on the law, not legal advice. Read the Act and the Rules, and take advice on your own facts.