• Home >
  • News >
  • IRDAI’s Public Insurance Registry Explained: What Data It Will Link, Who Gets Access and How Privacy Is Handled

IRDAI’s Public Insurance Registry Explained: What Data It Will Link, Who Gets Access and How Privacy Is Handled

IRDAI's Public Insurance Registry explained: what data it will link, who gets access and how privacy is handled

IRDAI has proposed a Public Insurance Registry that would connect insurance records across companies without creating one central database. The consultation paper sets out how policy, claims and identity data could be linked, who could access it and what privacy controls would apply.

The Insurance Regulatory and Development Authority of India released its Public Insurance Registry consultation paper on September 1, 2026. The proposal would create a common digital layer for insurers, intermediaries, policyholders, regulators and other authorised users. IRDAI has invited comments until September 30 through the official PIR consultation portal.

The registry could link product details, policy and claims records, intermediary information, grievances, policyholder identity and unclaimed amounts. It could also connect, for specific purposes, with CKYC, Aadhaar authentication, vehicle-registration systems, health and mortality registries, weather and disaster databases and court case-management systems, according to the consultation paper.

PIR Would Keep Source Systems as the Primary Record

IRDAI does not propose moving every insurance record into one database. Instead, the framework follows a “source-system primacy” model, under which the insurer, government agency or other institution maintaining a record remains the authoritative source.

The paper sets out three ways to handle information. Under the reference model, PIR would keep a pointer to data held elsewhere. A governed copy could hold information needed for a legitimate cross-insurer purpose under defined controls. An anonymised aggregate could support research, market analysis or protection-gap studies without identifying individual customers.

This structure means a detailed claim file, for example, could remain with the insurer while PIR helps an authorised user discover or verify relevant information.

Access Would Depend on Purpose and Consent

Access would not be identical for every participant. IRDAI and other authorised bodies could use relevant data for regulatory or investigative purposes, while customers could access their own information.

Insurers could access customer information for an identified purpose and with consent where required. The consultation framework says consent should be “specific, informed, revocable and auditable.” Researchers and other approved users could receive anonymised or aggregated datasets rather than identifiable policyholder records.

The framework also proposes role-based permissions, purpose limits, data masking and audit trails. In addition, insurer-specific pricing models, underwriting rules and product strategies would stay outside shared cross-industry datasets.

PIR would have to comply with the Digital Personal Data Protection Act, 2023, the Aadhaar Act, 2016 and the Information Technology Act, 2000.

Identity Matching Would Use Aadhaar, PAN and CKYC

The proposed identity framework would use strong identifiers such as Aadhaar, PAN and CKYC where available. However, older insurance records may not always contain a reliable common identifier.

In those cases, PIR could use probabilistic matching based on demographic information and assign confidence levels to a possible match. Low-confidence cases could require manual review. Existing records would also be standardised progressively at renewals or other significant policy events rather than through a one-time industry-wide conversion.

Also Read: How Insurance Works in India

Policyholders Could Gain a Consolidated Insurance View

For customers, one practical benefit could be easier discovery of policies held across different insurers. That may help families trace forgotten policies and identify unclaimed amounts. A portable claims history could also reduce repeated documentation when a customer changes insurers or seeks new cover.

However, broader data connectivity makes the design of consent equally important. Customers will need to understand what data an insurer wants, why it wants it and how long that permission lasts.

Frequent requests could also create consent fatigue if notices become routine or difficult to assess. Therefore, the scope and presentation of data-sharing permissions will matter as IRDAI develops the final framework.

IIB Would Operate the Registry Under IRDAI Ownership

The consultation paper proposes converting the Insurance Information Bureau into a not-for-profit company wholly owned by IRDAI. IIB would establish PIR under a separate regulatory framework.

IRDAI also proposes a phased rollout based on individual use cases, data readiness, legal requirements, privacy safeguards and technology readiness. The framework remains a consultation proposal, not an operational registry, with comments due by September 30, 2026.

If PIR changes how your insurance information is shared or used, MyRupia can help you understand what those changes mean for your existing policies and future purchases. Talk to a MyRupia expert for independent insurance guidance.

Disclaimer: This MyRupia article is for informational purposes only and is based on publicly available government, regulatory and industry sources. It should not be treated as investment, financial, tax, insurance, or legal advice. Information, examples, market data, and expert views mentioned in the article may change over time and should not be considered a recommendation to buy, sell, invest in, or surrender any financial product. Readers should evaluate their individual circumstances and consult a qualified financial professional before making decisions.

All Categories
Scroll to Top