gdpr

GDPR compliance software: six jobs, the tools for each, and the contract layer they skip

Meera HaldenContracts and legal ops writer10 min read

Written by Meera Halden GDPR compliance software is not one product. The regulation creates at least six recurring jobs: keeping a record of processing, managing consent, answering data subject requests, assessing risky processing, controlling processors, and logging breaches. Some vendors sell a platform that touches all six; others sell one job done well. A company choosing a GDPR compliance tool should first work out which jobs carry enough volume to justify software at all, then match each to the right kind of product. ## The six jobs, with the article behind each | Job | GDPR basis | What has to exist | Volume driver | |---|---|---|---| | Record of processing activities (RoPA) and data mapping | Article 30 | A record of purposes, data categories, recipients, transfers, retention and security measures | Number of systems and purposes | | Consent and cookie management | Articles 6, 7 and the ePrivacy rules for cookies | Proof of consent, easy withdrawal, banner configuration | Websites, apps, marketing channels | | Data subject requests (DSARs) | Articles 12 to 22 | Intake, identity check, search, response within deadline, log | Customer base and request rate | | Data protection impact assessments | Article 35 | Assessment for likely high-risk processing, with mitigations | New products and AI use | | Processor and vendor management | Article 28, plus Chapter V for transfers | Contracts meeting Article 28(3), transfer safeguards, oversight | Number of vendors handling personal data | | Breach log and notification | Articles 33 and 34 | Internal record of every breach; authority notice where required | Incidents | Article 30 lists what the controller's record must contain and carries a limited exemption for organisations with fewer than 250 employees, which does not apply where processing is likely to create a risk, is more than occasional, or includes special category or criminal offence data. In practice most businesses with customer data keep a record anyway, because the other five jobs depend on it. ## Data mapping and the record of processing This is the foundation, and it is where software earns its keep first for mid-size and larger organisations. A spreadsheet RoPA goes stale because nobody is told when a team adopts a new tool. Privacy platforms tackle this with questionnaires sent to system owners, discovery that scans connected systems for personal data, and a register that links each processing activity to systems, vendors, transfers and retention rules. TrustArc, for example, sells a Data Mapping and Risk Manager within its governance suite. OneTrust offers privacy automation across the data lifecycle. What to test: how the tool learns about a new system, how it handles a processing activity spread across five systems, and whether the record can be exported in the format your supervisory authority would expect to receive. ## Consent and cookies Consent management platforms put the banner on your website and app, record each visitor's choices, block trackers until consent, and pass signals to advertising and analytics tools. Cookiebot, a Usercentrics product, scans sites to find and classify cookies and trackers and displays configurable consent banners. TrustArc and OneTrust also sell consent and preference products. Questions for this category: does the scanner catch trackers loaded by tag managers, can it hold regional variations of the banner, and does it keep a consent log you can produce if a regulator asks how a specific person consented. ## Data subject requests Article 12(3) gives you one month to respond, extendable by two further months for complex or numerous requests if you tell the person within the first month. The hard part is not the clock, it is the search: finding one person's data across a CRM, a support desk, a billing system, email, backups and every processor. DSAR software provides an intake form, identity verification, a workflow that assigns searches to system owners, redaction, secure delivery and a log. TrustArc lists an Individual Rights Manager for request workflows. The return on this software tracks request volume closely. A company receiving a handful of requests a year can run a documented manual process; a consumer brand receiving many each week cannot. Look for a tool that records why a request was refused or charged for: Article 12(5) lets a controller refuse, or charge a reasonable fee for, requests that are manifestly unfounded or excessive, but the controller carries the burden of showing that, so the reasoning needs to be on file. ## Impact assessments and the risk register Article 35 requires a DPIA where processing is likely to result in a high risk to individuals, and lists cases such as large-scale processing of special category data and systematic monitoring of public areas. Assessment modules provide templates, scoring, mitigation tracking and approval records. Many companies now run their AI use-case reviews through the same workflow. A template in a document tool works for a few assessments a year; a platform helps when product teams launch features monthly and each needs a screening. ## Breach logs and the 72-hour clock Article 33 requires the controller to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of a breach, unless the breach is unlikely to result in a risk to individuals. It also requires a processor to inform its controller without undue delay. Every breach must be documented internally, including ones you decide not to report. Software helps with the log, the decision record and the notification draft. It cannot make your processors tell you quickly. That depends on the contract, which leads to the job most GDPR compliance tools treat lightly. ## The contract layer: processor terms and transfer clauses Vendor management modules in privacy platforms track which vendors process personal data, send them security and privacy questionnaires, assign risk tiers and record whether a data processing agreement is in place. That last field is usually a yes or no checkbox. Whether the agreement actually works is a legal question. Article 28(3) requires a processor contract to set out the subject matter, duration, nature and purpose of processing and the types of data and data subjects, and to bind the processor to, among other things: process only on documented instructions, keep staff under confidentiality, apply Article 32 security, follow the rules on sub-processors, assist with data subject requests and with security, breach, DPIA and consultation duties, delete or return data at the end, and allow audits. Where personal data leaves the EEA, transfer safeguards are needed too, most often the standard contractual clauses the European Commission adopted on 4 June 2021, which replaced the older sets made under the 1995 Directive. A checkbox that says "DPA signed" hides common problems: - The vendor's DPA allows new sub-processors with notice only through a web page nobody watches.

  • Breach notice is "without undue delay" with no outer limit, or a fixed window longer than your own 72-hour clock allows.
  • Audit rights are replaced entirely by the vendor's own reports.
  • Deletion at the end of service excludes backups, with no stated retention period.
  • The transfer clauses reference the old SCCs or the wrong module. If you are unsure how the DPA relates to your public notice, see privacy policy vs data processing agreement. For how DPAs and SCCs combine, read DPA vs standard contractual clauses, and for negotiating positions, our DPA negotiation playbook. ## Worked example: one vendor, two records A Dublin-based online retailer adds a customer support platform hosted by a US company. The privacy team opens a vendor record in its privacy platform, sends the security questionnaire, tiers the vendor as high because it will hold order history and support conversations, and adds it to the record of processing under the support purpose. Legal then reads the vendor's DPA. It covers most of Article 28(3), but three points need work. Sub-processor changes are announced on a web page with no email notice and no objection right. Breach notice is promised without undue delay but with no outer limit, which leaves the retailer unable to plan for its own 72-hour clock. The transfer section refers to SCCs without saying which module applies to a controller-to-processor transfer. Legal asks for email notice of new sub-processors with a right to object, breach notice within a fixed number of hours, and the correct SCC module attached. The vendor agrees to the first and third, and offers a fixed breach window shorter than the retailer's own deadline. Legal records the agreed positions; the privacy team updates the vendor record from a bare yes to a short summary of the terms that matter, with the review date set to the contract renewal. Two systems, two owners, one vendor, and nothing falls between them. ## Questions to put to a privacy platform vendor - How does the record of processing learn about a new system without someone remembering to tell it?
  • Show a data subject request flowing through five of our real systems, including one with no connector.
  • What does the vendor record store about the DPA: a checkbox, the document, or specific terms?
  • Can assessments be reused for AI use cases as well as DPIAs?
  • What does a breach entry capture, and can it produce a draft notification?
  • If we switch providers, what format does the full export of records, requests and assessments come in, and is there a fee for it?
  • Who maintains the regulatory content behind templates, and how quickly do guidance changes from supervisory authorities reach them? ## Matching tools to organisation size | Organisation | Likely setup | First purchase | |---|---|---| | Small B2B company, few systems, rare requests | Spreadsheet RoPA, manual DSAR process, template DPIAs | Consent management platform for the website | | Mid-size SaaS or e-commerce business | Privacy platform modules for RoPA and DSARs, consent tool, legal reviewing DPAs | DSAR workflow or data mapping, whichever hurts more | | Consumer brand with heavy marketing | Consent and preference management at the centre, DSAR automation | Consent and preference platform | | Large group with many entities | Full privacy platform, vendor risk integrated with procurement, AI governance | Platform with data mapping and vendor modules | Whatever you buy, assign an owner to each of the six jobs. Software without an owner produces a tidy dashboard of overdue tasks. ## What Adira does, and what it does not Adira is not a privacy management platform. It does not build a record of processing, run cookie consent, process data subject requests, host DPIA workflows or keep a breach register. Buy one of the tools above for those jobs. Adira covers the contract review in the processor job. Upload a vendor's DPA or a customer's data clauses and the Document Intelligence Dashboard marks each position as favourable, neutral or unfavourable to your company, flags red flags and missing clauses (an absent audit right, a missing deletion term), and lists key dates and obligations such as notice periods. Clause-Level Editing turns an instruction like "require breach notice within 48 hours" into a precise edit with a diff, and you export the result to Word or PDF to send to the vendor. Adira does not train on your contract corpus, and its own privacy policy addresses GDPR and UK GDPR. Plans start at USD 89 per seat per month billed annually, minimum three seats, with a 7-day free trial; details at adiralaw.com.

