Quick answer
The DPDP Act has no small-business exemption: any business processing digital personal data in India is a Data Fiduciary with obligations from 13 May 2027. Section 17(3) lets the Government exempt startups or other classes from certain provisions by notification, so check whether one has been issued. A proportionate plan focuses on a data list, a Rule 3 notice, basic Rule 6 security, a breach plan and a published contact.
- There is no turnover, headcount or user-count threshold for ordinary DPDP obligations.
- Section 17(3) allows the Government to exempt startups or classes from certain provisions only by notification.
- Penalties are maximums decided case by case; the Board must consider proportionality and the nature of the breach.
- Most small businesses can meet the core rules with a data inventory, notices, security basics and templates.
- A Data Protection Officer is not required; a published contact person under Rule 9 is.
Who this is for: Small business owners and MSMEs, Early-stage startup founders, Clinics, coaching centres and local services, Freelancers and agencies handling client data, Operations managers wearing the compliance hat
Does the DPDP Act apply to small businesses?
Yes. The DPDP Act applies to any person who processes digital personal data within India, and to non-digital data that is later digitised. There is no turnover, employee or customer threshold for the ordinary duties of a Data Fiduciary.
A local clinic with appointment software, a coaching centre with a student WhatsApp group, a five-person agency running campaigns, and a Shopify store all process personal data. Each is a Data Fiduciary for the data it decides how to use.
Where size does matter
- Significant Data Fiduciary status is notified based on factors such as volume and sensitivity of data and risk to rights. Small businesses are unlikely candidates.
- Third Schedule erasure timelines apply only to e-commerce entities and social media intermediaries with at least 2 crore registered users, and online gaming intermediaries with at least 50 lakh.
- Section 17(3) lets the Central Government, having regard to the volume and nature of personal data, notify certain Data Fiduciaries or classes, including startups, to whom certain provisions will not apply.
No such notification is reflected in the Rules of 13 November 2025. Check the Gazette before relying on any relief, and plan on the basis that the full set of obligations applies from 13 May 2027.
What does a proportionate plan look like?
"Proportionate" does not mean optional. It means meeting every obligation with the lightest mechanism that genuinely works for your scale. A large platform needs a consent management platform and a privacy engineering team. A small business usually needs good templates, a few settings changed in its existing tools, and one owner.
| Obligation | Large organisation | Small business |
|---|---|---|
| Notice (Rule 3) | Layered in-app notices per feature | One clear notice on forms, site and WhatsApp intro |
| Consent records | Consent platform with APIs | Form tool or CRM field with date and source |
| Security (Rule 6) | SIEM, DLP, key management | MFA, encrypted devices, role-based access in SaaS tools |
| Breach response (Rule 7) | 24x7 incident team | A written one-page plan and templates |
| Rights (Rule 14) | Self-serve privacy centre | Published email or form, tracked in a sheet |
| Contact (Rule 9) | Privacy office | Named owner's business email and phone |
The Board weighs proportionality when deciding penalties. Section 33 and the Schedule set maximum amounts per instance, and the Board must consider factors including the nature, gravity and duration of the breach, the type of data, mitigation steps and whether the penalty is proportionate. A documented, sincere programme is the best mitigation.
A ten-step plan for small businesses
- Name an owner. One person accountable for data protection, even part time.
- List your data. Write down what personal data you collect, where it sits (phone, Google Drive, CRM, accounting software, WhatsApp) and why. A spreadsheet is enough. See data mapping step by step.
- Delete what you do not need. Old exports, ex-customer spreadsheets and personal copies on staff phones are risk without value.
- Write one notice. Use the privacy notice template and put it on your website, forms and booking pages.
- Separate marketing consent. Ask for it with an unticked box or a clear WhatsApp opt-in, and record the date.
- Lock down accounts. Turn on multi-factor authentication for email, cloud storage and business apps; remove ex-staff access.
- Back up. Enable backups in your SaaS tools and test one restore.
- Prepare for breaches. Keep a one-page plan with contacts and customer and Board templates.
- Publish a contact and a request route. Rule 9 contact person and Rule 14 request channel, with a response period not exceeding 90 days.
- Check vendors. Make sure your key software providers offer data processing terms.
Meeting Rule 6 security on a small budget
Rule 6 sets minimum safeguards, but most can be met with features already in the tools a small business pays for.
- Rule 6(1)(a) encryption and masking: use full-disk encryption on laptops and phones; avoid storing ID numbers in plain spreadsheets; mask them where only the last digits are needed.
- Rule 6(1)(b) access control: individual accounts, not shared logins; least privilege in Google Workspace, Microsoft 365, Zoho or your CRM.
- Rule 6(1)(c) logs and monitoring: switch on audit logs in your SaaS admin consoles and review sign-in alerts.
- Rule 6(1)(d) continuity: automated backups with a tested restore.
- Rule 6(1)(e) one-year retention: keep those logs, and the related personal data, for one year for detection and investigation unless another law requires otherwise. Check your plan's log retention setting, because entry tiers often retain logs for a shorter period.
- Rule 6(1)(f) contracts: accept or sign the vendor's data processing terms.
- Rule 6(1)(g) organisational measures: a short written policy and a 30-minute annual staff briefing.
Note the separate one-year retention rule in Rule 8(3) for personal data, traffic data and processing logs.
Your software vendors are your Data Processors
A small business rarely builds its own systems. Accounting software, the website builder, the booking app, the CRM and cloud storage all process customer data on your behalf, which makes those providers Data Processors and leaves you, the Data Fiduciary, responsible under section 8(1).
What to check for each key tool
- Data processing terms: most established providers publish a data processing addendum. Rule 6(1)(f) requires your contract to include appropriate provisions for reasonable security safeguards.
- Admin controls: individual user accounts, role-based access, MFA enforcement and audit logs.
- Log and data retention: whether logs can be kept for one year, as Rule 8(3) requires, and whether deleted data can be fully purged afterwards.
- Breach notice: whether the provider commits to tell you promptly about incidents, because your Rule 7 clock starts when you become aware.
- Export and deletion: whether you can export a customer's data for an access request and delete it on erasure.
Keep the stack small
Every extra tool is another copy of customer data to secure and delete. Retiring two unused apps is often the cheapest compliance improvement available. If a provider cannot answer basic questions about security and deletion, treat that as a reason to switch before May 2027.
Common mistakes small businesses make
- Assuming the law is only for big tech. The penalty ceiling for failing to take reasonable security safeguards is up to ₹250 crore; the amount depends on the facts, but the obligation is the same.
- Using staff personal WhatsApp for customer data. You lose control over access, deletion and breach detection. Use a business account with admin control.
- Copy-pasting a foreign privacy policy. GDPR-style templates cite lawful bases and rights that do not match the DPDP Act, and miss Rule 3 requirements such as the route to complain to the Board.
- Making marketing consent mandatory. Consent must be free; a form that cannot be submitted without ticking "send me offers" is defective.
- Forgetting employees. Staff data is personal data. Employment purposes are a legitimate use under section 7, but security and retention duties still apply.
- No breach plan. Every personal data breach must be intimated to affected individuals and the Board; there is no small-incident exception.
- Waiting for May 2027. Six months is enough for a small business, but not if work starts in April.
Further reading on suhasbhairav.com
- BlogAI Security Risks for Businesses: Architecture
- BlogHuman-in-the-Loop Approval in SME AI Workflows for Production-grade Systems
- BlogAgent-based vendor risk auditing for sub-processors
- AI AutomationAI Automation for Security Compliance: Uses + Example
- AI SkillsAGENTS.md Template for Privacy and Data Governance Agents
Before 13 May 2027
Compliance checklist
Appoint a data protection owner
Give one named person responsibility and a few hours a month for DPDP tasks.
Section 8(1)
Build a one-sheet data inventory
List data types, systems, purposes, who has access and how long you keep each.
Rule 3(b)(i)
Publish a Rule 3 notice
Place one plain-language notice on your website, forms and booking flows.
Rule 3
Collect marketing consent separately
Use unticked opt-ins and record date, source and wording.
Section 6
Enable MFA and remove shared logins
Turn on multi-factor authentication and individual accounts in every business tool.
Rule 6(1)(b)
Turn on audit logs and backups
Enable logging, extend retention to one year and test a backup restore.
Rule 6(1)(c)-(e)
Write a one-page breach plan
Include who decides, who to inform and templates for customers and the Board.
Rule 7
Publish a contact and request route
Show a business email or form for questions and rights requests with a response period up to 90 days.
Rules 9 and 14
Check the Gazette for section 17(3) relief
Look for any notification exempting startups or classes before relying on it.
Section 17(3)
Answers
Frequently asked questions
Is there a startup exemption under the DPDP Act?
Is there a startup exemption under the DPDP Act?
Not automatically. Section 17(3) allows the Central Government to notify certain Data Fiduciaries or classes, including startups, to whom certain provisions will not apply, having regard to the volume and nature of data. No such notification appears in the Rules of November 2025, so check the Gazette before relying on any exemption.
Does a small shop that collects phone numbers need to comply?
Does a small shop that collects phone numbers need to comply?
Yes, if the numbers are stored digitally, for example in billing software or WhatsApp. The shop is a Data Fiduciary and must give notice, take reasonable security safeguards and use the numbers only for the purpose they were given. Marketing messages need separate consent.
Will a small business really face a ₹250 crore penalty?
Will a small business really face a ₹250 crore penalty?
The amounts in the Schedule are maximums per instance. The Board decides the actual penalty after an inquiry, considering factors such as the nature, gravity and duration of the breach, the type of data, mitigation and proportionality. That does not make compliance optional, but it does reward a documented, good-faith programme.
Do I need to hire a Data Protection Officer?
Do I need to hire a Data Protection Officer?
No. Only Significant Data Fiduciaries must appoint a DPO. Every other business must publish the business contact information of a person who can answer questions about its processing, under Rule 9, and mention it in every response to a rights request. That person can be the owner or a manager.
Do I need a consent management platform?
Do I need a consent management platform?
Not necessarily. The law requires valid consent and the ability to withdraw it easily, not a particular tool. A small business with a website form, a CRM field recording consent date and source, and an unsubscribe link may meet the requirement. Larger sites with many tracking tags usually benefit from a dedicated tool.
What is the minimum I should do before 13 May 2027?
What is the minimum I should do before 13 May 2027?
At minimum: list your personal data and where it lives, publish a Rule 3 notice, separate marketing consent, enable multi-factor authentication and backups, keep logs for one year, write a breach plan, and publish a contact person and a route for rights requests with a response period up to 90 days.
Legal references and sources
- Digital Personal Data Protection Act, 2023 — Section 17(3) (official text)
- Digital Personal Data Protection Rules, 2025 — Rules 3, 6, 7 and 9 (official text)
- Digital Personal Data Protection Act, 2023 — Section 33 and Schedule (penalties) (official text)
This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.
About the author

