Access meaning

This flowchart sets out the steps to be taken on an application for a reporting restriction order under the Family Procedure Rules 2010, PD 12I (Applications for reporting restriction orders) and the Practice Note (Official Solicitor: Deputy Director of Legal Services: Cafcass: Applications for reporting restriction orders), also known as the Cafcass Practice Note. For comprehensive, practical guidance on each stage shown and on transparency in the family courts—covering overviews, Practice Notes, precedents, procedural guides, client guides, legislation, forms and further reading—see: Media access and transparency—overview, or select the related documents listed on the right-hand side of the flowchart. For focused guidance on reporting restriction orders, consult the following Practice Notes: Reporting restriction orders—procedure Reporting restriction orders and notifying the media For information about providing advance notice to the media of a reporting restriction order application, refer to: Giving advance notice to the media of a reporting restriction order application—flowchart. For the full collection of Lexis+® UK flowcharts spanning numerous...

In this Checklist, the following defined terms are relevant: application programming interface (API) refers to an application programming interface API Data means any data or other content on the Platform reached by the Application or the API Licensee, and/or sent from the Platform to the Application via an API API Licensee means a provider of an Application that connects to the Platform/API API Licensor means the provider of a Platform/API Application means an application of an API Licensee that uses an API Platform means a platform of an API Licensor that is accessed through an API An API is a source code-level interface that enables applications (specifically, software components) to communicate with one another. It is the outward-facing element of an application that sets the rules for how that application will interact with other software. A developer does not need to grasp the entire codebase of an application to build something compatible with it. So long as the software...

The Investigatory Powers Act 2016 (IPA 2016) reshapes the statutory regime governing covert surveillance conducted by public authorities, a regime largely, but not entirely, previously contained in the Regulation of Investigatory Powers Act 2000 (RIPA 2000). This Checklist carefully sets out those public authorities that hold the power to apply for authorisation to obtain communications data under IPA 2016, Pt 3, preserving the established focus and scope throughout. Authorisations to secure communications data may only be granted where defined conditions are satisfied, by the Investigatory Powers Commissioner under IPA 2016, s 60A, by designated senior officers under IPA 2016, s 61, or by designated senior officers in urgent circumstances under IPA 2016, s 61A. In operational practice, the Office for Communications Data Authorisations carries out this function on the Commissioner’s behalf. The table below specifies which public authorities may apply to access communications data, the kinds of communications data they are permitted to request, together with the purposes for which such data may be obtained, whether...

STOP PRESS: This document is currently being updated to take account of the full implementation of the Data (Use and Access) Act 2025 (DUAA 2025), which amends both the UK GDPR and the Data Protection Act 2018. For further guidance on the compliance consequences of DUAA 2025, see Practice Note: Data (Use and Access) Act 2025—compliance implications. The UK General Data Protection Regulation (UK GDPR) grants data subjects several rights, including, among others: access to their personal data rectification erasure restriction of processing data portability a right of data subjects Individuals may ask an organisation at any time of their choosing to exercise one or more of these rights, and strict time limits and deadlines apply to responding to such requests promptly. See Practice Note: How to handle data subject requests. This Flowchart sets out a process for dealing with data subject requests made under the UK GDPR and reflects the requirements in the UK GDPR together...

STOP PRESS: This document is being revised to take account of the Data (Use and Access) Act 2025 (DUAA 2025), which updates the UK GDPR and the Data Protection Act 2018. For more on the compliance impact of DUAA 2025, see Practice Note: Data (Use and Access) Act 2025—compliance implications... This Flowchart steers you through the lawful mechanisms for sending personal data to a country outside the UK, for example: an adequacy decision or regulation appropriate safeguards such as standard contractual clauses (SCCs) or the International Data Transfer Agreement (IDTA), or binding corporate rules (BCRs) a derogation Such transfers are barred by the data protection regime unless one of these tools is in place. These mechanisms exist to ensure data subjects remain protected when their personal data leaves the UK... The mechanisms follow a hierarchy, and this Flowchart helps you select the route most suitable for your organisation and processing operations... This Flowchart reflects the UK General Data...

In Scotland, the gravest criminal offences are prosecuted there under the solemn procedure...

Antitrust Commission launches investigation into Google’s use of publisher and YouTube content for AI training The Commission has initiated a formal competition investigation to determine whether Google has infringed Article 102 TFEU by using web publishers’ material and content uploaded to YouTube for artificial intelligence (AI) purposes on unfair terms (AT.40983). Commission’s concerns The Commission is assessing whether Google has: used web publishers’ content to produce AI-driven features on Google Search, including AI Overviews (AI-generated summaries shown above organic results) and AI Mode (a chat-style search tab), without proper remuneration and without giving publishers a meaningful way to refuse such use without risking reduced access to Google Search, and/or used YouTube material, including videos and other uploads, to train its generative AI models without compensating creators and without providing an opt-out...

