Blog guideUpdated 2026-05-146 min readBy HubSecure Editorial TeamReviewed by workflow reviewers

Short summary

The right to erasure is not absolute. There are valid grounds to refuse a deletion request — but also serious consequences for ignoring a legitimate one. Here is how to handle it correctly.

  • What the workflow problem is.
  • What buyers should compare before choosing software.
  • How to move from research to workflow review.

The Right to Erasure (Right to Be Forgotten): A Complete Guide for Businesses

The right to erasure is not absolute. There are valid grounds to refuse a deletion request — but also serious consequences for ignoring a legitimate one. Here is how to handle it correctly.

Written byHubSecure Editorial Team

Practical guides for secure client portals, RBAC, onboarding and regulated client operations.

Reviewed byHubSecure Security & Compliance Review

Reviewed for security positioning, workflow accuracy and implementation clarity.

Last updatedMay 7, 2026

Checked against the current HubSecure marketing site and product positioning.

TL;DR

The right to erasure — sometimes called the right to be forgotten — gives individuals the right to have their personal data deleted without undue delay in certain circumstances. Article 17 of GDPR sets out both the right and its limits. Understanding both is essential for any regulated business that receives erasure requests from clients, former clients, employees, or prospects.

Related HubSecure buying path

Compliance CRM guidecompliance CRM for growing companiesCRM moduleHubSpot comparisoncompliance CRM guideGuide Librarybook a workflow demo

Related security, privacy and governance resources

Continue with HubSecure security and trust center, data processing agreement, subprocessors, compliance workflows, governed AI operator.

Related use case

This guide belongs to the Workspace Alternatives and Tool Consolidation Guides cluster. Continue with the product hub for workspace alternatives and tool consolidation.

When the right to erasure applies

An individual can request erasure when one of the following grounds applies:

When you can refuse erasure

The right to erasure does not apply when processing is necessary for one of the following purposes (Article 17(3)):

For regulated businesses: The most commonly applicable exemption is the legal obligation ground. AML-obliged entities must retain KYC records for five years post-relationship. A client asking you to delete their KYC file during that period can be refused on this basis — but you must tell them this and explain which legal obligation applies.

The 30-day response deadline

Like DSARs, erasure requests must be responded to within 30 calendar days of receipt. You must either confirm the erasure has been carried out, explain why you are refusing (including the specific exemption), or request an extension (maximum two months, with notice within the first 30 days).

What erasure actually means in practice

Erasure does not mean simply deleting the primary record. It means removing the individual's personal data from all locations where it exists:

Documenting erasure decisions

Whether you comply or refuse, document the decision. Record: who made the request, when, what data was affected, what decision was made, the grounds for that decision, and what action was taken. This documentation is essential if the individual complains to a supervisory authority.

When you refuse

Your refusal notice must: inform the individual of the specific grounds for refusal, advise them of their right to complain to a supervisory authority, and advise them of their right to seek judicial remedy. Be specific about which exemption applies — "we need it for legal reasons" is not sufficient.

Does erasure apply to paper records as well as digital records?

Yes. The right to erasure applies to all personal data, regardless of whether it is held digitally or in physical form. Paper records containing the individual's personal data must also be destroyed — following your secure disposal procedures.

What if erasing the data would make other records incomplete or inaccurate?

This is a genuine tension. Where complete erasure would distort other records (e.g., removing a party from a transaction record that must be maintained for tax purposes), consider whether restriction of processing rather than full erasure is more appropriate. Restriction means the data is stored but not used — and may satisfy the individual's concern without requiring destruction of legally required records.

Handle erasure requests with confidence

HubSecure's Vault and CRM give you a complete view of all data held about each client — making erasure audits, redaction, and deletion fast and fully documented.

Book a demo

Reviewed for regulated teams

Prepared by the HubSecure editorial team for operators, compliance leaders and IT reviewers evaluating secure client operations software.

Authors · Reviewers · Editorial policy

Next useful pages

Continue the workflow evaluation

These links connect this page to the most relevant buyer, migration, template and signup paths.

secure client portalsecure document collectioncompliance crm for growing companiesmodules / sentinelguides
Canonical hubs

Source-of-truth pages for this topic

These hub pages tell buyers and search engines how this page fits into the wider HubSecure information architecture.

Recommended next step

Continue the evaluation path

The next page should move the buyer from information to comparison, workflow review, template use or private rollout readiness.

Official references

Sources to verify the compliance context

HubSecure content is written for workflow evaluation, not legal advice. Use these official sources to verify regulatory and assurance context.