Skip to content
Capabilities · Compliant Data Collection

Let your forms create the legal record as they collect the data

Compliant Data Collection connects your web forms, apps and other collection points to GovernID. When a form opens, it shows the current approved privacy notice and consent text for that process. When the person submits, the legal parameters in force at that moment are added to the data and a collection report is created for that record alone. Nothing changes for the person filling in the form, the system receiving the data or your team.

Click a step, or press play.

sample-company.com/careersYour website
Sample CompanyCareers

Join us · Application form

ApplySent ✓

As the form opens, the current approved privacy notice and consent text for that process come from GovernID. The consent box starts unticked.

What Compliant Data Collection is

Compliant Data Collection means that when personal data is collected at a collection point connected to GovernID, the current approved privacy notice and consent text are shown, and the legal parameters in force at that moment are tied to the record as a collection report for that submission alone.

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. Compliant Data Collection is where GovernID’s method, Point Zero Privacy®, is applied: the legal groundwork is done in the RoPA before the data arrives, and tied to the record the moment it does. In GovernID’s own words, it works like transparent carbon paper on your form: it doesn’t change the work, it keeps the legal copy of every submission.

What it does, and doesn’t do

  • At the collection points you connect, it shows the right text and creates the legal record of every submission.
  • It installs nothing inside your company and doesn’t change your form, the receiving system or your team’s workflow. The data goes to your system as it always has.
  • It isn’t a data discovery or scanning tool and doesn’t find data in systems that aren’t connected to GovernID. It doesn’t delete data in your systems; it shows which records are due, and your team decides and acts.
What we hear from DPOs, legal and IT teams

Your RoPA knows the rules. Your forms don’t.

Your RoPA says why data is collected, on what legal basis and for how long. But the forms on your website, app and stores don’t carry that information. Does any of this sound familiar?

Which notice is the form on our site showing?

Your lawyer updated the notice last month. The careers page, the mobile app, the tablet in the store: do they all show the new version? Often nobody is sure. Forms connected to GovernID show the current approved version every time they open.

What did this person see on screen that day?

When the question comes a year later, you have the data but not the text the form showed that day. The collection report keeps the versions of the notice and consent text the person saw, together with the record.

Retention changed. What about the older records?

It was two years, now it’s three. Records from the same form no longer share a deletion date, and tracking that in a spreadsheet is nobody’s job. Each record carries its own retention period and deletion date.

Which text was the consent box ticked against?

Consent text changes too. “They consented” isn’t enough; you need to show to what, and with which text. The record shows the version of the consent text accepted and the data categories it covers.

A request came in: how many times did this person’s data enter our company?

Job application, loyalty programme, visitor check-in… each in a different system, under different terms. Searching by hand takes days. One search across connected collection points shows every entry with the terms of that day.

Won’t integration take months?

It’s the question IT teams ask most. Nothing is installed in your network and the form doesn’t need rebuilding; a form can be connected in as little as a few hours.

Why every record is different

Two records from the same form may not follow the same rules

Legal texts are alive: a notice is updated, a typo is fixed, retention changes. After each change, new records are held under the new terms and older ones under the old terms. So the data from one processing activity isn’t uniform, and each record has to be accounted for on its own.

Careers formPrivacy noticeRetentionDelete on
Application · 12 Mar 2026version 2.12 years12 Mar 2028
1 Jun 2026 · New notice approved, retention raised from 2 to 3 years
Application · 3 Sep 2026version 3.03 years3 Sep 2029

Sample data. We explain why records, not data types, are the unit of accountability on the Record Lineage page.

What changes

The legal groundwork is done before the data arrives, and tied to it the moment it does

Today’s formsWith Compliant Data Collection
Notice on the formEmbedded in the page, staticThe current approved version for that process, every time it opens
When the text changesUpdated form by formApproved in GovernID; connected forms show the new version
What the record holdsThe form dataData + text versions, purpose, legal basis, retention, notification status
RetentionOne period assumed per activityEach record has its own deletion date
When someone asks about a personManual searches, system by systemOne search across connected collection points
Workflow—Unchanged for the person, the receiving system and the team
The moment of collection in the law

Many obligations start at the moment data is collected

The duty to inform, demonstrating consent, retention and data subject requests all rest on the same question: under which terms was this data collected?

