GDPR Article 25: What “Privacy by Design” Actually Means for Your Business

Privacy by design is no longer optional — it’s a legal requirement that can cost UK businesses up to £17.5 million or 4% of global turnover if ignored.[1] GDPR Article 25 mandates that organisations “bake in” data protection from the earliest design stage of any system, service, or process, and maintain it throughout the entire data lifecycle.[2] The good news: companies that embrace privacy by design see an average return of $2.70 for every $1 invested, with 99% reporting measurable business benefits.[3][4]

This isn’t about ticking boxes or adding disclaimers to your website footer. It’s about fundamentally rethinking how your business collects, stores, and uses personal data — and the organisations getting it wrong are now facing record fines. In 2025 alone, ICO average fines jumped from £150,000 to over £2.8 million, with two-thirds related to security breaches that proper privacy by design could have prevented.[5]

Article 25 creates two distinct but related obligations. The first — “data protection by design” — requires organisations to implement “appropriate technical and organisational measures” when determining how they’ll process personal data, and to maintain those measures throughout processing.[6] The second — “data protection by default” — requires that only the minimum necessary personal data is processed for each specific purpose.[7]

The ICO states this plainly: these requirements apply “from the design stage right through the lifecycle” and cover “systems, services, products and business practices.”[2] Critically, this isn’t just about new initiatives — legacy systems designed before GDPR came into force must also be updated to comply.[8]

What “appropriate measures” actually means in practice is deliberately flexible. The law doesn’t prescribe specific technologies or processes. Instead, organisations must consider:

  • The “state of the art” (current technological standards — what was acceptable in 2020 may not be in 2026)
  • The cost of implementation balanced against risk
  • The nature, scope, and purposes of your processing
  • The likelihood and severity of risks to individuals

This means a small professional services firm handling client files will need different measures than a retailer processing millions of customer transactions — but both must demonstrate they’ve genuinely considered privacy in their operations.

Privacy by default means settings must protect data automatically

Article 25’s second limb — privacy by default — is often misunderstood. It doesn’t necessarily mean adopting a “default to off” solution for every data collection, but it does require that personal data isn’t automatically made widely accessible, and that you only collect what you genuinely need.

The ICO checklist emphasises that organisations must “ensure personal data is automatically protected in any IT system, service, product, and/or business practice, so that individuals do not have to take any action to protect their privacy.” This means pre-ticked consent boxes are prohibited, and bundling multiple consents into a single “I agree” checkbox violates the requirement for granular choice.[9]

For business owners, this translates into practical questions: Do your systems default to collecting more data than necessary? Do customers have genuine control over how their information is used? Would the average person understand what they’re consenting to?

Real enforcement actions show what failure looks like

The ICO’s enforcement pattern reveals exactly what goes wrong when organisations neglect privacy by design — and the penalties are substantial.

Doorstep Dispensaree (£275,000, reduced to £92,000) became the ICO’s first GDPR fine explicitly citing privacy by design failure.[10] The London pharmacy left approximately 500,000 patient documents — containing NHS numbers, medical information, and prescriptions for vulnerable elderly care home residents — in unlocked containers in an outdoor courtyard. The ICO found “little to no evidence” of measures to ensure data protection by design.[11] The company’s internal policies hadn’t been updated since 2015.[12]

Capita plc (£14 million settlement from £45 million proposed) demonstrated how ignoring known vulnerabilities creates catastrophic liability. A 2023 cyber attack compromised data of 6.6 million people across 325 pension schemes.[13][14] Three separate penetration tests had identified the exact vulnerability exploited — but no corrective action was taken. The company took 58 hours to respond to a security alert against a one-hour target. The ICO stated: “The scale of this breach and its impact could have been prevented had sufficient security measures been in place.”[15]

TikTok (£12.7 million) illustrated the consequences of inadequate age verification. The platform allowed an estimated 1.4 million children under 13 to use the service between 2018 and 2020, failing to obtain parental consent for children’s data processing.[16] The Information Commissioner was blunt: “TikTok should have known better. TikTok should have done better.”

