Privacy
Keep the record of processing activities, see which transfers abroad have a safeguard, decide where a data protection impact assessment is needed, and answer data subject requests in time.
The Privacy page keeps no records of its own. A processing activity is an asset. A recipient of personal data is a vendor. A data protection impact assessment (DPIA), a transfer impact assessment (TIA) and a data subject request are process submissions, and a risk from a DPIA is a risk in your register. You record each fact once, where it belongs. The Privacy page reads those records and shows what follows from them: where personal data goes, which transfers have a safeguard, which activity needs an assessment, and what is still open.
Every statement on the page is derived from what your organization recorded and from two adequacy lists as they stood on the date the page shows. devguard does not decide whether a processing or a transfer is lawful, and the page is not legal advice.
The page works like the total at the foot of a grocery receipt. It adds up what was entered, and an item nobody entered is not in it. A vendor that is not linked to its activity has no transfer here, however much data it receives.
These are the tasks, in the order the work usually runs:
- Set up the register, or update an older one.
- Start from common activities or record a processing activity, then link its vendors and its measures.
- Read the transfers abroad and record where a vendor processes data.
- Decide on a DPIA: carry one out, or record the decision not to.
- Decide on prior consultation where a high risk remains.
- Assess a transfer that rests on a contractual safeguard.
- Answer data subject requests.
- Read the register and the overview and print the register.
The reference lists every finding with what clears it. Integrators go straight to the API.
The page calls the Swiss Data Protection Act Swiss DSG. The framework catalog and the process templates use its English short form, nFADP. Both mean the same law.
Set up the register
The register is an asset class made from the preset Processing activity. Its fields hold what a record of processing activities names (DSG Art. 12, GDPR Art. 30), such as the purpose and the categories of data. Owner, retention and vendors are not fields of the class, because every asset has them already.
- Open Privacy. Without a register, the page reads Set up your processing register.
- Choose Create the register. The form for a new asset class opens with the preset's name, description and fields filled in.
- Change what you like and choose Create.
You can rename the class and add fields of your own. devguard recognizes the register by the preset the class came from, not by its name. Fields you add are printed in the report under Further details.
Update an older register
A class made from an earlier version of the preset lacks some of the fields this page reads. Privacy then shows the note The register uses an earlier field set.
- Choose Update the register in the note. On the class itself, the same action is Apply preset on the Fields tab.
The update adds fields and removes nothing:
- A field whose label and type match a preset field is recognized as that field. Nothing you can see changes.
- A preset field the class lacks is added at the end, in the language most of the class's labels are in. On a tie, it is your interface language.
- A field that has a preset field's label but another type keeps its values, and its label gains (earlier text). The preset field is added beside it. A class whose categories were paragraphs gets the two Pick several fields this way: the paragraphs stay, and you tag each activity from your own prose.
No value stored on an activity is changed. When you have moved the content of an earlier field, remove it on the Fields tab. Removing a field hides its values and does not delete them. You can run the update again at any time.
If Privacy offers to create a register although you already keep your activities in a class, that class does not carry the preset. One API call attaches it.
Start from common activities
An empty register offers eight activities that most organizations have: payroll and HR administration, recruiting, customer accounts and billing, customer support, newsletter and marketing emails, website analytics, supplier and partner management, and IT accounts and access logs.
- On Privacy, choose Choose activities.
- Choose the Owner role that keeps them current.
- Untick the activities you do not have, then choose the button that adds them. It names how many.
Each activity is added with its purpose, the role Controller, its categories of data subjects and of personal data, and a lawful basis, in the language of your register. Payroll also names its recipients. These are a starting point: open each activity and correct what does not match what you do. devguard leaves the retention period, the vendors and the DPIA screening to you, so the overview lists every activity that still needs a retention period.
Record a processing activity
- Open Privacy and choose Open in assets, then Add asset. On an empty register, choose Add activity instead. Either way the form opens with your register class chosen, as long as you keep one register class.
- Enter a Name, such as "Payroll", and choose the Owner role.
- Under Classification, check that the Asset class is your register class. The fields of the preset appear under Privacy, each with a line that says what the field does. Fields you added to the class yourself appear under Details.
- Fill in the Purpose and choose Controller or processor. Both are required.
- Tick the Categories of data subjects and the Categories of personal data. If you are a joint controller or a processor here, name the other party in Joint controller, or the controller you process for.
- In Recipients, name the recipients that are not vendors, such as authorities or group companies. Vendors are linked in the next task.
- If the GDPR applies to you, choose the Lawful basis (GDPR).
- Under Access Management, choose the Retention period. The register prints the name of the schedule you choose, so use one whose name says how long the data is kept.
- Under DPIA screening, tick the boxes that apply (see Decide on a DPIA) and choose Create.
The activity's Detail tab shows the same fields in a section Privacy, with the screening boxes under DPIA screening.
The options of the two category fields are a starting list. Add your own on the class's Fields tab.
For an activity with the role Processor, devguard asks for less: no categories, no retention period, no lawful basis and no DPIA. The report prints the shorter processor record for it.
Watch out: devguard reads the role from the text of the option. If you rename the options of Controller or processor on the class, the role is no longer recognized, and the activity is treated as a controller's.
Link the vendors
- Open the activity and go to its Privacy tab. Only assets of the register class have this tab.
- Under Vendors, open Link a vendor, search for the vendor and select it. It is linked at once and appears in the table.
To remove a vendor, open the menu at the end of its row (the three dots) and choose Remove. Detail in the same menu opens the vendor. devguard records each link and each removal as its own entry in the history.
You need the right to edit both assets and vendors. Without them, the tab shows the table without Link a vendor and without Remove. You can also set the link from the vendor: choose Edit and add the activity under Relations → Assets.
The tab then lists each vendor with its Relationship, its Safeguard and its DPA. All three come from the vendor's own record, and you change them there. The countries and the safeguard can also be changed on the tab: see Record where a vendor processes data. See Record where data is processed and File a vendor's documents.
Link the measures that protect an activity
Under Security measures, the activity's Privacy tab lists the controls linked to the activity and the treatment actions of its risks and vendors. The report prints the controls as the activity's security measures.
- To link a control, open Link a control, search for it and select it. To remove one, open the menu at the end of its row and choose Remove. This needs the right to edit assets.
- To add a treatment action, choose Add treatment action and the risk it treats. The treatment action form opens. When you save it, the action is linked to that risk and appears in the list. This needs the right to create treatment actions and the right to edit risks. While the activity has no risk, the button is unavailable: add a risk first.
Read the transfers abroad
The Privacy tab of an activity lists its Transfers abroad, one row per vendor and country. Nobody types these rows. devguard derives each one from the vendor's Countries where data is processed and its Transfer mechanism, in three steps.
Record where a vendor processes data
- On the activity's Privacy tab, under Transfers abroad, choose Add transfer and pick one of the linked vendors. To change a vendor that is already listed, choose Edit on its row instead.
- Pick the Countries where data is processed, sub-processors included, and the Transfer mechanism.
- Choose Save.
The dialog starts from the countries and the mechanism the vendor already records, and saving replaces them. Both are stored on the vendor, so every activity that uses it shows the change. This needs the right to edit vendors. Add transfer needs a linked vendor, so link the vendors first.
Which list applies
The frameworks you have adopted decide which adequacy list devguard reads.
| Adopted | List |
|---|---|
| Swiss nFADP | The Swiss list: the states the Federal Council recognizes as adequate. |
| GDPR | The EU list: the European Commission's adequacy decisions (GDPR Art. 45). |
| Both | Both lists. A country must be adequate under each. |
| Neither | The Swiss list. |
Both lists are stored in devguard with the date they were last checked against their sources. Privacy → Overview shows that date beside the card Transfers Abroad, and an activity's Privacy tab shows it under the heading Transfers abroad, for example Swiss DSG list as of and the date. A decision taken after that date is not on the page.
How a country stands under a list
| Standing | Meaning |
|---|---|
| Not a transfer | Switzerland under the Swiss list; the EU and EEA states under the EU list. A country that is not a transfer under every list that applies gets no row. |
| Adequate | The country is on the list. Where the list sets a condition, the row prints it, for example that only recipients subject to a named law are covered. devguard counts the country as adequate and leaves the condition for you to check. |
| Third country | The country is not on the list. |
The United States is the exception. Both lists carry it for certified recipients only, so devguard counts the US as adequate only when the vendor's Transfer mechanism is Adequacy decision. With that choice, your organization states that the recipient is certified under the Data Privacy Framework that applies to you. The vendor form says so when you make the choice, and asks you to link the recipient's listing as evidence with an expiry date. With any other mechanism, the US is a third country.
The status of a transfer
| Status | Meaning |
|---|---|
| Adequate | No list that applies calls the country a third country. |
| Safeguarded | A third country, and the vendor's mechanism is standard contractual clauses, binding corporate rules or other appropriate safeguards (GDPR Art. 46, DSG Art. 16). A transfer impact assessment belongs to this status. |
| Derogation | A third country, and the mechanism is a derogation. |
| No safeguard | A third country with any other mechanism, or with none. This includes Adequacy decision for a country that is not on the list. |
A vendor has one transfer mechanism, and it applies to every country of that vendor. On Privacy, the column Transfers abroad shows the worst status among an activity's rows.
Decide on a DPIA
A data protection impact assessment (DSG Art. 22, GDPR Art. 35) is the controller's task, so devguard asks nothing of an activity with the role Processor. For every other activity, the screening boxes you tick on it decide. Open the activity, choose Edit, and tick what applies under DPIA screening. Each box has a line that says what it means, and the two that decide alone say so. The preset's fields list every box.
| Need | When |
|---|---|
| Required | Two or more criteria are ticked, or one of the two boxes that decide alone: high-risk profiling, and the supervisory authority's list (GDPR Art. 35(4)). |
| Indicated | One criterion is ticked. |
| Not indicated | Nothing is ticked, or the role is Processor. |
A linked AI system counts as the criterion New technology or a novel use of one, once. An AI system is linked when an asset of a class made from the AI system preset is the activity's parent asset or one of its child assets. Alone it makes a DPIA indicated; with one other criterion, required.
The Privacy tab shows the need, the criteria met, and the status:
| Status | Meaning |
|---|---|
| Not needed | Not indicated, and no DPIA was filed for the activity. |
| Missing | Required or indicated, with no DPIA filed and no decision recorded. |
| Open | A DPIA was filed for the activity, and none is resolved yet. |
| Done | A DPIA for the activity is resolved. |
| Decided against | Required or indicated, with no DPIA filed and the decision recorded on the activity. |
Carry out a DPIA
A DPIA has two parts in devguard. The risks and their measures are recorded on the processing activity, where you can work on them for as long as the assessment takes. The DPIA itself is a form that you file once the risks are rated: a submission of a process made from the template Data protection impact assessment.
Set the process up once:
- Open Processes and choose Add process. Enter a name, choose the kind Report form and the owner role, then Create.
- On the Structure tab, open Templates, choose Data protection impact assessment, and choose Save structure. The template sets This process is about to An asset. A subject already chosen is kept.
Then, for each assessment:
- Open the activity's Privacy tab. Under Risks, choose Add risk for each risk the processing holds for the people whose data it uses. A risk added here is rated for the persons concerned and linked to the activity.
- Rate each risk, decide its treatment, link the treatment actions that carry it out, and set its residual rating, as for any risk.
- File the DPIA. In the employee portal, choose Send a report on the DPIA form. Fill it in, answer the question on prior consultation and the Decision, and choose Send report. Fill in a process in the portal says who sees the form there.
- In the app, open the submission under Processes → Submissions. In Summary, choose Pick an asset and choose the activity. The panel Risks for the persons concerned lists the activity's risks.
- Set the Status to Resolved under Handling and choose Save handling.
While a DPIA is open, a risk can also be added from its panel with Add risk. A DPIA whose answers must change is filed again, because a filed form is a record: pick the same activity on the new submission and resolve it. devguard reads the newest resolved DPIA of an activity. While none is resolved, it reads the newest one filed.
How DPIA risks work
A risk added for a processing activity is an ordinary risk in your register. It uses the same scales and the same matrix, it is treated and accepted like any other, and it counts in the risk overview. Three things set it apart:
- It is rated for the persons concerned, not for your organization. The rating form shows each impact level in the wording For the persons concerned from your risk settings.
- It carries the marker Persons concerned in the register, on its page, in the matrix and in the risk report.
- It is linked to its processing activity.
Only Add risk on the Privacy tab or on a DPIA sets the marker. You cannot give it to a risk in the risk register. An opportunity never carries it: one added there is linked to the activity and is not rated for the persons concerned.
Resolving the DPIA freezes the activity's risks for the persons concerned into the submission: each risk's level, whether it is a high risk for the persons concerned, whether it was accepted, and how many treatment actions were open, with the version of the risk settings. The panel then reads As recorded when the DPIA was finished, with the date. The risks themselves stay in the register and keep changing; the record does not. An edit after Unlock to edit keeps the frozen copy. Reopening the DPIA drops it, and the next resolve takes a new one. The Process Submissions report prints the frozen risks.
A finished DPIA keeps the activity it assessed. On a resolved DPIA, the asset in Summary can no longer be changed or removed, and the submission says A finished DPIA keeps the activity it assessed; reopen it to change that. Reopening the DPIA lifts this. The frozen risks stay readable on the submission and in its report after the activity is archived or deleted. The line Processing activity then reads No longer in the processing register.
Record the decision not to carry one out
- Open the activity and choose Edit.
- Under DPIA screening, write the decision and its reason in Decision not to carry out a DPIA, with the reason.
- Choose Save.
The status then reads Decided against, and the Privacy tab shows your text. A DPIA filed for the activity takes precedence over the recorded decision.
Decide on prior consultation
Prior consultation (DSG Art. 23, GDPR Art. 36) becomes a question when a high risk for the persons concerned remains despite the measures. It is the controller's duty, so an activity whose role is Processor never raises it. devguard raises it from two things you set:
- In Risks → Settings, each risk level has the flag High risk for the persons concerned. See Risk settings.
- A risk with the marker Persons concerned stands at a level: that of its residual rating where one is set, otherwise that of its initial rating.
While such a risk stands in a flagged level, the activity shows Decide on prior consultation on Privacy → Overview and on its Privacy tab. It clears for each risk on its own, in one of two ways:
- A finished DPIA on the activity covers the risk. The DPIA must be Resolved, its frozen risks must list this risk as a high risk, and its field Prior consultation with the authority, if a high risk remains despite the measures must record a consultation. A DPIA that is filed and not yet resolved clears nothing.
- Treatment brings the risk down to a level without the flag.
Which answer records a consultation depends on your frameworks, read as in Which list applies. Yes, the FDPIC counts with the Swiss nFADP adopted, or with neither framework. Yes, an EU supervisory authority counts with the GDPR framework adopted. No, our adviser meeting nFADP Art. 10(3) was consulted instead (nFADP Art. 23(4)) counts only while the GDPR framework is not adopted. With it adopted, the authority must have been consulted. The answer No never counts.
A risk that reaches a flagged level after the DPIA was finished raises the finding again, because the finished DPIA does not list it as high. File the DPIA again.
Accepting the residual risk does not clear it. Acceptance says what your organization is willing to bear, and this risk is borne by other people. For the same reason the flag is separate from the levels you accept.
The consultation is an answer of the DPIA form. You rate the risks on the activity before you file the DPIA. When you fill in the form, you therefore know whether a high risk remains: consult first, then record the outcome in the form. While the finding stands, the activity's DPIA submissions show the note Consult the authority or your data protection adviser, then file the DPIA again with the outcome recorded.
Watch out: devguard finds the consultation and the decision by the template's own field labels and options, in English or German. If you rename those fields or options in your copy of the form, their answers read as not given.
Assess a transfer
A transfer impact assessment (TIA) belongs to a transfer with the status Safeguarded. Adequate transfers and derogations need none. One TIA is about one vendor and serves every activity that uses the vendor.
Set the process up once, as for the DPIA: use the template Transfer impact assessment, which sets This process is about to A vendor. Then, for each vendor:
- In the portal, send the TIA form. Name every activity that uses the recipient in Processing activities covered, with their purposes.
- In the app, open the submission, and in Summary choose Pick a vendor.
- When the assessment is complete, set the Status to Resolved.
The Privacy tab shows the state under each vendor's transfers:
| State | Meaning |
|---|---|
| Not needed | No transfer of the vendor is safeguarded. |
| Missing | A TIA is needed, and none was filed for the vendor. |
| Open | A TIA was filed, and none is resolved yet. |
| Done | A TIA for the vendor is resolved. |
| Outdated | An activity was linked to the vendor after its last TIA was resolved. |
A TIA covers the purposes and the data of the activities it names. One that was finished before an activity was linked cannot have looked at that activity. Send a new TIA form for the vendor that names it, and resolve it.
Answer data subject requests
A request is a submission of a process made from the template Data subject request (GDPR) or Data subject request (nFADP). The template brings the response time: one month under the GDPR template, 30 days under the nFADP template.
- Set the process up from the template, as for the DPIA.
- When a request arrives, send the form in the portal. Record how you checked the person's identity in Identity verified how.
- Handle the request under Processes → Submissions: set it to Being handled, then to Resolved. See Handle a report.
The due date counts from the moment the request is filed in devguard, not from the date in Received on. File a request on the day it arrives. Where the law gives you more time, choose Extend due date on the request and give the reason.
Privacy counts every request that is not resolved under Open rights requests, and says how many are overdue. Requests made from the template Individual rights request (HIPAA) count as well. Each request with a due date is also on Deadlines.
Your website can file requests straight into the process through the API intake. devguard publishes no form of its own and does not check who the person is. The form on your website and the identity check stay with you.
Read the register and the overview
Privacy has two pages in the sidebar. Privacy is the register: it lists every activity. Privacy → Overview shows how far the register has come and what it needs next. Until the first activity is recorded, both pages show the empty state that sets up the register.
The register
The four tiles count the Processing activities, the Open findings, the DPIAs open or missing, and the Open rights requests. While findings are open, the Open findings tile carries the link What needs doing, which opens the overview.
Processing register lists every activity with its role, its categories of data subjects, the number of its vendors, the worst status among its transfers abroad, the status of its DPIA, and its owner. Select a name to open the activity's Privacy tab. Above the table, Generate report opens the report Record of Processing Activities, Open in assets opens the asset list filtered to the register, and Rights requests opens the submissions of your request process, once you have one.
The overview
Privacy → Overview opens the page Privacy Overview. It has three cards, like the overviews of vendors, assets and risks.
Transfers Abroad names the adequacy lists in force and their date, and counts every activity once, by the weakest standing among the countries its vendors process in: No transfer abroad, Adequate, Safeguarded, Derogation or No safeguard. Three figures follow: Open findings, which jumps to the list, DPIAs open or missing, and Requests overdue.
Register Progress shows one bar per step, with the number done out of the total:
- Categories recorded, Retention period set and Lawful basis recorded, counted among the activities where you are not the processor. Lawful basis recorded appears only while the GDPR framework is adopted.
- Processors with a current DPA, counted among the linked vendors that are processors or sub-processors.
- Vendors abroad with a safeguard, counted among the linked vendors with a transfer abroad. A vendor is done when none of its transfers reads No safeguard.
- Transfer impact assessments done, counted among the linked vendors that need one.
- DPIAs carried out or decided, counted among the activities whose DPIA status is not Not needed. Done and Decided against count as done.
The vendor steps count each vendor once, however many activities use it. A step is left out when your role cannot read the register behind it, vendors or processes.
What Needs Doing lists the open findings, grouped by kind, the most serious kind first. A row opens the place where the finding is cleared: the activity's Privacy tab, its detail page for a missing field, or the vendor. The findings table says what raises each kind and what clears it.
Print the register
- On Privacy, choose Generate report. It opens the report Record of Processing Activities, which is also a card under Reports.
- Choose All activities, As controller or As processor. Each choice shows how many activities it holds.
- Choose Generate Report, check the preview and choose Download PDF.
The cover names the legal basis of the record for the lists that apply to you (DSG Art. 12, GDPR Art. 30) and the date of the adequacy lists. Each activity is one section, in the order of its ID.
| Record | Rows |
|---|---|
| Controller | Owner, role, the other party where one is named, purpose, categories of data subjects, categories of personal data, categories of recipients (the linked vendors with their relationship, then your Recipients text), retention, destination states, security measures, and the lawful basis where one is set. |
| Processor | Role, the controller processed for, categories of processing (your Purpose text), destination states and security measures. |
Destination states prints one line per country with its status and, for a conditional adequacy, the condition. Security measures lists the controls linked to the activity and counts its risks rated for the persons concerned. Fields you added to the class, and fields kept from an earlier preset, follow under Further details. A row without a value reads Not recorded. An activity with no role recorded gets the controller record.
Reference
Findings
| Finding | Raised when | Cleared by |
|---|---|---|
| Transfer without a safeguard | A linked vendor processes data in a third country, and its transfer mechanism is neither a safeguard nor a derogation. One row per activity, vendor and country. | Setting the mechanism on the vendor that covers the country, or ending the transfer and removing the country or the link. |
| Adequacy claimed for a country without it | A vendor's mechanism is Adequacy decision, and one of its countries is a third country under a list that applies. | Choosing the mechanism that covers that country, or correcting the vendor's countries. |
| Decide on prior consultation | The role is not Processor, a risk with the marker Persons concerned stands in a level flagged as a high risk for them, and no finished DPIA on the activity lists that risk as high and records a consultation. | Resolving a DPIA that lists the risk as high and records the consultation, or treating the risk down to a level without the flag. Acceptance does not clear it. |
| DPIA required | Two or more criteria are ticked, or a box that decides alone, with no DPIA filed for the activity and no decision recorded. | Filing a DPIA and picking the activity on it, or recording the decision not to carry one out. |
| Transfer impact assessment needed | A vendor has a safeguarded transfer and no resolved TIA. | Filing a TIA for the vendor and resolving it. |
| No current data processing agreement | A linked vendor is a processor or sub-processor and has no DPA document that is still valid. | Uploading the signed agreement on the vendor's Evidence tab with the type DPA. |
| DPIA rests on measures not yet implemented | The resolved DPIA decided to proceed, and a risk with the marker Persons concerned has treatment actions that are unknown, planned or in progress. | Implementing those actions, or filing a new DPIA with another decision. |
| Transfer impact assessment outdated | An activity was linked to the vendor after its last TIA was resolved. | Filing a new TIA for the vendor that names the activity, and resolving it. |
| DPIA indicated | One criterion is ticked, with no DPIA filed and no decision recorded. | As for DPIA required. |
| Lawful basis missing | The GDPR framework is adopted, the role is not Processor, and Lawful basis (GDPR) is empty. | Choosing the lawful basis on the activity. |
| Categories missing | The role is not Processor, and the categories of data subjects or of personal data are empty. | Ticking both on the activity. |
| Retention period missing | The role is not Processor, and the activity has no Retention period. | Choosing a retention period on the activity. |
A finding about a vendor alone (the adequacy claim, the two TIA findings and the missing agreement) is listed once per vendor, however many activities use it.
The fields of the preset
| Field | Type | Notes |
|---|---|---|
| Purpose | Paragraph | Required. For a processor, the report prints it as the categories of processing. |
| Controller or processor | Pick one | Required. Controller, Processor or Joint controller. |
| Joint controller, or the controller you process for | Single line | The other party. |
| Categories of data subjects | Pick several | A starting list you can extend. |
| Categories of personal data | Pick several | A starting list you can extend. |
| Recipients | Paragraph | Recipients other than the linked vendors. |
| Lawful basis (GDPR) | Pick one | Consent, Contract, Legal obligation, Vital interests, Public task or Legitimate interests. |
| DPIA criteria | Yes or no, one box each | Evaluates or scores people (profiling). Automated decisions with legal or similarly significant effect. Systematic monitoring. Sensitive, criminal or highly personal data. Large scale. Combines datasets from different sources. Vulnerable people. New technology or a novel use of one. Can keep a person from a right, a service or a contract. Collects data without the person noticing. Discloses data to third parties. |
| Boxes that decide alone | Yes or no, one box each | High-risk profiling. On the supervisory authority's list of processing that needs a DPIA. |
| Decision not to carry out a DPIA, with the reason | Paragraph | Filled in, it settles a required or indicated DPIA. |
The asset form and the Detail tab group these fields under Privacy. The screening boxes and the decision sit under the sub-heading DPIA screening, introduced by Tick what applies: one criterion makes a DPIA indicated, two make it required. Each field has a line under it that says what the field does. The lines come with the preset, not from your class: a register that already exists shows them too, and you cannot edit them on the Fields tab.
What a role sees that cannot read vendors, risks or processes
Both Privacy pages and the Privacy tab are open to everyone who can read assets. A custom access role may read assets and not the registers behind them. devguard then withholds those parts and says so with Not shown. A withheld part is never shown as empty.
| The role cannot read | Withheld |
|---|---|
| Vendors | An activity's vendors and its transfers abroad, on both pages, the tab and the report. No finding that names a vendor is listed, and Register Progress leaves out the three vendor steps. |
| Risks | An activity's risks, and the risks of a DPIA. The two findings that rest on risks, prior consultation and unimplemented measures, are not raised. |
| Processes | The status of each DPIA and TIA with its link to the submission, and the figures DPIAs open or missing, Open rights requests and Requests overdue. The findings about a DPIA or a TIA that is missing or outdated are not raised, and Register Progress leaves out the steps for the transfer impact assessments and the DPIAs. Prior consultation is not raised either, because the consultation on record is in a submission that the role cannot see. |
| Controls, treatment actions | The matching list under Security measures on the tab. In the report, Security measures reads Not shown: your role cannot read controls in place of the controls. |
Such a role sees fewer findings than an admin. Its list says what it may read, not that nothing else is open.
Permissions
| Task | Needs |
|---|---|
| Open Privacy, its overview and the Privacy tab | The right to read assets |
| Create the register, update it, change its fields | The right to edit asset classes. Owners and admins have it. |
| Add or edit an activity | The right to edit assets |
| Start from common activities | The right to create assets |
| Link or remove vendors on the Privacy tab | The right to edit assets and the right to edit vendors |
| Record where a vendor processes data, on the Privacy tab | The right to edit vendors |
| Link or remove controls on the Privacy tab | The right to edit assets |
| Add a treatment action on the Privacy tab | The right to create treatment actions and the right to edit risks |
| Pick the activity or the vendor on a submission, and resolve it | The right to edit processes |
| Add a risk for the persons concerned, on the Privacy tab or on a DPIA | The right to create risks |
Where the register appears elsewhere
- The dashboard: the Compliance Scan lists the open findings, and the widget Privacy counts them.
- Assets: every activity is an asset, with its own number, reviews, evidence, tasks and history.
- Vendors: the vendor overview lists Adequacy claimed for a country without it as well.
- Risks: the risks rated for the persons concerned, with the marker Persons concerned.
- Processes: the DPIA, TIA and request submissions.
- Reports: Record of Processing Activities.
- The AI assistant, and through it the MCP server, reads the register with the tool
getPrivacyRegister.
API
The API reference lists every field. Calls go to https://app.devguard.ch/api with Authorization: Bearer <key>.
GET /privacy/register/ returns what the two pages show, for a caller who can read assets:
curl -G "https://app.devguard.ch/api/privacy/register/" \
-H "Authorization: Bearer $DEVGUARD_API_KEY" \
-d "organizationId=<organization-id>"| Field | Meaning |
|---|---|
listsAsOf | The date of the adequacy lists, as YYYY-MM-DD. |
regimes | The lists that apply: ch, eu or both. |
shows | vendors, risks, processes and controls. false where the caller's role cannot read that register. Its part of every activity is then empty because it is withheld. |
classes[] | The register classes. outdated is true when a class lacks preset fields. |
activities[] | Each activity with its role, purpose, dataSubjects, dataCategories, lawfulBasis, retention, controls[], vendors[], risks[] and dpia. |
vendors[].transfers[] | One entry per country: status (ADEQUATE, SAFEGUARDED, DEROGATION, UNSAFEGUARDED), tiaNeeded, and standings[] with one standing per list (HOME, ADEQUATE, THIRD) and its condition. |
vendors[].dpa, vendors[].tia | CURRENT, EXPIRED or NONE; and the TIA state (NOT_NEEDED, MISSING, OPEN, DONE, OUTDATED) with its submission. |
dpia | need (REQUIRED, INDICATED, NONE), state (NOT_NEEDED, MISSING, OPEN, DONE, DECIDED_AGAINST), the criteria ticked, aiSystemLinked, the decision text, the submission and consultationOwed. |
findings[] | One entry per finding: kind, and the activity, vendor and country it concerns, each null where it does not apply. |
progress[] | One entry per step of Register Progress: step (categories, retention, lawfulBasis, dpa, safeguards, tia, dpia), done and total. A step is left out as on the overview. |
requests | open and overdue: the counts of data subject requests. |
kind takes these values, in the order of the findings table: TRANSFER_UNSAFEGUARDED, ADEQUACY_NOT_AVAILABLE, PRIOR_CONSULTATION, DPIA_REQUIRED, TIA_NEEDED, DPA_MISSING, MEASURES_PLANNED, TIA_OUTDATED, DPIA_INDICATED, LAWFUL_BASIS_MISSING, CATEGORIES_MISSING, RETENTION_MISSING.
POST /asset-classes/{id}/apply-preset/ brings a class up to the preset, as Update the register does. It also attaches the preset to a class that does not carry it:
curl -X POST \
"https://app.devguard.ch/api/asset-classes/<class-id>/apply-preset/" \
-H "Authorization: Bearer $DEVGUARD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"presetKey": "processing-activity", "locale": "en"}'locale (en or de) is the language of added fields when the class's own labels do not settle it. A risk for the persons concerned is created with dpiaActivityId or dpiaRunId on POST /risks/; see Risks. DPIA, TIA and request submissions are not in the API. Requests can be filed through the API intake.
How is this guide?
Vendor reviews
Run a periodic review campaign over your vendors, approve each one or reject it with a finding, and finish with a report that records who decided what.
Devices
Keep a list of every company computer and phone, check each one against your security rules every hour, and give an auditor the result.