Sector guidesUpdated 22 November 20269 min read

DPDP for Insurers and InsurTech

How insurers, intermediaries and InsurTechs handle health and family data, agents and TPAs, claims analytics, nominees and AI underwriting under the DPDP Act and Rules.

By Suhas Bhairav · Reviewed against the DPDP Rules, 2025 (G.S.R. 846(E), 13 Nov 2025)

Core rules apply
13 May 2027
Sectoral regulator
IRDAI — stricter rules continue
Breach reporting
Every breach; 72-hour Board report (Rule 7)
Log retention
Minimum one year (Rule 8(3))
Grievance ceiling
90 days (Rule 14(3))
Security penalty
Up to ₹250 crore

Quick answer

Insurers and InsurTechs are Data Fiduciaries under DPDP from 13 May 2027. They must give Rule 3 notices covering proposers and insured family members, protect health and claims data with Rule 6 safeguards, report every breach with a 72-hour Board report, and bind agents, brokers, TPAs and AI vendors by contract. Stricter IRDAI requirements, including on records, continue to apply.

  • Proposal forms carry data about family members and nominees, so notice and consent design must cover people who are not the applicant.
  • Health data has no special DPDP category, but its sensitivity raises breach impact and penalty exposure.
  • Agents, brokers, TPAs and web aggregators must each be classified as processor or separate fiduciary.
  • Insurance record-keeping obligations prevail over erasure requests where they require retention.
  • DPDP's right to nominate under Rule 14(4) is a data-rights nomination, distinct from a policy nominee.

Who this is for: Life, health and general insurers, Insurance brokers and web aggregators, Third-party administrators, InsurTech startups, Insurance compliance and DPO teams

What does DPDP change for insurers?

Insurers process some of the most sensitive personal data in the economy: medical histories, lifestyle disclosures, income, family details, claims documents, hospital bills, and in motor and property lines, location and asset data. They do so through long chains — agents, brokers, web aggregators, bancassurance partners, TPAs, surveyors, hospitals, reinsurers.

From 13 May 2027, DPDP requires:

  • Rule 3 notices that itemise personal data and specify purposes.
  • Consent that is specific and unbundled where consent is the basis.
  • Rule 6 security safeguards, including over processors.
  • Rule 7 breach notice to every affected person and the Board, with a 72-hour detailed report.
  • Rule 8(3) one-year minimum retention of processing logs, then erasure unless law requires longer.
  • Rule 9 contact person and Rule 14 rights and grievance processes.

Sectoral rules issued by IRDAI — including on maintenance of records, outsourcing and cyber security — continue to apply. Where they are stricter, they prevail in practice; where they require retention, section 8(7) allows it. Insurance records are subject to sectoral localisation expectations too; check current IRDAI requirements for where policy and claims records must be held.

DPDP has no separate sensitive data category, but health data's sensitivity is a factor in SDF designation and in the Board's penalty assessment.

Proposers, insured family members and nominees

A single proposal form may contain data about the proposer, spouse, children, parents and nominees. Each is a Data Principal.

Design points:

  • Notice to whom? The proposer provides others' data. Give a Rule 3 notice to the proposer that explains what is collected about each insured person and why, and give insured adults their own notice and access to rights once the policy is issued — through the policy document, app or email.
  • Children on family floater policies. Children under 18 are covered by section 9. The proposer is typically the parent; Rule 10 requires verifying that the person giving consent is an identifiable adult, which reliable KYC details you already hold can satisfy (Rule 10(1)(a)).
  • Health disclosures. Collect only what underwriting needs. Avoid open-ended free-text medical fields where structured questions will do.
  • Nominees. Policy nominee details are collected for claim settlement; use them only for that purpose.

Two different "nominations" exist:

ConceptSourcePurpose
Policy nomineeInsurance law and policy termsReceives claim proceeds
DPDP nomineeSection 14; Rule 14(4)Exercises the Data Principal's data rights on death or incapacity

Do not conflate them in systems. See the DPDP right to nominate.

Agents, brokers, TPAs and aggregators: who is the fiduciary?

Role mapping is the hardest part of DPDP for insurers.

