India

India is not a variation on the pattern the courses teach. It is a different design, and three of its choices catch teams who assume otherwise: the vocabulary is its own, the law gives no right against a decision made by a machine, and a breach is told to every affected person, not only to a regulator on a clock.

Read this beside the course, not instead of it. The course gives you the international standard and why it exists; this gives you what India does with it.

The vocabulary is different, and it matters in writing

India does not say controller, processor or supervisory authority. The Act says Data Fiduciary for the organisation that decides how personal data is processed, Data Principal for the person it is about, and Data Processor for anyone processing on the Fiduciary's behalf. The regulator is the Data Protection Board of India, defined in section 2(c).

This is not pedantry. A policy written in European vocabulary and filed in India reads as though it were drafted for somewhere else, which is the first thing a reviewer notices.

Bears on: AI, data protection and privacy, Cyber security foundations, eKYC and digital identity verification

A personal data breach is told to everyone affected, with no hour fixed

Section 8(5) requires the Data Fiduciary to protect personal data in its possession or control, including where a Data Processor handles it, "by taking reasonable security safeguards to prevent personal data breach".

Section 8(6) then requires that, in the event of a breach, the Fiduciary "shall give the Board and each affected Data Principal, intimation of such breach in such form and manner as may be prescribed". Two things follow that surprise people. The duty runs to every affected individual, not only to the regulator. And the Act fixes no number of hours at all — the form and manner are left to be prescribed, so the familiar seventy-two hours is not the law here.

The Schedule to section 33(1) prices both: failing to give that notice may extend to two hundred crore rupees, and failing to keep reasonable safeguards in the first place to two hundred and fifty crore.

Bears on: Cyber security foundations, Incident response and post-incident review, IT service management foundations, Third-party cyber risk

There is no right against a decision made without a person

This is the gap most worth knowing. A Data Principal's rights under the Act are the right to information about processing (section 11), to correction, completion, updating and erasure (section 12), to grievance redressal (section 13) and to nominate another person to exercise those rights (section 14).

There is no right not to be subject to a decision based solely on automated processing, and no right to have such a decision reconsidered. The word "automated" appears in the Act only in its definitions.

So a design that relies on "the law will require a human reviewer" does not survive the journey to India. If a human check belongs in the process, it has to be there because the risk warrants it.

Bears on: AI agents: the basics, The role of AI in fraud, AI governance foundations, Fraud models in production, eKYC and digital identity verification, Agentic AI: how agents work, Agentic workflows and multi-agent systems

A Data Principal has duties, which is unusual

Section 15 places duties on the individual: to comply with applicable law when exercising rights, not to impersonate another person, and not to register a false or frivolous grievance. The Schedule prices a breach of those duties at up to ten thousand rupees.

Few data protection laws do this at all, and it changes the tone of a privacy notice written for India.

Bears on: AI, data protection and privacy, eKYC and digital identity verification

You cannot contract your way out of a supplier's failure

Section 8(1) makes the Data Fiduciary responsible for complying with the Act "irrespective of any agreement to the contrary", and expressly for processing "undertaken by it or on its behalf by a Data Processor". Section 8(2) allows a Processor to be engaged "only under a valid contract".

There is no statutory window in which a Processor must warn the Fiduciary. Where another law hands you a supplier deadline to rely on, India hands you none and forbids you to push the responsibility down the chain. The contract is the only clock you get, so it has to state one.

Bears on: Third-party cyber risk, Cloud security and zero trust

Transfers out of India are restricted by notification, not by adequacy

Section 16(1) lets the Central Government, by notification, restrict transfer of personal data to a country or territory outside India. Section 16(2) preserves any Indian law that gives a higher degree of protection or a stricter restriction.

So the question is not whether a destination has been found adequate. It is whether it has been notified, and whether a sectoral rule bites harder — which for a regulated financial institution it often does.

Bears on: Cloud security and zero trust, AI, data protection and privacy

e-KYC is the statutory term here, and it carries limits

Everywhere else in this catalogue, "eKYC" is industry usage. In India it is the wording of the rule. The Reserve Bank's Directions require a bank or other notified entity to "carry out authentication of the customer's Aadhaar number using e-KYC authentication facility" provided by the Unique Identification Authority of India, and allow biometric e-KYC authentication, including Aadhaar Face Authentication, by a bank official, business correspondent or business facilitator.

Where that authentication is done by OTP in non-face-to-face mode, the account is capped: the aggregate balance of all the customer's deposit accounts may not exceed one lakh rupees, credits across all those accounts may not exceed two lakh rupees in a financial year, and term loans sanctioned may not exceed sixty thousand rupees in a year. Such an account may not run beyond a year without fuller identification, including video-based customer identification.

Bears on: eKYC and digital identity verification, eKYC under the hood: from camera to decision, Running an eKYC service: accuracy and APIs, Identity document verification

The small account, a deliberate route in for people without documents

A Small Account is a savings account opened under rule 9(5) of the Prevention of Money-laundering (Maintenance of Records) Rules, 2005. The Directions cap it: credits of not more than one lakh rupees in a financial year, withdrawals and transfers of not more than ten thousand rupees in a month, and a balance never above fifty thousand rupees — with that balance cap set aside for government grants, welfare benefits and payment against procurements.

It is time-bounded, operational for twelve months and extendable by twelve more. It is a ramp, not a category, and it is the clearest answer in this catalogue to the question of what you do about a customer who cannot produce the documents.

Bears on: Onboarding friction and inclusion, eKYC and digital identity verification

Sources

The official documents this course relies on. Laws and guidance change, so check the current version.

  1. The Digital Personal Data Protection Act, 2023 (No. 22 of 2023) · Ministry of Law and Justice, Government of India
  2. Reserve Bank of India (Commercial Banks — Know Your Customer) Directions, 2025 (updated 1 October 2026) · Reserve Bank of India
Contact · Saolix GroupPeople. Products. Possibilities.

Your next chapter.
Let’s build it together.

Explore a product, discuss a project, or find the right expertise. Tell us where you want to go. We’ll help you take the next step.

Compliance & agentic AIManaged servicesConsulting & training