Many small and mid-size Indian businesses process more personal data than they realise: customer names and phone numbers in the billing system, employee Aadhaar and bank details in HR files, leads in a CRM, CCTV footage, WhatsApp chats with clients. The Digital Personal Data Protection Act, 2023 applies to all of it once it is in digital form.
The good news is that the Act is written in plain language, and the DPDP Rules, 2025 give an eighteen-month phased period for most obligations (PIB). This checklist turns the requirements into tasks a small team can actually complete. It is based on the official Act and Rules, and is guidance, not legal advice.
Who has to comply?
If your business decides why and how personal data is processed, you are a Data Fiduciary. If you process data on someone else's behalf, such as a payroll vendor or an IT service provider, you are a Data Processor, and your client remains responsible for what you do. The person the data is about is the Data Principal. For a child, which the Act defines as anyone under eighteen, that includes the parent or lawful guardian.
The checklist
Step 1: Know what data you have (week 1 to 2)
- List every system and file store that holds personal data: CRM, ERP, HR, email, spreadsheets, cloud drives, mobile apps, CCTV, WhatsApp Business.
- For each, note: what data, whose (customers, staff, vendors, children), why you collect it, who can access it, where it is stored, and which vendors touch it.
- Mark sensitive items: identity documents, financial details, health information, children's data.
You cannot write a correct notice, answer a rights request or report a breach without this inventory. It is the single most useful thing you will do.
Step 2: Fix the legal basis for each purpose (week 2)
- For each purpose, decide whether you rely on consent or on a legitimate use listed in Section 7 of the Act, such as data the person voluntarily provided for a specified purpose, or certain employment purposes.
- Remove purposes you cannot justify. If you do not need date of birth to deliver a service, stop collecting it.
Step 3: Rewrite your notices (week 3)
Rule 3 requires the notice to be understandable on its own, and to give in clear and plain language, at a minimum:
- an itemised description of the personal data;
- the specified purpose and a description of the goods, services or uses it enables;
- a link to your website or app and how the person can withdraw consent (as easily as they gave it), exercise their rights and complain to the Board (DPDP Rules, 2025).
The Act lets people receive the notice in English or any language in the Eighth Schedule to the Constitution. If your customers mostly speak Bengali or Tamil, offer it in those languages.
Step 4: Make consent real (week 3 to 4)
- Consent must be free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, under Section 6 of the Act (DPDP Act, 2023). Pre-ticked boxes and "by using this site you agree" banners do not meet that standard.
- Separate consents for separate purposes: service delivery and marketing are not the same.
- Build a withdrawal path that is as easy as giving consent, and make sure withdrawal actually stops processing in every system.
- Keep records of who consented to what, and when.
Step 5: Children's data (if relevant)
- Get verifiable consent from a parent or lawful guardian before processing a child's data, using the methods in Rule 10.
- Do not undertake tracking, behavioural monitoring or targeted advertising directed at children; Section 9(3) prohibits it.
- Schools, coaching platforms, gaming and e-commerce apps should treat this as a priority.
Step 6: Security safeguards (week 4 to 6)
Rule 6 lists minimum "reasonable security safeguards". Turn each into an action:
| Rule 6 safeguard | Practical SME action |
|---|---|
| Encryption, obfuscation, masking or tokenisation | Encrypt laptops and databases; mask Aadhaar and card numbers in screens and exports |
| Access control | Named accounts, MFA, least privilege, remove leavers on their last day |
| Visibility through logs, monitoring and review | Enable access logs on key systems and actually review them |
| Continued processing after compromise, such as backups | Tested, offline backups of customer and HR systems |
| Retain logs and personal data for one year for investigation | Set log retention to at least one year, unless another law requires otherwise |
| Security clauses in processor contracts | Add security and breach-notice clauses to vendor agreements |
| Technical and organisational measures | Written policies, staff training, an owner for data protection |
Step 7: Rights and grievances (week 6)
- Set up a simple way for people to request access, correction, completion, updating or erasure of their data, and to nominate someone to act for them.
- Publish the business contact of your Data Protection Officer, if applicable, or of a person who can answer questions about processing, prominently on your website or app, as Rule 9 requires.
- Respond within the time you publish, and no later than ninety days (PIB summary of the Rules).
- Run a grievance mechanism: the person must be able to complain to you before going to the Board.
Step 8: Retention and erasure
- Set a retention period for each purpose and delete data when the purpose is served or consent is withdrawn, unless a law requires you to keep it.
- Remember Rule 8(3): data, traffic data and processing logs must be kept for at least one year from processing for specified purposes before erasure.
- If you fall in a class listed in the Third Schedule (certain large e-commerce, gaming and social media platforms), note the three-year inactivity rule and the forty-eight-hour advance notice before erasure.
Step 9: Processor contracts
- Section 8(2) allows you to engage a processor only under a valid contract. List every vendor that handles personal data: cloud, payroll, CRM, courier, call centre, IT support.
- Add clauses on purpose limits, security, sub-processing, breach notification to you without delay, and deletion at contract end.
Step 10: Breach readiness
- Prepare templates for notices to affected people and to the Board, and a runbook for the 72-hour detailed report under Rule 7.
- Align it with the CERT-In 6-hour report so one incident triggers both.
What does non-compliance cost?
The Schedule to the Act sets maximum penalties of up to Rs 250 crore for failing to take reasonable security safeguards, up to Rs 200 crore each for failing to notify a breach and for breaching obligations about children, and up to Rs 50 crore for other violations. The Board decides actual amounts. For an SME, the more immediate costs are lost enterprise contracts and customer trust when a gap becomes visible.
A realistic timeline for a small company
With one owner and a few hours a week from IT, HR and sales, steps 1 to 4 take roughly a month, and steps 6 to 10 another month or two, depending on how many systems you run. Start with the inventory; everything else depends on it.
How Cehpoint can help
Cehpoint's DPDP Act compliance service runs the data inventory, rewrites notices and consent flows, implements the Rule 6 safeguards in your systems, and drafts processor clauses and breach runbooks. For broader compliance work across ISO 27001 or PCI-DSS, see our IT consulting and compliance service.