PartyLikely roleNotes
InsurerData FiduciaryDecides underwriting and claims purposes
Individual agentProcessor for the insurerActs on insurer's behalf; needs contract and controls
BrokerOften a separate fiduciary for advice and placementShares data with insurers for quotes
Web aggregatorSeparate fiduciary for lead generation; processor for some flowsCheck consent for sharing leads
TPAProcessor for insurer for claims administrationHandles hospital and claims data
Hospital in cashless networkSeparate fiduciary for treatmentShares data with TPA/insurer for claims
ReinsurerSeparate fiduciary or processor depending on arrangementOften offshore — check transfer rules

Consequences:

  • Processors need a valid contract (section 8(2)) with Rule 6(1)(f) security clauses, breach notice fast enough for your 72-hour Board report, one-year retention and erasure.
  • Separate fiduciaries need their own basis and notices; sharing between fiduciaries should be disclosed in notices.
  • Section 11 lets a Data Principal learn the identities of fiduciaries and processors her data was shared with. Keep a sharing register.

See Data Fiduciary vs Data Processor.

Claims analytics, fraud models and AI underwriting

AI is used across insurance: document extraction from claims, fraud scoring, health-risk underwriting, telematics pricing, and chat-based servicing.

  • Purpose limitation. Data collected for underwriting a policy is used for that policy's underwriting and servicing. Using it to train cross-portfolio pricing models is a new purpose — check notice and consent coverage.
  • Accuracy. Section 8(3) requires completeness, accuracy and consistency where data is used for decisions affecting the Data Principal. Claim rejections and underwriting decisions qualify. Provide correction routes and human review of adverse automated outcomes.
  • Fraud analytics. Document the basis. Section 17(1) exempts processing for prevention, detection and investigation of offences in specified ways, but it is narrow; take advice before relying on it for broad fraud scoring.
  • Telematics and wearables. Continuous location or activity tracking needs specific consent and a clear purpose. For children, section 9(3) bars tracking and behavioural monitoring.
  • Medical documents into LLMs. Mask identifiers before sending claim documents to an extraction model; prohibit vendor training on them.
  • Offshore reinsurance and analytics. DPDP allows transfers except to notified countries under section 16; check IRDAI requirements on where records must be held.

See masking for AI pipelines.

Breach, retention and rights

Breach. Insurers hold data that causes real harm when leaked: diagnoses, claims, financial details. Rule 7 requires notifying each affected person without delay — description, likely consequences, mitigation, protective steps and a contact — and the Board without delay, followed by a detailed report within 72 hours. Breaches at agents, brokers acting as processors, TPAs or vendors are still your breach to report where they process on your behalf. CERT-In's 6-hour incident reporting applies in parallel.

Retention. Insurance contracts can run for decades, and claims records have sectoral retention requirements. Section 8(7) allows retention necessary for compliance with law. Separate:

  • policy and claims records required by law — keep for the required period;
  • lead data from aggregators and unconverted quotes — erase when the purpose is over;
  • processing logs — at least one year under Rule 8(3), then erase.

Rights. Publish request channels and the identifiers needed — policy number, customer ID, registered mobile or email (Rule 14(1) and 14(5)). Respond to grievances within your published period, at most 90 days. Publish the Rule 9 contact person and include it in every response.

Insurer readiness plan to 13 May 2027

  1. Role register for every intermediary, TPA, hospital network, reinsurer and vendor.
  2. Proposal form redesign — itemised notice, minimised health questions, family-member notices.
  3. Consent unbundling for marketing, cross-sell and data sharing with partners.
  4. Contract refresh for processors with DPDP clauses.
  5. Retention schedule reconciling IRDAI record-keeping with DPDP purpose limits and Rule 8(3).
  6. AI governance — inventory of underwriting, claims and fraud models; accuracy and human-review controls.
  7. Breach workflow covering processors and the 72-hour report.
  8. Rights desk for policyholders and insured members.
  9. Lead hygiene — confirm aggregator leads arrive with valid consent for sharing.
  10. Re-notices — under section 5(2), send DPDP notices to existing policyholders whose consent was obtained before commencement.
  11. Training for agents and branch staff on what data they may collect, where to store it and when to share it.

