Customer Data Backup File During the Term Sample Clauses

Customer Data Backup File During the Term. During the Term, Customer may request and GR8 People will provide to Customer, no more than once per month, a copy of the Customer Data that has been uploaded or otherwise saved to the Subscription Service database for the current administrative fee of five-hundred dollars ($500 USD) per database per extraction, provided, however that GR8 People reserves the right to change such fee in its sole discretion upon thirty (30) days’ notice to Customer.
AutoNDA by SimpleDocs
Customer Data Backup File During the Term. During the Term, Customer may request and SilkRoad will provide to Customer, no more than once per month, a complete copy of
Customer Data Backup File During the Term. During the Term, Customer may request and SilkRoad will provide to Customer, no more than once per month, a complete copy of the Customer Data that resides in the Hosted Service database for the current administrative fee of five‐hundred dollars ($500 USD) per database per extraction, which may be chargeable via the Channel Partner. Schedule AService Level Agreement

Related to Customer Data Backup File During the Term

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

  • Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.

  • Database File The Servicer will provide the Successor Servicer with a magnetic tape (in a format reasonably acceptable to the Indenture Trustee and the Servicer) containing the database file for each Contract (i) as of the Initial Cutoff Date, (ii) the Subsequent Cutoff Date, (iii) thereafter, as of the last day of the preceding Due Period on each Determination Date prior to a Service Transfer and (iv) on and as of the Business Day before the actual commencement of servicing functions by the Successor Servicer following the occurrence of a Service Transfer.

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

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

  • Client Records 25.2.1 CONTRACTOR shall prepare and maintain accurate and 26 complete records of clients served and dates and type of services provided 27 under the terms of this Agreement in a form acceptable to ADMINISTRATOR.

  • Information Regarding the Collateral (a) Furnish to the Administrative Agent at least fifteen (15) days (or such shorter period as the Administrative Agent may agree) prior written notice of any change in: (i) any Loan Party’s legal name; (ii) the location of any Loan Party’s chief executive office, its principal place of business, any office in which it maintains books or records relating to Collateral owned by it or any office or facility at which Collateral owned by it is located (including the establishment of any such new office or facility, but excluding in-transit Collateral); (iii) any Loan Party’s organizational structure or jurisdiction of incorporation or formation; or (iv) any Loan Party’s Federal Taxpayer Identification Number or organizational identification number assigned to it by its state of organization. The Loan Parties shall not effect or permit any change referred to in the preceding sentence unless the Loan Parties have undertaken all such action, if any, reasonably requested by the Administrative Agent under the UCC or otherwise that is required in order for the Collateral Agent to continue at all times following such change to have a valid, legal and perfected first priority security interest in all the Collateral for its own benefit and the benefit of the other Credit Parties. (b) From time to time as may be reasonably requested by the Administrative Agent, the Lead Borrower shall supplement each Schedule hereto, or any representation herein or in any other Loan Document, with respect to any matter arising after the Restatement Effective Date that is required to be set forth or described in such Schedule or as an exception to such representation or that is necessary to correct any information in such Schedule or representation which has been rendered inaccurate thereby (and, in the case of any supplements to any Schedule, such Schedule shall be appropriately marked to show the changes made therein). Notwithstanding the foregoing, no supplement or revision to any Schedule or representation shall be deemed the Credit Parties’ consent to the matters reflected in such updated Schedules or revised representations nor permit the Loan Parties to undertake any actions otherwise prohibited hereunder or fail to undertake any action required hereunder from the restrictions and requirements in existence prior to the delivery of such updated Schedules or such revision of a representation; nor shall any such supplement or revision to any Schedule or representation be deemed the Credit Parties’ waiver of any Default resulting from the matters disclosed therein.

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

  • 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

  • Receivable Files Complete There exists a Receivable File pertaining to each Receivable. Related documentation concerning the Receivable, including any documentation regarding modifications of the Contract, will be maintained electronically by the Servicer in accordance with customary policies and procedures. With respect to any Receivables that are tangible chattel paper, the complete Receivable File for each Receivable currently is in the possession of the Custodian.

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