Skip to content
Capabilities · Legal Retention

Let your retention rules give every record its own deletion date

You set retention periods once in your RoPA, by process or by data category. Every record collected through GovernID carries its own deletion date, based on the period in force on the day it was collected. If the period changes later, records already collected keep their date. You see which records are due for deletion before they are overdue, and the systems that hold the data delete or anonymise it and, if you choose, mark the destroyed record in GovernID.

Click a step, or press play.

GovernIDSample Company

RoPA · Recruitment · Retention

Sample data
Identity, contactKept for 2 years after the application is decided.
CV (consent)Deleted if consent is withdrawn; otherwise kept for 1 year.
Destruction methodDeletion · anonymisation
RoPA versionversion 12 · 19 Nov 2026

The retention period is defined in the RoPA, by process or by data category. For data based on consent, a condition such as “deleted if consent is withdrawn” can be set too.

What Legal Retention is

Legal Retention means that the retention period is defined once in the RoPA, by process or by data category, and every record collected through GovernID is given its own deletion date based on the period in force on the day it was collected.

GovernID is a Privacy Management Automation platform: it makes the RoPA the single source for notices, consent, data subject requests, DPIAs and audit evidence, and records every data collection against it. The retention period is part of that source: under GovernID’s method, Point Zero Privacy®, the period is set in the RoPA before the data arrives and tied to the record the moment it does.

What it does, and doesn’t do

  • It applies the period you set in the RoPA to every record collected through GovernID and shows which records are due for deletion.
  • It doesn’t decide retention periods for you or give legal advice. You decide which period applies, taking your sector’s laws into account.
  • It doesn’t delete data in your systems itself. The systems that hold the data delete or anonymise it.
  • It isn’t a data discovery or scanning tool and doesn’t date records in systems that aren’t connected to GovernID. For those systems the period is documented in the RoPA and applying it stays with you.
What we hear from DPOs, legal and IT teams

A retention policy on paper doesn’t delete anything

The policy says two years. How old is the data in our systems?

The retention policy is written down, but nobody has in front of them which record must go when. Without a date on each record, the policy stays on paper.

The period changed. Which rule do older records follow?

When two years becomes three, records collected before and after the change must be deleted on different dates. Tracking that in a spreadsheet soon becomes impossible.

Does every piece of data in a process have the same period?

An application’s identity data needs one period; a CV kept with consent needs another. A single period per process leads to keeping too much or too little.

A yearly clean-up: too early or too late

When nobody knows the deletion date, the work turns into one big yearly clean-up. Some data goes before its time, some stays for months too long.

When someone withdraws consent, which data has to go?

When a person withdraws consent, only the part of the record based on consent has to go, not the whole record. If the record doesn’t make that distinction, either too much is deleted or nothing is.

How do we show it was deleted?

In an audit the question is “when and how was this data destroyed?”. If deletion happened in different systems, so does the evidence.

A common misconception

GDPR and KVKK don’t give you a retention period

Neither law sets a fixed period. GDPR requires that personal data is kept in a form that permits identification for no longer than is necessary for the purposes of processing (Art. 5(1)(e)). KVKK requires that data is kept for as long as the relevant legislation provides or the purpose of processing requires (Art. 4(2)(d)). The company sets the period, documents why, and applies it to every record. Periods in sector-specific laws are part of that decision.

Careers formRoPA versionRetentionDelete on
Application · 12 Mar 2026version 122 years12 Mar 2028
1 Jun 2026 · Retention raised from 2 to 3 years (RoPA version 13)
Application · 3 Sep 2026version 133 years3 Sep 2029

Sample data. We explain why every record is handled on its own on the Record Lineage page.

What changes

From policy to record

TodayWith Legal Retention
Where the period livesIn a policy document, a spreadsheet, inside codeIn the RoPA, by process or data category, versioned
Date on the recordNone; the deletion date is worked out again every timeEvery record carries its own deletion date from the moment it is collected
When the period changesOld and new records are assumed to follow the same ruleCollected records keep their date; new records get the new period
Deletion timingOne big yearly clean-upRecords due for deletion are listed period by period
EvidenceScattered emails and system logsEvery record’s deletion date and the destruction method in the RoPA are known; destroyed records can be marked through the API
Retention and destruction in the law

What the law asks, what GovernID provides, what stays with you

Türkiye’s regulation on deletion and destruction says it plainly: having a retention and destruction policy doesn’t mean data has been kept or destroyed in line with the law (Art. 5(2)). The proof is in the records.

