Get In Touch

DPDP Act 2027 Website and App Checklist: Safeguards, Breach Notice and Penalties

Disclaimer: All information on this page is taken from official government sources. We do not own or represent any government organization. This page is for sharing information and spreading awareness only. Please refer to the official sources for the latest updates.

Why a Checklist Beats a Policy Document

Most Indian businesses respond to the DPDP Act by buying a privacy policy. A policy is the easy half. The hard half is making the product behave the way the policy claims, which is where a checklist helps and a PDF does not.

This list is drawn from the Act itself, with the caveat that operational detail sits in the DPDP Rules, 2025, whose main business-facing provisions commence eighteen months after the Gazette publication dated 13 November 2025 — 13 May 2027 counted from that date. Verify against the official Rules before you rely on the date, and treat this page as awareness material rather than legal advice.

Collection and Notice

  • Inventory every collection point: forms, chat, OTP login, uploads, free tools, newsletter.
  • Write one sentence of purpose per point. No sentence, no field.
  • Place a section 5 notice with or before each consent request: data, purpose, how to exercise rights, how to withdraw, how to complain to the Board.
  • Offer the notice in English and, where you market in another Eighth Schedule language, a version in it.
  • Separate purposes with separate ticks; nothing pre-ticked.

If you rely on consent, you need to be able to show it. Store, per submission: the exact wording shown, the time, the purpose, and an identifier for the person. Keep the record as long as you keep the data.

Practically, that is one extra database column and one line in the notification email. Our own forms record it that way, and the mechanics are in DPDP consent, notices and website banners.

Security Safeguards

Section 8 requires reasonable security safeguards. Nobody expects a marketing website to run a security operations centre, but these are the basics an auditor would look for:

  • HTTPS everywhere, with HSTS where you can.
  • Admin accounts with unique logins and two-factor authentication. No shared passwords.
  • Least privilege: your content editor does not need database access.
  • Patching on a schedule: CMS, plugins, server packages.
  • Backups that are tested by restoring one, not by trusting a green tick.
  • Rate limiting and basic bot protection on forms.
  • No personal data in logs you keep for a year, and none in spreadsheets on personal laptops.
  • Written contracts with every processor: host, SMTP, CRM, analytics vendor.

Breach Handling

Decide this before you need it, because the day you need it nobody will be thinking clearly.

  • A definition of what counts as a personal data breach in your context.
  • One named person who decides, and a deputy.
  • Steps: contain, assess scope, record facts and times, notify as the Rules prescribe, inform affected people, fix the cause.
  • A log of every incident, including the ones that turned out to be nothing.
  • Vendor contacts and escalation routes written down, including out of hours.

Retention, Rights and Grievances

  • Write retention per category and delete on schedule. We use 12 months for leads that never become projects.
  • Build a route for access and summary, correction, erasure and nomination requests, and log each one.
  • Publish a grievance contact with an acknowledgement and response process, and say that unresolved complaints can go to the Data Protection Board of India.
  • Set the age of a child at 18 and handle guardian consent if you serve minors.
  • Keep a short record of processing activities so you can answer questions without archaeology.

Our own version of all this is public in the CrazzyCodes privacy policy if you want a working example rather than a template.

How Penalties Actually Work

The large figures quoted in headlines come from the Schedule to the Act. They are maximums the Data Protection Board may impose after an inquiry under section 33, with the Board considering factors such as the nature and gravity of the breach and any mitigation. They are not automatic fines triggered by a complaint.

The practical reading: documented effort matters. A business with a notice, consent records, a retention schedule and an incident log is in a different position from one with none of those, regardless of the ceiling in the Schedule.

Official sources: MeitY DPDP Act page and the DPDP Rules, 2025 PDF. For the build work, see website development India.

DPDP checklist — common questions

What does a DPDP compliance checklist cover for a website?

A collection inventory with a purpose per field, a section 5 notice at each consent point, consent records, reasonable security safeguards, a breach process, retention with actual deletion, rights and grievance routes, and children's age set at 18.

What should a consent record store?

The exact wording shown, the time, the purpose and an identifier for the person. Keep it for as long as you keep the underlying data so you can show what was agreed.

What counts as reasonable security safeguards?

In practice: HTTPS, unique admin accounts with two-factor authentication, least privilege, scheduled patching, tested backups, form rate limiting, no personal data in long-lived logs, and written contracts with processors.

How should a business handle a personal data breach in India?

Contain it, assess the scope, record the facts and times, notify as the Rules prescribe, inform affected people, fix the cause and log the incident. Decide who owns that decision before an incident happens.

Are DPDP penalties automatic?

No. The Schedule sets maximums that the Data Protection Board may impose after an inquiry under section 33, taking account of the nature and gravity of the breach and any mitigation.

What retention period should I use for leads?

Pick a defensible period tied to the purpose and apply it. We delete or anonymise leads that never become projects within 12 months, and sooner on request.

Does an app need the same checklist as a website?

Largely yes, plus SDK review, store privacy declarations, in-app notices before permissions, and a route for rights requests inside the app rather than only by email.

Want the technical list for your site?

The free audit shows the forms, scripts and third-party tools your pages load right now.

Get My Free Audit
DPDP Act 2023 Compliance Checklist Breach Notification Security Retention Grievance
CrazzyCodes Logo

CrazzyCodes

CrazzyCodes is a digital agency founded in 2020 in Mumbai, building websites, stores, apps and search and ads campaigns for businesses across India, the UAE and the UK.

← Previous Article Children's Data, Apps and Websites under the DPDP Act Next Article → Your Rights under the DPDP Act, 2023