Advanced Computer Software Group (£3.07 million) marked the first major ICO enforcement against a data processor rather than controller. A ransomware attack disrupted 82 NHS organisations including the NHS 111 helpline[17], leaving patient records inaccessible for nearly 300 days. The attack succeeded because a customer account lacked multi-factor authentication.[18]

Practical implementation goes far beyond IT systems

Privacy by design isn’t solely a technology problem — it applies equally to business processes, physical spaces, and organisational culture.

Customer onboarding and marketing requires clear opt-in consent mechanisms (not pre-ticked boxes), granular privacy options allowing customers to consent to specific uses separately, and preference centres where customers can see how their data is used. Research shows 58% of consumers believe brands hit with data breaches are untrustworthy, and 70% would stop shopping with a brand after a security incident.[19]

HR and employee data handling demands minimum necessary data collection during recruitment and employment, role-based access controls so only authorised personnel can view sensitive records, clear retention policies for employee files, and secure disposal processes when data is no longer needed.

Physical office design encompasses secure storage areas for documents containing personal data, access controls to areas where processing occurs, clear desk policies, secure document destruction facilities, and privacy screens on monitors in public-facing areas.

Procurement and vendor management requires verifying that processors provide “sufficient guarantees” for technical and organisational measures. Only 55% of organisations have proper contractual terms with vendors defining data ownership and liability, despite 81% believing vendors provide sufficient transparency. A processor’s breach is your breach — controllers remain accountable for third-party violations.[20]

The business case for privacy investment is compelling

Beyond avoiding fines, privacy by design delivers measurable returns.

Risk reduction is substantial. GDPR-ready companies are significantly less likely to experience breaches (74% versus 89% for least-prepared organisations). When breaches do occur, they affect fewer records (79,000 versus 212,000) and cause shorter system downtime (6.4 hours versus 9.4 hours). Only 37% of privacy-mature companies had breach losses exceeding $500,000, compared to 64% of those with weaker practices.[21]

Customer trust translates to revenue. Some 91% of consumers are concerned about online data privacy, and 85% want to know a company’s privacy policy before making a purchase.[22] Research from Harvard Business Review found that customers who received transparency and control remained loyal even after data breaches — “empowered customers are more willing to share information and more forgiving of data privacy breaches.”[23]

Competitive differentiation is emerging. Privacy is becoming what “organic” or “cruelty-free” was in the past decade — a genuine market differentiator. Companies using purpose-built privacy solutions score 15% higher on trust indices[24], and external certifications are becoming important factors in enterprise buying decisions. Strong privacy frameworks also enable cross-border data transfers with reduced friction.

Cost avoidance is significant. It’s “much easier and more cost-effective to build the right privacy and security defaults into a new technology from the outset than have to introduce costly retrofits,” as Deloitte notes.[25] GDPR-ready companies also experience shorter sales cycles — 3.4 weeks of delays versus 5.4 weeks for less-prepared competitors.

Common mistakes create unnecessary exposure

The most frequent privacy by design failures follow predictable patterns — and they’re all avoidable.

Treating compliance as a one-time project remains pervasive. Many organisations viewed GDPR as “a few policy updates, a checkbox in the onboarding flow, and a privacy notice on the footer — done.” Privacy by design requires continuous review throughout the data lifecycle.

Focusing exclusively on digital systems while ignoring paper records creates significant gaps. The ICO identifies “loss and theft of paperwork, insecure file storage, improper disposal and data sent to the wrong recipient” as major breach risks. The Doorstep Dispensaree case demonstrates the consequences of neglecting physical documents.

Using generic templates instead of tailored approaches provides false confidence. Different business units handle personal data for different purposes — a one-size-fits-all privacy notice across marketing, HR, and customer services fails because each requires specific technical and organisational safeguards.[26]

