legal247

Right to erasure: when must you delete former members, customers and employees?

In brief

The right to erasure under GDPR Art. 17 must be honoured when the data is no longer needed, when consent is withdrawn or when an objection under Art. 21 succeeds. A business may keep what the Norwegian Bookkeeping Act requires or what is needed for a specific legal claim. The request must be answered within one month, and striking out a name or marking the person as having left is not erasure.

A woman who left a sports club four years ago still receives invitations to its annual general meeting. She emails the club and asks for everything about her to be deleted. The treasurer replies politely that she is now “marked as a former member” in the membership system. The example is invented, and the reply is wrong. She is still registered, and the club now holds one more piece of information about her.

What does the right to erasure under the GDPR mean?

The right to erasure entitles data subjects to have data about them erased without undue delay when one of the grounds in GDPR Art. 17(1) applies. The most important in practice are that the data is no longer necessary for the purpose, that consent is withdrawn, that the data subject objects successfully under GDPR Art. 21, and that the processing is unlawful.

The duty applies even without a request. Under the storage limitation principle in GDPR Art. 5(1)(e) of the GDPR, personal data must not be kept for longer than the purpose requires. An erasure request often reveals that the business should have deleted the data long ago.

What did the Advocate General say about the Ghent baptismal register?

Case C-12/25 Bisdom Gent concerns a Belgian man who was baptised a Catholic as a child and later asked the Diocese of Ghent to remove him from all its registers. The diocese recorded that he had left and struck out his name, but left the data legible. The Belgian data protection authority ordered erasure, and the diocese challenged the decision in the courts.

Advocate General Laila Medina delivered her Opinion on 1 October 2026, according to the CJEU press release. In her view the baptismal register is a filing system within the meaning of the GDPR, and the church’s autonomy does not change that. The processing could be lawful on the basis of legitimate interests. The baptised person can nevertheless obtain erasure by objecting, and the church must then demonstrate compelling legitimate grounds that override his interests. That assessment is for the national court to make on the facts.

An Opinion is not a judgment, and the Court is not bound by it. Still, the reasoning fits a club’s membership register just as well as a parish book. The GDPR applies in Norway through the EEA Agreement, so the CJEU’s interpretation matters here too.

The topic is live in Norway for another reason. The Norwegian Data Protection Authority (Datatilsynet) wrote on 5 October 2026 that it has received enquiries from people registered as members of religious or life stance communities without ever having joined. The authority says they can demand erasure of the data and of the membership, and that they can complain if the community does not respond within one month. Anyone can check where they are registered on Min side at the Brønnøysund Register Centre.

When must former members, customers and employees be deleted?

The main rule is simple. When the relationship ends, the original purpose falls away, and the data must be deleted unless another purpose with its own legal basis justifies keeping it.

For clubs and associations, membership is the very basis for the processing. After a member leaves, the address, phone number and payment history are no longer needed for membership activities. Data revealing membership of a religious community, a political party or a trade union is special category data under GDPR Art. 9(1). GDPR Art. 9(2)(d) allows such organisations to process data about former members, but the provision is an exemption from the prohibition. It confers no right to keep the data forever.

The same applies to customers once the contract has been performed and any claims settled. Customer records, notes and purchase history used only for sales and service must be deleted when the period for complaints and claims has expired. If the customer objects to marketing, the objection is absolute under GDPR Art. 21(3), and there is no balancing to be done. More on the legal basis for marketing is in the article on marketing consent.

For former employees, Datatilsynet states that the employer may keep the data only for as long as necessary. Records required by the accounting rules, and information on who was employed in which period, may be kept. Warnings and other material relevant to a dispute may, according to the authority’s guidance on personnel files, be kept until the dispute has been finally resolved.

When may the business keep the data?

The exemptions are in GDPR Art. 17(3). For most businesses, two of them matter in practice, namely legal obligations and legal claims.

The Norwegian Bookkeeping Act (bokføringsloven) is the most common legal obligation. Under Bookkeeping Act § 13, accounting reports and documentation of recorded entries, among other things, must be kept for five years after the end of the financial year, while contracts and correspondence containing significant additional information must be kept for three years and six months. The obligation covers the invoice with the customer’s name and address. It does not cover the customer record, the newsletter list or the customer service notes. The statutory text changes from 1 January 2027, and it should be checked whether the retention periods are affected.

