One standard for group companies, central management with a single login
In GovernID every group company is a separate controller and sees only its own records. The group’s legal and compliance team sets the privacy approach once: data categories, groups of people, purposes, retention periods, legal texts, recipients. These definitions are transferred to the companies, and the person the companies invite manages them all with a single login, switching between accounts.
The group lead, with a single login. Click a step.
RoPA
Sample data
ActivityGroup of peopleReview
Loyalty programmeCustomerMatches record
RecruitmentJob applicantMatches record
My institution
HSample Holding
Group companies that invited you
PSample Retail
LSample Logistics
ESample Energy
Start selecting data to transfer
A company that joins does not start from a blank pageThe group’s definitions reach the company’s own account in a few steps.
Show what is the same in both
Data categories24Selected
Groups of people12Selected
Processing purposes18Selected
Retention periods13Selected
Legal texts6 / 40Partly
Technical and organisational measures9Selected
Sample EnergyIts own additionStatus
The group’s definitions+ SubscriberTransferred
Subscription processSubscriberDraft
You can open this account because Sample Energy invited you. Even within the group, a company that has not invited you stays closed to you, and each company sees only its own records.
What GovernID is
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.
What it does for a group of companies
It carries the group’s shared language, the Privacy Taxonomy, to every company; a company that joins the group does not start from a blank page.
It keeps every company as a separate controller: its own users, its own RoPA, its own records.
The person the companies invite switches between their accounts with a single login; every company has the same screens and the same report structure.
Even within a group, no one can open a company’s account unless that company invites them.
It does not open one company’s records to another, and it does not make legal decisions for you. It is not a security tool.
What we hear from groups of companies
The group has a privacy standard. But do the companies actually work to it?
In most groups the standard lives in a policy document, and the registers live in each company’s own spreadsheet. Does any of this sound familiar?
Every company has given the same data category a different name.
“Identity” in one company, “ID details” in the next, “Civil registry” in the third. The registers cannot be put side by side and the reports cannot be compared. In GovernID the group’s Privacy Taxonomy is prepared once and carried to every company with the same names; each company adds its own entries and the shared language stays.
Does the company we just acquired have to start privacy from zero?
The first months after an acquisition or a new set-up often go into making sense of old files. In GovernID the new company opens with the group’s Privacy Taxonomy, enters its processes through the same wizard and works in the group’s language from day one.
Each company has its own consultant, and each does the work their own way.
The group ends up with documents that look nothing alike. In GovernID consultants work on the same screens as users invited by the company; whichever consultant you work with, the output has the same structure.
Did both companies record the data we share within the group?
Shared HR, accounting or a call centre means data flows within almost every group, and the record is often missing on one side. In GovernID transfers to group companies are recorded in each company’s own RoPA, with the receiving company, purpose, legal basis and safeguards.
Which of our companies’ registers are up to date, and which aren’t?
Being up to date usually depends on one person remembering. In GovernID each company’s process owners are reminded at the interval you set; they confirm the record or report the change. For companies in Türkiye, the changes to reflect in VERBİS, the regulator’s registry, are shown automatically.
Companies should not see each other’s records, yet they should work the same way.
Doing both at once looks hard. In GovernID each company is set up as a separate controller and sees only its own records, while the method, the screens and the report structure are the same in every company.
We know the job
A group is not one company, and the law sees it that way too
Neither KVKK nor the GDPR exempts data flows within a group from the general rules. Each group company is responsible for its own processing, and a transfer to a group company is still a transfer. Below is where each obligation lands in GovernID; assessment and decisions stay with you.
KVKK
Art. 3(1)(ı) Data controllerEach group company is set up in GovernID as a separate controller, with its own users, RoPA and records.
Art. 8 Transfer of personal dataA transfer to a group company also needs one of the conditions in Art. 5 or 6. It is recorded in each company’s RoPA with the receiving company, purpose and legal basis.
Art. 10(1)(c) Recipients in the noticeThe notice is generated from the RoPA, so transfers to group companies reach the recipients section of the notice from the RoPA.
Art. 16 Data Controllers’ RegistryThe registration duty is assessed for each company separately. Each registered company’s VERBİS output is generated from its own RoPA and versioned.
GDPR
Art. 4(19) and Recital 48 Group of undertakingsA legitimate interest may exist in transmitting data within the group for internal administrative purposes; the basis is still set for each transfer. In GovernID the legal basis is recorded for each purpose and group of people.
Art. 30 Records of processing activitiesThe record is each controller’s own duty; every company has its own RoPA, kept in the same language through the group’s Privacy Taxonomy.
Art. 26 and 28 Shared servicesA group company providing shared services may be a joint controller or a processor; that qualification is your assessment. The details of the transfer sit in each company’s RoPA.
Art. 37(2) A single DPO for the groupA group may appoint a single DPO. The DPO switches between all company accounts with a single login and works with the same screens and report structure in each.
How it works in a group
Set it once, apply it in every company
Rolling out across the group
01Prepare the group taxonomy
The group, or a lead company, defines data categories, groups of people, purposes, retention periods and recipients once.
02Transfer it to the companies
With Inter-Organizational Data Transfer, the taxonomy, legal texts, retention periods, recipients and measures are selected and transferred to each company’s account; what is already the same in both is shown.
03Each company builds its RoPA
Processes are entered through the wizard in the company’s own account; the company extends the taxonomy to fit its business.
04Each company produces its own output
Notices, consent texts, DPIAs and, for companies in Türkiye, the VERBİS output come from the company’s own RoPA.
Legal preparation starts independently of integration; you plan the connection of data collection points company by company, on your own timeline. Companies can join at different times; the single licence scales with the size of the group.
Does your group have companies abroad? Companies in other countries work under their own country’s law, in separate accounts hosted in their own country.
No. Each company works in its own account as a separate controller, with its own users, RoPA and records. What they share is the group’s Privacy Taxonomy and the screens and report structure that are the same in every company. The person the companies invite switches between the accounts with a single login, and cannot open the account of a company that has not invited them.
Can our group companies see each other’s records?
No. Each company sees only its own records, even within the group.
Can a company add its own entries after the taxonomy is carried over?
Yes. Each company can add its own groups of people, data categories and purposes, and decides who may change its taxonomy.
How are transfers within the group recorded?
A transfer to a group company is recorded in the transferring company’s RoPA with the receiving company, purpose, legal basis and safeguards, and reaches the recipients section of the notice from the RoPA. You decide the legal basis of the transfer.
Does each group company need its own VERBİS registration?
Under KVKK, the duty to register is assessed for each controller separately. In GovernID, each registered company’s VERBİS output is generated from its own RoPA, versioned, and the changed parts are shown.
Can the group have a single DPO or a single consultant?
GDPR Art. 37(2) allows a group to appoint a single DPO, provided the DPO is easily accessible from each establishment. In GovernID, the DPO or consultant the companies invite switches between their accounts with a single login, manages each company in its own account and works with the same screens in each. A company that has not invited them stays closed to them.
Can our companies join at different times?
Yes. Legal preparation starts independently of integration, and companies join on their own timeline. GovernID comes with a single licence that scales with the size of the group.
Our group also has companies abroad. What happens?
A company abroad works in a separate account, under its own country’s law and hosted in its own country; companies in the EU are hosted within the EU. See the Multinational companies and Data Residency pages.
Let’s plan a demo around your group’s structure
We will show how a group taxonomy is carried to two companies and how each company works with its own records.