Skip to content
Capabilities · Classified at Collection

Every field collected through GovernID is classified before the first record arrives

Before a data set enters the company, what it contains is already known; nothing is guessed afterwards. Your legal and compliance teams clarify the process with the business units and pick the category of each field when the form is designed, and special category data is flagged from the start. Your RoPA, DPIA recommendations and reports read that decision.

Click a step, or press play.

sample-company.com/careersYour websiteSample
Sample CompanyCareers

Join us · Application form

I have read the privacy notice for my application.

Apply
GovernIDNew record · 14.11.2026 10:42
4 fields classified1 special categoryPrivacy notice version 3

The form on your site stays as it is; its design and its place are yours.

What Classified at Collection is

Classified at Collection means that the category of every personal data field collected through GovernID, and whether it is special category data, is set before any data is collected, when the form is designed.

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. Classified at Collection is the first step of GovernID’s method, Point Zero Privacy®.

What it does, and doesn’t do

  • It classifies every field from the forms and collection points connected to GovernID, before the first record.
  • It doesn’t scan your systems or guess the category of the data inside them.
  • It is not a security or data loss prevention (DLP) tool. Information security stays your company’s responsibility; GovernID keeps the record of your privacy obligations.
What we hear from DPOs, legal and IT teams

Asking “what is this?” after the data has arrived is exhausting

The category question comes back with every audit, every request and every new system. Does any of this sound familiar?

What exactly is in this column?

The field is called “note2”. A tool says “probably health data”, and making sure is still up to you. For fields collected through GovernID the question doesn’t come up: your legal team chose the category when the form was designed.

When will we find out we collect special category data?

Usually in an audit, a request or a breach, which is the latest possible moment. In GovernID the sensitive field is flagged before the first record arrives, and GovernID recommends a DPIA for the process.

Does the RoPA say one thing while the form collects another?

Forms change while the RoPA stays put, and the gap often shows up only at the next review. In GovernID the RoPA and the forms use the same category list, so they speak the same language.

“Name”, “Full name”, “Applicant name”… are they all the same?

Every team names fields its own way, and the report ends up with three separate lines. In GovernID a field’s category is the same whatever its name, and reports read the category.

Which processes use health data?

When someone asks about a category, you open and read one process file after another. In GovernID you open a category and see every process that uses it in one list.

Which categories go into our records of processing?

The category list is gathered again every year by email, and it gets unclear who sent which list. In GovernID, your reports, including the VERBİS output for Türkiye, are prepared from the same classification your collection points use.

The Point Zero Privacy® difference

Scanning tells you what you hold, not why you hold it

Data discovery solutions scan servers and databases after data has entered the company, and tell you what is inside. GovernID tells you why it is there: for what purpose, on which legal basis and under which notice it was collected, and how long you may keep it. That is the question privacy audits ask: not what the data is, but why you hold it and on which legal basis. The whole point of privacy compliance work is being able to show, during an audit, that you comply with the law; the GDPR states this as the accountability principle (Art. 5(2)). Those answers exist at one moment only: the moment of collection.

Before data enters

The content is settled

Your legal and compliance teams work through the process with the business units: which data will be taken from which people, why, and on which legal basis. Every field on the form is designed with that decision.

As data enters

What arrives is known

As the data set comes in, the categories it contains are already known and special categories are flagged. There is nothing to interpret afterwards.

After data has entered

Why it is held is known

Data discovery answers “what is inside?”. GovernID answers “on which legal basis may we hold this?”. If you already have a data discovery solution, GovernID complements it: one shows what is inside, the other why it is there.

Scanning afterwardsClassified at collection
WhenAfter data is in your systemsBefore data arrives, when the form is designed
Who sets the categoryA tool estimates it from the contentYour legal and compliance teams, after clarifying with the business units, once
Special category dataVisible if a scan finds itFlagged before the first record
What the data set containsEstimated from the scan resultsKnown before data enters
Legal basis, purpose, notice, retention periodUsually not visibleKept with every record
ScopeExisting data in the scanned systemsData collected through GovernID
The question it answers“What do we have?”“On which legal basis may we hold this?”

One doesn’t replace the other; they complement each other. Your data discovery solution keeps showing what is inside for data collected earlier; GovernID stops new data from entering the company unclassified and without its legal basis on record. Read about the Point Zero Privacy® method.

Data categories in the law

Categories come up in almost every obligation the law sets

The RoPA, special category conditions, DPIAs and registry notifications all rest on the same question: which categories of data do you take from which people?

