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.
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.
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. The deletion date is calculated and tied to the record the moment it is collected. The person sees the same date in the Privacy Center. When the period changes, the change shows in a new RoPA version. Records already collected keep their date; new records get the new period. Records due for deletion are listed. Your connected systems delete or anonymise the data and, if you choose, mark the destroyed record through the API.
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.
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.
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.
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.
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 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.
In an audit the question is “when and how was this data destroyed?”. If deletion happened in different systems, so does the evidence.
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.
Sample data. We explain why every record is handled on its own on the Record Lineage page.
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.
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.
Write the retention sentence once in the Privacy Taxonomy with a parameter; pick the period in each process.
Different data in the same process can have different periods.
Calculated from the period in force when the record is collected, and it doesn’t change afterwards.
A change of period shows in a new RoPA version; two versions can be compared.
List records that are due, coming due or past their date, process by process; for example those due next month.
Connected systems receive records due for deletion and can mark the records they destroyed in GovernID.
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.
No. Your legal team decides the period. GovernID keeps that decision in the RoPA and applies it to every record collected through GovernID.
New records get the new period. Records already collected keep the deletion date they were given. The change shows in a new RoPA version.
Yes. You can choose one period for the process or a separate period per data category.
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.
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.
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.
In the Privacy Center, on each of their records: collection date, retention period and deletion date.
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.
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.
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