Antitrust Commission issues SO to Meta over WhatsApp AI access limits; flags possible interim measures The Commission has delivered a statement of objections to Meta, outlining its preliminary assessment that Meta blocked third-party artificial intelligence (AI) assistants from accessing and engaging with users on WhatsApp, infringing Article 102 TFEU (AT.41034). The Commission considers that Meta’s behaviour risks preventing competitors from entering or growing in the rapidly expanding market for general-purpose AI assistants and has therefore indicated its intention to impose interim measures (subject to Meta’s rights of defence) to avoid serious and irreparable harm to competition. Background On 15 October 2025, Meta announced changes to its WhatsApp Business Solution Terms, effectively prohibiting third-party general-purpose AI assistants from the platform. Consequently, from 15 January 2026, Meta’s own assistant, Meta AI, has been the only AI assistant available on WhatsApp. On 4 December 2025, the Commission opened formal proceedings to examine whether this policy shift amounts to an abuse of dominance. The investigation covers the EEA, excluding Italy, where...

Antitrust Advocate General suggests Google’s refusal to provide third party access to Android Auto platform may breach Article 102 TFEU Advocate General Laila Medina issued her opinion in Case C- 233/23 Alphabet and Others, a national reference from Italy that seeks guidance and clarification on whether Google’s stance of denying third-party access to Android Auto (a mobile app for Android devices) infringes Article 102 TFEU. For context, Google is the developer of Android OS, an open-source operating system for Android mobile devices. In 2015, Google rolled out Android Auto, an app for mobile devices with an Android operating system that allows motorists to use certain smartphone apps via a car’s integrated display. Independent developers are able to produce iterations of their own apps that work with Android Auto by applying templates supplied by Google. Enel X (part of the Enel Group) delivers electric car charging services. In May 2018, it introduced JuicePass, an app which provides a suite of features for charging electric vehicles. In September 2018, Enel X...

Resource Note This Resource Note signposts key commentary, analysis and materials to aid interpretation and offer practical direction on using Chapter 2 of the Disclosure Guidance and Transparency Rules (DTR 2). Where relevant, it draws on: the Financial Conduct Authority (FCA) Handbook FCA Knowledge Base—Procedural and Technical notes (formal guidance binding on the FCA) FCA consultation and discussion papers, policy and feedback statements, and warnings Primary Market Bulletins and other FCA publications legacy UKLA technical and procedural notes and the UKLA’s newsletter List!, where still pertinent assimilated EU legislation EU Directives and EU Regulations, where helpful to construing a provision Lexis+® UK analysis and resources Setting the scene What it covers: DTR 2 prescribes the framework for issuers to disclose and manage inside information, supporting timely and even-handed release of market-sensitive information. It also identifies specific situations permitting a delay to public disclosure of inside information, together with the safeguards required to keep such information...

This Practice Note sets out the essentials of Regulation (EU) 2024/2847, the EU Cyber Resilience Act (CRA): its background, timeline, aims, and how it aligns with other EU laws. For details on the CRA’s scope or core duties for economic operators, see the following Practice Notes: The EU Cyber Resilience Act—scope and classification of products The EU Cyber Resilience Act—obligations, compliance and enforcement Regulation (EU) 2024/2847, known as the CRA, is the first EU measure to set mandatory cybersecurity requirements for ‘products with digital elements’ across the EU. From December 2027, products that do not satisfy these requirements cannot be placed on the EU market. Accordingly, compliance will be crucial for market entry for both hardware and software. Manufacturers, importers and distributors will have extensive cybersecurity responsibilities and risk significant fines for non-compliance. The CRA was published in the Official Journal of the EU on 20 November 2024, entered into force on 10 December 2024, and applies in full from 11...

Data security sits at the heart of the EU General Data Protection Regulation (EU GDPR). The sixth data protection principle—integrity and confidentiality—requires you to adopt suitable technical and organisational measures so that personal data is processed with appropriate security, including: protection against unauthorised or unlawful processing accidental loss, destruction, or damage This Practice Note reflects Data Protection Commission (DPC) guidance on personal data breaches under the EU GDPR, and also draws on guidance from the European Data Protection Board (EDPB). Data security requirements Article 32 puts practical detail behind the GDPR’s integrity and confidentiality principle. You must implement appropriate technical and organisational measures to achieve a level of security proportionate to the risk, taking into account: the nature, scope, context, and purpose of processing the risk of varying likelihood and severity for the rights and freedoms of data subjects Where appropriate, your security measures should include: the pseudonymisation and encryption of...

