Free readiness check

Where do you stand on DPDP and CERT-In?

About five minutes. No sign-up, and nothing you enter is stored. You get a score, the areas it comes from, and your biggest gaps with the section of the law each one relates to.

Notice

When you ask someone for consent, do you show them a clear, separate notice listing what personal data you collect and exactly what you will use it for?

Consent is only valid if the person was told, in plain words, what they were agreeing to. A line buried in terms and conditions does not count.

Can people read that notice in English or in an Indian language of their choice?

The Act gives the person the choice of English or any language in the Eighth Schedule to the Constitution. An English-only notice does not offer that choice.

Consent records

For any one person, can you show what they consented to, when, and which version of your notice they were shown?

If consent is ever questioned, it is for you to prove it was given and that a notice was shown. Without a record tied to the notice wording, you cannot.

Can people withdraw their consent as easily as they gave it, and does your processing then actually stop?

Withdrawal has to be as easy as giving consent, and you (and your vendors) must stop processing within a reasonable time afterwards.

Lawful basis

For anything you do with personal data without consent, have you written down which "legitimate use" in the Act you are relying on?

The Act allows processing only with consent or for one of a short, closed list of legitimate uses (such as employment, or a legal obligation). There is no general "legitimate interest" ground to fall back on.

Data accuracy

Where personal data is used to make a decision about someone, or is passed to another organisation, do you take steps to keep it accurate and complete?

The duty to keep data complete, accurate and consistent applies exactly in those two situations — a decision affecting the person, or disclosure to another Data Fiduciary.

Security safeguards

Is the personal data you hold protected by encryption or masking, controlled access, monitoring logs and tested backups?

Failing to take reasonable security safeguards carries the Act's highest penalty ceiling — up to ₹250 crore.

Breach readiness

If personal data were breached tomorrow, do you have a written plan — that people have practised — for telling the Data Protection Board and every affected person?

Both the Board and each affected person must be told. Not telling them carries a penalty ceiling of up to ₹200 crore.

Could you get a detailed report to the Board within 72 hours of becoming aware of a breach?

The Rules require the Board to be told without delay, with a detailed report within 72 hours of your becoming aware (unless the Board allows longer). Affected people must be told without delay as well.

Retention and erasure

Do you erase personal data once its purpose is over or consent is withdrawn — unless a law requires you to keep it?

Keeping data "just in case" is not allowed. It must be erased when the purpose is no longer served or consent is withdrawn, and your vendors must erase it too.

Rights and grievances

Have you published the contact details of a person who answers questions and complaints about personal data?

People must be able to find who to ask. The contact details of that person (or your Data Protection Officer, if you have one) have to be published.

Do you have a working process, with a published response time, for requests to see, correct or erase personal data and for grievances?

People have the right to a summary of their data, to correction and erasure, and to grievance redressal. You are expected to publish how to make a request and how long you take to respond.

Children's data

If you handle data of anyone under 18, do you get verifiable consent from a parent or guardian, and avoid tracking them or targeting ads at them?

Children's data needs a parent's or guardian's verifiable consent, and tracking, behavioural monitoring and targeted advertising aimed at children are prohibited. The penalty ceiling is up to ₹200 crore.

Vendors and processors

Do you have a written contract with every vendor that handles personal data for you?

You may use a Data Processor only under a valid contract, and you stay responsible for what they do with the data regardless of what the contract says.

Transfers outside India

Do you know which countries personal data is sent to or stored in, and do you check for Government restrictions and sector rules that apply?

Transfers are allowed unless the Central Government restricts a country by notification — and stricter sector rules, such as a regulator's localisation requirement, still apply on top.

Significant Data Fiduciary duties

If you could be notified as a Significant Data Fiduciary, are you ready with a Data Protection Officer based in India, an independent data auditor and periodic impact assessments?

Only the Central Government decides who is a Significant Data Fiduciary. If you process personal data at large scale or of a sensitive kind, it is worth knowing how far you are from these duties before a notification arrives. The penalty ceiling is up to ₹150 crore.

CERT-In incident reporting

Could you report a cyber security incident to CERT-In within 6 hours of noticing it — including at night or on a holiday?

CERT-In must be told within 6 hours of your noticing a reportable incident, or of it being brought to your notice. This is a separate duty from telling the Data Protection Board about a personal data breach, and the clock is much shorter.

Do the people who would spot an incident know which kinds must be reported to CERT-In?

The Directions list the types of incident that must be reported, from data breaches and ransomware to unauthorised access and attacks on cloud systems. An incident nobody recognised as reportable will not be reported in 6 hours.

Have you told CERT-In who your Point of Contact is, and is that information still current?

Every organisation covered by the Directions must designate a Point of Contact to interface with CERT-In and send the details in the prescribed format, updating them when they change.

CERT-In logs and time

Do you keep the logs of all your IT systems for a rolling 180 days, stored within India?

Logs of all ICT systems must be kept securely for a rolling 180 days and maintained within Indian jurisdiction, and handed to CERT-In with an incident report or on its direction.

Are the clocks on all your systems synchronised to the NIC or NPL time servers, or to a source traceable to them?

Without a common clock, logs from different systems cannot be lined up to reconstruct an incident. The Directions require synchronisation with the NTP servers of NIC or NPL, or with servers traceable to them.

A question left unanswered is counted as “no”.