How do we tell what applies to us right now?

By checking which sections have been brought into force at the moment you are deciding, rather than by asking whether the Act is live. That is a different question from the one people usually ask, and it is the only one with an accurate answer available.

Does the staging make it safe to defer?

It makes deferring a decision rather than a default. Some obligations are already live and others are not, so waiting is a choice about which parts to prepare for later, and it is worth making that choice knowingly rather than by assuming nothing has started.

What does it change about choosing an AI tool?

The same questions as any other regime, with a timing dimension added. Where material is processed and what a vendor commits to still decide it, and whether a particular obligation attaches today depends on the calendar as well as on the arrangement.

Glossary

DPDP Actdigital personal data protection act

India's data-protection law, whose provisions commence in stages rather than all at once, so what applies today is not the whole Act.

In plain terms

India's data-protection law, arriving in instalments. The unusual thing about it for a business is not what it says but when it says it: parts are live and parts are not, so the honest answer to whether it applies is that some of it does and the rest is coming.

Why it matters

Because the ordinary way of asking about a regulation gives a misleading answer here. Asking whether the law is in force invites a yes or a no, and neither is right, so a business that took one of them and planned accordingly is either preparing for obligations that have not arrived or missing ones that have.

How it works

Commencement is staged by notification rather than arriving in one moment. Different sections take effect at different times, so the operative question is which parts are live now, and that question has to be asked again later rather than answered once.

That makes planning the distinctive difficulty. An organisation cannot treat the whole Act as either a current requirement or a future project, because it is both at once, and the parts likeliest to affect an AI adoption are not necessarily the parts that arrived first.

The substance sits in a familiar family. Notice, purpose, security and handling by third parties are recognisable to anyone who has worked through another modern regime, so the structure is not the surprise and the timetable is.

For AI tools the exposure follows the same route as everywhere else: material about people in India processed by a service somewhere else. What is different is that the answer to whether a particular obligation attaches depends on the calendar as well as the facts.

The practical posture is checking rather than concluding. A business with operations or customers in India needs a current reading of what is in force at the moment it decides, because a reading taken a year earlier will be describing a different set of obligations.

The question people ask, and the one with an answer

The reason this deserves the whole visual is that the failure is not about the law's content, it is about the shape of the question, and shape-of-question failures are unusually persistent because nobody notices they have made one. A colleague asked whether the Act applies will give the most useful answer they can, and both available answers mislead: yes overstates what is currently required and invites work that has no deadline attached, while no understates it and leaves live obligations unattended. Neither person has been careless. The right-hand column costs no more effort and produces something an organisation can act on, with the third row being the one that actually distinguishes it: a reading of what is in force is a reading of a date, so the output of the exercise should include when to repeat it. That is a small habit and it is the difference between a conclusion that stays true and one that quietly stops being true while everybody continues to rely on it.

Seen in the wild

Planning an assistant rollout for an Indian team and finding the obligations depend on when the rollout lands.
ChatGPT
Checking where a search vendor processes material for a regional deployment covering India.
Glean
Keeping processing local to avoid the cross-border question entirely while the timetable settles.
LM Studio

Common misconceptions

People assume

It is either in force or it is not.

In fact

Neither answer is right, because it commences in stages. A business asking the yes-or-no question gets a misleading answer whichever way it is answered, and the useful question is which sections are live at the moment of deciding.

People assume

We can settle this once and move on.

In fact

A reading of what applies is a reading of a particular moment. The set of obligations changes as further sections commence, so a conclusion reached during one planning cycle is describing a position that will have moved by the next.

Questions

How do we tell what applies to us right now?: By checking which sections have been brought into force at the moment you are deciding, rather than by asking whether the Act is live. That is a different question from the one people usually ask, and it is the only one with an accurate answer available.
Does the staging make it safe to defer?: It makes deferring a decision rather than a default. Some obligations are already live and others are not, so waiting is a choice about which parts to prepare for later, and it is worth making that choice knowingly rather than by assuming nothing has started.
What does it change about choosing an AI tool?: The same questions as any other regime, with a timing dimension added. Where material is processed and what a vendor commits to still decide it, and whether a particular obligation attaches today depends on the calendar as well as on the arrangement.