Use of Data (a) In connection with the provision of the services and the discharge of its other obligations under this Agreement, State Street (which term for purposes of this Section XXIX includes each of its parent company, branches and affiliates (''Affiliates")) may collect and store information regarding a Trust and share such information with its Affiliates, agents and service providers in order and to the extent reasonably necessary (i) to carry out the provision of services contemplated under this Agreement and other agreements between the Trusts and State Street or any of its Affiliates and (ii) to carry out management of its businesses, including, but not limited to, financial and operational management and reporting, risk management, legal and regulatory compliance and client service management.
Disposition of Data Upon written request from the LEA, Provider shall dispose of or provide a mechanism for the LEA to transfer Student Data obtained under the Service Agreement, within sixty (60) days of the date of said request and according to a schedule and procedure as the Parties may reasonably agree. Upon termination of this DPA, if no written request from the LEA is received, Provider shall dispose of all Student Data after providing the LEA with reasonable prior notice. The duty to dispose of Student Data shall not extend to Student Data that had been De-Identified or placed in a separate student account pursuant to section II 3. The LEA may employ a “Directive for Disposition of Data” form, a copy of which is attached hereto as Exhibit “D”. If the LEA and Provider employ Exhibit “D,” no further written request or notice is required on the part of either party prior to the disposition of Student Data described in Exhibit “D.
Use of Data by User Registry Operator will permit user to use the zone file for lawful purposes; provided that (a) user takes all reasonable steps to protect against unauthorized access to and use and disclosure of the data and (b) under no circumstances will Registry Operator be required or permitted to allow user to use the data to, (i) allow, enable, or otherwise support the transmission by email, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than user’s own existing customers, or (ii) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator or any ICANN-‐accredited registrar.
Source of Data A description of (1) the process used to identify claims in the Population, and (2) the specific documentation relied upon by the IRO when performing the Quarterly Claims Review (e.g., medical records, physician orders, certificates of medical necessity, requisition forms, local medical review policies (including title and policy number), CMS program memoranda (including title and issuance number), Medicare contractor manual or bulletins (including issue and date), other policies, regulations, or directives).
Marking of Data Pursuant to Paragraph A above, any Data delivered under this Agreement shall be marked with the following legend: Use, duplication, or disclosure is subject to the restrictions as stated in Agreement HR0011-XX-9-XXXX between the Government and the Performer.
Storage of Data The Company agrees to store and process the School District Data in a manner that is no less protective than those methods used to secure the Company’s own data. The Company agrees that School District Data will be stored on equipment or systems located within the United States.
Consent to Use of Data You agree that the Licensor may collect and use technical data and related information, including but not limited to technical information about your device, system and application software, and peripherals, that is gathered periodically to facilitate the provision of software updates, product support and other services (if any) related to the Software. The Licensor may use this information, as long as it is in a form that does not personally identify you, to improve its products or to provide services or technologies.
Exchange of Data 67.7.1 To the extent technically feasible, the Parties involved in transporting Transit Traffic will deliver calls to each involved network with Common Channel Signaling (CCS)/Signaling System 7 (SS7) protocol and the appropriate ISUP/TCAP messages to facilitate full interoperability and billing functions. The Parties agree to send all message indicators received.