Gaps between documented policy and operational practice create liability rather than protection. Privacy policies stating data is encrypted when it isn’t, retention schedules that aren’t enforced, and training policies that never actually train staff all represent compliance failures waiting to be exposed.

Poor vendor management extends risk beyond organisational boundaries. Sharing data without valid Data Processing Agreements, assuming standard security is sufficient without verification, and treating vendor relationships as one-time due diligence rather than ongoing monitoring all create exposure to third-party breaches.

Document digitisation directly enables privacy by design principles

Managing physical documents under GDPR presents unique challenges. Subject Access Requests must be fulfilled within 30 days, the right to erasure must be implemented “without undue delay,” and audit trails must demonstrate who accessed what information and when. These requirements are fundamentally easier to meet with properly digitised records.

Faster SAR compliance becomes achievable when documents are searchable. Digital archives with OCR and indexing enable rapid location of specific data — search by date, department, document type, or phrase. Digital records can be located and compiled in hours rather than days, and redaction tools allow easy removal of third-party personal data before disclosure.

Controlled access and role-based permissions implement the Article 25 requirement that “personal data are not made accessible without the individual’s intervention to an indefinite number of natural persons.” Digital systems enable precise access segmentation — only HR sees employee records, only finance views financial reports — that paper filing systems cannot achieve.

Automated audit trails track who accessed documents, when access occurred, what modifications were made, and deletion activities. These provide “irrefutable proof on what information was leaked, when, and by whom” — essential for demonstrating accountability and detecting unusual activity.

Automated retention management eliminates the human error inherent in manual compliance. Digital systems can automatically archive or delete documents when retention periods expire, with rule-based automation ensuring consistent enforcement across the organisation.

Data migration projects present opportunities for data minimisation. Rather than digitising everything, organisations should audit existing data, identify whether retention is justified, and purge unnecessary records during the migration process. This turns a potential compliance burden into an opportunity for improved data hygiene.

ICO guidance provides a practical compliance framework

The ICO’s official guidance offers a clear checklist that business owners can use to assess their position:

  • Consider data protection issues as part of the design and implementation of systems, services, products and business practices
  • Make data protection an essential component of core functionality
  • Anticipate risks and privacy-invasive events before they occur, and take steps to prevent harm
  • Only process personal data needed for your purposes, and only use it for those purposes
  • Ensure personal data is automatically protected in any IT system, service, product, or business practice
  • Adopt a “plain language” policy for public documents
  • Provide individuals with tools to determine how their data is used
  • Offer strong privacy defaults, user-friendly options and controls, and respect user preferences
  • Only use data processors that provide sufficient guarantees of their technical and organisational measures
  • Use privacy-enhancing technologies where appropriate

The ICO’s February 2023 “Privacy in the product design lifecycle” guidance extends these principles through six stages — kick-off, research, design, development, launch, and post-launch — offering practical direction for embedding privacy throughout project delivery.[27][28]

Conclusion: Privacy by design is both obligation and opportunity

GDPR Article 25 transforms privacy from an afterthought into a core business requirement. The enforcement trend is clear: ICO fines are increasing dramatically, processors face direct accountability alongside controllers, and basic security hygiene failures — missing multi-factor authentication, ignored vulnerability scans, delayed incident response — are creating substantial liability.

Yet the organisations treating privacy by design as strategic investment rather than compliance burden are seeing genuine returns: reduced breach risk, stronger customer trust, competitive differentiation, and operational efficiency from better data management practices.

For UK businesses, the path forward requires embedding privacy considerations from the earliest design stage, maintaining them throughout the data lifecycle, extending due diligence to vendors and partners, and recognising that physical documents require the same rigorous approach as digital systems. Document digitisation and centralised data management provide practical mechanisms to implement these principles — enabling the searchability, access controls, audit trails, and automated retention that GDPR compliance demands.

