Council digital simplification mandate could reshape GDPR compliance and incident reporting, but the proposed changes remain subject to negotiations with the European Parliament.
The Council of the European Union has agreed its negotiating position on the Digital Omnibus proposal covering data protection, online privacy, data regulation and cyber incident reporting. The mandate supports changes to the GDPR, broader exemptions from cookie consent, consolidation of parts of the EU data acquis and national entry points for reporting incidents under several EU laws.
For DPOs and compliance teams, the mandate is important because it indicates where member states want the final legislation to land. It is not yet law. The Council presidency can begin negotiations only after the European Parliament adopts its own position, and the final text may differ from both. Existing GDPR, ePrivacy and incident-reporting obligations therefore remain in force.
The Council supports targeted amendments rather than a general relaxation of the GDPR.
The Council says its position is intended to reduce administrative burdens while maintaining protection for personal data and fundamental rights. It retains the current definition of personal data but proposes a new provision to clarify when pseudonymised information remains personal data for a particular recipient. Under the mandate, pseudonymised data would not be personal data for a third party that cannot identify the individual, while processors would continue to treat the data as personal data when processing it for a controller.
The mandate also addresses requests that are manifestly unfounded or excessive. A controller would still carry the burden of demonstrating the relevant circumstances, including reasonable grounds for considering a request excessive or evidence of abusive intent. This would not create a general basis for refusing difficult, repeated or inconvenient requests.
Personal data breach notification would move to a higher threshold and a longer deadline.
Under the Council mandate, notification to the supervisory authority would be required where a personal data breach is likely to result in a high risk to individuals, aligning the Article 33 threshold with the threshold for communication to affected people under Article 34. The proposed deadline would be 96 hours after awareness, rather than the current 72 hours, where notification within that period is feasible.
The proposal would not remove the need to assess and document every breach. Controllers would still have to record the facts, effects and remedial action and demonstrate compliance. The mandate also envisages common EU lists of circumstances that are and are not likely to create a high risk, together with a common notification template.
Organisations should not redesign breach procedures yet. The final threshold and deadline may change during negotiations. Incident teams should continue working to the rules currently in force and preserve the ability to escalate quickly, because other laws and contracts may impose different or shorter reporting periods.
National entry points would coordinate reports required under several EU laws.
The Commission originally proposed a single EU entry point for cyber and data incidents. The Council instead supports a national entry point in each member state, supplemented by an EU information point and provisions for cross-border notifications. The aim is to let organisations submit information through one national route when the same incident triggers duties under several EU instruments.
A common entry point would simplify submission, but it would not necessarily make the underlying legal tests identical. A ransomware incident could engage the GDPR, NIS2, sector-specific rules and contractual obligations, each with its own scope, threshold and recipient. Organisations would still need a decision process that identifies every applicable regime and explains how the information in a combined report satisfies each requirement.
Cookie rules would retain consent while expanding specified exemptions.
The Council proposes to retain the framework for cookies and comparable tracking technologies while clarifying additional situations in which consent would not be required. The examples identified by the Council include technologies necessary to provide a service requested by the user, first-party audience measurement and measures needed to protect the security of a service or device.
Where consent remains necessary, the mandate would require an easy and intelligible refusal using a single-click button or equivalent means. If a person refuses consent, the controller would generally have to wait at least six months before asking again for the same purpose. The text also anticipates automated, machine-readable ways to communicate privacy choices.
Businesses should avoid interpreting the proposed exemptions broadly before a final text is adopted. Analytics, advertising and third-party tracking arrangements often involve purposes and recipients beyond basic audience measurement. Each technology would still need to be classified against the final legal conditions and the personal data processing that follows.
The mandate seeks more consistent DPIA requirements across the European Union.
The Council supports an EU-level list of processing operations that are likely to present a high risk and a common template and methodology for data protection impact assessments. This could reduce differences between national supervisory-authority lists and make it easier for organisations operating in several member states to apply a consistent assessment process.
A harmonised list would still be a starting point rather than a substitute for judgement. Controllers would remain responsible for assessing the nature, scope, context and purposes of their processing. DPOs should continue to identify risks that arise from the organisation’s actual deployment, including combinations of data and technologies that may not be captured by a standard example.
Research and AI provisions would require careful use of new flexibility.
The mandate supports a principle-based definition of scientific research and targeted exemptions from some GDPR obligations where appropriate safeguards apply. It also proposes provisions addressing the development and operation of AI systems, including clarification of legitimate interests and a limited derogation for incidental and residual special category data in training, testing or validation data.
The proposed AI derogation would be constrained. It would not cover special category data deliberately acquired or used because of their sensitive characteristics. Controllers would need measures to avoid and remove such data, prevent its use in outputs or disclosure to third parties, document their assessment and monitor whether the safeguards work.
Organisations developing AI should therefore resist treating the mandate as a broad permission to train on personal data. The lawful-basis analysis, reasonable expectations of individuals, transparency, rights, security and data minimisation would continue to matter. The final legislation will determine the exact scope of any new flexibility.
Data regulation would be consolidated and trade secret safeguards strengthened.
The wider package would consolidate rules for data altruism, data intermediation and the re-use of protected public-sector data. It would also allow stronger safeguards where disclosure under the Data Act could expose trade secrets to jurisdictions with inadequate protection or enforcement.
For businesses involved in data sharing, these proposals connect privacy governance with commercial confidentiality. A disclosure assessment may need to consider whether personal data can lawfully be shared, whether access is required under the Data Act and whether technical and contractual measures adequately protect trade secrets. Separate teams should not reach inconsistent conclusions about the same dataset.
DPOs should monitor the negotiations without weakening current controls.
The Council mandate provides a useful basis for scenario planning. Organisations can identify policies, templates and systems that might be affected by a 96-hour breach deadline, a high-risk notification threshold, EU-wide DPIA materials, new cookie exemptions or national incident-reporting portals. That analysis should be kept separate from operational procedures that must comply with current law.
DPOs should also record where apparent simplification could move work rather than remove it. A higher breach threshold increases the importance of a well-evidenced risk assessment. Cookie exemptions require accurate technical classification. Combined incident reporting still depends on knowing which legal regimes apply. Clear records will remain essential even where fewer forms or notices are required.
Discover how Aphaia helps organisations prepare for changes to the EU digital rulebook.
Aphaia helps organisations monitor legislative developments, assess how proposed changes affect existing controls and maintain compliance during regulatory transitions. Integrated privacy and cyber governance can help businesses align breach response, DPIAs, cookie practices, data sharing and AI development without acting on proposals before they become law.

