Skip to content

Consent Management

Consent you can demonstrate, years later

GovernID consent management shows a separate consent text for each purpose at the moment of collection and keeps, on every record, the approved version the person saw, the data categories it covers, when it was given and when it was withdrawn.

A ticked box proves very little on its own

A consent flag in a database answers one question: yes or no. It cannot say which text the person saw, which data it covered, or when they changed their mind. When a person or a regulator asks, those answers have to be rebuilt from old forms and emails.

Consent management: given, versioned, withdrawn

Consent management in GovernID keeps the whole life of each consent on the record: the text and version the person saw, the data it covers, when it was given and when it was withdrawn. 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.

Simplified preview

One person, one consent, four moments

Emma gives consent when she joins a loyalty programme, then withdraws it. Below, the same events happen at two companies: one without GovernID, one with GovernID.

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

Emma C.
Mobile app12 Mar 2024Loyalty programme sign-upEmma Clarke+44 7••• ••• 412I consent to personalised offers based on my purchase history.I consent to my photo being used in campaign posts.Privacy noticeSend
Legal Text ManagementPersonalised offers · Consent text
v416 Sep 2024Approved · Live
v312 Jan 2024LiveArchived
New forms show v4.
Privacy Center · Emma C.My records and consents
Personalised offersGiven 12 Mar 2024Withdraw consent
Request received
Consent Management List
Emma C. · Personalised offersRequested 3 Feb 2025PendingApproved
I withdrew my consent. Why am I still getting offers?
RegulatorWhen, and with which text, did you collect this consent? When was the withdrawal handled?
Without GovernID
Consent flag in a databaseone field
Personoffers_ok
Emma C.10
The earlier value was overwritten.
What the database can sayCannot be shownoffers_ok = 0Which text? Which version? When was it given, when withdrawn? Unknown.
With GovernID
GovernID recordEmma C.
Loyalty programme sign-up12 Mar 2024 · Mobile appPrivacy notice v5Phone verified
Personalised offersConsent text v3 · Customer transaction, ContactGiven 12 Mar 2024Withdrawn 3 Feb 2025Request approved 4 Feb 2025Current text is v4; this record stays on v3
Photo used in campaignsConsent text v1 · Visual recordNot given
What the GovernID record can sayCan be shown
Consent given: 12 Mar 2024 · text v3
Data covered: Customer transaction, Contact
Withdrawn: 3 Feb 2025 · request approved 4 Feb 2025

March 2024. Below, the same events happen at two companies: one without GovernID, one with GovernID. Emma joins the loyalty programme. The notice is a link; each purpose has its own empty box. She ticks personalised offers only.

September 2024. A new version of the consent text is approved. New forms show v4; Emma’s record stays on v3, the version she agreed to. The database flag still just says “1”.

February 2025. Emma withdraws in the Privacy Center. The request is tracked until it is approved; the GovernID record adds the withdrawal date without erasing when consent was given. In the database, “1” becomes “0”.

2026. Emma or a regulator asks. The database shows only “0”; the GovernID record shows the text, its version, the data it covered, and when consent was given and withdrawn.

Sample data; the number is masked. Screens are simplified.

  1. Given. Emma joins a loyalty programme. The notice is a link; each consent purpose has its own empty box. She ticks one.
  2. Text updated. The consent text moves to a new approved version. New forms show it; Emma’s record keeps the version she agreed to.
  3. Withdrawn. Emma withdraws in the Privacy Center. The request is tracked until it is approved; the record keeps both dates.
  4. Asked. When Emma or a regulator asks, the record shows the text, the version, the data it covered, and when consent was given and withdrawn.

What the law asks, and what GovernID records

