Refine By
Clear all filter
About 742 results for "cybersecurity"
CHECKLISTS
This Checklist is designed for use by a buyer undertaking data protection due diligence in the course of acquiring the shares or assets of a business that processes personal data in the context of using, developing or supplying generative artificial intelligence (GenAI) systems. It aims to surface data protection risks and enable a buyer to form a comprehensive view of a target’s risk profile in respect of its GenAI systems, models or tools used for internal operational purposes or provided externally to third parties (Business GenAI Systems). GenAI—a type of artificial intelligence that creates new content, such as text, images, audio, video or code, based on patterns learned from training data—is now widely adopted across industries and national borders. GenAI systems typically rely on substantial volumes of data, including personal data, to train and refine their underlying models. Their development and deployment may therefore give rise to significant compliance challenges under the EU’s General Data Protection Regulation, Regulation (EU) 2016/679 (EU GDPR) regime, particularly in relation
PRACTICE NOTES
This Practice Note introduces the requirements of the EU’s General Data Protection Regulation, Regulation (EU) 2016/679 (EU GDPR) where a processor will process personal data on behalf of a controller in a commercial context. It assumes a degree of familiarity with key data protection concepts and terms and the role of key regulators. For a general introduction to EU GDPR, see Practice Note: The EU’s General Data Protection Regulation (EU GDPR). The requirements under the United Kingdom General Data Protection Regulation, Assimilated Regulation (EU) 2016/679 (UK GDPR) are outside the scope of this Practice Note. For more information about the requirements under the UK GDPR, see Practice Note: Supply chains under data protection law—arrangements between controllers and processors. In brief Data protection laws in the EEA (the EU plus Iceland, Norway, and Liechtenstein) seek to ensure information about living individuals (within the definition of ‘personal data’) is used fairly and responsibly. To help ensure that, the EU GDPR (which applies in the EEA) imposes a large number of obligations on those ‘processing’ personal data (and on
PRACTICE NOTES
A key objective of the EU’s General Data Protection Regulation, Regulation (EU) 2016/679 (the EU GDPR) is to achieve a level of consistency in relation to how data protection is implemented and enforced across the EU and EEA. Under the EU GDPR, each Member State can specify one or more independent public authorities to be responsible for monitoring the application of the EU GDPR, ie a ‘supervisory authority’. This Practice Note: • introduces the European Data Protection Board (EDPB) • introduces the European Data Protection Supervisor (EDPS) • provides a consolidated list of supervisory authorities in the EU and EEA For guidance on sanctions and enforcement under the EU GDPR, see Practice Note: EU GDPR—sanctions and enforcement. The EDPB The EDPB is at the centre of the EU GDPR regime and its guidance and opinions are highly influential. It consists of the head of each of the EU national supervisory authorities, and the EDPS. The EDPB replaced the Article 29 Working Party (Working Party) which was established under Directive 95/46/EC (Data Protection
NEWS
EU Law analysis: On 17 September 2026, the European Commission published its draft proposal for the ‘Keeping Internet Digital Spaces Accountable and Trustworthy’ Act (well done to those who had already spotted that EU KIDS Act is an acronym!). The headline measure is a prohibition on autonomous accounts for under 15s on social media and video-sharing platforms that pose specified risks. The proposal would also impose safety-by-design obligations on what the Commission brands ‘Social Media+’—social media, video-sharing platforms, online games, AI companions and general conversational chatbots, app stores and operating systems.
PRACTICE NOTES
STOP PRESS: On 10 November 2026, the European Data Protection Board adopted, following public consultation, the final version of the Recommendations 1/2026 on the Application for Approval and on the elements and principles to be found in Processor Binding Corporate Rules (Art 47 GDPR). These recommendations repeal and replace, while in substance build on, Working Party Guidance—WP 257 rev.01: Working Document on BCRs for processors and Working Party Guidance—WP 265: Recommendation on the Standard Application form for Approval of Processor Binding Corporate Rules for the Transfer of Personal Data. The recommendations became effective on the date of the publication of the final version and are expected to be implemented by all BCR-P holders, as well as new and ongoing BCR-P applicants, either during the application process or as part of their 2028 annual update, depending on their particular circumstances. For further information, see Practice Note: EU GDPR—EDPB supranational level guidance tracker. This Practice Note discusses Binding Corporate Rules (BCRs), which are one of the mechanisms
PRECEDENTS
STANDARD CONTRACTUAL CLAUSES SECTION I Clause 1 Purpose and scope   (a) The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) (1) for the transfer of personal data to a third country. (b) The Parties: (i) the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter ‘entity/ies’) transferring the personal data, as listed in Annex I.A (hereinafter each ‘data exporter’), and (ii) the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A (hereinafter each ‘data importer’) have agreed to these standard contractual clauses (hereinafter: ‘Clauses’). (c) These Clauses apply with respect to the transfer of personal data as specified in Annex I.B. (d) The Appendix to these Clauses
NEWS
MLex: Google's new plans to give users more choice in how they receive online ads are likely to face close scrutiny from European Commission officials, as they weigh possible legislative proposals on web cookies and digital advertising in the coming months.
NEWS
MLex: Potentially conflicting legal requirements, national governance approaches to ensure regulatory consistency, as well as clear legal advice to minimise the compliance burden, are the main issues seen by EU Member States in the interplay between the EU AI Act and the EU’s General Data Protection Regulation, Regulation (EU) 2016/679 (EU GDPR). European governments have pointed out that the two laws' diverging regulatory approaches might lead to conflicting outcomes, which should be avoided with systematic cooperation between the responsible authorities.
NEWS
MLex: The EU’s draft data-sharing law is primarily concerned with non-personal industrial data. But attempts to fully exclude personal data from some provisions of the EU Data Act will force policymakers starting end-game talks on 29 March 2023, on the final shape of the law to wrestle with the practical distinction between personal and non-personal data. Failure to create clear rules could leave companies wondering which to apply.
PRECEDENTS
1 In this [clause], 2021 EU SCCs means module four (processor to controller) of the standard contractual clauses set out in Commission Implementing Decision (EU) 2021/914. The [Importer Party] shall comply with the data importer’s obligations, and the [Exporter Party] shall comply with the data exporter’s obligations, set out in the 2021 EU SCCs, which are hereby incorporated into and form part of this Agreement. In such incorporated 2021 EU SCCs: 1.1 for the purposes of Annex I.A,
PRECEDENTS
STANDARD CONTRACTUAL CLAUSES SECTION I Clause 1 Purpose and scope   (a) The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with [OPTION 1: Article 28(3) and (4) of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation). OR OPTION 2: Article 29(3) and (4) of Regulation (EU) 2018/1725 of the European Parliament and of the Council of 23 October 2018 on the protection of natural persons with regard to the processing of personal data by the Union institutions, bodies, offices and agencies and on the free movement of such data, and repealing Regulation (EC) No 45/2001 and Decision No 1247/2002/EC.] (b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article
PRACTICE NOTES
This Practice Note is intended to be used to track the status of adequacy decisions relating to cross-border/international transfers of personal data under the EU’s General Data Protection Regulation, Regulation (EU) 2016/679 (the EU GDPR). It includes relevant opinions, reports and guidance issued by EU bodies relating to the status of new and existing decisions. For a comprehensive introduction to the EU GDPR, collating key practical guidance, see: UK data protection law collection. Background Although the text of the EU GDPR refers throughout to the ‘Union’, it is stated on page one of the regulation that it is a text ‘with EEA relevance’, meaning all provisions are intended to be applicable in respect of all EEA members, not just those that also have EU membership. Since the EU GDPR has been incorporated into the EEA Agreement and is in force, references to EU Member States in the EU GDPR can generally be read to also include EEA members. For further information on that incorporation, see the European Free Trade Association’s GDPR tracker. Article 44 of the EU GDPR prohibits