Frequently asked questions

Do small companies need GDPR compliance software?
Many do not need a full privacy platform. A company with simple processing can keep its record of processing, DSAR log and breach log in well-structured spreadsheets and use a consent management platform for its website. Software becomes worth it when request volume, the number of systems holding personal data, or the number of processors makes manual tracking unreliable.
Is a cookie banner tool enough for GDPR?
No. A consent management platform handles consent for cookies and trackers on websites and apps. GDPR also requires records of processing, handling of data subject requests, impact assessments where processing is high risk, processor contracts and breach documentation. The cookie tool covers one of those jobs.
What is the deadline for answering a data subject access request?
Under Article 12(3) GDPR the controller must respond without undue delay and in any event within one month of receiving the request. That period can be extended by two further months where necessary, taking into account the complexity and number of requests, provided the person is told within the first month.
Does GDPR compliance software write our data processing agreements?
Generally not. Privacy platforms track vendors, send assessments and record whether a DPA exists. The terms themselves, whether a processor's paper meets Article 28(3) and whether transfer clauses are in place, are reviewed by legal, often in a contract tool or by hand.
Do we need a GDPR compliance tool if we are based outside the EU?
If GDPR applies to you, for example because you offer goods or services to people in the EU or monitor their behaviour, the same obligations apply wherever you are based. The tooling question is the same: which of the six jobs carry enough volume to justify software.
Was this useful?

See how Adira drafts in your voice and reads contracts from your side.

Explore the showroom

Working through a contract like this? Weave is Adira’s free tool to read, mark up, and connect any contract in your browser — no account needed.

Try Weave — free

Book a demo

See Adira on your own contracts

A 30-minute walkthrough with our team. Tell us a little about you, then pick a time that suits you.

Prefer email? [email protected]