Skip to content

Record Lineage

Why you need record management, not data management

Data management tells you what data your company holds. Record management lets you account for why each piece is there. Wherever a copy of personal data sits in your company, can you show where it was born and under which terms?

Managing data types does not account for them

Data management looks at types of data: phone numbers, addresses, blood groups. In most companies each department manages only the data in its own processes this way. Once data is shared with another team, ownership blurs. The same person’s phone number ends up in several copies across the company, and for none of them can anyone say under which right, for which purpose and since when it is there.

Record Lineage, from collection to deletion

  1. Collect. Record Lineage starts at collection: each submission arrives with the notice and consent versions shown, the purpose, the legal basis and the retention period in force.
  2. Record. GovernID writes a collection report for that record alone.
  3. Trace. Search a person’s email, phone number or ID and see each time their data entered your company, and under which terms.
  4. Act. See which records are due for deletion, and which consents were withdrawn, record by record.

Simplified preview

One person, three forms, three records

Ayşe gives the same details three times, in three different places. Below, the same events happen at two companies: one without GovernID, one with GovernID. As time passes, the gap grows.

Try it: click any step to explore, or just watch.or hit play and watch.

Ayşe Y.
Website12 Mar 2024Job applicationAyşe Yılmaz+44 7••• ••• 412Privacy noticeSend
Mobile app5 Jun 2024Loyalty sign-upAyşe Yılmaz+44 7••• ••• 412I consent to campaign messages.Privacy noticeSend
Visitor tablet14 Feb 2025Visitor check-inAyşe Yılmaz+44 7••• ••• 412Privacy noticeSend
When Ayşemakes a Data Subject Access Requestorthe supervisory authorityruns an audit
Ayşe Yılmaz · +44 7••• ••• 412Ayşe Yılmaz · +44 7••• ••• 412Ayşe Yılmaz · +44 7••• ••• 412Ayşe Yılmaz · +44 7••• ••• 412Ayşe Yılmaz · +44 7••• ••• 412Ayşe Yılmaz · +44 7••• ••• 412
Without GovernID
Data managementby data type
Full namePhone
Ayşe Yılmaz+44 7••• ••• 412
Ayşe Yılmaz+44 7••• ••• 412
Ayşe Yılmaz+44 7••• ••• 412
Report · Data managementCannot be shownTime to prepare a DSAR: 14 days*Found: full name, phone (3 copies)How and why it was collected is unknown.
With GovernID
Record managementAyşe Y.
Job application12 Mar 2024 · WebsiteKeptMarked for deletionNotice v3RecruitmentKept 2 years
Loyalty programme5 Jun 2024 · Mobile appKeptMarked for deletionNotice v2Campaigns · consentMembership end + 2 yrs
Visitor check-in14 Feb 2025 · Visitor tabletKeptMarked for deletionNotice v1Building securityKept 1 year
Report · Record managementCan be shownTime to prepare: 5 minutes3 records, each with its own terms
Job applicationMarked for deletion12 Mar 2024 · Notice v3 · Steps before a contract · 2 years
Loyalty programmeKept5 Jun 2024 · Notice v2 · Consent (5 Jun 2024) · membership end + 2 years
Visitor check-inMarked for deletion14 Feb 2025 · Notice v1 · Legitimate interests · 1 year

March 2024. Below, the same events happen at two companies: one without GovernID, one with GovernID. Ayşe applies for a job on the website. Her details enter both companies.

June 2024. Ayşe joins your loyalty programme in your mobile app and consents to campaign messages.

February 2025. Ayşe visits your office and checks in on the visitor tablet. Under data management the same details pile up a third time.

Two years later. Nothing changes under data management. Under record management the visitor and job application records reach their end dates and are marked for deletion; the loyalty record stays.

May 2027. Ayşe makes a request, or the supervisory authority audits you. Data management finds only a name and a phone number; record management reports every entry and its terms.

Sample data; the number is masked. * Gartner, Market Guide for Subject Rights Request Automation, 2021: 85% of organisations process an access request within two weeks. The record management time is illustrative.

A record is a dataset and the terms it was collected under

A record is the set of data collected together at one moment, such as a job application form. GovernID adds the legal parameters in force at that moment: the notice and consent versions shown, the purpose, the legal basis and the retention period. The same person can give your company their name, phone number and email three times: in a job application, in a loyalty programme sign-up and at your visitor desk. The data is the same, but the three records have different purposes, notices and retention periods, and each one has to be accounted for on its own.

Every record keeps its birth details

Adding GovernID does not change how your collection points work. Wherever a piece of data sits today, you can show how and why it is there, which notice it was collected under and on what terms.

One process, two sets of rules

Take a newsletter form that has been running for three years. On 1 March you correct its notice and extend retention from two years to three. Records collected before that date keep notice version 1 and a two-year end date. Records collected after it carry version 2 and a three-year end date. When someone asks which notice they were shown, you show the version presented when the data was collected, not the text on your site today.

Why the record level matters

  • Proving what was shown and agreed. Under the GDPR, the controller has to be able to demonstrate consent (Art. 7(1)) and compliance with the principles (Art. 5(2)). Under KVKK, the duty to inform the person sits with the data controller (Art. 10). A record that carries its own notice and consent versions is that evidence.
  • Deleting on time. Each record’s retention runs from its own collection date. Under KVKK, data is deleted at the first periodic destruction after the obligation arises, and the interval cannot exceed six months (Regulation on Deletion, Art. 11). The GDPR’s storage limitation principle points the same way (Art. 5(1)(e)). End dates kept per record show which records have reached that point.
  • Answering one person. A request from one person is answered with that person’s records across your collection points. See DSAR Automation.

Every record carries its own legal context

Collection report per record

Date, notice and consent versions, purpose, legal basis and retention for each record.

Person trace

Every entry of the same person across connected collection points.

Version-aware

Records keep the versions they were collected under, even after texts change.

Due for deletion

Records with their own end dates, listed by process.

Notification status

Whether contacts were notified and how they answered.

Consent given and withdrawn

For each record, the date consent was given and, if it was withdrawn, the date of withdrawal.

Proof

Answer for each record

Show what applied to this record, not what the policy says today.

Trace people, not tables

Follow one person across forms, systems and years.

Delete on each record’s own date

Each record is listed for deletion when its own end date comes.

Frequently asked questions

What does a collection report contain?

The date, the notice and consent versions shown, the purpose, legal basis and retention period, and the notification status from Contact Verification.

If we change a notice, what happens to records already collected?

They keep the versions they were collected under. Only records collected after the change carry the new version.

Does it work for data collected outside GovernID?

Record Lineage covers records collected through collection points connected to GovernID. See Compliant Data Collection.

Can our group companies see each other’s records?

No. Each company sees only its own records, even within a group.

Give every record its own history

See a collection report and trace one person across your collection points.