STUDENT DATA Contractor acknowledges that student data is protected by both federal and state law. See Wis. Stat. § 118.125; 20 U.S.C. § 1232g(b); 34 C.F.R. § 99.1
Client Data The Subrecipient shall maintain client data demonstrating client eligibility for services provided. Such data shall include, but not be limited to, client name, address, income level or other basis for determining eligibility, and description of service provided. Such information shall be made available to Grantee monitors or their designees for review upon request.
Fund Data 8.1. The Fund (i) will provide or ensure that other Persons provide all Fund Data to DST in an electronic format that is acceptable to DST (or as otherwise agreed in writing) and (ii) confirm that each has the right to so share such Fund Data. As between DST and the Fund, all Fund Data shall remain the property of the applicable Fund. Fund Data shall not be used or disclosed by DST other than in connection with providing the Services and as permitted under Section 11. Subject to the terms of this Agreement, DST shall be permitted to act upon instructions from an Authorized Person with respect to the disclosure or disposition of Fund Data but may refuse to act upon such instructions where it doubts, reasonably and in good faith, the authenticity or authority of such instructions.
8.2. DST shall keep records relating to the services to be performed hereunder, in the form and manner as it may deem advisable. To the extent required by Section 31 of the 1940 Act, DST agrees that all such records prepared or maintained by DST relating to the services to be performed by DST hereunder are the property of the Fund and will be preserved, maintained and made available in accordance with the Act, and will be surrendered promptly to the Fund on and in accordance with its request. For the avoidance of doubt, the preceding sentence shall apply to any Funds that are collective trusts as if they were 1940 Act registered funds. DST shall maintain and store such records for a rolling period of 7 years starting from the date that such records were created, or such longer period as required by applicable Law or its internal policies or until such earlier time as it returns such records to the Fund.
Information Regarding Collateral (a) Level 3 and the Borrower will furnish to the Collateral Agent prompt written notice of any change (i) in any Loan Party’s corporate name or in any trade name used to identify it in the conduct of its business or in the ownership of its properties, (ii) in any Loan Party’s identity or corporate structure or (iii) in any Loan Party’s Federal Taxpayer Identification Number. Each of Level 3 and the Borrower agrees not to effect or permit any change referred to in the preceding sentence unless all filings (or arrangements therefor satisfactory to the Collateral Agent) have been made under the Uniform Commercial Code or otherwise that are required in order for the Collateral Agent to continue at all times following such change to have a valid, legal and perfected security interest in all the Collateral. Each of Level 3 and the Borrower also agrees promptly to notify the Collateral Agent if any material portion of the Collateral is damaged or destroyed.
(b) Each year, at the time of delivery of the certificate pursuant to paragraph (c) of Section 5.01, Level 3 shall deliver to the Collateral Agent certificates of an authorized officer of Level 3 (i) setting forth the information required pursuant to (A) the Annual Perfection Certificate and (B) until such time as the Collateral Permit Condition is satisfied with respect to Level 3 LLC, the Annual Loan Proceeds Note Perfection Certificate, or confirming that there has been no change in such information since the dates of the Effective Date Perfection Certificate or the Effective Date Loan Proceeds Note Perfection Certificate, as the case may be, or the date of the most recent certificates delivered pursuant to this Section and (ii) certifying that all Uniform Commercial Code financing statements (excluding fixture filings) or other appropriate filings, recordings or registrations, including all refilings, rerecordings and reregistrations, containing a description of the Collateral required to be set forth therein have been filed of record in each United States governmental, municipal or other appropriate office in each jurisdiction identified pursuant to clause (i) above to the extent necessary to perfect and continue the perfection of the security interests under the applicable Security Documents for a period of not less than 18 months after the date of such certificate (except as noted therein with respect to any continuation statements to be filed within such period).
Class Data Not later than 15 days after the Court grants Preliminary Approval of the Settlement, Defendant will simultaneously deliver the Class Data to the Administrator, in the form of a Microsoft Excel spreadsheet. To protect Class Members’ privacy rights, the Administrator must maintain the Class Data in confidence, use the Class Data only for purposes of this Settlement and for no other purpose, and restrict access to the Class Data to Administrator employees who need access to the Class Data to effect and perform under this Agreement. Defendant has a continuing duty to immediately notify Class Counsel if it discovers that the Class Data omitted class member identifying information and to provide corrected or updated Class Data as soon as reasonably feasible. Without any extension of the deadline by which Defendant must send the Class Data to the Administrator, the Parties and their counsel will expeditiously use best efforts, in good faith, to reconstruct or otherwise resolve any issues related to missing or omitted Class Data.
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Customer Data 5.1 The Customer shall own all rights, 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.
5.2 The Supplier shall follow its archiving procedures for Customer Data as set out in its Back-Up Policy available at XxxxxXXX.xxx or such other website address as may be notified to the Customer as such document may be amended by the Supplier in its sole discretion from time to time the current version of which is set out at Schedule 3 of this Agreement. In the event of any loss or damage to Customer Data, the Customer's sole and exclusive remedy shall be for the Supplier to use reasonable commercial endeavours to restore the lost or damaged Customer Data from the latest back-up of such Customer Data maintained by the Supplier in accordance with the archiving procedure described in its Back-Up Policy. The Supplier shall not be responsible for any loss, destruction, alteration or disclosure of Customer Data caused by any third party (except those third parties sub-contracted by the Supplier to perform services related to Customer Data maintenance and back-up).
5.3 The Supplier shall, in providing the Services, comply with its Privacy and Security Policy as such document may be amended from time to time by the Supplier in its sole discretion.
5.4 If the Supplier processes any personal data on the Customer’s behalf when performing its obligations under this agreement, the parties record their intention that the Customer shall be the data controller and the Supplier shall be a data processor and in any such case:
(a) the Customer shall ensure that the Customer is entitled to transfer the relevant personal data to the Supplier so that the Supplier may lawfully use, process and transfer the personal data in accordance with this agreement on the Customer's behalf;
(b) the Customer shall ensure that the relevant third parties have been informed of, and have given their consent to, such use, processing, and transfer as required by all applicable data protection legislation;
(c) the Supplier shall process the personal data only in accordance with the terms of this agreement and any lawful instructions reasonably given by the Customer from time to time; and
(d) each party shall take appropriate technical and organisational measures against unauthorised or unlawful processing of the personal data or its accidental loss, destruction or damage.
5.5 The Supplier and the Customer shall comply with their respective obligations as set out in Schedule 4 of this Agreement
Product Data Illustrations, standard schedules, performance charts, instructions, brochures, diagrams, and other information furnished by Developer to illustrate a material, product, or system for some portion of the Work.
Market Data Zero Hash may make certain information and research data, including historical market information available to you through the Platform or Zero Hash System, as applicable (“Market Data”). Market Data may be provided through third-party providers and may be updated at different time intervals, and accordingly, quotes, news, research data, market information and the various trade status reports, including intraday updates of balances and positions information and may differ due to the different Market Data and sources and their update intervals. Any such Market Data is provided as-is and for informational purposes only. Zero Hash makes no representation as to the accuracy or completeness of any Market Data. Further, Market Data may represent aggregated data from across multiple third-party trading venues and does not necessarily represent the prices of any asset as made available by Zero Hash or ZH Liquidity. Your reliance on any Market Data is at your sole discretion. The provision of Market Data relating to any asset shall not be considered Zero Hash’s, or its affiliates, endorsement of any such asset. You understand and agree that past performance of any asset is not indicative of future performance. You shall not decompile or redistribute any Market Data.
CONTRACT DATA The Consultant is advised to read the NEC3 Professional Service Contract (Third edition with amendments of June 2006 and April 2013) and the relevant Guidance Notes and Flow Charts, published by the Institution of Civil Engineers, in order to understand the implications of this Data which is required. Copies of these documents may be obtained from the Engineering Contract Strategies (telephone (00) 000 000 0000). Each item of data given below is cross-referenced to the clause in the NEC3 Professional Service Contract to which it mainly applies.
