Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, MyLineToo 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.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:
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.
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C.
9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.
How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.
Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.
Customer Data 8.1 You, not bookinglab or JRNI, have sole responsibility for the entry, deletion, correction, accuracy, quality, integrity, legality, reliability, appropriateness, and right to use the Customer Data. bookinglab and JRNI is not responsible for any of the foregoing or for any destruction, damage, loss, or failure to store any Customer Data beyond its reasonable control or resulting from any failure in data transmission or operation of the Booking Service by you.
8.2 As of the MSA Start Date, JRNI is certified under ISO 27001 and shall maintain an information security program for the Services that complies with the ISO 27001 standards or such other standards as are substantially equivalent to ISO 27001.
8.3 If JRNI and/or bookinglab processes any Personal Data on your behalf when performing its obligations under this Agreement, the Parties acknowledge that you shall be the Data Controller and JRNI and/or bookinglab shall be a Data Processor and in any such case:
(a) you shall ensure that you are entitled to transfer the relevant Customer Personal Data to JRNI and/or bookinglab so that they may lawfully use, process and transfer the Customer Personal Data in accordance with this Agreement on your behalf;
(b) you 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 Laws;
(c) 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; and
(d) notwithstanding any other provision of this Agreement, but subject always to Appendix B(1) Data Protection and B(2) Data Processing Activities, nothing shall prevent JRNI or bookinglab from disclosing Customer Personal Data or Customer Data to their Group Companies, Affiliates and third party service providers as necessary to provide the Services in accordance with clause 3, and otherwise in order to comply with Applicable Law or at the request of a governmental, regulatory or supervisory authority.
8.4 From the MSA Start Date the Parties shall comply with Appendix B(1) Data Protection and Appendix B(2) Data Processing Activities
8.5 ensure that Customer Data and Personal Data deemed as a special category of Data under GDPR is not given to us in any form unless pre-agreed by us in writing
8.6 You are solely responsible and liable for any transfer of Customer Data made by you (or made by JRNI or bookinglab at your request) from the Booking Service to a third party and for ensuring that such transfer is in compliance with the Parties' obligations under the Data Protection Laws.
COMPUTER GRAPHICS FILES The Engineer agrees to comply with Attachment G, Computer Graphics Files for Document and Information Exchange, if determined by the State to be applicable to this contract.
Books, Records and Regulatory Filings (a) The Sub-Adviser agrees to maintain and to preserve for the applicable periods any such records as are required to be maintained by the Sub-Adviser with respect to the Fund by the 1940 Act and rules adopted thereunder, and by any other applicable laws, rules and regulations. The Sub-Adviser further agrees that all records that it maintains for the Fund are the property of the Fund and it will promptly surrender any of such records upon request; provided, however, that the Sub-Adviser may retain copies of such records for the applicable periods they are required by law to be retained, and thereafter shall destroy such records.
(b) The Sub-Adviser agrees that it shall furnish to regulatory authorities having the requisite authority any information or reports in connection with its services hereunder that may be requested in order to determine whether the operations of the Fund are being conducted in accordance with applicable laws, rules and regulations.
(c) The Sub-Adviser shall make all filings with the SEC required of it pursuant to Section 13 of the 1934 Act with respect to its duties as are set forth herein. The Sub-Adviser also shall make all required filings on Schedule 13D or 13G and Form 13F (as well as other filings triggered by ownership in securities under other applicable laws, rules and regulations) in respect of the Portfolio as may be required of the Fund due to the activities of the Sub-Adviser. The Sub-Adviser shall be the sole filer of Form 13F with respect to the Portfolio of the Fund.
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.