ObligationWhat GovernID providesWhat remains for your company
KVKK Art. 16(2), (3)(c) · Türkiye
Controllers that must register do so before processing starts; the notification describes the groups of people and the data categories.
The VERBİS output is prepared from the RoPA categories that the forms use too.Filing the notification in VERBİS and keeping it current.
GDPR Art. 30(1)(c)
The record of processing activities describes the categories of data subjects and of personal data.
The categories in the RoPA and those chosen on forms come from the same list.Keeping the RoPA in line with real processes and making the classification decisions.
GDPR Art. 9 · KVKK Art. 6
Separate and stricter conditions for processing special category data.
Special categories come flagged, and the processes that use them are listed.Choosing the legal basis and meeting the processing conditions.
GDPR Art. 35(3)(b)
Processing special category data on a large scale requires a DPIA.
GovernID recommends a DPIA for processes that handle special category data.Assessing the scale, carrying out the DPIA and making the decision.
In four steps

Classification happens at design time

  1. 1
    Define the process in your RoPA. Record which data categories you take from each group of people, and for what purpose.
  2. 2
    Design the form. Pick a category and sub-category for each field, for example Contact › Email address or Health › Blood group. Your existing forms connect to GovernID too.
  3. 3
    Collect. Each record arrives classified; special category fields are flagged, and contact details can be verified by email or SMS where needed.
  4. 4
    Use it everywhere. Your RoPA, DPIA recommendations, the VERBİS output, Breach Impact Analysis and the preliminary DSAR report read the same classification.
What’s on screen

Know what each field holds before the first record arrives

Category and sub-category

Two levels for every field. Start from the ready-made list and extend it any time in Privacy Taxonomy.

Special category flag

Categories such as health, biometric or genetic data come flagged in the ready-made list; for categories you add, you set the flag.

Same language as your RoPA

Forms and the RoPA use the same category list, so the same category means the same thing in every process.

Verification by data type

Choose email or SMS verification at data type level for the contact details that need it.

Used in processes

Open any category and see every process that uses it.

Category names in nine languages

Category names are kept in the product’s nine languages, so forms in different languages use the same category.

Whose work it makes easier

The category decision is made once, and everyone reads the same answer

DPOs and compliance teams

The RoPA and the forms use the same list. Special category data is visible before it is collected, and the DPIA recommendation comes with the process.

DPOs and compliance teams
Legal teams

The person who knows what the field means picks its category, once. Because the notice is generated from the RoPA, the categories you describe come from the same list as what the form collects.

Legal teams
IT and data teams

You don’t have to guess what fields hold or build classification spreadsheets for legal. The answer to “where is this data used?” is in GovernID.

IT and data teams
What you will see in the demo

Let’s classify the fields of a form together

  1. 01
    We open a category and its special category flag in Privacy Taxonomy.
  2. 02
    We pick the category of each field on a form.
  3. 03
    We submit a sample entry; the record arrives classified.
  4. 04
    We list the processes that use a category.
  5. 05
    We show the DPIA recommendation on a process with special category data.
Request demo
Frequently asked questions

About Classified at Collection

What is Classified at Collection?

It means the category of every personal data field collected through GovernID, and whether it is special category data, is set before any data is collected, when the form is designed. The RoPA, DPIA recommendations and reports read that classification.

Does GovernID scan our systems?

No. GovernID doesn’t scan your systems; it classifies every field from the forms and collection points connected to it, before any data is collected.

We already have a data discovery solution. Do we still need GovernID?

They do different jobs and complement each other. Data discovery shows what is inside your systems. GovernID records why data collected through it is there: for what purpose, on which legal basis and under which notice it was collected, and how long it may be kept.

Who sets the category?

The people you allow to design forms, in most companies the legal or compliance team. The category is chosen once and applies to every record collected with that form.

How do you know what a data set contains before it arrives?

Because the content is decided before data arrives. Your legal and compliance teams clarify the process with the business units and pick the category of every field on the form. So when a data set collected through GovernID comes in, its categories are not an estimate but a decision made in advance.

Can we add our own categories?

Yes. You start from the ready-made list and add or change categories and sub-categories in Privacy Taxonomy at any time.

Who decides which categories are special category data?

Special categories come flagged in the ready-made list. For categories you add, your company sets the flag.

What happens when a form collects special category data?

The field is flagged as sensitive, and GovernID recommends a DPIA for the processes that use it. The decision to carry out the DPIA stays with your company.

Do we have to replace our forms?

No. Your existing forms connect to GovernID and keep working as they do; their fields are classified with the same category list.

Can we see where a category is used?

Yes. Each category lists the processes that use it.

See it on one of your own forms

Pick one of your forms; we’ll look together at how its fields are classified before data arrives, and how special category data shows up early.

Request demo