Large insurers may be considered for SDF notification given data volume and sensitivity; keep DPIA-ready documentation. See DPDP for hospitals and health-tech for the cashless-claims side.

Further reading on suhasbhairav.com

Before 13 May 2027

Compliance checklist

  1. Classify every intermediary's role

    Record agents, brokers, aggregators, TPAs, hospitals and reinsurers as processors or separate fiduciaries.

    DPDP Act s. 8(1)

  2. Redesign proposal-form notices

    Itemise data for proposer and each insured person and specify purposes in plain language.

    Rule 3

  3. Minimise health questions

    Collect only the medical data needed for underwriting, using structured questions.

    DPDP Act s. 6(1)

  4. Verify parents for children on family policies

    Use reliable KYC details already held to confirm the consenting parent is an identifiable adult.

    Rule 10(1)(a)

  5. Separate policy nominees from DPDP nominees

    Keep claim nominees and data-rights nominees as distinct records.

    Rule 14(4)

  6. Update processor contracts

    Add safeguards, breach notice, retention and no-training terms for TPAs and vendors.

    Rule 6(1)(f)

  7. Reconcile retention schedules

    Keep legally required records, erase unconverted leads, and keep logs one year.

    DPDP Act s. 8(7); Rule 8(3)

  8. Add human review to adverse AI outcomes

    Ensure accuracy controls and correction routes for claims and underwriting decisions.

    DPDP Act s. 8(3)

  9. Prepare breach reporting across partners

    Require partners to notify you fast enough for the 72-hour Board report.

    Rule 7(2)(b)

Key dates

  1. DPDP Rules notified

  2. Core DPDP obligations apply to insurers and intermediaries

Answers

Frequently asked questions

Does DPDP apply to insurance companies in India?

Yes. Insurers, brokers, aggregators and InsurTechs that process digital personal data are Data Fiduciaries or Processors under the DPDP Act, with core obligations from 13 May 2027. IRDAI's sectoral rules continue to apply alongside, and stricter requirements, such as record retention, continue to govern.

Is a TPA a Data Processor under DPDP?

Usually, when it administers claims on the insurer's behalf and instructions. The insurer then remains responsible under section 8(1), must have a valid contract under section 8(2), and should include security, breach notice, retention and erasure terms. Where a TPA decides purposes for itself, it may be a separate fiduciary for those.

Can a policyholder ask an insurer to delete her data?

She can request erasure, but section 8(7) allows retention where necessary for compliance with law. Policy and claims records subject to insurance record-keeping requirements will be kept for the required period. Data with no remaining purpose or legal need, such as unconverted quotes, should be erased.

Is a DPDP nominee the same as an insurance policy nominee?

No. A policy nominee receives claim proceeds under insurance law and the policy terms. A DPDP nominee under section 14 and Rule 14(4) exercises the Data Principal's data protection rights if she dies or becomes incapacitated. Insurers should store and handle them separately.

Does every insurance data breach have to be reported?

Yes. Rule 7 has no materiality threshold. Every personal data breach must be notified to each affected person without delay and to the Board, with a detailed report within 72 hours. Breaches at processors such as TPAs or vendors are included. CERT-In reporting within 6 hours also applies to specified incidents.

Can insurers use wearables or telematics data for pricing?

Only with specific, informed consent and a Rule 3 notice that itemises the data and the pricing use. Continuous tracking is intrusive, so limit collection to what pricing needs and set retention. For children, section 9(3) prohibits tracking and behavioural monitoring.

Legal references and sources

  • Digital Personal Data Protection Act, 2023 — Sections 5, 6, 7 and 8 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rules 3, 6 and 7 (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 14(4) (nomination) (official text)
  • Digital Personal Data Protection Rules, 2025 — Rule 8(3) (official text)

This guide explains the law for engineering and business teams. It is not legal advice; confirm how it applies to your organisation with qualified counsel, and check the Gazette for later notifications or amendments.

About the author

Suhas Bhairav

Suhas Bhairav

Systems architect and applied AI practitioner who designs production AI systems for Indian and global companies, with a focus on privacy-by-design under the DPDP Act and the EU AI Act.