Deleting Somebody on Request

What people usually mean

Somebody asking to be deleted is normally asking for one of three things, and establishing which saves a great deal of work.

Stop sending me marketing, which is the most common by a distance and is solved in a minute.

Remove my details from your systems, meaning they do not want to be contacted or held on file.

Or erase everything, including records of work you did, which is the one that cannot be fully honoured.

Asking which they mean, politely, is a reasonable first response and frequently the whole answer.

This is a general description rather than legal advice, and the specific rights and exceptions depend on your jurisdiction.

What you can usually remove

• Mailing list entries, immediately.
• Unconverted enquiries with no continuing purpose.
• Marketing profiles and segmentation records.
• Photographs not required for a warranty or claim.
• Notes and correspondence beyond your retention period.
• Duplicate copies in spreadsheets and drives.

The last is the one that gets missed, and it is why the same person reappears in a mailing six months later from a list somebody kept separately.

What you usually cannot

The part that has to be explained rather than apologised for.

Financial records attached to a transaction are generally subject to statutory retention, and an invoice cannot be deleted because the customer would prefer it gone.

Records needed for a warranty you are still honouring, or for a claim that is live or reasonably foreseeable, are similarly retained.

Employment records have their own requirements.

And a suppression record, which is the note that this person asked not to be contacted, is itself something you keep, because deleting it entirely is how somebody gets added back next time a list is imported.

That last point is worth explaining when it comes up, since it sounds contradictory and is in the person's interest.

Suppression is not the same as deletion

A distinction worth understanding and worth explaining.

Removing somebody from a mailing platform entirely means nothing prevents them being re-added when a list is next imported from your customer system.

Keeping a minimal suppression entry, usually just the address and the date, means the platform will not send to them regardless of what is imported later.

That is the mechanism that makes an unsubscribe actually hold, and it is why platforms handle it that way by default.

If somebody objects to even that being held, the honest answer is to explain what it is for and let them decide, rather than deleting it and having them reappear.

A worked example

A firm received a request from a former customer to delete everything they held.

The instinct was to comply fully, which would have meant destroying invoices from a job completed eighteen months earlier.

They checked with their accountant, then replied explaining what they had done and what they had kept.

Removed: mailing list entry, two enquiry records, a copy of his details on a shared spreadsheet, and nine photographs of the job.

Kept: the invoice and payment record, for the statutory period, with the reason stated, and a suppression entry so he would not be contacted again.

He replied that this was fine and that he had only wanted the emails to stop.

The whole thing took an hour, and the explanation was what made a partial deletion acceptable rather than a refusal.

Tell them what you did

The step that determines how this is received.

A response saying your details have been removed, when they have not entirely, is inaccurate and creates a problem if the person later discovers they are still on file.

Instead: here is what we have deleted, here is what we have kept, here is why, and here is how long we will keep it.

That is a short paragraph and it converts a refusal into an explanation, which is how most people receive it.

Confirm the marketing has stopped specifically, since that is usually the actual concern and people want to hear it addressed.

Do the sweep properly

The practical failure that undermines everything else.

Deleting from the main system and missing four other locations means the person hears from you again, and a second contact after a deletion request is considerably worse than the first.

Work through the inventory: mailing platform, customer system, spreadsheets, shared drives, form archives, email, phones, and any third-party service.

Search on variants, since a mailing list may hold an old address that a system search will not find.

And note what you did, so if they appear again you can establish where from and close that route rather than repeating the exercise.

When somebody else asks on their behalf

A situation that arises more often than expected and briefly stalls people.

A solicitor, a family member, an executor, or a representative writes asking you to remove somebody's records.

The principle is the same as for any request: satisfy yourself that the person is entitled to make it before acting, because deleting somebody's records on the instruction of a stranger is its own problem.

For a solicitor, a letter on their file usually carries an authority reference. For a family member, written authorisation from the person themselves is the straightforward answer, and asking for it is reasonable rather than obstructive.

Where somebody has died, the position differs by jurisdiction and by what you hold, and it is worth checking rather than assuming either that the records are now unprotected or that nothing can be done.

In every case, reply promptly explaining what you need, rather than leaving the request unanswered while you work it out.

The counter-case

Deletion requests should not become an occasion for excessive caution in either direction.

Refusing to delete anything on the grounds that records might one day be useful is not defensible, and treating every request as a threat produces a defensive response to somebody who usually just wants the emails to stop.

Equally, deleting a live customer's entire history on request, including records of work under warranty, can leave both parties worse off, and it is reasonable to explain that before doing it.

Where a request arrives in the middle of a dispute, keeping what is relevant to that dispute is normal practice rather than obstruction, and saying so plainly is better than a vague refusal.

Proportionate and explained beats both full compliance and reflexive resistance.

How to handle it

1. Ask what they actually want removed.
2. Stop the marketing immediately, and say so.
3. Delete what has no continuing purpose.
4. Keep what you are obliged to, and note why.
5. Sweep every location, including spreadsheets and phones.
6. Keep a suppression entry so they stay off lists.
7. Tell them what was deleted and what was kept.

Step five is the one that decides whether the request stays resolved, since a second contact afterwards undoes all of it.

Handling the earlier question is covered in a customer asking what you hold about them.

Frequently asked questions

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.