ObligationWhat GovernID providesWhat remains for your company
GDPR Art. 13(1)–(2) · KVKK Art. 10(1)
Where data is collected from the data subject, the information is given at the time the data is obtained.
Every time the form opens, it shows the current approved privacy notice for that process.Deciding what the notice says and approving it.
KVKK Notice Communiqué Art. 5(1)(e) · GDPR Art. 5(2)
Under KVKK the burden of proving that the information was given lies with the controller; the accountability principle requires compliance to be demonstrated.
Each record keeps the version of the notice the person saw and when the data was collected.Documenting the notice separately at collection points that aren’t connected.
GDPR Art. 7(1) · KVKK Art. 3(1)(a), Notice Communiqué Art. 5(1)(f)
Where processing is based on consent, the controller must be able to show that consent was given. Under KVKK, explicit consent relates to a specific matter and is based on information; the notice and the consent are handled separately.
The consent text is shown separately from the notice, with an unticked box; the record shows the version accepted and the data categories it covers.Deciding whether consent is needed and which legal basis applies.
GDPR Art. 5(1)(e) · KVKK Art. 4(2)(d), Erasure Regulation Art. 11
Data is kept no longer than necessary for the purpose. Under KVKK, a controller with a retention and destruction policy erases at the first periodic destruction, whose interval can’t exceed six months.
Each record carries its own retention period and deletion date; records due for deletion are listed with a query.Erasing, destroying or anonymising the data in your own systems.
GDPR Art. 15(1)(d), (g) · KVKK Art. 11(1)(a)–(b), Art. 13(2)
People have the right to learn whether their data is processed and to ask about it; the GDPR also lists the retention period and the source. Under KVKK a request is concluded within thirty days at the latest.
With an email, phone or ID number, every entry of the person’s data at connected collection points is listed with the terms of that day.Checking unconnected systems separately and answering the request.

In GovernID your notices and consent texts are prepared from your RoPA; the legal provisions are loaded for your company’s country.

In four steps

Prepare, connect, collect, account for it

  1. 1
    Prepare the rules in advance. Define the process in your RoPA: purpose, legal basis, retention period, notice and consent texts. The legal groundwork is finished before any data arrives.
  2. 2
    Connect the collection point. Add a single script to your existing web form, embed a GovernID form, or connect by API. See Easy Integration.
  3. 3
    The form opens with the right text. The person sees the current approved notice and consent text, fills in the form and submits. The data goes to your system as usual.
  4. 4
    Every submission carries its own record. GovernID creates the collection report for that submission. Person and deletion queries run on these reports.
What’s on screen

Every record arrives with its own legal rules

Current notice and consent text

Connected forms show the approved version for that process every time they open. You approve the text once in GovernID; GovernID works in nine languages.

Legal parameters per record

Each record carries its purpose, legal basis, retention period and the deletion date calculated from it.

A collection report for every submission

When it was collected, with which notice and consent versions and under which terms, in one report. Reports can’t be altered; only you can delete them.

Contact notification and verification

If you choose, a notification describing the transaction goes to the email and phone on the form, and the answer is added to the record. See Contact Verification.

Keeps collecting if the connection drops

Collection points connected by API keep collecting if the connection drops; records are sent when it’s back.

Person and deletion queries

List a person’s records across connected collection points, or the records due for deletion. See DSAR Automation.

Who it helps

The decision in the RoPA, the practice on the form and the proof on the record, in one place

DPOs and compliance teams

The decision you make in the RoPA becomes the rule applied on the form. In a request you show every entry of the person’s data; in an audit, the terms in force that day.

DPOs and compliance teams
Legal teams

The text you approve is the text connected forms show. When you change it, older records stay tied to the old version and new ones to the new.

Legal teams
IT and data teams

Nothing is installed in your network and forms aren’t rebuilt. You don’t need to embed legal texts in forms, ship a release for every change or keep retention periods in code.

IT and data teams
What you will see in the demo

Let’s connect a form together and create the first record

  1. 01
    We connect a sample application form to GovernID.
  2. 02
    We update and approve the notice in GovernID; the form shows the new version.
  3. 03
    We send a sample application and open its collection report: text versions, purpose, legal basis, deletion date.
  4. 04
    We search all of a person’s records across connected collection points with an email address.
  5. 05
    We list the records due for deletion.
Request demo
Frequently asked questions

About Compliant Data Collection

What is Compliant Data Collection?

When personal data is collected at a collection point connected to GovernID, the current approved notice and consent text are shown, and the legal parameters in force at that moment are tied to the record as a collection report for that submission alone.

Do we need to change our forms?

No. A single script can be added to your existing web form, a GovernID form can be embedded on your site, or your system can connect by API. Nothing changes for the person filling in the form, the receiving system or your team.

Where do the notice and consent text come from?

From your legal texts in GovernID. They are prepared from your RoPA and approved, and each collection point shows the version approved for its process.

What happens when we update the text?

Once you approve the new version, connected forms start showing it. Records collected earlier stay tied to the version shown on their day.

What does the collection report contain?

When the data was collected, the collection point and process, the versions of the notice shown and the consent accepted, purpose, legal basis, retention period and deletion date; and, if notification is on, its status.

If retention changes, what happens to earlier records?

Each record keeps the retention period and deletion date in force on the day it was collected. Records collected after the change follow the new period.

Does GovernID delete our data?

It doesn’t delete the data in your systems. It lists the records that are due; deciding and carrying out erasure, destruction or anonymisation stay with your team.

What if the connection to GovernID drops?

Collection points connected by API keep collecting; records are sent when the connection is back.

Can records be altered?

No. Collection reports can’t be altered; only you can delete them.

Is it included in our licence?

Live data automation is an extension of the same licence that scales with the records you manage. You turn it on when you’re ready.

Forms whose data already knows its rules

Pick one of your forms; we’ll watch together how the right text is shown and how the first record’s collection report is created.

Request demo