In this article

The right to erasure, often called the right to be forgotten, lets data subjects, the people the data are about, ask a company to delete their personal data once there is no longer a reason to process it. It is set out in GDPR Article 17. On paper it sounds simple: find the data and delete it. In an electronic document archive, though, the same personal data sits in many places at once: in the document's description, in the file and its versions, in the change history, in workflows and in backups.

We explain what Article 17 says and when a company may keep data, then show how to find one person's data in CONTMAN Archive and CONTMAN HR, erase it and leave a trail, and what the system will not do for you. The legal position described is as of 28 October 2026. This is not legal advice: the retention periods that apply to your company are best agreed with your data protection officer or a lawyer.

What GDPR Article 17 says

The controller must erase personal data without undue delay where one of six grounds applies:

  • the data are no longer necessary for the purposes for which they were collected;
  • the person has withdrawn consent and there is no other legal ground for the processing;
  • the person has objected (Article 21) and the company has no overriding legitimate grounds to continue, or the objection concerns direct marketing;
  • the data have been processed unlawfully;
  • erasure is required by a legal obligation;
  • the data were collected in connection with information society services offered to children (Article 8(1)).

The controller must tell the person what action it has taken on the request without undue delay, and within one month at the latest. For complex or numerous requests, this can be extended by two further months, provided the person is told about the extension and the reasons within the first month (Article 12(3)). If the company does not act on the request, it explains why within the same month and informs the person of the right to complain to a supervisory authority and to seek a judicial remedy (Article 12(4)). Handling a request is free of charge unless it is manifestly unfounded or excessive (Article 12(5)), and where there is reasonable doubt about the requester's identity, the company may ask for additional information (Article 12(6)).

Erasure does not stop at your own archive. Every recipient to whom the data were disclosed must be told about the erasure, unless this proves impossible or involves disproportionate effort, and the person must be told who those recipients are if they ask (Article 19). If the company itself made public the data it has to erase, it takes reasonable steps to inform other controllers processing them that the person has asked for any links to, and copies or replications of, the data to be erased (Article 17(2)).

When a company may, or must, keep the data

The right to be forgotten is not absolute. Article 17(3) GDPR disapplies it to the extent that processing is necessary, among other things, for compliance with a legal obligation (point (b)) and for the establishment, exercise or defence of legal claims (point (e)).

Legal obligations. Two examples from Polish law: an employer keeps personnel documentation for the period of employment and for 10 years from the end of the calendar year in which the employment ended, unless other provisions require a longer period (Polish Labour Code, Article 94 point 9b). A taxpayer required to keep tax books keeps them, together with the related documents, until the tax liability is time-barred, unless the tax acts provide otherwise (Polish Tax Ordinance, Article 86 § 1); the liability becomes time-barred 5 years after the end of the calendar year in which the tax payment deadline passed (Article 70 § 1).

Legal claims. Data needed for claims may be kept, but only to the extent necessary and only for as long as they are needed for that purpose.

Sometimes restriction of processing (Article 18) is the answer instead of erasure, for example when the company no longer needs the data but the person needs them for their own legal claims.

There is another side, too: data must not be kept longer than necessary (Article 5(1)(e)), and the controller must be able to demonstrate compliance with the principles (accountability, Article 5(2)). The Polish Labour Code requires employers to destroy personnel documentation, in a way that prevents its content from being reconstructed, within 12 months after the period for collecting it has ended (Article 94⁷ § 1 read with Article 94⁶ point 2). Deleting data once the period is over is an obligation, not a favour.

Why erasure is hard in an electronic document archive

In an electronic archive, one person's data spreads across many layers:

  • the document's description, meaning field values such as a name or an e-mail address;
  • the file and all its versions, because every upload and replacement creates a new version;
  • what is derived from the file: the PDF preview, thumbnails, signature verification reports and the text extracted for search, including through OCR;
  • notes;
  • the document history, which shows description values as they were when saved;
  • workflows: process variables, decision comments and process history events;
  • copies of values in notifications and background jobs;
  • share links, through which a recipient sees the file and the description;
  • the signature in a PDF file, which carries the signer's name;
  • backups, which are made outside the application.

The archive will not work through all of these by itself, but it can turn erasure into a repeatable procedure.

How CONTMAN Archive helps you honour the right to erasure

CONTMAN Archive will not decide for you whether a request must be granted, but it helps you find the data, erase it, keep what must be kept and show what was done. For how retention rules and the legal hold fit into the archive as a whole, see our post on choosing an ECM system.

Find every document about the person

There is no list of all documents in the archive: you find them through search. The search screen ("Wyszukiwanie") looks in the document's description and, in categories where content processing ("Przetwarzanie treści") is switched on, in the content of the files as well. That switch is off by default, and scans are only read when the OCR module is on, which is up to the installation's operator. Before you treat the results as complete, check where full-text search works.

The search scopes (everywhere, metadata only or file content only), filters by field and the related documents tab ("Powiązane") all help: when a field such as a customer number is marked as a linking field, that tab shows the other documents with the same value. You can save the criteria ("Zapisz wyszukiwanie") to check, after the deletion, that nothing is left. Search shows only documents from categories the person may read, so whoever handles requests needs read access to every category that may hold personal data.