Legal claims justify keeping what is needed for a specific, foreseeable dispute. The general limitation period is three years under Limitation Act § 2 of the Norwegian Limitation Act (foreldelsesloven), which gives a natural frame for customer relationships where there has been no conflict. A general fear that someone might sue one day is not enough. In our view the business must be able to point to the claim the data will be used for.

Where the processing is based on legitimate interests, the data subject may object under GDPR Art. 21(1). The business must then demonstrate compelling legitimate grounds that override the interests, rights and freedoms of the data subject. The Advocate General accepted that proper administration of the sacraments could be such a ground, but only after a balancing on the facts. An ordinary club or online shop will rarely have grounds of that weight.

The archiving exemption in GDPR Art. 17(3)(d), read with GDPR Art. 89(1), is narrower than many assume. In the Advocate General’s view, archiving in the public interest must serve society as a whole, rest on a legal obligation to keep the archive and give the authorities or the public some form of access. A company’s or club’s own history archive will seldom meet those conditions. Personal Data Act § 17 of the Norwegian Personal Data Act (personopplysningsloven) restricts the rights of access, rectification and restriction for such processing, but says nothing about erasure.

Situation Main rule What may be kept
Former member Delete once the membership has ended and fees are settled Accounting records under Bookkeeping Act § 13
Former customer Delete once the contract is performed and claim periods have expired Invoices and contracts for the statutory periods, a marketing suppression list
Former employee Clear out the personnel file when employment ends Period of employment, accounting records, documents for a specific dispute
Objection to processing based on legitimate interests Delete unless the business demonstrates compelling legitimate grounds What is necessary for the ground demonstrated

Is it enough to block or strike out the data?

No. Restriction of processing under GDPR Art. 18 is a separate right and a temporary measure, for instance while the business considers an objection. It is not erasure.

The Advocate General addressed exactly this point. Striking out the name in the baptismal register while it remains legible, and adding a note that the person has left, is not erasure in her view. The data must be made illegible to the extent needed for the person to be no longer identified or easily identifiable. The church may keep the fact that a baptism took place at a given place and time, and the pages need not be torn out of the book.

Marking someone as a former member is not erasure. It is a new piece of information about the same person.

In digital systems this means that a flag such as “inactive” or “deleted” is not enough if the record can still be found by a search. If the business chooses to anonymise rather than delete, the result must actually be anonymous, see the article on anonymisation under the EDPB guidelines.

How quickly must a right to erasure request be answered?

Within one month of receipt, under GDPR Art. 12(3). The period may be extended by two further months where the request is complex or there are many requests, but the data subject must be told of the extension and the reasons within the first month.

If the business refuses in whole or in part, the data subject must be told within the same period why, and that they can complain to Datatilsynet, under GDPR Art. 12(4). When data is erased, the business must notify recipients to whom it has disclosed the data under GDPR Art. 19, unless this proves impossible or involves disproportionate effort. Erasure requests often arrive together with access requests, and the deadlines for a subject access request under the GDPR run in parallel.

What should the business do?

Most erasure requests that go wrong do so because nobody knows where the data is. Further measures are on the data protection topic page.

  1. Set a deletion deadline for each category in the membership register, the customer system and the HR system, with the legal basis for the deadline.
  2. Separate accounting records from everything else, so that the invoice can stay while the customer record and notes are deleted.
  3. Map where the data sits outside the main system, typically in email, spreadsheets, newsletter tools and shared folders.
  4. Give one person responsibility for receiving, logging and answering erasure requests within the deadline.
  5. Write the reply so that it states what has been deleted, what has been kept, the legal basis for what has been kept and when it will be deleted.
  6. Run a deletion round once a year and document it, so that you can show Datatilsynet that the deadlines are actually followed and do not just sit in a procedure.

Questions and answers

May we keep a suppression list of people who have asked not to receive marketing?

In our view yes, provided the list contains only what is needed to recognise the person, typically an email address or phone number, and is used only to prevent further contact. The purpose is then to respect the objection. The list must not be used for anything else, and the person should be told that it exists.

Must we also erase the data from backups?

The GDPR has no specific rule on backups. A common approach is to erase the data in production systems at once and make sure it is not restored if a backup is brought back into use, while the backup itself is deleted in the normal rotation. The arrangement should be documented, and the data subject should be told about it.

Can a former employee demand that the entire personnel file be erased?

Not automatically. The employer may keep what the Bookkeeping Act requires, a record of who was employed in which period and whatever is needed in a dispute that has been notified or is ongoing. The rest of the file must be deleted once it is no longer needed, even if the former employee never asks.

Next legal review: 30 November 2026