Data minimisation as standard – only purpose-specific data is processed without requiring user action

Privacy by Default Under GDPR Article 25(2): Implementing Default Privacy Settings

Privacy by Default (GDPR Article 25(2)) requires organisations to implement privacy-friendly default settings as standard.

  • 01Systematic integration of data protection into all development processes
  • 02Cost-efficient compliance through early consideration
  • 03Minimization of data protection risks through proactive measures
  • 04Competitive advantages through privacy-friendly innovation
11+Years of experience
120+Employees
540+Projects
ISO 27001certified

What does Privacy by Default require under GDPR Article 25(2)?

GDPR Article 25(2) mandates that personal data is protected through default settings: only the data necessary for the specific processing purpose may be collected by default. This obligation covers the amount of data collected, the extent of processing, the storage period and accessibility. In particular, data must not be made accessible to an indefinite number of persons without the data subject's intervention.

The EDPB Guidelines 4/2019 specify seven design principles as a binding reference framework. Violations can result in fines of up to EUR 10 million or 2% of annual turnover. ADVISORI guides you from analysing existing systems through implementing privacy-friendly default configurations to comprehensive documentation for supervisory authorities.

We support you in developing Privacy by Design & Default from theoretical concepts into practical, integrated organizational processes.

2 service modules

Service scope

01

Privacy by Design Strategy Development

Development of a comprehensive strategy for integrating data protection into all organizational processes.

  • Analysis of current development and business processes
  • Development of a tailored Privacy by Design roadmap
  • Definition of Privacy by Design principles and standards
  • Establishment of governance structures and responsibilities
02

Privacy by Default Implementation

Systematic implementation of privacy-friendly default configurations across all systems and applications.

  • Development of privacy-friendly default settings
  • Integration into existing IT systems and applications
  • Establishment of automated privacy compliance checks
  • Continuous monitoring and adjustment of configurations

5 phases

Our Approach

We follow a systematic approach to implementing Privacy by Design & Default that addresses both technical and organizational aspects.

  1. Analysis of existing development and business processes

  2. Development of a tailored Privacy by Design strategy

  3. Gradual integration into all relevant processes

  4. Training and change management for all stakeholders

  5. Continuous monitoring and optimization of implementation

Sarah Richter

Your contact

Sarah Richter

Head of Information Security, Cyber Security

10+ years of experience, CISA, CISM, Lead Auditor, DORA, NIS2, BCM, Cyber and Information Security

Our Expertise

  • 01In-depth expertise in privacy-friendly system architecture
  • 02Proven methods for integration into existing development processes
  • 03Practical experience in implementation across organizations of various sizes
  • 04Ongoing support throughout the cultural transformation

GDPR Obligation

Privacy by Design & Default are not optional but mandatory GDPR principles. Organizations must be able to demonstrate that they have integrated these principles into their development and business processes.

7 QUESTIONS, BRIEFLY ANSWERED

Frequently asked questions about GDPR Privacy by Design & Default

What exactly does GDPR Article 25(2) require for Privacy by Default?

Article 25(2) GDPR requires controllers to implement technical and organisational measures ensuring that, by default, only personal data necessary for each specific processing purpose is processed. This obligation covers the amount of data collected, the extent of processing, the storage period and accessibility. In particular, data must not be made accessible to an indefinite number of persons without the data subject's intervention.

What concrete measures satisfy the Privacy by Default requirement?

Typical measures include: opt-in rather than opt-out for marketing consent, minimal mandatory fields in forms, shortest retention period as default, restricted profile visibility, deactivated tracking cookies on first use, anonymous usage as standard, and automatic data deletion after purpose fulfilment. The EDPB Guidelines 4/2019 describe seven design principles as a binding reference framework.

How does Privacy by Default differ from Privacy by Design?

Privacy by Design (Article 25(1) GDPR) requires integrating data protection into systems from the development stage, for example through pseudonymisation or data minimisation in the architecture. Privacy by Default (Article 25(2) GDPR) demands that default settings ensure only the data necessary for each specific purpose is processed. Design secures the architecture; Default protects users who do not actively change settings.

How are data minimisation and Privacy by Default connected?

Data minimisation (Article 5(1)(c) GDPR) is the principle limiting collection to what is necessary. Privacy by Default is the technical tool to implement data minimisation in practice: default settings ensure only purpose-specific data is collected without requiring users to actively intervene. Together they form the foundation of a privacy-friendly system.

Does Privacy by Default apply to existing systems or only new developments?

Article 25 GDPR applies to all processing operations, including legacy systems. Controllers must assess whether existing default settings meet the current state of the art and retrofit where necessary. Supervisory authorities expect continuous adaptation to new risks and technological capabilities. A one-time setup is not sufficient.

What fines apply for violating Privacy by Default requirements?

Violations of Article 25 GDPR can be sanctioned under Article 83(4) GDPR with fines of up to EUR 10 million or 2% of worldwide annual turnover. Supervisory authorities have imposed fines where software solutions lacked privacy-friendly default settings or personal data was collected without purpose limitation.

What are the seven EDPB design principles for Article 25 GDPR?

The seven principles developed by Ann Cavoukian are: (1) Proactive not reactive, (2) Privacy as the default setting, (3) Privacy embedded into design, (4) Full functionality with positive-sum approach, (5) End-to-end lifecycle security, (6) Visibility and transparency, (7) Respect for user privacy. These principles have been incorporated into the EDPB Guidelines 4/2019 on Article 25 GDPR.