Before you delete anything, record who has received the data. The document history, which needs only the read documents permission, lists every share, including active ones, and every opening and download through a link. The shares tab ("Udostępnienia") shows only active links and needs the permission to share documents by link ("Udostępnianie dokumentów linkiem"), which no role has by default. Once the document is deleted, its history can no longer be opened, and you will need that list to notify the recipients (Article 19).

Delete a whole document

Deleting a document by hand removes it with its descriptions, notes and every file version, together with previews, thumbnails, signature verification reports and extracted text. If file storage fails, the deletion does not go through, the document stays, and the deletion has to be repeated. It requires the delete documents permission ("Usuwanie dokumentów") in every category of the document, and it cannot be undone. It also deletes the document's workflow processes and tasks, and its share links stop working.

After deletion, the document's history can no longer be opened in the application, but a manual deletion does not wipe the values in the history entries: they remain in the database. Only a retention rule wipes them, so documents whose description holds the person's data are better deleted by a rule.

Erase selected data and keep the document

When a document has to stay, clearing a field by hand is not enough, because the history still shows the values as they were at every save. Selected data are erased with retention rules from the document retention module ("Retencja dokumentów"). Their actions are: set a field value, clear a field, delete notes, delete the file and delete the document, the last one always on its own. A rule's history entry never contains the removed value, and the archive also wipes it from the document's other history entries. The rule also removes copies of the cleared values from the workflow variables they were copied into when a workflow started.

  • A cleared value can no longer be found as a field value, but the same text in the file remains searchable unless the rule deletes the file.
  • Deleting the file removes it with all its versions, previews and extracted text; no new file can be added afterwards.
  • A rule cannot clear a required field, but it can write a placeholder into it with the set field value action, wiping the previous value from the history.

Retention rules: deletion when the period ends

A rule is set up for a category. The period runs from the document's creation or from a chosen date field and can be 1 to 1,000 days, months or years. With a date field, its latest value counts, and a document without a value is never touched by the rule. The archive looks for overdue documents once a day and carries out the actions in a time window set by the operator. Between the deadline and the action there is a grace period of 1 to 365 days, 7 by default.

A new rule is a draft until someone activates it. Checking the scope ("Sprawdź zasięg") shows how many documents it would affect today, and the activation dialog warns that the actions cannot be undone. Saving, activating and checking the scope require administrative mode and the retention rules permission ("Reguły przechowywania danych") for the category. The document retention module is off by default; the installation's operator switches it on.

A rule leaves a trail for accountability: the data retention section on the document ("Przechowywanie danych") shows the scheduled action, the history records the rule's actions, and the rule's runs section ("Przebiegi") gives the counters for every run. Once a document has been deleted, the counters and the rule's name are the evidence. The archive keeps the run history for 365 days by default, so it is worth keeping a register of requests outside it as well.

A single request: an example configuration

A rule works on a whole category, while a request concerns one person. You can bring the two together with a configuration that the administrator prepares once:

  1. In a category, for example customer correspondence, add a date field for the date of data erasure ("Data usunięcia danych"). Fields can be added even when the category already holds documents.
  2. Set up a rule counted from that field, with a period of 1 day and the delete document action, or with field actions.
  3. Check the scope and activate the rule. The rule never touches documents without the date, so nothing happens until someone enters one.

When a request comes in, a person with the edit documents permission ("Edycja dokumentów") in that category enters today's date in the documents found. With the default grace period, the action falls due eight days later, which is within the one-month deadline, and the grace period leaves time to catch a mistake. The conditions: for the delete document action, the rule's category must be the document's primary category; a version signed in CONTMAN Sign makes the rule skip the document unless the rule is set to include signed documents ("Obejmij dokumenty podpisane"); and a running workflow defers the action until it ends. You can check the outcome in the document's data retention section. A rule counted from a field that is still being prepared is blocked, so the new field has to be ready first.

A legal hold for data needed for claims

Placing a legal hold ("Załóż blokadę prawną") with a reason means that no rule will change or delete the document while the hold lasts. It is placed by a person with the edit documents permission in any category of the document, without administrative mode, one document at a time; when it is released, the grace period starts again. The hold belongs to the document retention module and applies to rules only: it does not stop a person who has the delete documents permission in all of the document's categories, and it does not prevent edits.

Personnel files in CONTMAN HR

In CONTMAN HR (the personnel files module, "Teczki pracownicze"), each employer is a document category, so permissions and retention rules work for personnel files just as they do for the rest of the archive, and you find a personnel file by the employee's first and last name or employee ID ("ID pracownika"). A rule can be counted, for example, from the expiry date field ("Data ważności"); documents without that date are skipped, so you need a second rule counted from the document's creation, or a deliberate decision. The system does not calculate the period the Polish Labour Code requires: the employer sets it.

