Covered Data All instances of "Student Data" should be replaced with "LEA Data". The protections provided within this DPA extend to all data provided to or collected by the Provider.
User Data In addition to any disclosures authorized by Section 24, You and Your Authorised Users consent and agree that the RIM Group of Companies may access, preserve, and disclose Your or Your Authorised Users' data, including personal information, contents of your communication or information about the use of Your BlackBerry Solution functionality and the services or software and hardware utilized in conjunction with Your BlackBerry Solution where available to RIM ("User Data"), to third parties, including foreign or domestic government entities, without providing notice to You or Your Authorized Users under the laws of countries where the RIM Group of Companies and its service providers, other partners and affiliates are located in order to: (i) comply with legal process or enforceable governmental request, or as otherwise required by law; (ii) cooperate with third parties in investigating acts in violation of this Agreement; or (iii) cooperate with system administrators at Internet service providers, networks or computing facilities in order to enforce this Agreement. You warrant that You have obtained all consents necessary under applicable law from Your Authorised Users to disclose User Data to the RIM Group of Companies and for the RIM Group of Companies to collect, use, process, transmit, and/or disclose such User Data as described above.
De-Identified Data Provider agrees not to attempt to re-identify de-identified Student Data. De-Identified Data may be used by the Provider for those purposes allowed under FERPA and the following purposes:
Your Data Subject to the limited rights granted by You hereunder, We acquire no right, title or interest from You or Your licensors under this Agreement in or to Your Data, including any intellectual property rights therein.
Licensee Data Licensee acknowledges and agrees that Licensee will be solely responsible for backing-up, and taking all appropriate measures to protect and secure, Licensee Data. Licensee acknowledges that Nuix may make, store and maintain back up copies of Licensee Data, but is not obliged to do so. Nuix will not be liable for any loss or corruption of Licensee Data.
Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.
Business Records Keep, and cause each Subsidiary to keep, adequate records and books of account with respect to its business activities in which proper entries are made in accordance with GAAP reflecting all its financial transactions.
Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.
Client Records 26.2.1 CONTRACTOR shall prepare and maintain accurate and complete records of clients served and dates and type of services provided under the terms of this Contract in a form acceptable to ADMINISTRATOR.
Access to Software Access Rights to Software which is Results shall comprise: Access to the Object Code; and, where normal use of such an Object Code requires an Application Programming Interface (hereafter API), Access to the Object Code and such an API; and, if a Party can show that the execution of its tasks under the Project or the Exploitation of its own Results is technically or legally impossible without Access to the Source Code, Access to the Source Code to the extent necessary. Background shall only be provided in Object Code unless otherwise agreed between the Parties concerned.