Suhas Bhairav
Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.
Related guides
- Sector guidesDPDP Compliance Checklist for SaaS & AI Startups (2026–27)A 12-point DPDP checklist and month-by-month plan for SaaS and AI startups to be ready when the core DPDP Rules apply on 13 May 2027.
- Templates & playbooksWhat DPDP Compliance Costs: Budget Drivers for Indian CompaniesThe factors that drive DPDP compliance budgets for Indian companies, the effort categories to plan for, and how to scope spend sensibly before 13 May 2027, without guesswork figures.
- Templates & playbooksDPDP Privacy Notice Template (Rule 3 Compliant)A copy-ready DPDP privacy notice template mapped clause by clause to Rule 3 and section 5, with a short consent notice, a full notice and implementation guidance.
- DPDP Rules 2025DPDP Reasonable Security Safeguards Under Rule 6Rule 6 lists the minimum security safeguards every Data Fiduciary must take from 13 May 2027. Failure can attract a penalty of up to ₹250 crore, the highest in the DPDP Act.
- DPDP Act 2023DPDP Section 17 Exemptions ExplainedSection 17 switches off parts of the DPDP Act for legal claims, courts, crime, offshore outsourcing, mergers, loan defaults, notified State bodies, research and notified startups.
- DPDP Act 2023DPDP Penalties Explained: What a Data Breach CostsThe full DPDP Act penalty schedule, from ₹10,000 to ₹250 crore per instance, the section 33(2) factors the Board weighs, and how penalties are imposed and appealed.