Key Articles Explained
Art. 6
Legal Basis for Processing
Six lawful grounds: consent (must be freely given, specific, informed, unambiguous); contract (processing necessary to perform a contract with the data subject); legal obligation; vital interests; public task; legitimate interests (requires a balancing test — the controller's interests must not override the individual's rights and freedoms).
Art. 7
Conditions for Consent
Consent must be demonstrated, freely given, specific to a purpose, informed (clear language), and unambiguous. Pre-ticked boxes are not valid. Consent to different processing activities must be obtained separately. Records of when and how consent was obtained must be kept.
Art. 13–14
Transparency Obligations
Art. 13 applies when data is collected directly from the data subject; Art. 14 when obtained from third parties. Both require the same core information: controller identity, DPO contact details, purposes and legal basis, recipients, retention periods, rights information, and right to withdraw consent or lodge a complaint.
Art. 17
Right to Erasure
Individuals can request erasure when data is no longer necessary; consent is withdrawn with no other legal basis; they object and there are no overriding legitimate grounds; data was unlawfully processed; or erasure is required by EU or member state law. Important exceptions apply for freedom of expression, legal claims, and public health.
Art. 28
Data Processing Agreements
Every relationship where a third party processes personal data on your behalf requires a written DPA. The DPA must cover: subject matter and duration, nature and purpose of processing, type of data, categories of data subjects, and the processor's obligations — including restrictions on sub-processing and assistance with data subject rights.
Art. 30
Records of Processing Activities (RoPA)
Mandatory for most organisations. The RoPA must document: controller name and contact, purposes of processing, categories of data subjects and personal data, recipients, international transfers, retention periods, and security measures. Must be maintained in writing and available to the supervisory authority on request.
Art. 32
Security of Processing
Controllers and processors must implement "appropriate" technical and organisational measures, considering the state of the art, costs, nature, scope, context, and risk. Examples given by the Regulation include pseudonymisation, encryption, resilience, backup, and regular testing. "Appropriate" means proportionate to the risk — not necessarily the highest possible standard.
Art. 33–34
Personal Data Breach Notification
Art. 33: notify your lead DPA within 72 hours of becoming aware of a breach likely to result in risk to individuals' rights and freedoms — unless the breach is "unlikely to result in a risk". Art. 34: notify affected individuals "without undue delay" if the breach is likely to result in high risk. Document all breaches regardless of whether notification is required.
Art. 35
Data Protection Impact Assessment (DPIA)
Mandatory before processing that is "likely to result in a high risk" — including large-scale processing of sensitive data, systematic profiling, large-scale public monitoring, and any processing type on the DPA's required list. The DPIA must assess the necessity, proportionality, and risks of the processing, and set out mitigation measures.
Sector Implications
Technology & SaaS
Tech companies are typically both controllers (for their own employee and customer data) and processors (for their customers' end-user data). The dual role requires careful legal structuring: service agreements must contain Art. 28 DPAs, sub-processors must be disclosed, and technical architecture must support data deletion and portability. Cookie consent — enforced under the ePrivacy Directive in conjunction with GDPR — is a near-universal compliance challenge.
Healthcare
Health data is "special category" data under Art. 9, requiring an additional legal basis beyond the Art. 6 grounds. Processing health data requires explicit consent or reliance on Art. 9(2)(h) (healthcare provision). DPIAs are typically mandatory. Breach notification timelines are strictly enforced given the sensitivity of health information.
Financial Services
Banks and fintechs process personal data at scale across multiple purposes: credit assessment, fraud prevention, regulatory compliance, and customer communication. Each purpose requires its own legal basis. Automated credit decisions trigger Art. 22 (no solely automated decisions with significant effects) unless specific conditions are met. Tension between GDPR data minimisation and AML record-keeping obligations requires careful management.
Retail & E-commerce
Cookie consent banners, email marketing consent, loyalty programme data retention, and cross-border payment data flows are the primary GDPR touchpoints for retail. The "legitimate interests" basis for personalised marketing has been significantly narrowed by DPA guidance and CJEU case law — explicit consent is often the only defensible basis.
Full Compliance Checklist
1
Map all personal data flows across your organisation — what data is collected, where it's stored, who can access it, and where it goes (data mapping / Records of Processing Activities)
2
Identify and document the legal basis (Art. 6 ground) for each processing activity — create or update your RoPA (Art. 30)
3
Review and update all privacy notices to ensure they meet Arts. 13–14 requirements (purposes, retention, rights, transfers)
4
Audit your cookie consent implementation — confirm it meets the freely given, specific, informed, unambiguous standard and that analytics/marketing cookies are not loaded before consent
5
Execute written Data Processing Agreements with all third-party processors (cloud storage, payroll, email marketing, CRM, etc.)
6
Build a data subject rights fulfilment process — verify you can respond to access, deletion, rectification, and portability requests within 30 days
7
Implement a personal data breach response procedure — detection, assessment, internal escalation, DPA notification (72 hours), and individual notification where required
8
Assess whether you need to appoint a Data Protection Officer (DPO) — mandatory for public authorities, organisations engaging in large-scale systematic monitoring, or large-scale special category data processing
9
Review all international data transfers — confirm adequacy decisions, SCCs, BCRs, or other transfer mechanisms are in place for any transfers outside the EEA
10
Conduct Data Protection Impact Assessments (DPIAs) for any high-risk processing activities (large-scale profiling, special category data, systematic public monitoring)
11
Implement technical security measures proportionate to the risk: encryption at rest and in transit, access controls, pseudonymisation where appropriate, and regular penetration testing
12
Train all staff who handle personal data on GDPR obligations, your internal policies, and how to recognise and escalate a potential data breach
How to Use the Verdaio GDPR Tools
Verdaio offers two complementary tools for GDPR compliance. The GDPR Quick Check covers 24 questions across six compliance areas (lawful basis, rights, data security, breach response, processors, and records) and delivers an instant gap analysis showing which areas are at risk and which GDPR articles are implicated — free, no signup required.
The Full GDPR Assessment + RoPA is a premium deep-dive that goes beyond the quick check to produce a draft Record of Processing Activities (Article 30), a fine exposure analysis based on your specific gaps, and a prioritised remediation roadmap. It is designed to give compliance teams and DPOs a structured starting point for their GDPR programme.
GDPR Quick Check (free) → | Full GDPR Assessment + RoPA →