The Contract comprises the completed Standard Building Contract Without Quantities for use in Scotland 2016 published by the SBCC subject to the following amendments: Recitals and Articles updated: contractor to provide a master programme and Schedule of Information Requirements; CDP responsibility accepted; Principal Contractor duties priced; arbitration deleted; Schedule of Amendments prevails; Third Party Agreements duties. Contract Particulars: arbitration entries removed; Rectification Period set at 12 months; fluctuations and certain PII/guarantee entries deleted. Conditions: key definitions revised (Practical Completion, Copyright Material, Design sub‑contractors, Funder, Site); Scottish jurisdiction; approvals mean principles only; entire agreement; variations in writing. Design/materials/programming: contractor accepts ER/CP; quality and non‑deleterious materials; programme reporting; site risk; drawings/info supply; tighter discrepancy notices. Time/defects: mitigate and advise on delay; narrower Relevant Events; Practical Completion clarified; stronger rectification, consequential damage and indemnity; phased as‑built/occupation information. IP/confidentiality/BIM: broader licence, moral rights waivers and delivery; confidentiality reinforced; BIM where adopted. Management/sub‑contracting: access, approved Site Manager, meetings; prescribed sub‑contracts; collateral warranties/third‑party rights; CDM duties; insurance...

Definitions Partner(s) • refers to EITHER: [ the following: [ insert names of partners ] OR those [ insert type of group, eg councils or academies in a geographical area or a type of public body ], as described in the Find a Tender service (FTS) Notice. ] The expression Partner(s) shall be understood accordingly. Partner Contract • denotes any arrangement, whatever its form, between the Supplier and the Partner(s) that stems from this Agreement. 1 Use of Agreement by Partner(s) The Supplier accepts and agrees that the Buyer has entered into this Agreement for its own benefit and for the benefit of the Partner(s). Beyond supplying the [ Goods OR Services OR Works ] to the Buyer under this Agreement, the Supplier shall also supply such [ Goods OR Services OR Works ] to any Partner that makes a request, PROVIDED THAT doing so shall not disrupt, compromise, or diminish the level of service the Supplier provides to...

From: [ [ insert job title ], ] [ Name ] [ Insert, eg The Senior Leadership Team ] has established a [ insert period ] objective in order to raise our Governance and Compliance benchmarks even further. This entails ensuring every colleague fully comprehends and reliably adheres to our policies, procedures and relevant laws at the highest possible level. Focus areas include data protection, access to our products and services, and appropriate dealings with customers, suppliers and competitors...

The continuing enforceability of the right of access After the A Land is first registered, whether a right of access remains enforceable hinges on the date when the title to the A Land was first entered on the register. If that initial registration occurred before 13 October 2003, the Land Registration Act 1925, ss 5 and 9 (LRA 1925), provided that the first proprietor of the A Land took the estate subject to any overriding interests that already affected the A Land...

A well-known problem amongst procurement professionals A widely recognised headache for procurement practitioners arises from the duty in regulation 53 of the Public Contracts Regulations 2015 (PCR 2015), SI 2015/102 (PCR 2015, SI 2015/102, reg 53). It requires the ‘procurement documents’ to be accessible at the time a public contract is advertised in the Official Journal of the European Union (the Official Journal, or OJEU). In essence, contracting authorities must use the internet to provide unrestricted, complete and immediate access, at no cost, to those documents from the day a notice, issued under regulation 51, appears in the Official Journal, or from the day an invitation to confirm interest is dispatched. The issue most often raised, particularly for public procurements run under the restricted procedure (and comparable routes that involve a pre-qualification phase ahead of the award stage), is whether the invitation to tender and the specification must already be available when the contract notice is published in the OJEU. Timing this disclosure often proves challenging for contracting authorities...

The Freedom of Information Act 2000 (FIA 2000) and the Data Protection Act 1998 (DPA 1998) are distinct regimes, save for the overlap raised here. They otherwise operate separately from one another as a rule. FIA 2000 contains various exemptions. Those exemptions mean the kind, character or even the presence of the information need not be revealed under FIA 2000. For this scenario, the pertinent carve-out is in FIA 2000, s 40, in particular FIA 2000, ss 40(1) and 40(5)(a). Where the material amounts to personal data and the data subject seeks disclosure via FIA 2000, the exemption applies in absolute terms...