SourceWhat the law asksWhat GovernID records
GDPR Art. 4(11)Consent is a freely given, specific, informed and unambiguous indication of the person’s wishes.A separate consent text for each purpose, an empty box on the form, and the person’s choice on the record.
GDPR Recital 32Pre-ticked boxes are not consent; where there are several purposes, consent is needed for each.One box per purpose; each consent text lists the data categories it covers.
GDPR Art. 7(1)The controller must be able to demonstrate that the person consented.The approved consent text version, the date given, the data categories covered and the contact verification status.
GDPR Art. 7(2)A consent request must be clearly distinguishable from other matters.Privacy notices and consent texts are separate legal texts, shown separately on the form.
GDPR Art. 7(3)Consent can be withdrawn at any time, as easily as it was given; earlier processing stays lawful.One-step withdrawal in the Privacy Center; the date given is kept and the withdrawal date is added.
GDPR Art. 9(2)(a)Special category data needs explicit consent.The consent text shows which special category data it covers.
KVKK Art. 3(1)(a), 5(1), 6(3)(a)Explicit consent is specific, informed and freely given, including for special category data (as amended by Law No. 7499).One text per subject, with the notice link kept apart from the consent box.
KVKK Board Principle Decision 2026/347 (Official Gazette, 24 March 2026)Privacy notices and explicit consent texts are drafted separately.The two texts are managed and versioned separately.

Under KVKK, withdrawal is not set out in the Law itself; the Personal Data Protection Authority explains that it takes effect from the moment it reaches the controller (KVKK guidance on explicit consent, in Turkish).

What stays with your team

  • Deciding whether consent is the right legal basis for a process.
  • The legal content of each consent text.
  • Acting on approved withdrawals in your own systems, manually or through your ITSM automation.

What you will see in the demo

  1. A form with the notice as a link and a separate, empty box for each consent purpose.
  2. A record with the consent text, its approved version and the data categories it covers.
  3. A new consent text version approved, while existing records keep the old one.
  4. A withdrawal made in the Privacy Center, arriving in the consent list.
  5. The record after approval, showing both the date given and the date withdrawn.

Request demo

Every consent, with its text, its version and its dates

One purpose, one box

Each consent text covers one purpose and lists its data categories.

Version on the record

The approved version the person saw stays on the record.

Given and withdrawn dates

Withdrawal adds a date; it never erases when consent was given.

Withdrawal in one step

People withdraw from their own records in the Privacy Center.

Approval flow

Each withdrawal is tracked with dates and status until your team closes it.

Consent texts in 9 languages

The person reads the consent text in their own language.

Proof

What was consented to

Each consent is recorded with the text and version the person saw.

Withdrawal is tracked

A withdrawal request is tracked until it is closed; the record keeps both the date consent was given and the date it was withdrawn.

Ready when asked

When the person or the supervisory authority asks, the text, version, data covered and dates are shown in one record.

Frequently asked questions

What does GovernID record for each consent?

The consent text and its approved version, the data categories it covers, the person’s choice, the date it was given and, if withdrawn, the date of withdrawal. The record also shows the privacy notice version and the contact verification status.

Can people withdraw consent themselves?

Yes. In the Privacy Center they see their records and the consents behind them, and withdraw with one step. The request is tracked in your consent list until your team approves it.

Do we lose the history when consent is withdrawn?

No. Withdrawal adds a date; the date consent was given stays on the record. Withdrawal does not affect processing carried out before it (GDPR Art. 7(3)), so both dates matter.

Are the privacy notice and the consent text kept separate?

Yes. They are separate legal texts, each with its own versions. The form shows the notice as a link and each consent purpose as its own box (GDPR Art. 7(2); in Türkiye, KVKK Board Principle Decision 2026/347).

What if a person says a record isn’t theirs?

They can say so in the Privacy Center. The notice is listed separately, with dates and status, for your team to handle.

Does GovernID manage cookie consent?

No. GovernID manages consent for personal data collected through your forms and other collection points. Cookie preferences stay in your website’s cookie consent tool.

How do we act on withdrawals in our other systems?

Withdrawal requests are listed in GovernID with dates and status. Your team acts on them in your own systems, manually or through your ITSM automation; we can walk through the options in a demo.

Does it work with our existing forms?

Yes. Connected forms show the consent text from GovernID, so each form uses the approved version. See Compliant Data Collection.

Make every consent demonstrable

See a consent given, versioned and withdrawn in GovernID.