DCC DATA Sample Clauses

DCC DATA. 18.1. The Contractor shall not at any time be entitled: 18.1.1 to copy, disclose or use any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement and to the extent strictly required to comply with its obligations under this Agreement; and 18.1.2 to store (or retain) any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement and to the extent strictly required to comply with any: 18.1.2.1 applicable Law of Scotland or England and Wales; or 18.1.2.2 express provisions of this Agreement that require the Contractor to retain such data on a non-persistent basis.
Sample 1Sample 2See All (5)
DCC DATA. ‌ The parties agree that as at the Signature Date, the provisions of clause 28.1 below do not apply to this agreement on the basis that the contractor will not receive either any transactional data or industry registration data in the performance of its services. In the event that a future requirement arises which means that the contractor will need to come into possession of either transactional data and / or industry registration data, then this clause 28.1 would become applicable once an appropriate Change Authorisation Note has been agreed between the parties for the requirement concerned. 28.1 The Contractor shall not at any time be entitled:‌ 28.1.1 to copy, disclose or use any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 30.8) and to the extent strictly required to comply with its obligations under this Agreement; and 28.1.2 to store (or retain) any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 30.8) and to the extent strictly required to comply with any: 28.1.2.1 applicable Law of Scotland or England and Wales; or 28.1.2.2 express provisions of this Agreement that require the Contractor to retain such data on a non-persistent basis. 28.2 The Contractor shall (and shall ensure all Contractor Persons shall) not (unless expressly agreed by the DCC in writing) delete or remove any proprietary notices contained within or relating to the DCC Data, Documentation or DCC Software. 28.3 Subject to the opening paragraph of the Clause 28 the Contractor shall comply with Clause 28.1 in all circumstances and in addition shall (and shall ensure all Contractor Persons shall) not store, copy, disclose, or use any DCC Data except as necessary for the performance by the Contractor of its obligations under this Agreement or as otherwise expressly authorised in writing by the DCC (whether in this Agreement or otherwise, including pursuant to Clauses 30.4 to 30.7 (inclusive), 30.11, 30.13, 30.14 or 30.16). 28.4 To the extent that any DCC Data is held and/or processed by or on behalf of the Contractor, the Contractor shall supply that DCC Data to the DCC as requested by the DCC from time to time. 28.5 Subject to Clause 34.10, the Contractor shall, at all times during the Service Period, preserve the integrity of all DCC Data, Contractor Systems Data and Contractor CMDB Da...
Sample 1Sample 2See All (4)
DCC DATA. ‌ 8.1. You shall not at any time be entitled (i) to copy, disclose or use any DCC Data except in compliance with all of your obligations under this Agreement and to the extent strictly required to comply with your obligations under this Agreement; and (ii) to store (or retain) any DCC Data except in compliance with your obligations under this Agreement and to the extent strictly required to comply with any applicable law of Scotland or England and Wales; or any express provisions of this Agreement that require you to retain such DCC Data. 8.2. You shall not (unless expressly agreed by the DCC in writing) delete or remove any proprietary notices contained within or relating to DCC Confidential Information, DCC Data, Deliverables or DCC IPR. 8.3. You shall, at all times when in your possession, preserve the integrity of all DCC Data (including preventing the loss, corruption, degradation or unauthorised access of such DCC Data) in accordance with any requirements set out in this Agreement or, if none, in accordance with Good Industry Practice. 8.4. You undertake to provide to the DCC copies of all DCC Data in your possession, custody or control on demand and, in any event, upon termination or expiry of this Agreement. You hereby agree to irrevocably delete DCC Data in your possession, custody or control on demand.
Sample 1Sample 2Sample 3
DCC DATA. 9.1 The Contractor shall not at any time be entitled: 9.1.1 to copy, disclose or use any DCC Data except in compliance with all the Contractor's obligations under this Agreement and to the extent strictly required to comply with its obligations under this Agreement; and 9.1.2 to store (or retain) any DCC Data except in compliance with the Contractor's obligations under this Agreement and to the extent strictly required to comply with any; (a) applicable law of Scotland or England and Wales; or (b) express provisions of this Agreement that require the Contractor to retain such data. 9.2 The Contractor shall not (unless expressly agreed by the DCC in writing) delete or remove any proprietary notices contained within or relating to the DCC Data, documentation or DCC Software. 9.3 The Contractor shall, at all times during the Term, preserve the integrity of all DCC Data (including preventing the loss, corruption or degradation of such DCC Data) in accordance with any requirements set out in the Schedule or, if none, in accordance with Good Industry Practice. 9.4 To the extent that any DCC Data is held and/or processed by or on behalf of the Contractor, the Contractor shall supply that DCC Data to the DCC as requested by the DCC from time to time. 9.5 The Contractor undertakes to provide to DCC copies of all DCC Data in its possession, custody or control on demand and, in any event, upon termination or expiry of this Agreement (whereupon such DCC Data shall be irrevocably deleted by the Contractor).
Sample 1
DCC DATA. 35.1 The Contractor shall not delete or remove any proprietary notices contained within or relating to the DCC Data. 35.2 The Contractor shall not store, copy, disclose, or use the DCC Data except as necessary for the performance by the Contractor of its obligations under this Agreement or as otherwise expressly authorised in writing by the DCC. 35.3 To the extent that DCC Data are held and/or processed by the Contractor, the Contractor shall, to the extent not expressly prohibited by Law, supply that DCC Data to the DCC as requested by the DCC in any format reasonably required by the DCC. 35.4 The Contractor shall, take all commercially reasonable measures, acting in accordance with Good Industry Practice and the applicable provisions of this Agreement, to preserve the integrity of DCC Data and prevent the corruption or loss of DCC Data at all times that the relevant DCC Data is under its control or the control of any Sub-contractor. 35.5 The Contractor shall ensure that any system on which the Contractor holds any DCC Data, including back-up data, is a system that complies with the Security Policy and the Security Management Plan. 35.6 If any of the DCC Data are corrupted, lost or sufficiently degraded as a result of the Contractor's breach of Clause 35.4 so as to be unusable, the DCC may:- 35.6.1 require the Contractor (at the Contractor's expense) to restore or procure the restoration of DCC Data and the Contractor shall do so as soon as practicable but not later than five (5) Business Days from the date of receipt of the DCC’s notice; and/or 35.6.2 itself restore or procure the restoration of DCC Data, and shall be repaid by the Contractor any reasonable expenses incurred in doing so. 35.7 The Contractor shall notify the DCC promptly if, at any time, the Contractor suspects or has reason to believe that DCC Data has or may become corrupted, lost or sufficiently degraded in any way for any reason and, the Contractor shall as soon as reasonably practicable (and in any event within five (5) Business Days) inform the DCC of the remedial action the Contractor proposes to take.
Sample 1
DCC DATA. 48.1 The Contractor shall not at any time be entitled: 48.1.1 to copy, disclose or use any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 50.8) and to the extent strictly required to comply with its obligations under this Agreement; and 48.1.2 to store (or retain) any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 50.8) and to the extent strictly required to comply with any:
Sample 1
AutoNDA by SimpleDocs
DCC DATA. 28.1 The Contractor shall not at any time be entitled: 28.1.1 to copy, disclose or use any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 30.8) and to the extent strictly required to comply with its obligations under this Agreement; and 28.1.2 to store (or retain) any Transactional Data or Industry Registration Data except in compliance with all the Contractor's obligations under this Agreement (including Clause 30.8) and to the extent strictly required to comply with any: 28.1.2.1 applicable Law of Scotland or England and Wales; or 28.1.2.2 express provisions of this Agreement that require the Contractor to retain such data on a non-persistent basis. 28.2 The Contractor shall (and shall ensure all Contractor Persons shall) not (unless expressly agreed by the DCC in writing) delete or remove any proprietary notices contained within or relating to the DCC Data, Documentation or DCC Software.
Sample 1

