The Digital Personal Data Protection Act, 2023 uses an insurance policy to explain consent. The illustration under Section 6(2) has X buying a policy on an insurer's app and consenting to its issue. X is the buyer, the insured and the only person whose data moves. It's a tidy picture.
Indian policies rarely look like that. Take a 38-year-old in Pune. His family floater covers his wife, two school-going children and his widowed mother. His employer's group health plan adds the same wife and children again. His term plan names his mother as nominee. One man signed. Five people's data, much of it health data, now sits with an insurer, a broker and a Third Party Administrator (TPA).
The dates are close. Under the DPDP Rules, 2025, Rule 4 on Consent Managers came into force on 13 November 2026. Notice, consent, children's data and Data Principal rights follow on 13 May 2027. And since 5 February 2026, policyholder information has had its own statutory shield. Section 14C of the Insurance Act bars sharing it with third parties without the customer's express consent, save where law or public duty demands.
This article takes each person on a typical policy and asks three questions. Who must consent? Who must be told? Who can exercise rights?
Five people, one signature
Section 2(j) defines the Data Principal as the individual the data relates to. It lets someone else stand in for her in only two cases. A parent or lawful guardian stands in for a child. A lawful guardian stands in for a person with disability. Nobody stands in for an adult spouse or an elderly parent.
Here is how that plays out on an ordinary family and group book.
| Person on the policy | Data Principal? | Who consents | Who gets the notice |
|---|---|---|---|
| Proposer | Yes | Proposer | Proposer |
| Adult spouse or parent | Yes, in her own right | She does | She does |
| Child under 18 | Yes, with the parent | Parent, verifiably | Parent |
| Adult dependant with a guardian | Yes, with the guardian | Guardian, checked under Rule 11 | Guardian |
| Employee in group cover | Yes | Employee, with Section 7(i) for the employer | Employee |
| Employee's spouse and children | Yes | Spouse herself, parent for children | Spouse, parent |
| Nominee | Yes | Unsettled, see below | Unsettled, see below |
Why the proposer's signature doesn't cover an adult spouse
Most proposal forms end with one declaration. The proposer confirms the details are true and agrees to their use. Under Section 6(1), consent signifies agreement to processing of "her personal data". He can agree for himself. He can't agree for his wife, and the Act gives him no proxy role for her.
The fallback grounds don't fit well either. Section 7(a) covers data the Data Principal "has voluntarily provided". The wife provided nothing. Her husband typed her thyroid history into the form. The Act also has no contract-performance ground and no general legal-obligation ground. Some sector commentary that gets the Act wrong describes such grounds as if they exist.
That leaves consent from the adult insured herself. Section 6(10) puts the burden of proving notice and consent on the Data Fiduciary. An insurer that can't produce the wife's own consent will struggle before the Board.
The IRDAI rulebook points the same way without quite saying so. The Master Circular of 5 September 2024 asks for express consent "of the policyholder" before medical records are shared through the Ayushman Bharat Health Account (ABHA). For online sales, consent must come from the prospect's own registered mobile number or email. Section 14C speaks of "the customer". Each of these hooks hangs on the buyer. None reaches the member who never bought anything.
There's a further twist most coverage misses. Sections 11 and 12 give access and erasure rights against the fiduciary "to whom she has previously given consent". Rule 14(2) repeats the framing. So a wife who never consented has a weaker hold on those rights. That gives the insurer no comfort, because it is still processing her data without a clear ground under Section 4.
Minors, the 18th birthday and dependants with a disability
Section 9(1) requires verifiable consent of the parent before any processing of a child's data. A breach of Section 9 can attract a penalty of up to ₹200 crore under the Schedule. Any floater that covers children brings this into the core book.
Rule 10 says what verification means. The insurer must check that the person claiming to be the parent is an identifiable adult. It may rely on reliable identity and age details it already holds. For a proposer who has completed KYC, Rule 10(1)(a) is usually met from records on file.
Some commentary says insurers must collect documents proving the parent relationship. Rule 10 doesn't ask for that. It tests adulthood and identity. Underwriting may still want a birth certificate for its own reasons, and that's a separate decision.
The Fourth Schedule exempts clinical establishments and healthcare professionals treating a child. It doesn't name insurers or TPAs. So the hospital can treat a nine-year-old without fresh parental consent, but the claim that follows is still the insurer's Section 9 problem. Section 9(3) also bars tracking or behavioural monitoring of children. Wellness programmes that reward step counts should switch off for every member under 18.
Then the child turns 18. Section 2(f) ends childhood at eighteen, and the parent's standing ends with it. The Act and Rules say nothing about consent the parent gave earlier. Our reading is cautious. A parent's consent no longer speaks for an adult, so the insurer needs the young adult's own consent.
Renewal is the natural moment to collect it. Build a date-of-birth trigger that flags every member who turns 18 before the next renewal. Then send that member a notice and a consent request of their own, on their own mobile number.
Some floaters cover an adult son or daughter with a disability. Rule 11 requires the insurer to check that the guardian was appointed by a court, a designated authority or a local level committee. A parent's word isn't enough. MeitY's Removal of Difficulties Order dated 5 October 2026 corrected Section 9(1) to make this coverage explicit.
Group health: the employer fills in the spreadsheet
Group cover reverses the flow. Under the Master Circular, the employer is the master policyholder and employees are members. The insurer must obtain member details from the employer early, so cashless claims work from the first day. In practice that's an HR export of names, dates of birth and dependants, emailed to a broker.
Each party in that chain plays a different role.
The employer is a Data Fiduciary for its own HR data. Section 7(i) lets it process employee data to provide a benefit the employee seeks. That clause names the employee. It says nothing about a spouse or child, so dependants need their own consent route.
The broker decides how it places and services the cover, which usually makes it a fiduciary for that work. The insurer decides underwriting and claims, so it's a fiduciary too. The TPA, in most arrangements, processes claims on the insurer's behalf as a Data Processor.
Roles decide who answers for what. Under Section 8(1), the insurer answers for everything its processors do. Rule 6(1)(f) requires security terms in the processor contract. Trace the HR file's path with data mapping before the next group renewal.
Then test the broker and TPA contracts against third-party vendor obligations under DPDP. A large group book full of dependants' health data justifies a Data Protection Impact Assessment, whether or not the insurer is ever notified as a Significant Data Fiduciary.
Nominees: data about someone who never dealt with the insurer
The Master Circular has the proposal form capture the nominee's mobile number, email, addresses, relationship and bank account. The nominee hasn't applied for anything. Often she doesn't know she's been named.
Section 5 ties the notice duty to a request for consent. If the insurer never asks the nominee for consent, the text doesn't demand a Section 5 notice. That isn't a safe harbour. The insurer still needs a ground under Section 4, and Section 7(a) fails because the nominee didn't provide the data. The law here is genuinely open.
Our recommended position has three parts. Collect only what IRDAI requires at proposal. Send the nominee a short notice when the policy issues, with a link to consent and to rights. Treat the claim, when the nominee approaches the insurer herself, as the point where Section 7(a) starts to work.
Breach handling carries a second clock. The IRDAI cyber security guidelines of 24 April 2023 apply to insurers, brokers and TPAs alike. Cyber incidents go to CERT-In within six hours, with a copy to IRDAI. Run both clocks from one incident playbook.
Claims: the spouse's discharge summary in the proposer's inbox
Health claims move the most sensitive data of people who never signed. The Master Circular has insurers and TPAs collect claim documents from hospitals directly. The policyholder isn't asked to submit them. So the wife's discharge summary travels from hospital to TPA to insurer. Then it often lands in the proposer's registered email.
That last step is the risk. The proposer isn't the wife's proxy. Sending him her diagnosis is a disclosure the insurer has to justify. The same applies when he calls the helpline and asks what his adult son claimed for.
Rights requests need verification tied to the member. Rule 14 lets a fiduciary name the identifier it needs, such as an enrolment ID or a mobile number. Issue every adult member their own identifier. Route requests through a rights request portal that checks the requester against that member.
Rule 14(3) caps grievance response at ninety days. IRDAI's complaint timeline is fourteen days. A single queue serving both should run to the shorter clock.
Portability adds one more flow. When a family ports a floater, underwriting details and claim history move between insurers through the Insurance Information Bureau of India within 72 hours. Every member's history moves together. Each adult's notice should say so in plain words.
Death claims: two nominees who may not be the same person
Section 39(7) of the Insurance Act makes a parent, spouse or child named as nominee "beneficially entitled" to life policy proceeds. Courts still disagree on what that means. In February 2025, the Karnataka High Court held that Section 39 doesn't override succession law. It noted that the Andhra Pradesh and Rajasthan High Courts had read it the other way.
The DPDP Act adds a second, different nominee. Section 14 lets a Data Principal nominate any individual to exercise her data rights after death or incapacity. Rule 14(4) has her do so under the fiduciary's terms of service. The Section 39 nominee collects the money. The Section 14 nominee speaks for the data.
They may be different people, and nothing makes one the other by default. So don't copy the policy nominee into a DPDP nomination field automatically. Ask the life assured separately, and let her name the same person if she wants.
Incapacity matters as much as death. A critical illness can leave the insured unable to act for weeks. The Section 14 nominee is the one who can then ask what the insurer holds and correct it.
The in-force book is the harder problem
New business can be fixed in the proposal flow. Policies already on the books are harder. Section 5(2) requires a notice, as soon as reasonably practicable, to anyone who consented before commencement. The insurer may keep processing until she withdraws.
That helps with the proposer. It does little for spouses, children and parents who never consented at all. For them, renewal is the cleanest fix, because the customer is already in front of you. Renewals falling before 13 May 2027 are the cheapest place to start. Group schemes renew too, and the HR file is where that work begins.
We've set out the sequencing in more detail in working back from 13 May 2027.
What to change before 13 May 2027
These are the tasks we'd put at the top of the programme plan.
| Task | Owner | When |
|---|---|---|
| Separate Rule 3 notice to each adult insured | Product and legal | New business and every renewal |
| Consent from each adult, against their own identifier | Digital and operations | Enrolment and renewal |
| Rule 10 parent check, reusing proposer KYC | Underwriting | Enrolment of any minor |
| Date-of-birth trigger for members turning 18 | Policy administration | Before the next renewal |
| Rule 11 guardian check for adult dependants | Underwriting | Enrolment |
| Consent route for dependants in group schemes | HR, broker and insurer | Next group renewal |
| Nominee notice with a consent link | Policy servicing | At policy issue |
| Separate Section 14 nomination | Product | New business and service requests |
| Own contact details for every adult member | Operations | Ongoing |
| Rights requests verified by member identifier | Grievance team | Before May 2027 |
Most insurers will fold this into a wider DPDP readiness assessment. The consent pieces belong on one consent management layer. Then a spouse who withdraws at renewal is reflected in underwriting, claims and marketing at once.
Section 6(7) also lets a Data Principal act through a registered Consent Manager. Rule 4 has been in force since 13 November 2026. We've explained how the Consent Manager framework works for fiduciaries.
Count the people, then count the consents
Pick one family floater from your book this week. Count the people it covers. Then count the consents you could prove under Section 6(10).
For most insurers the second number is one. Each adult missing from that count is a Data Principal whose data you hold without proof of a ground.
This article is general information, not legal advice on any specific policy or scheme.
Sources
- India Code, "The Digital Personal Data Protection Act, 2023 (Act No. 22 of 2023)", as on 19 November 2025. Link
- Ministry of Electronics and Information Technology, "Digital Personal Data Protection Rules, 2025, G.S.R. 846(E)", Gazette of India, 13 November 2025. Link
- King Stubb and Kasiva, "DPDP Act 2023: Government Issues Removal of Difficulties Order 2026 Clarifying Consent and Data Audit Requirements", 8 October 2026. Link
- Insurance Regulatory and Development Authority of India, "Master Circular on Protection of Policyholders' Interests, 2024", 5 September 2024. Link
- Ministry of Law and Justice, "The Sabka Bima Sabki Raksha (Amendment of Insurance Laws) Act, 2025 (No. 40 of 2025)", Gazette of India, 21 December 2025. Link
- Taxmann, "Sabka Bima Sabki Raksha (Amendment of Insurance Laws) Act Effective from 5 Feb 2026", February 2026. Link
- Khaitan and Co, "Insurance 2.0, Insurance reforms to commence from 5 February 2026", February 2026. Link
- High Court of Karnataka, "Smt. Neelavva v. Smt. Chandravva, RFA No. 100471 of 2023", 20 February 2025. Link
- JSA, "JSA Newsletter, Insurance Law, April to June 2023 Edition", July 2023. Link