Using Shurgard Mobile App Clause Samples

The 'Using Shurgard Mobile App' clause defines the terms and conditions under which users may access and utilize the Shurgard mobile application. It typically outlines user responsibilities, permitted uses, and any restrictions on the app’s features, such as account management, payment processing, or facility access. By establishing clear guidelines for app usage, this clause helps ensure both the security of user data and the proper functioning of the app, while also protecting the company from misuse or unauthorized activities.
Using Shurgard Mobile App. The Mobile App is available to all Customers who accept to be bound by these General Terms (including but not limited its Article 2 .a) in order to: (i) obtain a touchless access to a Shurgard Storage Facility using, where applicable, their geolocation data (the "Touchless Access"); and (ii) for Customers already having a Storage Agreement in place with Shurgard, create an account (the "Mobile App Account") allowing them to access different features (the "Services") in relation to their Storage Agreement (such as invoice management). However, the use of the Mobile App is not mandatory and the Customer is not under any obligation to use the Mobile App and create an account in order to benefit from their Storage Agreement, which remains unaffected. Shurgard will have the right to modify, add, or remove any feature of the Mobile App without prior notification for the Customer. For the sake of clarity, any such change to the Mobile App does not entail any change to any Storage Agreement in place, or any change to these General Terms which remain subject to the rules set out under article 17.3. 2.a.1 In order to access the Mobile App, the Customer must agree to the current version of the General Terms.
Using Shurgard Mobile App. 2bis.1 The Mobile App is available to all customers who agree to be bound by these General Terms (including but not limited to this article 2bis) in order to: (i) obtain touchless access to a Shurgard storage facility using, where applicable, their geolocation data ("Touchless Access"); and (ii) for customers already having a Storage Agreement in place with Shurgard only: create an account (the "Mobile App Account") allowing them to access different features in relation to their Storage Agreement as set out in article 2bis.12 (the " Mobile App Services"), as amended by ▇▇▇▇▇▇▇▇ from time to time in accordance with article 2bis.3 below. 2bis.2 Use of the Mobile App is not mandatory, and the Customer is not under any obligation to use the Mobile App or create a Mobile App Account in order to benefit from the Storage Agreement, which remains unaffected. 2bis.3 Shurgard has the right to modify, add, or remove any feature of the Mobile App without prior notification to the Customer to reflect any changes to the Mobile App Services or changes needed to reflect changes in the law. For the sake of clarity, any such change to the Mobile App does not entail a change to any Storage Agreement in place, or a change to these General Terms, which remain subject to the rules set out under article 16.2. 2bis.4 In order to access the Mobile App, the Customer must agree to the current version of these General Terms.

Related to Using Shurgard Mobile App

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.