Skip to content
Capabilities · Contact Verification

Ask the owner of the email and phone number on your form, the moment the data arrives

When a form collects an email address or a phone number, GovernID sends an email to that address and an SMS to that number describing the transaction, and asks the person whether they did it. The answer is added to the record, together with which channel was verified. You choose where it applies.

Click a step, or press play.

sample-company.com/careersYour website
Sample CompanyCareers

Join us · Application form

I have read the privacy notice for my application.

Apply

The person fills in the form on your site; the email and phone number arrive exactly as typed.

What Contact Verification is

Contact Verification means that when an email address or phone number is collected through a form connected to GovernID, a notification describing the transaction is sent to it, the person is asked whether they did it, and the answer is added to the record, channel by channel.

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. Contact Verification is part of GovernID’s method, Point Zero Privacy®: whether the person was told and what they answered is tied to the record at the moment the data is collected.

What it does, and doesn’t do

  • On the forms you choose, it verifies the email address by email and the phone number by SMS, at the moment the data is collected.
  • It doesn’t check identity documents, government e-ID or biometrics. What it verifies is whether the owner of that email address and phone number confirms the transaction.
  • It isn’t a security or fraud prevention tool, and it doesn’t correct or delete records on its own. Your team makes the decision; GovernID keeps the record of your privacy obligations.
What we hear from DPOs, legal and IT teams

A contact detail on a form counts as correct until someone asks

And the one asking is usually a complaint, a request or an audit. Does any of this sound familiar?

Does this email address really belong to the applicant?

Forms accept whatever is typed: a typo, a friend’s address, a made-up number. GovernID asks the owner of the address, and the answer stays on the record.

What if someone calls to say “I never applied to you”?

If all you have is a row from the form, that’s a hard conversation. If the person was asked at the time, the record shows what they answered, or that they didn’t answer.

Who is actually reading what we send?

Notices, answers to requests, messages about consent: they all go to that contact detail. If it’s wrong, you may think you’ve met an obligation while writing to someone else.

A request came in. Is this person really the owner of the record?

It’s the first question in any data subject request. An email and phone number the person verified earlier give your assessment something concrete to rely on.

Did they really tick the consent box themselves?

The box is ticked, but by whom? If the person confirmed they did it, that sits right next to the consent record.

Who will notice a wrong contact detail, and when?

Usually through a complaint, months later. An “I don’t know about this” answer shows up on your team’s list as soon as it arrives.

Why it matters

Asking once, when the data arrives, answers many questions that come later

Whether a contact detail is correct is usually asked at the latest possible moment. GovernID asks it while the answer is still easy: when the data is collected.

Without verificationWith Contact Verification
Email and phone on the formAccepted as typedIts owner is asked when the data arrives
Whether the person knowsAssumedA notification describing the transaction goes out; the answer stays on the record
Which channelUnknownEmail and phone are shown separately
“That wasn’t me”Learned late, through a complaintLands on your team’s list with the answer
When a request comes inAssessed by looking at the form rowChannels verified earlier support the assessment
In an auditHard to say “the person knew”The notification and answer are shown with the record
Contact details in the law

A correct contact detail is the quiet precondition of many obligations

The accuracy principle, the duty to inform, data subject requests and demonstrating consent all rest on the same thing: can you reach the right person?

ObligationWhat GovernID providesWhat remains for your company
GDPR Art. 5(1)(d) · KVKK Art. 4(2)(b)
Personal data must be accurate and, where necessary, kept up to date. The GDPR requires every reasonable step to be taken so that inaccurate data is erased or rectified without delay.
Whether the contact detail was confirmed by its owner shows on the record; “I don’t know about this” answers are listed.Reviewing the listed records and correcting or erasing them where needed.
GDPR Art. 14(3)(a)–(b) · KVKK Notice Communiqué Art. 6(1)
Where data isn’t obtained from the data subject, for example when someone else types their contact details into a form, information is due within a reasonable period and, if the data is used to communicate with them, at the latest at the first communication.
A notification describing the transaction, with a link to the privacy notice, goes to the owner of the contact detail when the data is collected.Meeting the duty to inform and deciding what the privacy notice says.
GDPR Art. 12(6), Recital 64 · KVKK Application Communiqué Art. 5(1)
A controller with reasonable doubts about a requester’s identity may ask for additional information. Under KVKK, a request may also be made from an email address the person gave earlier and that is registered in the controller’s system.
The email and phone the person verified show on the record. People sign in to the Privacy Center with their email; additional emails and phone numbers are added only after verification.Assessing the requester’s identity and answering the request.
GDPR Art. 7(1) · Art. 5(2)
Where processing is based on consent, the controller must be able to demonstrate that the person consented; the accountability principle requires compliance to be demonstrated.
Next to the consent record, it also shows whether the owner of the contact detail confirmed the transaction.Assessing whether consent is valid and which legal basis applies.

