Key takeaways
- IRDAI released a consultation paper on 1 September 2026 proposing a Public Insurance Registry for India.
- The PIR is designed as interoperable digital public infrastructure—not one giant central database holding every insurance record.
- Policyholders could use it to discover and compare products, verify licensed sellers, view policies and claims, and identify unclaimed benefits.
- The proposal also covers insurers, intermediaries, reinsurers, lenders, regulators, government agencies and approved researchers.
- Nothing is live yet. IRDAI has invited feedback until 30 September 2026, and the use cases still need detailed technical specifications.
India’s proposed Public Insurance Registry is an access layer intended to connect trusted insurance information across the sector. It could help a policyholder see policies and claims, check whether an insurer or intermediary is licensed, compare products and find unclaimed benefits. However, IRDAI’s plan remains a consultation proposal. It is not a working consumer portal, a final regulation or a confirmed launch timetable.
The Insurance Regulatory and Development Authority of India released the paper on 1 September 2026 and invited comments until 30 September. The primary consultation is available through the Insurance Information Bureau’s PIR portal. The announcement has also been reported independently by Moneycontrol, The Economic Times, Business Standard and India Today.
What the Public Insurance Registry is meant to solve
Insurance information is fragmented. A household can have life, health, motor, property and travel policies from several providers. Records may sit in different apps, email accounts and paper folders. Insurers, hospitals, agents, lenders and regulators can also hold different versions of the same basic facts.
That fragmentation creates friction. A policyholder may struggle to locate an old policy, confirm a nominee or understand a claim’s status. An insurer may repeat identity and policy checks. A lender may need to verify whether pledged property has valid cover. Regulators may receive information in formats that are difficult to compare.
IRDAI says the PIR should create a consistent and authoritative view of insurance information while allowing appropriate records to remain with the institutions that hold them. That distinction is important. The proposal is not simply to copy every sensitive document into a single central store. It is to create standards, identity mechanisms and authorised connections that can return verified information.
The plan supports the objectives of the Sabka Bima Sabki Raksha Act, 2025. IRDAI links it to consumer protection, wider coverage, market efficiency, competition and financial resilience. Technology can reduce friction, but the registry will not by itself make a policy affordable or guarantee that a claim is paid.
How the PIR could help policyholders
The consultation describes a broad set of possible user journeys. A customer could discover and compare insurance products using standard information. The same system could help verify whether an insurer, agent or intermediary is authorised before a purchase.
After buying cover, a policyholder could get a connected view of policies and claims. That may be especially useful for families with products from several insurers or for nominees trying to identify benefits after a death. The registry may also help surface unclaimed amounts that a family did not know existed.
Service requests could become easier if identity and policy information can be verified once and used through an authorised workflow. Updating contact details, tracking a claim or proving ownership may require fewer manual documents. Existing electronic insurance accounts already offer some consolidation; IRDAI’s insurance repository FAQ explains that older framework. The new PIR proposal is wider because it imagines a common information layer across many stakeholders and use cases.
Consumers should not assume that every feature will appear in the first release. IRDAI says the identified use cases are conceptual and will be converted into functional and technical specifications as the project progresses.
Eight stakeholder groups in IRDAI’s proposal
| Stakeholder | Possible use of the registry |
|---|---|
| Policyholders | Compare products, verify sellers, view policies and claims, locate benefits |
| Insurers | Improve underwriting, pricing, claims and customer service |
| Reinsurers | Use standard exposure and loss information for risk assessment |
| Intermediaries | Speed up verified onboarding and policy servicing |
| Regulators | Monitor customer outcomes, protection gaps and emerging risks |
| Financial institutions | Verify policy ownership and collateral cover |
| Government agencies | Study coverage gaps and design public programmes |
| Researchers | Use approved anonymised datasets for evidence-based analysis |
These uses are connected. Better data standards could make a customer’s policy easier to service and also help a regulator compare outcomes across the market. Yet access must stay purpose-limited. A lender, researcher or government department should not automatically see a person’s complete insurance history merely because the registry exists.
Privacy, consent and security are the hard part
Insurance records can reveal health conditions, family relationships, income, property and claims history. Connecting those records can improve service, but it also increases the impact of weak access controls or misuse. IRDAI is therefore asking for views on privacy, consent safeguards, identity, commercial confidentiality and governance.
Consent must be understandable and revocable. A customer should know which information is requested, who is requesting it, why it is needed and how long the permission lasts. A generic “agree” button would not be enough for a system that can connect highly sensitive records.
Accuracy is another risk. A wrong date of birth, nominee, claim status or policy number can cause real harm. The final design needs a visible correction process, an audit trail and responsibility for resolving mismatches between institutions.
Cybersecurity will require more than a secure login. The system needs strong authentication, encryption, monitoring, vendor controls and a tested incident-response plan. Access should follow the least-privilege principle: a participant receives only the fields necessary for an approved task.
What PIR could change for insurers and competition
IRDAI expects better information to support product design, underwriting, pricing, claims and customer service. An insurer could reduce repeated checks where verified data is available. Standard reporting may also reduce regulatory friction and make industry-wide comparisons more reliable.
More transparency could make it easier for customers to compare products and service quality. That can shift competition away from opaque sales pitches toward price, coverage and outcomes. It may also expose protection gaps—groups or regions where people consistently lack useful cover.
The registry will not eliminate commercial confidentiality. Insurers have proprietary pricing models, underwriting methods and customer information. The consultation asks how to share enough verified data for public value without revealing trade secrets or enabling unfair profiling.
For intermediaries, verified identities and licences could speed onboarding and reduce mis-selling by unregistered actors. The market is also consolidating: Lapaas Voice’s report on the InsuranceDekho–RenewBuy integration shows why consistent information and service standards matter as distribution platforms grow.
What happens next
The immediate step is consultation. Stakeholders and members of the public can respond through the designated portal or by email using IRDAI’s prescribed template. The deadline is 30 September 2026.
After reviewing feedback, the regulator and technical partners would need to define governance, data standards, identity rules, consent flows, security controls and a transition plan. Insurers and other institutions would then need time to connect systems, clean records and test customer journeys.
There is no confirmed launch date. Any article describing the PIR as an already operational national database is premature. The useful news today is that IRDAI has moved the idea into a formal consultation with defined stakeholder use cases and a public feedback deadline.
For now, customers do not need to register for a new account or upload documents anywhere. They should rely on existing insurer and IRDAI channels. Any unofficial website asking for policy files or identity information in the name of the new registry should be treated cautiously until IRDAI announces an authorised service.
FAQs
What is the Public Insurance Registry?
It is IRDAI’s proposed digital public infrastructure for trusted, interoperable access to insurance information across authorised participants.
Is the Public Insurance Registry live?
No. IRDAI released a consultation paper on 1 September 2026. The use cases remain conceptual, and no public launch date has been announced.
Will all insurance data be stored in one central database?
The proposal describes an information and access layer that can create a consistent view while allowing appropriate data to remain with source institutions. The final architecture is still under consultation.
How could policyholders benefit?
Possible benefits include comparing products, verifying insurers and intermediaries, viewing policies and claims, simplifying service requests and identifying unclaimed benefits.
What are the biggest risks?
Privacy, consent, cybersecurity, inaccurate records, exclusion of offline users and misuse of data are the central design risks.
When is the consultation deadline?
IRDAI has invited comments and suggestions until 30 September 2026 through the designated PIR consultation channel.
Get the day’s top stories in your inbox
One concise email. No spam, unsubscribe anytime.
