RoPA
RoPA
- Group of people
- Candidates
- Purpose
- Recruitment
- Legal basis
- Steps prior to a contract
- Retention
- 2 years
- Kept in
- HR system, Archive server 02
- Recipients
- Payroll provider, domestic
A RoPA is hard to build, and harder to keep current
Building a RoPA means collecting facts from every department. Keeping it current means noticing every change in how they work. When one person, often the DPO, carries both, the record falls behind the business. A spreadsheet doesn’t help: it doesn’t ask the right questions, it doesn’t notice change, and it doesn’t feed your notices or assessments.
One activity, three groups of people
Take recruitment. One activity concerns candidates, their references and the employees who interview them. Each group gives different data, for different purposes, on different legal bases. GovernID records them that way.
| Group of people | Data | Purpose | Legal basis | Transfer |
|---|---|---|---|---|
| Candidates | Contact details, CV, interview notes | Assessing the application; keeping the CV for future roles | Steps before a contract; consent for future roles | Applicant tracking system hosted abroad |
| References | Name, contact details, reference statement | Checking the candidate’s references | Legitimate interest | None |
| Interviewers | Name, evaluation scores | Recording the hiring decision | Legitimate interest | None |
The legal bases are an example. Your legal assessment decides them for each activity. The privacy notice for each group is generated from its own row, and because candidates’ data is sent abroad, GovernID suggests a DPIA.
A simple activity uses the same wizard and takes only the entries it needs.
A guided flow, from data categories to transfers
The same wizard opens when you add an activity and when you change one, so a change is recorded with the same care as the first entry.
Simplified preview
The logic of the wizard, in nine steps
The animation shows the order of the wizard, not its depth. On the real screens each step holds far more detail, and every step builds on the person groups and data categories chosen before it.
What the real screens add
- Activity Activity code, owner department, departments that share the data, the people who gave the information, linked legal texts and the destruction method.
- Groups and data Each person group gets its own data categories. Special category data is marked separately.
- Purposes and legal basis Set for each group and data category. Special category data gets its own legal basis.
- Retention A period for every group and data category, which feeds the destruction policy.
- Transfers Pairs are proposed from the storage locations. For each pair you keep, you record the data per group, the purpose and the legal reason, and for transfers abroad the transfer mechanism.
- Missing definitions A form, purpose, retention rule or recipient can be added from inside the wizard.
Try it: click any step to explore, or just watch.or hit and watch.
- Activity
- Recruitment
- Department
- Human Resources
- Process owner
- Head of HR
- Privacy notice
- Applicant privacy notice
- Destruction
- Deleted when retention ends
Data categories come from the linked points.
Interview notes, a reference statement and evaluation scores are all assessments, from different people.
Legal bases shown are an example.
Periods feed the destruction policy. Periods shown are an example.
No domestic recipient in this example. Only the pairs that happen are kept.
- Group
- Candidates
- Data
- Contact details, CV, interview notes
- Purpose
- Assessing the application
- Transfer mechanism
- Standard contract
Missing a form, purpose or recipient? Add it from inside the wizard.
- Describe the activity. Name and description in several languages, department, process owners, the notice and consent texts it uses, and how data is destroyed at the end.
- Link the collection points. Choose the forms and systems the activity uses. Their data categories become the starting point, and special category data is marked.
- Groups of people. Select the groups concerned, then untick the data you don’t collect from each group.
- Purposes. Choose purposes from your list and, where needed, set them per group and data category.
- Legal basis. Choose legal bases for personal data and for special category data, and link each one to the purposes it covers.
- Retention. One period for everything, or a period per group and data category, using reusable retention rules.
- Storage. Servers, cloud, software, physical archives and generative AI tools. If the activity has no transfers, you can finish here.
- Domestic transfers. GovernID lists every pair of storage location and recipient. Keep the ones that happen and record the data, purpose and legal basis for each group.
- International transfers. The same, plus the transfer mechanism for each group.
Missing a form, purpose, retention rule or recipient? Add it from inside the wizard, without leaving the activity.
Where does the data go? Data mapping
Your RoPA is also your data map; it is not drawn separately. The storage locations, recipients and transfers you record in each activity show, across processes, where personal data is stored, who receives it and on what basis. When the process changes, the map changes with it. For example, ask “Which processes use health data, who receives it and in which countries?” and export the answer.
| Source | What the law asks | What GovernID provides | What stays with you |
|---|---|---|---|
| GDPR Art. 30(1)(d); KVKK Art. 16(3)(ç)–(d) | Categories of recipients, including in third countries, in the record. | Recipient groups in each activity, per data category. | Getting a complete list of recipients from process owners. |
| GDPR Art. 30(1)(e); KVKK Art. 16(3)(d) | Transfers to third countries and the country. | Receiving companies with their countries; transfer basis and safeguards per transfer abroad. | Assessing whether the basis is legally sufficient. |
| GDPR Art. 44–49; KVKK Art. 8, 9 | Each transfer rests on one of the conditions in the law. | Purpose, legal basis and transfer basis for each transfer. | Putting the safeguard in place. |
| KVKK Art. 9(5) | Notifying the Authority of a standard contract within five business days. | The standard contract basis is visible in the transfer record. | Notifying on time. |
- Generative AI tools are recorded as storage locations and recipients like any other system.
- The dashboard shows the domestic and international split of storage points and recipients.
Your DPO is no longer alone
The people who run each process know first when it changes. GovernID gives them a part in keeping the RoPA current.
- My Processes. Each process owner sees only the activities they own.
- Regular confirmation. Owners confirm their activities monthly, every three months or every six months, and get an email reminder when a review is due.
- Changes with approval. Where you allow it, departments update their own activities and each change waits for an approver, usually the DPO, legal counsel or compliance manager.
- Process Review Status. The privacy team sees which activities were confirmed, which are due and which were flagged.
The history of every activity, in plain language
Every change to an activity is recorded, and the version before it is kept. So you can answer questions like: how did our recruitment process work two years ago? Which privacy notice did candidates see? Which data did we collect, and on what legal basis?
- Every version kept. Each change creates a new version that shows who changed what, and when. Earlier versions stay as they were.
- Readable by anyone. An activity and its history are shown in plain, structured language, so a manager or auditor without legal training can follow them.
- Compare versions. See what changed between any two versions, field by field.
- Export any version to PDF. Export the current version of an activity, or any earlier one, to PDF.
This history is part of your Corporate Privacy Memory. It is your organisation’s record of how it processed personal data, and it lets you account for what you did at the time, for example after an incident, a complaint or an audit. See Corporate Privacy Memory.
Everything built from the same record
- Privacy notices for each group of people, generated from the activity.
- DPIA suggestions when special category data or international transfers are recorded. The decision stays with you.
- Generative AI as a location. Record AI tools as storage locations and transfer recipients, like any other system.
- Department access and exports. Export one activity as a report, or the whole register to Excel.
- VERBİS output for companies in Turkey, produced by analysing the RoPA and versioned with it.
Simple when the activity is simple, detailed when it isn’t
A wizard for every activity and every change
Simple activities, quickly
Data per group of people
Purpose and legal basis per group
A transfer scenario per group
The business keeps it current
Proof
One source
Current, not annual
Accountable for the past
Frequently asked questions
Is RoPA the same as a personal data inventory?
Yes. The Turkish KVKK calls it a personal data inventory; the GDPR calls it a record of processing activities. GovernID keeps both in the same record.
Can one activity cover several groups of people?
Yes. Record the data, purposes, legal bases and transfers for each group separately, inside the same activity.
Do simple activities need the same detail as complex ones?
No. A simple activity takes only the entries it needs. You add detail when the activity has it.
Who keeps it up to date?
Process owners confirm their activities on a schedule you choose, or edit them and send changes for approval. See Process Owner Reviews.
Can we see an activity as it was two years ago?
Yes. Every change is versioned, with who made it and when. You can read any past version in plain language, including the privacy notice it used and the data it collected, and export any version to PDF.
Does it cover international transfers?
Yes. Record each transfer with its recipient, data categories, purpose and legal basis for each group whose data is sent, and the transfer mechanism for international transfers.
Do we need a separate data mapping tool?
No. The data map comes from the storage locations, recipients and transfers you record for each activity in the RoPA. GovernID does not scan your systems; the map comes from the activities you record.