The Right to Be Forgotten Meets an Insurer That Can't Find the Data

A customer sends a deletion request — the right to erasure under privacy law — and asks you to remove everything you hold about them. It sounds like a simple instruction. Then someone has to actually do it, and the uncomfortable truth surfaces: the insurer doesn't know everywhere the customer's data lives. It's in the policy system, the claims system, a data warehouse, three spreadsheets, an email archive, a marketing tool, and a couple of vendor platforms nobody fully maps. You can't delete what you can't find, and most insurers can't find all of it.

Why "delete my data" is so hard to honor

Fulfilling an erasure or access request assumes something most insurers don't have: a reliable, complete view of where a single customer's data is scattered. Data has spread across decades of systems, integrations, and copies, and nobody maintained a map of it. So the request either gets a partial, best-effort response — which is a compliance risk if a copy is missed — or it triggers a frantic manual hunt across teams, which doesn't scale past a handful of requests. Neither is a real answer; both are symptoms of not knowing your own data landscape.

Where it breaks down

  • No customer-level data map. You can list your systems, but you can't say with confidence which ones hold this specific person's data, in what fields, under what identifiers.
  • Broken identity. The customer is "J. Smith" in one place and "John Smith" in another with a different ID, so a deletion in one system leaves copies untouched elsewhere.
  • Uncontrolled copies. Extracts, backups, and analyst spreadsheets hold shadow copies no governance process tracks.
  • Manual fulfilment. Each request is a bespoke project, so volume — or an audit — turns a legal right into an operational crisis.

Why it's really a data-foundation problem

The privacy request is just the moment the weakness becomes visible. The underlying issue is that you don't have a resolved view of the customer and a map of where their data lives — the same gap that breaks customer 360, fair-value reviews, and open-insurance data sharing. An insurer that can resolve a customer across every system and knows what each system holds can fulfil erasure as a routine, auditable process. One that can't will keep discovering, request by request, that its data owns it rather than the other way around. Privacy readiness is a data-governance and entity-resolution capability, not a legal form.

What good looks like

  1. A resolved customer identity that ties every record across every system to one real person.
  2. A living data map that says where a customer's data lives, in which fields, under which identifiers.
  3. Governed copies so extracts and backups are tracked, not shadow data nobody can reach.
  4. Automated, auditable fulfilment that executes and evidences a request end to end.

Privacy law didn't create the problem — it exposed one that was already there. The insurers who handle erasure and access requests calmly are the ones whose data foundation already knows the customer and the map. Building that foundation — resolution, cataloguing, governed copies — is exactly the kind of work we do with insurers at IntelliBooks.

"Delete everything you have about me" is a one-sentence request. Whether you can answer it honestly is a measure of whether you actually know your own data.

Comments

Post a Comment

Popular posts from this blog

Why Your Insurance Data Warehouse Didn't Fix Anything

You built the data warehouse. It took eighteen months and cost more than planned. Policy data, claims data, billing — it's all in there. The project was declared a success and everyone moved on. And yet: underwriting still can't see the whole customer. The AI initiative is still stalled. Someone still asks for a report and waits three weeks. Nobody says it out loud, but the question hangs there — what exactly did we buy? You're not alone, and it isn't because you built it badly. It's because a warehouse solves a problem you didn't have. The problem a warehouse solves Warehouses solve location . Before: your data was in eight systems. After: it's in one place. That's genuinely valuable — you can run a query across policy and claims without begging two teams for extracts. But notice what that fixes: it fixes where the data is . It doesn't touch what the data means , whether it's trustworthy, or whether the records refer to who you think t...
Read more

Embedded Insurance: Why the API Is the Easy Part

Embedded insurance is the idea that coverage should be offered at the moment of need, inside someone else's product — travel insurance at checkout, device protection when you buy the phone, cover for the rental car in the booking flow. It's one of the fastest-growing distribution models in the industry, and every insurer has a strategy slide about it. Most of those strategies underestimate the same thing, and it isn't the partnerships or the product. It's the data plumbing. Everyone assumes the API is the hard part. The API is the easy part. What embedded insurance really demands The promise of embedded is speed and invisibility: a customer buys a flight and, in the same breath, is offered exactly the right travel cover at exactly the right price, and accepts with one tap. No forms, no friction. Deliver that and you've won. But "exactly the right cover at exactly the right price in one tap" makes brutal demands on your back end: You must price i...
Read more

Insurance Knowledge Graphs: The Foundation AI Needs Before It Can Think

Every insurer wants enterprise AI. Few realise they're missing something much more fundamental. Knowledge. Not data. Knowledge. Insurance companies already possess enormous amounts of information. Policy systems contain customer records. Claims platforms hold loss histories. CRM systems track interactions. Document repositories store underwriting reports. Data warehouses consolidate analytics. Yet AI still struggles to answer surprisingly simple questions. Not because the information doesn't exist. Because the relationships between that information remain invisible. Data tells you what exists A customer database tells you who someone is. A policy database tells you what they bought. A claims system tells you what happened. An accounting platform tells you what was paid. Each system is internally consistent. Together they rarely behave like a connected enterprise. Humans mentally assemble those relationships every day. Computers usually canno...
Read more