industry-guides7 min read20 June 2026

PDPA for Insurance Companies: Claims Data Guide

A practical PDPA compliance Singapore guide for insurers handling claims data. Learn your PDPC requirements, consent rules, retention limits and breach duties.

ComplyHQ Team

PDPA for Insurance Companies: Claims Data Guide

If your business underwrites policies, manages claims, or operates as an agency in Singapore's insurance sector, PDPA compliance in Singapore is not optional — it is a core operational duty. Insurance is one of the most data-intensive industries: a single motor or health claim can pull together NRIC numbers, medical reports, bank details, accident photos, and witness statements. The Personal Data Protection Act 2012 (PDPA) governs how your organisation collects, uses, discloses, and protects every piece of that information. This guide breaks down what claims data compliance actually requires, the specific PDPC requirements that apply to insurers, and the practical steps your business can take to avoid costly penalties.

TL;DR — Key Takeaways

  • Claims data is among the most sensitive personal data your business handles; it routinely includes NRIC, medical, and financial details that trigger the PDPA's highest-risk obligations.
  • Insurers must satisfy all 11 PDPA obligations, but Consent (s13–17), Protection (s24), Retention Limitation (s25), and Data Breach Notification (Part 6A) are the most claims-relevant.
  • You must notify the PDPC within 3 calendar days of any notifiable breach, and breaches affecting 500+ individuals are automatically notifiable.
  • PDPC financial penalties can reach up to 10% of annual turnover in Singapore or S$1 million, whichever is higher, for serious breaches.
  • Appointing a Data Protection Officer (DPO) is mandatory under Section 11(3) — there are no exemptions for small agencies.

Why claims data is the highest-risk personal data your business holds

Insurance claims data is high-risk because it combines identity, health, and financial information in a single file — the exact data categories that cause the most harm when leaked. Under the PDPA, this kind of data attracts a higher "reasonable security arrangement" standard, meaning regulators expect stronger safeguards than for ordinary contact details.

When a customer files a claim, your organisation typically collects: their NRIC or FIN, medical and treatment records, police and accident reports, photographs, salary and bank statements, and sometimes data about third parties (witnesses, dependants, beneficiaries). The PDPC treats data whose unauthorised disclosure could cause significant harm — including financial loss, identity theft, or distress — as warranting heightened protection. Health and financial data sit squarely in that category.

Definitive statement: A claims file that contains an individual's NRIC number combined with medical or financial details will, in almost every case, meet the PDPC's "significant harm" threshold — which means a breach of that file is presumptively notifiable to both the regulator and the affected individual.

This is why insurers cannot treat data protection as a tick-box exercise. The volume, sensitivity, and third-party exposure of claims data make it a priority enforcement area for the PDPC.

What does PDPA compliance in Singapore require from insurers?

PDPA compliance in Singapore requires insurers to meet all 11 data protection obligations set out in the Act, with particular rigour around consent, purpose limitation, protection, retention, and breach notification. In practice, this means knowing exactly what data you hold, why you hold it, who you share it with, and how you secure it.

Here are the obligations that matter most for claims handling:

Your business must obtain consent and clearly notify policyholders of the purposes for collecting their data — and you may only use claims data for those notified purposes or reasonably related ones. For example, consent given for "processing your claim" reasonably extends to fraud checks and loss adjusting, but not to cross-selling unrelated investment products without separate consent.

Actionable step: Review your proposal forms and claims forms. Ensure every purpose — claims assessment, fraud investigation, reinsurance, and disclosure to adjusters — is plainly stated at the point of collection.

2. The Protection Obligation (Section 24)

Section 24 requires your organisation to make reasonable security arrangements to protect personal data in your possession or under your control. For claims data, "reasonable" means encryption of files at rest and in transit, role-based access controls so only assigned adjusters can open a file, and audit logs. The 2020 amendments (in force from 2021) also clarified that this obligation explicitly covers protection against unauthorised access, modification, and disposal.

3. The Retention Limitation Obligation (Section 25)

You must cease retaining claims data once the legal and business purpose has ended. Insurers face a balancing act here: MAS and the Insurance Act require records to be kept for audit and dispute resolution (commonly 5–7 years post-settlement), but the PDPA prohibits keeping data indefinitely "just in case". Build a documented retention schedule that maps each data type to its statutory minimum and a hard disposal date.

4. Accountability & the DPO requirement (Section 11)