Only an empty personnel file can be deleted, and deleting a case in part D or E removes all its documents and files in one step; both require the delete documents permission in the employer's category. An employee has one personal record in the organisation and a separate file with each employer. A record that still has files cannot be deleted, and deleting a record requires the personal records permission ("Kartoteki osobowe") with the right to delete. Identification data in personal records and new files in employer categories are always encrypted, and the PESEL number (the Polish national identification number) never enters the search index or the change history.

Limits worth knowing

  • Manual deletion and history. The history entries of a manually deleted document stay in the database with the description values.
  • Text in the file. When a rule only clears a field, the file versions, extracted text, previews and file name remain; the scope check lists them.
  • Signed PDFs. A rule does not change a signed PDF: the signer's name stays in the signature until the whole version is gone. By default, a rule skips documents with a version signed in CONTMAN Sign and waits for the workflow to finish; both safeguards can be overridden. A PDF signed outside the system has no such protection.
  • Workflows. No rule action touches comments on decisions in workflow tasks; they go only with the document. Process history events remain even after the document is deleted.
  • Background copies. A copy of a value in notifications, document generation jobs and external calls disappears at the latest after periods set by the operator.
  • Documents in several categories. A rule deletes notes, files and documents only where its category is the document's primary category.
  • Backups. The installation's operator makes them on its own schedule, and a backup holds the data as they were when it was made, until the end of its own retention period. If the operator keeps archived database log files (WAL) or uses versioned file storage, those copies and earlier file versions also stay until the end of their own period. Agree these periods with the operator, and after restoring a backup, repeat the deletions made since.
  • HR module history. The module's history entries about a personal record (creation, changes with the previous data, deletion) and about a personnel file stay in the database even after these are deleted. The record's data appear in them with the employee ID and the encrypted first and last name, without the PESEL number.
  • Legal assessment. The system does not judge whether a rule meets legal requirements. The company sets the periods and the exceptions.

The right to be forgotten in practice: examples

These scenarios are illustrative, and the category and field names are made up for this article.

A candidate withdraws consent to future recruitment

For example: a candidate agreed that the company could keep her CV for future recruitment and, a few months later, withdraws that consent. With no other legal ground, the company erases her data without undue delay (GDPR Article 17(1)(b)).

The job applications category has content processing switched on, along with the field and rule from the configuration above. Searching everywhere for her name and e-mail address also finds her cover letter and the messages that mention her. First, HR records from the document history who has received the CV: every share, and every opening and download through a link. Then HR enters the date of data erasure, and the rule deletes the documents after the grace period, wiping the values from the history; a document in a running workflow only once the workflow is over.

A former employee asks for erasure

For example: an employee left two years ago and asks for all their data to be erased. The employer must keep the personnel documentation for years to come (Polish Labour Code, Article 94 point 9b), so here Article 17(3)(b) GDPR disapplies the right to erasure. Within a month, the company explains why and informs the person of the right to complain, and it assesses any data held outside the personnel documentation separately.

If the documentation may serve as evidence in proceedings, and the employer is a party to them or has learned that a claim has been filed or proceedings opened, the retention period is extended (Polish Labour Code, Article 94⁴), and with the document retention module on, the documents can be placed under a legal hold. Once the period and the time for collecting the documentation are over, the documents are deleted by the rule on the employer's category or by a person with the delete documents permission. The empty personnel file can then be deleted, and the personal record, with the personal records permission, only once the employee has no files with other employers in the organisation.

A customer whose invoices must stay

For example: an individual customer ends the relationship and asks for their data to be erased. The company keeps the invoices under tax law (GDPR Article 17(3)(b)), but quotes and correspondence are no longer needed (Article 17(1)(a)), provided there is no dispute.

The customer number field is a linking field, so the related documents tab leads to the customer's documents. The invoices are deleted only by a rule counted from the issue date field, with a period agreed with the accounts team. In the correspondence, the person handling the request enters the date of data erasure, so the rule deletes it after the grace period. In the customer cards category, a rule counted from the same kind of field clears the phone and e-mail fields and writes a placeholder such as "Customer deleted" into the required customer name field; the card stays because the customer number appears on the invoices. In its reply, the company explains which data it keeps and why.

The right to erasure step by step

  1. Log the request with the date it was received: the one-month deadline runs from it.
  2. Confirm the requester's identity if you have reasonable doubts.
  3. Find the data with search and the related documents tab, and save the criteria.
  4. Assess the grounds and exceptions with your data protection officer.
  5. Identify the recipients before erasing: the document history lists every share and every opening and download through a link.
  6. Erase the data with a rule; keep the data needed for claims (a legal hold protects them from rules only).
  7. Notify the recipients of the data and, if the person asks, tell them who the recipients are.
  8. Reply on time, or tell the person about an extension and the reasons for it.
  9. Record what was done: the rule's name, the run date and its counters; then run the saved search again.

Summary

The right to be forgotten in an electronic archive is not a single button but a procedure: find the data, erase it wherever it lives, keep what must be kept, and be able to prove it. We write about encryption and access control in Secure document storage, and about consistent descriptions that make search easier in Keeping documents in order. Book a demo of CONTMAN Archive, and we will show you how to prepare your archive for erasure requests.