Playbook, insurance broker

A deletion request, and the three records it lands on

The request arrives as one sentence and lands on at least three things. A marketing contact can usually go. A client record sits under a retention period the firm can point at. A claims file is the hardest of them, because liability cover can produce a claim long after the policy expired and the file is the evidence of what was arranged. None of that is a refusal, but it is not a yes either, and the assistant has to say so without pretending to know which record the person is on.

Why this is not the general answer

The handling pattern for data deletion requests holds across every trade. What follows is the part that does not.

  • The retention period here is driven by how long a claim can still arrive rather than by an accounting rule, and on liability business that horizon runs for years after the policy ended.
  • The broker is not the only holder: the insurer keeps its own record of the risk and of any claim, so clearing everything on the broker's side does not remove somebody from the transaction.
  • The file is the record of what was disclosed and what was arranged, the material the firm would rely on if it were ever said that the wrong cover was placed, so deleting it removes the firm's own position as well as the customer's data.
  • A commercial client asking about deletion is often asking about employee data held on a scheme rather than about its own record, and those are separate requests with separate answers.

How it arrives

  • wipe everything you hold about me
  • i want off your renewal reminders
  • how long do you keep my details after i leave
  • can you remove my claim history from your system
  • does the insurer still have my data if you delete it
  • we have staff leaving how do we get their details removed

What has to be indexed for this to work

Material behind this answer
Your retention schedule, by type of recordEnquiry, quotation not taken up, live policy, expired policy, claim. Different periods and a different reason for each. A single retention sentence covering the firm is unanswerable, because every one of these requests is about one of those rows.
The reasons a record is kept, in plain wordsThe period over which a claim can still be notified, your own need to evidence what was arranged, and any obligation to keep a record of business placed. Somebody told only that the firm is required to keep it hears a brush off.
What is passed to insurers and what they holdWhich parties receive the data and the fact that they then hold it under their own arrangements. This is the part that surprises people, and hearing it from a page beats discovering it after a deletion appeared to be completed.
How to stop marketing without losing the policyThe unsubscribe route, and a plain statement that stopping marketing does not stop renewal correspondence or contact about a claim. Most requests that read as delete me are this one, and answering it exactly is a real result.

The reply

A reply worth copying
This could mean more than one thing. If it is marketing you want stopped, that is the quickest of them and the route is on our privacy page [1]. If you mean the record of your policies, we hold those for a set period because a claim can be notified long after a policy has ended, and the period is written down [2]. Anything on a claim is handled separately again [3]. I cannot look you up or delete anything from here, so give me your name and an email and the request goes to the person who deals with them.

It separates the marketing case out first, because that is what most people mean and it is the one that can actually be granted. The reason for retention is given as a fact about claims rather than as an appeal to rules, which is the difference between an explanation and a refusal. And it says plainly that nothing here touches a record before it takes any details.

Where it stops

The trigger. The visitor asks for a specific record to be erased, names a policy or a claim, or asks what is held about them.

The handover, worded
I cannot see or delete anything, and a request like this needs recording properly. Leave me your name and an email, and it goes to the person who handles these, who will tell you what can be removed now and what is held and why.

It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.

Never say this here

Out of bounds

  • Never confirm a record has been deleted, because nothing in this chat writes to any system and the person will stop chasing it.
  • Never say the firm holds nothing about somebody, since the assistant cannot look anybody up and an old quotation may still exist.
  • Never quote a retention period the firm has not published, as the periods differ by record and a wrong one becomes a promise.
  • Never suggest the insurer will delete its copy as well, because that is another firm's decision under its own arrangements.

Questions

Can it handle the easy ones, such as unsubscribing?
It can point at your unsubscribe route and explain what stopping marketing does and does not stop. It cannot remove anybody itself, because it has no write access to anything at all.
A client wants their claims file gone. What is the honest answer?
That it is not a decision made at the counter. The file evidences what was disclosed and what was arranged, and a request against it goes to whoever owns data requests in the firm, with the reasons given back in writing.
Does answering these on the site create a risk?
The opposite, where the material is accurate. The risk is an improvised answer promising deletion the firm cannot perform. A published retention schedule and a marketing route give the assistant something exact to quote.

Keep reading

Try it on your own material

Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.