ObligationWhat GovernID providesWhat remains for the company
Storage limitation
GDPR Art. 5(1)(e) · KVKK Art. 4(2)(d)
The period is defined in the RoPA by process or data category; every record collected through GovernID carries its own deletion date.Setting the period and documenting why; assessing periods in sector-specific laws.
Period in the record of processing
GDPR Art. 30(1)(f) · KVKK Registry Regulation Art. 3(1)(h), 5(1)(ğ)
Periods are part of the RoPA and every change shows in a RoPA version. The VERBİS output (Türkiye) is produced from the same RoPA.Keeping the VERBİS entry up to date (Türkiye); the maximum period published there is the basis for destruction.
Telling people the period
GDPR Art. 13(2)(a), 14(2)(a), 15(1)(d)
The privacy notice produced from the RoPA includes the retention period. People also see the retention period and deletion date of each of their records in the Privacy Center.Approving the privacy notice; where the period isn’t fixed, explaining the criteria used to set it.
Deletion when the purpose ends or consent is withdrawn
GDPR Art. 17(1)(a)–(b) · KVKK Art. 7(1) · KVKK Deletion Regulation Art. 7(1)
Records due for deletion are listed. When a consent withdrawal is approved, only the part of the record based on consent is marked for destruction.Choosing and carrying out deletion, destruction or anonymisation (KVKK Deletion Regulation Art. 7(4)–(5)).
Periodic destruction
KVKK Deletion Regulation Art. 11(1)–(3)
Records due now and soon are listed period by period; connected systems receive the list.Setting the interval in the policy (at most six months; within three months if no policy is required) and carrying out destruction.
Proof of destruction and the policy
GDPR Art. 5(2) · KVKK Deletion Regulation Art. 5, 6(1)(g), 7(3)
The periods and destruction methods in the RoPA are the source for the retention and destruction table in your policy. Your systems can mark the records they destroyed through the API; since the record’s content is deleted, the record is also removed from GovernID after a set period.Preparing the retention and destruction policy where required (Türkiye: controllers registered with VERBİS); keeping destruction logs in your own systems for at least three years.

References are taken from Regulation (EU) 2016/679, Türkiye’s Law No. 6698, the Regulation on the Data Controllers’ Registry and the Regulation on the Deletion, Destruction or Anonymisation of Personal Data. The legal provisions that apply are loaded for the country chosen at first setup.

In four steps

From retention rule to deletion

  1. 1
    Define the period. In the RoPA, choose one period for the process or a separate period per data category. The period is combined with a retention sentence you prepare in the Privacy Taxonomy, for example “deleted if consent is withdrawn, otherwise kept for 1 year”.
  2. 2
    Record the destruction method. For each process, write in the RoPA how data is destroyed at the end of the period.
  3. 3
    Records get their date. Every record collected through Compliant Data Collection carries its deletion date, based on the period in force that day. If the period changes later, the collected record keeps its date.
  4. 4
    Delete what is due. List the records due or coming due for deletion. Systems connected by API receive the list, delete or anonymise the data and, if you choose, mark the destroyed record.
What’s on screen

Every record knows when it has to go

Reusable retention sentences

Write the retention sentence once in the Privacy Taxonomy with a parameter; pick the period in each process.

Period per data category

Different data in the same process can have different periods.

A deletion date on every record

Calculated from the period in force when the record is collected, and it doesn’t change afterwards.

Versioned RoPA

A change of period shows in a new RoPA version; two versions can be compared.

Deletion query

List records that are due, coming due or past their date, process by process; for example those due next month.

Marking deletion by API

Connected systems receive records due for deletion and can mark the records they destroyed in GovernID.

What you will see in the demo

Let’s turn a retention rule into a record together

  1. 01
    We set retention periods per data category in a sample process.
  2. 02
    We send a sample application and open the record’s deletion date.
  3. 03
    We change the period and compare the new RoPA version with the old one; the collected record’s date stays the same.
  4. 04
    We see the same record on the person’s Privacy Center screen.
  5. 05
    We list the records due for deletion.
Request demo
Frequently asked questions

About legal retention

How long do GDPR and KVKK say we can keep data?

Neither sets a fixed period. GDPR requires not keeping data longer than necessary for the purpose (Art. 5(1)(e)); KVKK requires keeping it for as long as the relevant legislation provides or the purpose requires (Art. 4(2)(d)). The company sets the period and documents it in its RoPA.

Does GovernID decide retention periods for us?

No. Your legal team decides the period. GovernID keeps that decision in the RoPA and applies it to every record collected through GovernID.

What happens when we change a retention period?

New records get the new period. Records already collected keep the deletion date they were given. The change shows in a new RoPA version.

Can different data in one process have different periods?

Yes. You can choose one period for the process or a separate period per data category.

What happens if someone withdraws consent?

The request lands in your list. When the people you authorise approve it, only the part of the record based on consent is marked for destruction; data based on other legal grounds stays for its own period.

Does GovernID delete data in our systems?

No. The systems that hold the data delete or anonymise it. GovernID shows which records are due; your systems can mark the records they destroyed through the API.

How do we see which records are due for deletion?

With a deletion query, process by process: both records already due and those due next month. Systems connected by API can receive the same list and mark the records they destroyed.

Where do people see the deletion date?

In the Privacy Center, on each of their records: collection date, retention period and deletion date.

What happens to the record in GovernID?

When its retention period ends, the record is marked for destruction and destroyed after a set period. If your systems mark a record as destroyed, the record is also removed from GovernID after a set period, since its content has been deleted.

Is writing a retention policy enough?

No. Türkiye’s deletion regulation says explicitly that having a policy doesn’t mean data was kept or destroyed lawfully (Art. 5(2)), and GDPR expects you to be able to demonstrate compliance (Art. 5(2)). GovernID makes the periods and destruction methods in your RoPA the source for your policy, and shows the practice through per-record deletion dates.

Put a deletion date on every record

Pick one of your processes; we’ll watch together how the retention rule in your RoPA becomes a deletion date on each record.

Request demo