The ICO’s message is unambiguous: “Cybercriminals don’t wait, so businesses can’t afford to wait either — taking action today could prevent the worst from happening tomorrow.” Privacy by design isn’t just about avoiding fines. It’s about building the kind of trustworthy, well-governed business that customers increasingly demand.

  1. “Direct marketing guidance: Enforcement”. Information Commissioner’s Office.[]
  2. “Data protection by design and default”. Information Commissioner’s Office.[][]
  3. BigID (14 January 2023). “The ROI of a Modern Privacy Program”. bigid.com[]
  4. Harvy Jang (26 January 2026) “Privacy and Data Governance — Keys to Innovation and Trust in the AI Era”. Cisco Blogs[]
  5. Scott Dooley (17 December 2025) “ICO Enforcement in 2025: Record Fines and What They Mean”. Measured Collective[]
  6. Ruth Boardman (26 November 2019) “EDPB Publishes Guidelines on Data Protection by Design and by Default”. Bird & Bird[]
  7. Privacy by Design GDPR: Complete Implementation Guide for 2025. Secure Privacy. 5 November 2025[]
  8. “Guidelines 4/2019 on Article 25, Data Protection by Design and by Default”. European Data Protection Board. 20 October 2020[]
  9. Masha Komnenic (3 November 2025) “Pre-Ticked GDPR Checkboxes for Cookies Are Not Allowed”. Termly[]
  10. “London pharmacy fined after “careless” storage of patient data “. European Data Protection Board. 20 December 2019[]
  11. Lucy Hart, Benjamin SLinn (March 13, 2020) “UK Data Privacy Compliance: Lessons from the ICO’s First Fine”. Global Compliance News[]
  12. Emmanuel Ronco, Natalie Farmer & Chloe Hassard (30 January 2020) “UK ICO Finally Issues GDPR Fine”. Cleary Cybersecurity and Privacy Watch[]
  13. Jay Doraisamy, Oliver Yaros, Katherine Carter, Ellen Hepworth (24 October 2025) “Capita Cyber Security Breach – £14 Million Fine Issued”. Mayer Brown[]
  14. Ella Ditri (22 October 2025)“ICO fines Capita for UK GDPR infringements following March 2023 data breach”. Clifford Chance[]
  15. Connor Jones (15 October 2025) “Capita fined £14M after 58-hour delay exposed 6.6M records”. The Register[]
  16. “TikTok fined £12.7m for misusing children’s data”. Macfarlanes. 25 April 2023[]
  17. “ICO Fines Advanced Computer Software Group £3 Million Following Ransomware Attack”. Hunton. 2 April 2025[]
  18. Oscar Ting (11 April 2025) “ICO fines processor after inadequate security measures lead to widespread disruption to critical services”. Clifford Chance[]
  19. “Building Trust: Data Security & Privacy for UK eCommerce Customers (UK GDPR)”. eDesk. 30 May 2025[]
  20. Robb Hiscock (1 March 2023). “How to Approach the ICO’s ‘Privacy in the Product Design Lifecycle’”. OneTrust.[]
  21. “Maximizing the value of your data privacy investments, Data Privacy Benchmark Study”. Cisco. January 2019[]
  22. Haider Iqbal “Privacy by Design: Making Privacy a Business Enabler”. Thales[]
  23. Cynthia Larose and Brian Lam (28 March 2025) “How to Leverage Privacy as a Key Competitive Advantage”. MintzEdge[]
  24. “Privacy as a Strategic Business Advantage: How to Turn Compliance into Competitive Edge”. TrustArc[]
  25. “Ryerson, Deloitte partner to offer privacy certification”. Deloitte[]
  26. “The 5 most common data privacy mistakes – and how to avoid them”](https://kpmglaw.ie/insight-data-privacy-mistakes.html). KPMG Law. 8 January 2024[]
  27. Julie Rubash (27 February 2023) “UK ICO issues Privacy by Design guidance”. Sourcepoint[]
  28. Christopher Beveridge (25 April 2023) “The ICO’s new guidance on privacy in the product design lifecycle”. BDO[]