Refine By
Clear all filter
About 92483 results for "*"
CHECKLISTS
This Checklist outlines the issues that need to be considered when drafting a mobile app end-user licence agreement (EULA) to be distributed on an app store. For template EULAs, see Precedents: • Mobile app end-user licence agreement (EULA)—generic • Mobile app end-user licence agreement (EULA)—for Apple App Store • Mobile app end-user licence agreement (EULA)—for Google Play The third column can be used to record observations or comments as the Checklist is worked through. Checklist Further information Notes (if any) Take instructions ☐ Take instructions in order to understand the features and functionality of the app that may impact the drafting of the EULA See below for specific requirements for certain features such as augmented reality. Identify the relevant app store’s requirements ☐ Apple App Store: ensure the EULA contains Apple’s minimum terms Although Apple provides a default EULA, it allows app providers to upload their own provided the minimum terms are included.See Precedent: Mobile app end-user licence agreement (EULA)—for Apple App Store. ☐ Google Play: ensure the
PRECEDENTS
We are [app provider’s name and address], the creators of [app name] (referred to below as the ‘app’). You must be at least [13] years old and resident in the UK to use the app. By downloading the app, you are agreeing to the terms of this agreement which are legally binding. Please read it together with our privacy policy before you download and use the app. Only download the app if you have read the rules and agree to them. If you do not agree to these terms, we will not allow you to use the app and you should not download it. In this agreement, references to the ‘App Store’ means Apple’s App Store, and we refer to the rules contained in the Apple Media Services Terms and Conditions as the ‘App Store rules’. 1 This agreement 1.1 This agreement is made between us you and us. Apple is not a party to this agreement and has no responsibility for the app or its content. 1.2 We license you to download the app onto any Apple-branded
PRECEDENTS
We are [app provider’s name and address], the creators of [app name] (referred to below as the ‘app’). You must be at least [13] years old and resident in the UK to use the app. By downloading the app, you are agreeing to the terms of this agreement which are legally binding. Please read it together with our privacy policy before you download and use the app. Only download the app if you have read the rules and agree to them. If you do not agree to these terms, we will not allow you to use the app and you should not download it. In this agreement, references to ‘Google Play’ means the app distribution platform operated by Google and known as Google Play, and we refer to Google’s terms of service (and other applicable terms) collectively as ‘Google’s rules’. 1 This agreement 1.1 This agreement is made between us you and us. Google is not a party to this agreement and has no liability under it. 1.2 We license you to download and use the app provided you follow all of the rules described
PRECEDENTS
We are [app provider’s name and address], the creators of [app name] (referred to below as the ‘app’). You must be at least [13] years old and resident in the UK to use the app. By downloading the app, you are agreeing to the terms of this agreement which are legally binding. Please read it together with our privacy policy before you download and use the app. Only download the app if you have read the rules and agree to them. If you do not agree to these terms, we will not allow you to use the app and you should not download it. 1 This agreement 1.1 We license you to download and use the app provided you follow all of the rules described in this agreement. The licence: 1.1.1 is only for you personally (and anyone else that the app store lets you share the app with) and for non-business use; 1.1.2 starts when you download the app; and 1.1.3 covers content, materials, or services accessible from, or bought in, the app including all of our support resources. It also covers updates
PRECEDENTS
Background to this thought leadership Precedent This Precedent was produced as part of a thought leadership project by the Data Protection Intelligence Group in October 2021. Subsequent updates were made by Lexis+® UK in February 2022 and in early 2026.It is intended as a starting point to assist organisations and development of thinking on this new privacy expectation in the market. This Precedent will continue to evolve based on emerging guidance, market practice and engagement. It provides a template of the basic text that may be included in information addressed to this age group.It should be: —implemented on the app and enhanced (eg with layering of information, diagrams, cartoons, graphics, video, audio, gamified and/or interactive content) to attract and interest children in this age range as appropriate to the app provider’s branding and service—implemented so the information is presented in appropriately small chunks (eg by presenting topics or groups of topics on separate sub-pages within an easily navigated framework to avoid any page being too long); the information in this
PRECEDENTS
Background to this thought leadership Precedent This Precedent was produced as part of a thought leadership project by Lexis+® UK in February 2022. Subsequent updates were made by Lexis+® UK in early 2026.It is intended as a starting point to assist organisations and development of thinking on this new privacy expectation in the market. This Precedent will continue to evolve based on emerging guidance, market practice and engagement. It provides a template of the basic text that may be included in information addressed to this age group.It should be: —implemented on the app and enhanced (eg with layering of information, diagrams, cartoons, graphics, video, audio, gamified and/or interactive content) to attract and interest children in this age group as appropriate to the app provider’s branding and service—implemented so the information is presented in appropriately small chunks (eg by presenting topics or groups of topics on separate sub-pages within an easily navigated framework to avoid any page being too long); the information in this notice is not intended to be presented to
PRECEDENTS
Background to this thought leadership Precedent This Precedent was produced as part of a thought leadership project by Lexis+® UK in April 2022. Subsequent updates were made by Lexis+® UK in early 2026.It is intended as a starting point to assist organisations and development of thinking on this new privacy expectation in the market. This Precedent will continue to evolve based on emerging guidance, market practice and engagement. It provides a template of the basic text that may be included in information addressed to this age group.It should be: —implemented on the app and enhanced (eg with layering of information, diagrams, cartoons, graphics, video, audio, gamified and/or interactive content) to attract and interest children in this age group as appropriate to the app provider’s branding and service—implemented so the information is presented in appropriately sized chunks (eg by presenting topics or groups of topics on separate sub-pages within an easily navigated framework to avoid any page being too long); the information in this notice is not intended to be presented to
PRECEDENTS
Background to this thought leadership Precedent This Precedent was produced as part of a thought leadership project by the Data Protection Intelligence Group in October 2021. Subsequent updates by Lexis+® UK were made in February 2022 and in early 2026.It is intended as a starting point to assist organisations and development of thinking on this privacy expectation in the market. This Precedent will continue to evolve based on emerging guidance, market practice and engagement. It provides a template of basic text that may be adapted for inclusion in a cartoon, video and/or audio and other features (eg a message with emojis) designed to attract and interest children as appropriate to the app provider’s branding and service.It should be: —supported by appropriate just-in-time notifications and warnings (eg if a child changes a setting), and—enhanced with appropriate functionality to allow users to easily get an overview of, and navigate between, topicsFor further guidance on how the basic text might be adapted, see Practice Note: Conveying privacy information to children aged
PRECEDENTS
Policy version: [insert date of this policy][—for previous versions of this policy see here ] [Insert name of mobile app] [for [insert operating system(s)]] (the app) is provided by [insert name and description of app provider] [trading as [insert trading name, if different]] (‘we’, ‘our’ or ‘us’). We take your privacy very seriously. Please read this privacy policy carefully as it contains important information on [who we are and] how and why we collect, store, use and share any information relating to you (your information). It also explains your rights in relation to your information and how to contact us or the relevant regulator in the event you have a complaint. Our collection, storage, use and sharing of your information is regulated by law, including under the UK General Data Protection Regulation (UK GDPR). We are the controller of your information obtained via the app, meaning we are the organisation legally responsible for deciding how and for what purposes it is used. If you are aged under [13] you must not use the app as it is not designed for
PRECEDENTS
This Agreement is made on [insert date] (the Commencement Date) between the following: Parties 1 [insert supplier name], a company incorporated in England and Wales whose registered number is [insert company number] and whose registered office is at [insert registered office] (Supplier); and 2 [insert customer name], a company incorporated in England and Wales whose registered number is [insert company number] and whose registered office is at [insert registered office] (Customer), each of the Supplier and the Customer being a party and together the Supplier and the Customer are the parties. Background (A) The Supplier is [an experienced developer of mobile applications and] [insert the Supplier’s background details and the background to the relevant transaction]. (B) The Customer is [insert the Customer’s background details]. (C) The Supplier wishes to develop the Mobile App (as defined below) and the Customer wishes to engage the Supplier to develop the same on the terms of this Agreement. The parties agree: 1 Definitions and interpretation 1.1 Words shall have the meanings given to them in this Agreement including without limitation, as set out below: Acceptance • means the successful
PRECEDENTS
This Agreement is made on [insert date] (the Commencement Date) between the following: Parties 1 [insert supplier name] a company incorporated in England and Wales whose registered number is [insert company number] and whose registered office is at [insert registered office] (Supplier); and 2 [insert customer name] a company incorporated in England and Wales whose registered number is [insert company number] and whose registered office is at [insert registered office] (Customer), each of the Supplier and the Customer being a party and together the Supplier and the Customer are the parties. Background (A) The Supplier is [insert the Supplier’s background details and the background to the relevant transaction]. (B) The Customer is [insert the Customer’s background details]. (C) The Supplier wishes to develop the Mobile App (as defined below) and the Customer wishes to engage the Supplier to develop the same on the terms of this Agreement. The parties agree: 1 Definitions and interpretation 1.1 Words shall have the meanings given to them in this Agreement, including as set out below: App Store • means the online system, market place or store (as specified in paragraph
PRACTICE NOTES
This Practice Note explores the network and facilities sharing arrangements entered into by mobile network operators (MNOs). In examining the key types of infrastructure sharing, the strategic rationale behind the practice, infrastructure sharing models, competition issues, and future developments, it presents an overview of how legal and regulatory risks may be best managed in the UK market. Navigating the complex waters of negotiating network and facilities sharing arrangements can bring significant benefits for MNOs. Strategic sharing initiatives continue to present significant cost saving opportunities, whether collaborating with market competitors, or through tie-ups with independent tower companies or facilities providers. However, as this Practice Note illustrates, it remains key to ensure that inherent legal and regulatory risks are managed effectively when negotiating and concluding arrangements. Brexit This Practice Note focuses on the position in the UK market and includes consideration of relevant UK competition law. This primarily focuses on the block exemptions which may be applicable to the type of sharing arrangements discussed here. Block exemptions specify conditions under which certain types of