Key takeaways
- GDPR compliance software keeps the records the GDPR expects (Article 30 record, Article 35 DPIAs, Article 33(5) breach register, requests under Articles 15 to 22) and the evidence of Article 32 security measures.
- It does not make you compliant: under Articles 5(2) and 24 of Regulation (EU) 2016/679 the controller stays responsible for compliance and for being able to demonstrate it.
- Two clocks to track: 72 hours from awareness, where feasible, to notify a breach to the supervisory authority (Article 33(1)); one month to answer requests, extendable by two further months (Article 12(3)).
- No tool detects a breach, chooses the lawful basis or certifies you: GDPR certification under Article 42 comes from accredited bodies or the supervisory authority and does not reduce the controller's responsibility.
- Choose on seven points: fit with your processing, integrations, correct clocks, quality and export of evidence, the vendor's role as processor, exit, fit with ISO/IEC 27001, NIS2 and DORA.
- The same evidence (access review, restore test, penetration test) serves ISO/IEC 27001, GDPR Article 32(1)(d) and NIS2 Article 21(2)(f): collect it once, map it many times.
GDPR compliance software is a category of tools that keeps the records the GDPR expects and tracks the work around them: the record of processing activities (Article 30), DPIAs (Article 35), breach records and notifications (Articles 33 and 34), requests from individuals (Articles 15 to 22) and evidence of security measures (Article 32). It does not make an organisation compliant. Under Articles 5(2) and 24 of Regulation (EU) 2016/679 the controller is responsible for compliance and for being able to demonstrate it: the software holds the proof, people make the decisions.
Article references are to the GDPR as published: a check on the EU Publications Office on 28 October 2026 shows no amending act, only three corrigenda.
Why the GDPR creates a documentation problem
The GDPR does not require any software. It requires accountability: the controller is responsible for the principles in Article 5(1) and has to be able to demonstrate compliance with them (Article 5(2)). Article 24(1) adds that the technical and organisational measures taken to ensure and demonstrate compliance are reviewed and updated where necessary.
In practice this means living documents: a record of processing, risk assessments, processor contracts, breach records, a trail of each request from an individual, and proof that security measures work. In a mid-market organisation they start in spreadsheets, and the trouble starts when they drift apart: a new SaaS tool goes live and the record is not updated, a DPIA describes a replaced system, nobody can show when a request was answered. That drift is what GDPR compliance software is meant to stop.
The functions that map to the Regulation
Record of processing activities (Article 30)
Each controller keeps a record with the contents listed in Article 30(1): purposes, categories of data subjects and of personal data, recipients, transfers to third countries, envisaged time limits for erasure where possible, and a general description of the security measures where possible. Processors keep their own record (Article 30(2)). The record is kept "in writing, including in electronic form" (Article 30(3)) and made available to the supervisory authority on request (Article 30(4)).
The exemption for organisations employing fewer than 250 persons falls away if the processing is likely to result in a risk, is not occasional, or includes special categories of data or data on criminal convictions (Article 30(5)). In our reading, recurring processing such as payroll is not occasional, so the exemption is narrower than it looks.
What a tool adds: an inventory linked to systems, vendors and retention periods, with version history and an export the authority can read.
Data protection impact assessment (Article 35)
Where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons, the controller carries out a DPIA before the processing starts (Article 35(1)). Article 35(3) lists three cases where it is required in particular, Article 35(7) sets the minimum contents (description and purposes, necessity and proportionality, risks, measures), and each supervisory authority publishes its own list of processing that needs one (Article 35(4)).
What a tool adds: templates built on Article 35(7), a step for the advice of the data protection officer where one is designated (Article 35(2)), a link from each DPIA to the record, and review reminders. The judgement on necessity, proportionality and residual risk stays with people, as does prior consultation of the authority under Article 36.
Personal data breaches (Articles 33 and 34)
The controller notifies the competent supervisory authority without undue delay and, where feasible, not later than 72 hours after becoming aware of a breach, unless it is unlikely to result in a risk to the rights and freedoms of natural persons (Article 33(1)). A processor informs the controller without undue delay (Article 33(2)). Every breach is documented, including those that are not notified (Article 33(5)). When the risk to individuals is high, they are informed without undue delay (Article 34(1)).
What a tool adds: a breach register that meets Article 33(5), a clock from the moment of awareness, templates with the minimum content of Article 33(3), and a record of why you notified or not.
What it does not do is notice the breach. The 72 hours run from awareness, and awareness comes from monitoring systems, logs and identities, not from the privacy tool. That part sits with security operations, which is where detection and response services come in.
Requests from individuals (Articles 15 to 22)
The rights cover access, rectification, erasure, restriction, portability, objection and automated decision-making. The controller provides information on the action taken without undue delay and in any event within one month of receipt of the request. That period can be extended by two further months where necessary, telling the person within the first month and giving the reasons (Article 12(3)). Responses are free of charge as a rule (Article 12(5)), and where there are reasonable doubts about identity the controller can ask for additional information (Article 12(6)).
What a tool adds: an intake channel, an identity check, a clock on the one-month limit and a record of what was sent. The hard part is the search: if the tool is not connected to the CRM, the HR system, mailboxes and file shares, someone still searches by hand.
Security of processing (Article 32)
Controller and processor implement technical and organisational measures appropriate to the risk. Article 32(1) gives four examples, the last being a process for regularly testing, assessing and evaluating the effectiveness of those measures (Article 32(1)(d)).
This is where privacy management tools are usually thin: they store a description of the measures. The proof that the measures work (multi-factor authentication enforced, backups restored in a test, vulnerabilities patched, access reviewed) lives in IT systems. Collecting it continuously is the job of compliance automation platforms, which connect to the cloud, the identity provider and endpoint management. Access is the area where auditors ask first, and the one we cover in identity and compliance.
Processors and consent
Two more records tools often cover: processors, which have to provide sufficient guarantees (Article 28(1)) and allow audits under their contract (Article 28(3)(h)), and consent, which the controller has to be able to demonstrate (Article 7(1)).
Categories of tools, described neutrally
- Privacy management platforms. Record of processing, DPIAs, breach register, request handling, processor register. This is the core of what is sold as GDPR compliance software.
- Consent and preference management. Captures and stores consent and its withdrawal on websites and apps.
- Data discovery and classification. Scans systems for personal data and feeds both the record and request handling.
- Compliance automation and GRC platforms. Map controls to several frameworks (ISO/IEC 27001, SOC 2, NIS2, GDPR) and collect evidence from systems.
- Security operations tools. SIEM and managed detection are not compliance software, but they produce the alert that starts the Article 33 clock. See our overview of SIEM tools.
Many products span more than one category, so compare functions, not labels. A GDPR compliant badge on a product describes, at best, how the vendor handles its own processing. It says nothing about yours.
What no software can do for you
- Choose the lawful basis. Article 6 and, for legitimate interest, the balancing test stay with the controller.
- Decide whether a breach is likely to result in a risk. The tool records the decision, it does not take it.
- Replace the DPO where Article 37(1) requires one.
- Certify you. A GDPR certification under Article 42 is issued by accredited certification bodies (Article 43) or by the competent supervisory authority, on criteria approved by that authority or by the European Data Protection Board (Article 42(5)). Even then it does not reduce the controller's responsibility (Article 42(4)). The Board keeps a public register of approved mechanisms (Article 42(8)). A dashboard score is none of these.
- Close the gaps it finds. A missing contract or a stale DPIA still needs an owner.
Fines sit on two levels: up to EUR 10 million or 2 % of worldwide annual turnover, whichever is higher, for the obligations in Articles 25 to 39, which include the record, security, breach notification and DPIAs (Article 83(4)); up to EUR 20 million or 4 % for the principles, consent and the rights in Articles 12 to 22 (Article 83(5)). The measures implemented under Articles 25 and 32 are one of the factors in setting the amount (Article 83(2)(d)), and that is where good evidence counts.
How to choose: seven questions
- Does it start from your processing? Map your main processing activities before buying, even roughly, so the tool follows your record and not a vendor template.
- Does it connect to where personal data lives? Check integrations against your stack: CRM, HR, email, file storage, cloud. Manual fields everywhere mean a spreadsheet with a better interface.
- Are the clocks right? One month for requests, extendable by two; 72 hours from awareness for notifications. Check how the tool records the starting point.
- What does the evidence look like? Timestamps, author, versions and an export an authority or auditor can read without your licence.
- What role does the vendor play? The tool will hold your breach details, request files and staff names. In most set-ups that makes the vendor your processor, so you need an Article 28 contract and, if data leaves the EU, a transfer basis under Chapter V (Articles 44 to 49).
- Can you leave? Full export of records and history in an open format, tested before signing.
- Does it fit your other frameworks? If you also run ISO/IEC 27001, NIS2 or DORA, avoid building two parallel evidence sets for the same controls.
GDPR software, ISO 27001 and evidence automation
An ISO/IEC 27001 management system covers much of the Article 32 ground: risk assessment, access control, cryptography, backup, logging and incident management. Two caveats, in our reading: an ISO/IEC 27001 certificate is not, in itself, an approved certification mechanism under Article 42, and the ISO risk assessment looks at information security risk within the scope of the management system, while the GDPR asks about risk to the rights and freedoms of people. For a management system dedicated to privacy there is ISO/IEC 27701, on privacy information management. More on the certification route on our ISO 27001 page.
The practical consequence is that the same piece of evidence can serve several purposes. An access review, a restore test or a penetration test report supports the ISO/IEC 27001 audit, the testing process of GDPR Article 32(1)(d) and, for organisations in scope of NIS2, the policies and procedures to assess the effectiveness of risk-management measures in Article 21(2)(f) of Directive (EU) 2022/2555. Collect it once, map it many times.
Evidence automation handles proof from systems; privacy management handles records, assessments and requests. Some organisations need both, some cover the second with a well-kept register. If you are adding AI to processes that use personal data, the DPIA and Article 22 questions are covered in GDPR compliant AI.
Where to start
- Build or refresh the record of processing, even in a spreadsheet.
- Mark the processing that is likely to be high risk and check that each has a current DPIA.
- Walk through a breach on paper: which alert starts it, who decides on risk, who notifies, where it is recorded.
- Measure how long requests from individuals take today, and where the search gets stuck.
- Then choose a tool for the gaps you found.
If you want to work out which parts of your GDPR evidence can be collected automatically and which need a decision from your team, talk to us.
