Skip to content
The GovernID method

Point Zero Privacy®

Most privacy work starts after data is already inside the company. Point Zero Privacy® moves it to the moment before. The legal groundwork is done in your RoPA, so data arrives classified and carrying its own legal context.

Compliance that starts after collection is always catching up

When data is collected first and governed later, teams spend their time reconstructing: which notice the person saw, what they agreed to, which purpose the data serves and how long it can be kept. Scanning systems later can show where data sits, but rarely the terms it was collected under. That knowledge exists at one moment only: the moment of collection.

One company, many channels, one question

A company collects personal data through many channels at once: web forms, a mobile app, job applications, a call centre, stores and events. The data spreads across systems such as HR, CRM, marketing and ERP, and over time it is copied between them. Then a person or a regulator asks: which notice was this person shown, what did they agree to, and where is their data?

Point Zero Privacy® creates the answer at the moment of collection. When a person submits a form, GovernID creates a record of the notice and consent texts, purpose, legal basis and retention period that applied at that moment. The data still goes to your systems, and its record sits outside the company, in GovernID. Once nothing new arrives without a record, working through the data you already hold becomes a finite job.

Try it: click any step or press Play.

Step 1 / 6 · Data collection without GovernID

  1. Personal data from dozens of channels spreads across company systems, with no record of the moment of collection.
  2. Collected data is copied between systems; with each copy, the information on where the data sets came from is lost.
  3. In an audit of personal data management or a data subject request, systems are reviewed one by one: on average 2 weeks.
  4. Personal data collection points connect to GovernID via API. The flow of data inside the company does not change.
  5. Data still flows to the same systems and is copied. Each collection creates a record in GovernID; copies link to their source.
  6. For an audit or a data subject request, the records are waiting in GovernID; the result is on screen in about half a second.

Query: “Which notice was Emma Clarke shown, what did she agree to, and where are the copies of her data?”

Without GovernIDDay 0

  • HRName, phone, emailNotice, consent, source: no record
  • CRMName, phone, emailNotice, consent, source: no record
  • MarketingName, phone, email, photoNotice, consent, source: no record
  • File serverApplication document, photoNotice, consent, source: no record

On average 2 weeks of manual review

With GovernID0.5 s

No GovernID in this round

Records for Emma Clarke Sample data

  • ▲ Job application 12 Mar 2025Notice: Version 3 · Consent: None · Retention: 12 Mar 2027Copies: HR, File server
  • ■ Mobile app 4 Jun 2025Notice: Version 5 · Consent: Marketing messages ✓ · Retention: End of membership + 2 yearsCopies: CRM, Marketing
  • ○ Event 18 Sep 2025Notice: Version 2 · Consent: Use of photos ✓ · Retention: 18 Sep 2026Copies: Marketing, File server

Result on screen in about half a second

Times are indicative.

Point Zero Privacy: before, at and after collection

  1. Before collection. Define each process in your RoPA: purposes, legal bases, data categories, retention periods, recipients and transfers. Generate the privacy notice and consent texts from the same record, and link every form field to a data category.
  2. At collection. When a person submits a form, GovernID creates a record with the notice and consent versions they were shown and the purpose, legal basis and retention period that applied at that moment. Contact details can be verified by email or SMS as they arrive.
  3. After collection. Each record is managed on its own terms. It is kept, shown to the person and listed for deletion according to what applied when it was collected. Requests, assessments and audits start from the record, not from a search.

Evidence created at collection, not rebuilt for the audit

  • Every field collected through GovernID is classified before the first record arrives.
  • Notices and consent texts come from your RoPA, so what you tell people matches what you do.
  • When a notice or retention period changes, new records follow the new terms and earlier records keep theirs.
  • People can see the records that contain their verified contact details in your Privacy Center.
  • Every change to a process, text or record is kept in your Corporate Privacy Memory, with who changed what and when.

Frequently asked questions

Is Point Zero Privacy® a separate product?

No. It is the method GovernID is built on. Every licence starts from it with your RoPA, assessments and legal texts. Records created at collection come with live data automation.

Do we have to replace our forms?

No. GovernID connects to the forms you already use, and your collection points keep working as they do.

What about data we collected before GovernID?

Existing records can be brought into GovernID in bulk, with a record created for each. What those records usually lack is what was never captured at the time: the notice version shown, whether consent was given and with which text, and whether contact details were verified. That is why we start at the moment of collection: stop unrecorded collection first, then work through the data you already hold.

Which privacy law does it follow?

The law of your company’s country. GovernID loads the legal bases and transfer provisions of that law when your company is set up. See Regulations.

Is Point Zero Privacy® a trademark?

Yes. Point Zero Privacy® is a registered trademark of GovernID.

See point zero on one of your own processes