Every organisation, including a two-person insurance agency, must appoint at least one Data Protection Officer and publish their business contact information. The DPO is responsible for ensuring your organisation's compliance and acting as the contact point for the PDPC and individuals.

For a full walkthrough of these duties across all data types, our PDPA Compliance Checklist for Singapore SMEs gives you a step-by-step audit you can run in an afternoon.

How the Data Breach Notification Obligation applies to claims data

Under Part 6A of the PDPA, your business must notify the PDPC within 3 calendar days, and affected individuals as soon as practicable, when a data breach is likely to cause significant harm or affects 500 or more people. For claims data, this threshold is reached easily because of the medical and financial content involved.

The mandatory Data Breach Notification regime has been in force since 1 February 2021. Here is the assessment flow your organisation should follow:

  1. Contain — Stop the breach (revoke access, isolate systems, recall mis-sent documents).
  2. Assess — Determine whether the breach is "notifiable": does it risk significant harm, or affect 500+ individuals?
  3. Notify the PDPC — Within 3 calendar days of determining it is notifiable.
  4. Notify individuals — As soon as practicable, unless an exemption (e.g. data was encrypted, or remedial action makes harm unlikely) applies.
  5. Document & remediate — Record the incident, root cause, and corrective steps.

Definitive statement: Sending a claimant's full medical report to the wrong email address is a reportable data breach if it is likely to cause significant harm — even a single misdirected email can start the PDPC notification clock.

A common real-world scenario in insurance is the "wrong attachment" error — an adjuster emails Claimant A's documents to Claimant B. Because claims documents contain NRIC and health data, these incidents frequently cross the significant-harm threshold. Our detailed data breach response guide for Singapore businesses walks through exactly what to do in the first 72 hours.

What are the PDPC penalties for insurers who get it wrong?

PDPC financial penalties for serious PDPA breaches can reach up to S$1 million, or up to 10% of an organisation's annual turnover in Singapore (whichever is higher) for businesses with local turnover exceeding S$10 million. Smaller agencies are capped at S$1 million but are still routinely fined for inadequate security.

The enhanced penalty cap took effect on 1 October 2022. Financial-sector and data-rich organisations have been a consistent enforcement focus. Common failure points the PDPC has penalised across industries include:

  • Weak access controls — staff able to access files unrelated to their work.
  • Unencrypted data — sensitive records stored or transmitted in the clear.
  • Failure to conduct security reviews — no periodic testing of systems holding personal data.
  • Vendor lapses — a data intermediary (e.g. a claims-processing outsourcer) mishandling data your organisation remains accountable for.

That last point is critical for insurers: under Section 4(2)–(3), your organisation stays responsible for personal data processed by intermediaries on your behalf. A weak vendor contract is your liability. To understand how the PDPC has actually ruled in comparable matters, review our breakdown of real PDPA penalties and enforcement cases.

A practical compliance roadmap for insurance businesses

The fastest path to compliance is a data inventory followed by gap remediation across consent, security, retention, and breach readiness. Most insurance SMEs can reach a defensible baseline within weeks, not months, by working through the obligations in priority order.

Step 1 — Map your claims data flow

Document every point where claims data enters, moves through, and leaves your organisation — from the first notification of loss to final settlement and archival. You cannot protect what you have not mapped.

Update proposal and claims forms so purposes are explicit. Add a clear privacy notice covering disclosure to adjusters, reinsurers, and investigators.

Step 3 — Secure the data

Apply encryption, role-based access, and audit logging to all claims systems. If you are pursuing a recognised security standard, our ISO 27001 certification guide for Singapore SMEs shows how it reinforces PDPA Section 24 compliance.

Step 4 — Train your people

The largest source of breaches is human error. Every adjuster, agent, and admin staff member should understand consent, the "wrong attachment" risk, and the breach escalation path. See our guide on PDPA staff training requirements for a culture-first approach.

Step 5 — Build a breach response playbook

Have a written, tested plan so your team can hit the 3-day PDPC notification deadline under pressure.

This is where automation earns its keep. Manually maintaining a data inventory, consent records, retention schedules, and a breach register across a busy claims operation is error-prone. ComplyHQ offers AI-powered compliance that handles your PDPA obligations in minutes, not weeks — generating your data protection policies, mapping your obligations, and keeping your documentation audit-ready as regulations change. For insurers needing deeper system integration or bespoke claims-platform tooling, Adaptels builds custom digital solutions for Singapore SMEs that bake compliance in by design.

Frequently overlooked data protection gaps in insurance