Related to DCC 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.

  • Exchange Control Information Exchange control reporting is required for cash transactions exceeding AUD10,000 and for international fund transfers. The Australian bank assisting with the transaction will file the report for you. If there is no Australian bank involved in the transfer, you will have to file the report.

  • 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.

  • Regulatory Materials (a) On a Program-by-Program basis, commencing on the Effective Date until the Regulatory Transfer Date, Prothena shall have the right, in consultation with Celgene, to prepare, file and maintain all Regulatory Materials (including any Regulatory Approvals) necessary for the Development and Manufacture of any Collaboration Candidates and Collaboration Products for such Program (collectively, the “Program Regulatory Materials”), and to interact with Regulatory Authorities in connection with the Development and Manufacture of any Collaboration Candidates and Collaboration Products for such Program. Prothena will provide Celgene with a reasonable opportunity to comment substantively on all material Regulatory Materials prior to filing or taking material action, and will reasonably and in good faith consider any comments and actions recommended by Celgene, including with respect to filing strategy. In addition, Prothena will allow Celgene or its representative to attend any and all meetings with Regulatory Authorities to the extent such attendance is not prohibited or limited by such Regulatory Authority. (b) If Celgene exercises its Phase 1 Portion Participation Right for a given Program, then immediately after such exercise, Prothena shall initiate the transfer of all Program Regulatory Materials, including for clarity any IND for the relevant Collaboration Candidates and/or Collaboration Products that are the subject of such Program to Celgene. The date on which such Program Regulatory Materials are transferred to Celgene shall be the “Regulatory Transfer Date” for such Program. Thereafter, Celgene shall have the right, in consultation with Prothena, to prepare, file, and maintain such Program Regulatory Materials, and to interact with Regulatory Authorities in connection with the Development and, as applicable, Manufacture of such Collaboration Candidates and Collaboration Products for such Program in accordance with the terms and conditions of Section 2.5. Additionally, with respect to any Phase 1 Clinical Trial conducted by Celgene pursuant to Section 2.5, Celgene will provide Prothena with a reasonable opportunity to comment substantively on all material Program Regulatory Materials prior to filing or taking material action, and will reasonably and in good faith consider any comments and actions recommended by Prothena, including with respect to filing strategy. In addition, with respect to any Phase 1 Clinical Trial conducted by Celgene pursuant to Section 2.5, Celgene will allow Prothena or its representative to attend any and all meetings with Regulatory Authorities to the extent such attendance is not prohibited or limited by such Regulatory Authority. For clarity, if the Regulatory Transfer Date does not occur prior to the expiration of the Option Term for such Program, Section 2.6.1(a) (and not this Section 2.6.1(b)) shall apply.

  • 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.

  • Background Data The Disclosing Party's Background Data, if any, will be identified in a separate technical document.

  • Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.

  • Regulatory Filing In the event that this Interconnection Service Agreement contains any terms that deviate materially from the form included in Attachment O of the Tariff, Transmission Provider shall file the Interconnection Service Agreement on behalf of itself and the Interconnected Transmission Owner with FERC as a service schedule under the Tariff within thirty days after execution. Interconnection Customer may request that any information so provided be subject to the confidentiality provisions of Section 17 of this Appendix 2. An Interconnection Customer shall have the right, with respect to any Interconnection Service Agreement tendered to it, to request (a) dispute resolution under Section 12 of the Tariff or, if concerning the Regional Transmission Expansion Plan, consistent with Schedule 5 of the Operating Agreement, or (b) that Transmission Provider file the agreement unexecuted with the Commission. With the filing of any unexecuted Interconnection Service Agreement, Transmission Provider may, in its discretion, propose to FERC a resolution of any or all of the issues in dispute between or among the Interconnection Parties.

  • Regulatory Filings (a) Each of Parent and Acquisition Sub (and their respective Affiliates, if applicable), on the one hand, and the Company, on the other hand, shall (x) file with the FTC and the Antitrust Division of the DOJ a Notification and Report Form relating to this Agreement and the transactions contemplated hereby as required by the HSR Act as soon as reasonably practicable from the date following execution and delivery of this Agreement but in no event later than ten (10) Business Days following the execution and delivery of this Agreement, and (y) file comparable pre-merger or post-merger notification filings, forms and submissions with any foreign Governmental Authority that is required by any other Antitrust Laws as soon as reasonably practicable from the date following execution and delivery of this Agreement but in no event later than ten (10) Business Days following the execution and delivery of this Agreement. Each of Parent and the Company shall (i) cooperate and coordinate with the other in the making of such filings, (ii) supply the other with any information that may be required in order to make such filings, (iii) supply any additional information that reasonably may be required or requested by the FTC, the DOJ or the Governmental Authorities of any other jurisdiction in which any such filing is made under any other Antitrust Laws, and (iv) use reasonable best efforts to take all action necessary to cause the expiration or termination of the applicable waiting periods under the HSR Act or other Antitrust Laws as soon as practicable, and to obtain any required consents under any other Antitrust Laws applicable to the Offer and/or the Merger as soon as practicable, and to avoid any impediment to the consummation of the Offer or the Merger under any Antitrust Laws, including using reasonable best efforts to take all such action as reasonably may be necessary to resolve such objections, if any, as the FTC, the DOJ, or any other Governmental Authority or Person may assert under any applicable Antitrust Laws with respect to the Offer and/or the Merger. (b) Each of Parent and Acquisition Sub (and their respective Affiliates, if applicable), on the one hand, and the Company, on the other hand, shall promptly inform the other of any communication from any Governmental Authority regarding any of the transactions contemplated by this Agreement in connection with any filings or investigations with, by or before any Governmental Authority relating to this Agreement or the transactions contemplated hereby, including any proceedings initiated by a private party. If any party hereto or Affiliate thereof shall receive a request for additional information or documentary material from any Governmental Authority with respect to the transactions contemplated by this Agreement pursuant to the HSR or any other Antitrust Laws with respect to which any such filings have been made, then such party shall use its reasonable best efforts to make, or cause to be made, as soon as reasonably practicable and after consultation with the other party, an appropriate response in compliance with such request. In connection with and without limiting the foregoing, to the extent reasonably practicable and unless prohibited by applicable Law or by the applicable Governmental Authority, the parties hereto agree to (i) give each other reasonable advance notice of all meetings with any Governmental Authority relating to the Offer or the Merger, (ii) give each other an opportunity to participate in each of such meetings, (iii) keep the other party reasonably apprised with respect to any oral communications with any Governmental Authority regarding the Offer or the Merger, (iv) cooperate in the filing of any analyses, presentations, memoranda, briefs, arguments, opinions or other written communications explaining or defending the Offer and the Merger, articulating any regulatory or competitive argument and/or responding to requests or objections made by any Governmental Authority, (v) provide each other with a reasonable advance opportunity to review and comment upon, and consider in good faith the views of the other with respect to, all written communications (including any analyses, presentations, memoranda, briefs, arguments and opinions) with a Governmental Authority regarding the Offer and the Merger, (vi) provide each other (or counsel of each party, as appropriate) with copies of all written communications to or from any Governmental Authority relating to the Offer or the Merger, and (vii) cooperate and provide each other with a reasonable opportunity to participate in, and consider in good faith the views of the other with respect to, all material deliberations with respect to all efforts to satisfy the conditions set forth in clauses (A) and (C)(1) of Annex A and Section 9.1(c). Any such disclosures, rights to participate or provisions of information by one party to the other may be made on a counsel-only basis to the extent required under applicable Law or as appropriate to protect confidential business information or the attorney client privilege or attorney work product. (c) Each of Parent, Acquisition Sub and the Company shall cooperate with one another in good faith to (i) promptly determine whether any filings not contemplated by Section 8.2(a) are required to be or should be made, and whether any other consents, approvals, permits or authorizations not contemplated by Section 8.2(a) are required to be or should be obtained, from any Governmental Authority under any other applicable Law in connection with the transactions contemplated hereby, and (ii) promptly make any filings, furnish information required in connection therewith and seek to obtain timely any such consents, permits, authorizations, approvals or waivers that the parties determine are required to be or should be made or obtained in connection with the transactions contemplated hereby. (d) Notwithstanding anything to the contrary in this Agreement, in connection with any filing or submission required or action to be taken by either Parent or the Company to consummate the Offer and the Merger, in no event shall Parent or any of its Subsidiaries or Affiliates be obligated to propose or agree to accept any undertaking or condition, to enter into any consent decree, to make any divestiture or accept any operational restriction, or take or commit to take any action (i) the effectiveness or consummation of which is not conditional on the consummation of the Offer and the Merger or (ii) that individually or in the aggregate (x) is or would reasonably be expected to be materially adverse (with materiality, for purposes of this provision, being measured in relation to the size of the Company and its Subsidiaries taken as a whole) to (A) the Company and its Subsidiaries, taken as a whole, or Parent and its Subsidiaries, taken as a whole, either before or after giving effect to the Offer or the Merger, or (B) Parent’s ownership or operation of any material portion of the business or assets of the Company and its Subsidiaries, taken as a whole, or (y) would reasonably be expected to deny Parent the material benefit of the bargains contemplated by the transactions contemplated by this Agreement. The Company shall agree, if requested by Parent in writing, to commit to take any of the forgoing actions with respect to the assets or business of the Company in furtherance of this Section 8.2; provided, however, that any such action may be conditioned upon the consummation of the Merger and other Transactions contemplated by this Agreement.

  • Billing Information 6.1 NLT and the RL shall provide each other with information within their possession that is necessary to allow them to provide accurate and timely billing to each other and to any other relevant third parties.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!