How does Data Privacy work in Acuna GRC?
Direct answer
Data Privacy in Acuna GRC keeps your record of processing activities, data inventory, privacy assessments, processor agreements, data subject requests and breaches in one place. Each processing activity records its legal basis, data, flows, third parties, transfers and retention. A nine-question screener shows whether a DPIA is required, requests run on a 30-day deadline and breaches on a 72-hour clock.
Data Privacy in Acuna GRC keeps your record of processing activities, data inventory, privacy assessments, processor agreements, data subject requests and breaches in one place. Each processing activity records its legal basis per applicable law, a data grid of subjects, elements and categories, data flows, the legal role of each third party, transfers and retention, and moves through Draft, In Review, Approved and Needs Update. A nine-question screener shows whether a DPIA is required; DPIAs and TIAs start pre-filled from the activity, and DPAs, responses and breach notices are generated as Word documents. Requests run on a 30-day deadline and breaches on a 72-hour clock.
Which laws does Data Privacy cover, and who uses it?
Data Privacy covers the GDPR and the Swiss FADP. An administrator ticks the privacy laws that apply on the Privacy Laws page of the Comply workspace, and that choice drives the legal bases offered on each processing activity, the tabs of the record wizard, the figures on the privacy dashboard, the citations in generated documents and the wording of privacy portal emails. A company subject to both laws keeps one register, with a legal basis recorded for each law on each activity.
The people involved each have their own part:
- The privacy officer or DPO owns the register, runs the assessments and handles requests and breaches.
- Business owners describe the processing they run, in the app or through a questionnaire link that works once and then stops.
- Vendor managers generate DPAs for processors and follow DPA status on supplier records.
- Data subjects submit requests through the public Privacy Portal, which carries your name and logo and needs no Acuna GRC account.
Data Privacy is an add-on module, switched on per organization; the administrator then decides who sees it and switches the Privacy Portal on separately.
How does the register map to GDPR Article 30 and FADP Article 12?
Both laws ask for a record of processing activities: GDPR Article 30 and Article 12 of the revised FADP. In Acuna GRC each processing activity gets a reference such as PA-001 and a detail page with tabs for the overview, the legal basis, data and subjects, assets and recipients, retention and security, risks and findings, and an activity log.
The fields line up with what the record must contain:
- Purpose and description on the overview.
- A data grid with every combination of data subject, data element and data category, with special-category rows highlighted.
- Recipients as assets or third parties, with the legal role of each third party (Controller, Joint Controller, Processor or Sub-Processor) recorded apart from where the data flows.
- A transfer justification per recipient, with a cross-border transfer suggested from the recipient’s country.
- A retention period and trigger, per-category overrides and the security measures.
The register exports as CSV, PDF or XLSX with the record-of-processing columns, including the data flow and legal-role columns. From the same records the module builds a data inventory at asset level, so a system that hosts a data element an activity uses still appears, and draws a data flow diagram per activity.
What happens when an assessment, a request or a breach comes up?
- DPIA. The nine-question screener on each activity derives a risk level and whether a DPIA is required or advisory. The DPIA wizard shares those threshold answers, so register and assessment agree, and a signed DPIA is kept with its report. See when is a DPIA required?
- TIA. Where a cross-border transfer is recorded, the TIA wizard pre-fills the safeguard type from the transfer rows and computes a transfer risk that defaults to High until a person reviews it. See what is a transfer impact assessment?
- DPA. The DPA wizard generates a Word agreement for each processor from the activity record; you upload the signed copy and the supplier record shows a live DPA status. See what is a data processing agreement?
- Requests. Seven request types, from access to automated decision, run on a 30-day due date with one extension of up to 60 days. Under the GDPR the legal limit is one calendar month, extendable by two further months, while the FADP sets 30 days. See how long do you have to respond to a DSAR?
- Breaches. The breach wizard records the type, the risk to rights and the affected activities, assets and third parties, and a live 72-hour clock counts down to the GDPR Article 33 deadline. A notice for the authority is generated for every breach, and one for affected individuals when the risk is High. The FADP asks for a report as soon as possible when a breach is likely to lead to a high risk. See the GDPR 72-hour rule.
What mistakes does the module help you avoid?
- A register written once. Activities move through Draft, In Review, Approved and Needs Update with a next review date, so each one comes back when due.
- A register kept by the privacy team alone. The business owner questionnaire puts the facts in the hands of the people who run the processing, and Apply answers to PA merges the reply.
- Privacy kept apart from security. Findings from the screener become issues in the Assure workspace, risks link to the activities they affect, and third parties are the same register used for supplier risk.
- Lost legacy data. The Acuna team can import your OneTrust export of activities, data mappings, assets and third-party links.
How Acuna GRC handles it
- Module
Data Privacy
Processing activities, data inventory and flows, DPIAs, DPAs, TIAs, data subject requests and breaches, with a public privacy portal.
- Module
Cookie Manager
Part of Data Privacy: a cookie banner on your websites, a consent record for every visitor choice, and a reviewed list of each site’s cookies for your cookie policy.
- Service
DPO as a service
An external DPO from Swiss experts: your record of processing, DPIAs, data subject requests and breaches, run in Acuna GRC for the GDPR and the Swiss FADP.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 12, 28, 30, 33 and 35
- Federal Act on Data Protection (FADP), Articles 12, 22, 24 and 25
This page explains the rules in general terms and is not legal advice.
Frequently asked
Can we use our own templates for the generated documents?
Yes. You can upload a Word template for each of the six generated documents (DPA, TIA, DPIA, DSAR response and both breach notices), see its placeholders, and return to the default at any time.
Is Data Privacy part of the core platform?
It is an add-on module, switched on per organization by Acuna. It then shares the core registers of assets, third parties, risks and issues, and an administrator decides who sees it.
Do data subjects need an account to submit a request?
No. They use the public request page of the Privacy Portal, give their name and email, describe the request and submit. The request arrives in DSARs with a Via portal chip and its 30-day clock started.
See how Acuna GRC runs this.
Tell us your frameworks and your team. We show you how Acuna GRC runs the program.
Hosted in Switzerland, the EU or the US
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