Even diligent insurers tend to miss a few recurring issues. Watch for these:

  • Third-party data in claims — Witness and beneficiary details are personal data too, and you owe them the same obligations.
  • Legacy paper files — Old claims folders in storage rooms are a Section 24 liability if unsecured.
  • WhatsApp and personal devices — Agents photographing claim documents on personal phones is a major, often invisible, breach risk.
  • Marketing reuse — Using claims data to pitch new products without separate consent breaches the Purpose Limitation Obligation.

Addressing these gaps closes the distance between "mostly compliant" and genuinely defensible. PDPA compliance in Singapore is ultimately about being able to demonstrate accountability — knowing what you hold, why, and how it is protected.

Key takeaways

Claims data is the highest-stakes personal data your insurance business handles, and the PDPA holds you accountable for every step of its lifecycle. Focus first on consent clarity, Section 24 security, a defensible retention schedule, and a tested breach-response plan that can meet the PDPC's 3-day deadline. With penalties reaching S$1 million or 10% of Singapore turnover, the cost of getting compliance right is far lower than the cost of getting it wrong — and modern tools make a defensible baseline achievable in a fraction of the time it once took.

Sources & References

  1. PDPC — Personal Data Protection Act Overview — official summary of the PDPA 2012 and its obligations.
  2. PDPC — Advisory Guidelines on Key Concepts in the PDPA — guidance covering consent, protection, and breach notification thresholds.
  3. PDPC — Enforcement Decisions and Financial Penalties — published decisions showing how penalties are applied.
  4. Monetary Authority of Singapore (MAS) — Insurance Regulation — insurance regulation, including record-keeping requirements relevant to retention.
  5. Singapore Statutes Online — Personal Data Protection Act 2012 — full legislative text including Sections 11, 13–18, 24, 25, and Part 6A.

Simplify Your Compliance

ComplyHQ's AI can assess your PDPA compliance gaps in under 15 minutes and generate the policies you need.

Try Free Assessment

Frequently Asked Questions

Can an insurance agent in Singapore share a client's claims data with a third-party adjuster without fresh consent?
Yes, provided the disclosure falls within the purposes your client was notified of at the point of consent, such as 'assessing and processing your claim'. Under the PDPA's Consent and Purpose Limitation Obligations (Sections 13–18), claims handling, loss adjusting, and fraud investigation are typically reasonable related purposes. However, you must ensure the adjuster is bound by a written data processing agreement and only receives the minimum data needed. Always document the disclosure in your claims file.
How long can an insurer keep claims data after a policy ends?
The PDPA's Retention Limitation Obligation (Section 25) requires you to stop retaining personal data once it no longer serves a legal or business purpose. For insurance, MAS Notices and the Insurance Act often require records to be kept for a defined period (commonly 5 to 7 years after a claim is settled) for audit and dispute purposes. Once that statutory period lapses, you must securely dispose of or anonymise the data. Keeping claims data 'just in case' indefinitely is a common PDPA breach.
Do I need to report a data breach involving claims data to the PDPC?
Yes, if the breach is likely to result in significant harm to affected individuals or involves the personal data of 500 or more individuals, you must notify the PDPC within 3 calendar days of assessing it as notifiable. Claims data — which often includes NRIC numbers, medical histories, and financial details — almost always meets the 'significant harm' threshold. You must also notify affected individuals unless an exception applies. This is the Data Breach Notification Obligation under Part 6A of the PDPA.
Tags:PDPASingapore complianceSMEdata protectionPDPC

Ready to get PDPA compliant?

Stop guessing about compliance. ComplyHQ uses AI to assess your gaps, generate policies, and guide you through every PDPA obligation.

Gap AssessmentPolicy GeneratorAI Compliance Chat
18 June 20267 min read

PDPA Compliance for Startups: Essential Steps

Learn the essential steps for PDPA compliance for startups in Singapore. Practical guide covering DPO appointment, consent, and data protection for SMEs.

Read more
7 June 20268 min read

PDPA for Education Sector: Managing Student Data in Singapore Schools and Centres

Learn how Singapore schools, tuition centres, and enrichment providers must handle student data under the PDPA. Practical compliance steps for education SMEs.

Read more
7 June 20267 min read

PDPA for Real Estate and Property Agents in Singapore: Compliance Guide

Real estate and property agents must comply with Singapore's PDPA. Learn key obligations, consent requirements, and data handling best practices for your agency.

Read more