The notification doesn’t on its own fulfil the duty to inform; it makes sure the person knows their data was collected. In GovernID your privacy notices are prepared from your RoPA.

In four steps

Notify, ask, record

  1. 1
    Choose where it applies. Turn notification and verification on for the email and phone data types; where it isn’t needed, it stays off.
  2. 2
    Use the form as usual. The form on your site, or a GovernID form, works unchanged; the person simply fills it in.
  3. 3
    Tell the person and ask. When the data arrives, an email goes to the address and an SMS to the number. Both describe the transaction and offer two choices: “This was me” or “I don’t know about this”.
  4. 4
    See the answer on the record. The record shows each channel’s status and the answer given; “I don’t know about this” answers are listed for your team to review.
What’s on screen

Know whether the contact details you collect really belong to the person

Your choice

You turn notification and verification on for the email and phone data types; it isn’t mandatory.

Email and SMS, separately

Each channel is verified separately, so you know whether the person confirmed the email, the phone, or both.

Two choices, a clear answer

The person says “This was me” or “I don’t know about this”. The second answer is listed for your team to review.

Status on every record

Email and phone verification status shows in the record list and in the record detail; the list can be exported to Excel.

In the person’s language, with the privacy notice

The notification is sent in the language the person used on the form and links to the privacy notice for that transaction. GovernID works in nine languages.

Sent from within the country

Verification emails and SMS messages are sent through local providers in the country where your data is hosted. See Data Residency.

Who it helps

Asked once, everyone sees the same answer

DPOs and compliance teams

A concrete step for the accuracy principle: wrong or borrowed contact details land on a list. When a request arrives, you already have the channels the person verified.

DPOs and compliance teams
Legal teams

“The person knew” is backed by a record: when they were told, through which channel, what they answered. The same information sits next to the consent record.

Legal teams
IT and data teams

You don’t need to build a verification flow for each form or set up email and SMS sending separately. The verification status sits with the record in GovernID.

IT and data teams
What you will see in the demo

Let’s send and verify an application together

  1. 01
    We turn on verification for the email and phone fields of a form.
  2. 02
    We send a sample application; the email and SMS arrive at the same time.
  3. 03
    We answer one with “This was me” and the other with “I don’t know about this”.
  4. 04
    We see the status of both channels on the record.
  5. 05
    We look at how the “I don’t know about this” answer appears on your team’s list.
Request demo
Frequently asked questions

About Contact Verification

What is Contact Verification?

When an email address or phone number is collected through a form connected to GovernID, a notification describing the transaction is sent to it, the person is asked whether they did it, and the answer is added to the record, channel by channel.

Is this identity verification?

No. GovernID doesn’t check identity documents, government e-ID or biometrics. What it verifies is whether the owner of that email address and phone number confirms the transaction.

Is verification required for every form?

No. You turn notification and verification on for the email and phone data types.

What happens if the person answers “I don’t know about this”?

The channel shows as “Rejected” on the record, and the answer lands on the same review list as “This doesn’t belong to me” requests from the Privacy Center. GovernID doesn’t delete or change the record on its own; checking it and deciding stay with your team.

What if the person never answers?

The record stays “awaiting answer”; the form and the data collection aren’t affected.

Are email and phone verified separately?

Yes. Each channel’s status shows separately on the record, so you know which one the person confirmed.

Where are the notifications sent from?

Verification emails and SMS messages are sent through local providers in the country where your data is hosted.

Does the notification fulfil our duty to inform?

Not on its own. The notification makes sure the person knows their data was collected and links to the privacy notice; deciding the scope of the duty to inform and what the notice says stays with your company. In GovernID your privacy notices are prepared from your RoPA.

Do verified contact details help with data subject requests?

Yes, as something to rely on. The email and phone the person verified earlier show on the record; the Privacy Center is accessed with an email, and additional contact details are added only after verification. Assessing the requester’s identity stays with your company.

Do we need to change our forms?

No. It works with forms connected to GovernID; the form on your site stays as it is.

See it on one of your own forms

Pick one of your forms; we’ll watch together how the email and SMS notification goes out and how the answer is added to the record.

Request demo