Limitations to Database Access Sample Clauses

Limitations to Database Access 
AutoNDA by SimpleDocs

Related to Limitations to Database Access

  • Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.

  • Investment; Access to Data The undersigned has carefully reviewed and understands the risks of, and other considerations relating to, a purchase of the Common Stock and an investment in the Company. The undersigned has been furnished materials relating to the Company, the private placement of the Common Stock or anything else that it has requested and has been afforded the opportunity to ask questions and receive answers concerning the terms and conditions of the offering and obtain any additional information which the Company possesses or can acquire without unreasonable effort or expense. Representatives of the Company have answered all inquiries that the undersigned has made of them concerning the Company, or any other matters relating to the formation and operation of the Company and the offering and sale of the Common Stock. The undersigned has not been furnished any offering literature other than the materials that the Company may have provided at the request of the undersigned; and the undersigned has relied only on such information furnished or made available to the undersigned by the Company as described in this Section. The undersigned is acquiring the Shares for investment for the undersigned's own account, not as a nominee or agent and not with the view to, or for resale in connection with, any distribution thereof. The undersigned acknowledges that the Company is a start-up company with no current operations, assets or operating history, which may possibly cause a loss of Purchaser’s entire investment in the Company.

  • Information Access and Audit Rights 25.1 Information Access 25.2 Reporting of Non-Force Majeure Events 25.3 Audit Rights 25.3.1 25.3.2 25.4 Audit Rights Periods 25.4.1 Audit Rights Period for Construction-Related Accounts and Records 25.4.2 Audit Rights Period for All Other Accounts and Records 25.5 Audit Results 25.5.1 26.1 General 26.2 Responsibility of Principal 26.3 No Limitation by Insurance

  • Geographic Area and Sector Specific Allowances, Conditions and Exceptions The following allowances and conditions shall apply where relevant. Where the Employer does work which falls under the following headings, the Employer agrees to pay and observe the relevant respective conditions and/or exceptions set out below in each case.

  • Access to Personal Information by Subcontractors Supplier agrees to require any subcontractors or agents to which it discloses Personal Information under this Agreement or under any SOW to provide reasonable assurance, evidenced by written contract, that they will comply with the same or substantially similar confidentiality, privacy and security obligations with respect to such Personal Information as apply to Supplier under this Agreement or any SOW. Supplier shall confirm in writing to DXC that such contract is in place as a condition to DXC’s approval of use of a subcontractor in connection with any SOW. Upon request of DXC, Supplier will provide to DXC a copy of the subcontract or an extract of the relevant clauses. Supplier shall ensure that any failure on the part of any subcontractor or agent to comply with the Supplier obligations under this Agreement or any SOW shall be grounds to promptly terminate such subcontractor or agent. If during the term of this Agreement or any SOW, DXC determines, in its exclusive discretion, that any Supplier subcontractor or agent cannot comply with the Supplier obligations under this Agreement or with any SOW, then DXC may terminate this Agreement in whole or in part (with respect to any SOW for which such subcontractor or agent is providing services), if not cured by Supplier within the time prescribed in the notice of such deficiency.

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

  • Protection of Customer Data The Supplier shall not delete or remove any proprietary notices contained within or relating to the Customer Data. The Supplier shall not store, copy, disclose, or use the Customer Data except as necessary for the performance by the Supplier of its obligations under this Call Off Contract or as otherwise Approved by the Customer. To the extent that the Customer Data is held and/or Processed by the Supplier, the Supplier shall supply that Customer Data to the Customer as requested by the Customer and in the format (if any) specified by the Customer in the Call Off Order Form and, in any event, as specified by the Customer from time to time in writing. The Supplier shall take responsibility for preserving the integrity of Customer Data and preventing the corruption or loss of Customer Data. The Supplier shall perform secure back-ups of all Customer Data and shall ensure that up-to-date back-ups are stored off-site at an Approved location in accordance with any BCDR Plan or otherwise. The Supplier shall ensure that such back-ups are available to the Customer (or to such other person as the Customer may direct) at all times upon request and are delivered to the Customer at no less than six (6) Monthly intervals (or such other intervals as may be agreed in writing between the Parties). The Supplier shall ensure that any system on which the Supplier holds any Customer Data, including back-up data, is a secure system that complies with the Security Policy and the Security Management Plan (if any). If at any time the Supplier suspects or has reason to believe that the Customer Data is corrupted, lost or sufficiently degraded in any way for any reason, then the Supplier shall notify the Customer immediately and inform the Customer of the remedial action the Supplier proposes to take. If the Customer Data is corrupted, lost or sufficiently degraded as a result of a Default so as to be unusable, the Supplier may: require the Supplier (at the Supplier's expense) to restore or procure the restoration of Customer Data to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer, and the Supplier shall do so as soon as practicable but not later than five (5) Working Days from the date of receipt of the Customer’s notice; and/or itself restore or procure the restoration of Customer Data, and shall be repaid by the Supplier any reasonable expenses incurred in doing so to the extent and in accordance with the requirements specified in Call Off Schedule 8 (Business Continuity and Disaster Recovery) or as otherwise required by the Customer.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Definition of Customer Information Any Customer Information will remain the sole and exclusive property of the Trust. “Customer Information” shall mean all non-public, personally identifiable information as defined by Xxxxx-Xxxxx-Xxxxxx Act of 1999, as amended, and its implementing regulations (e.g., SEC Regulation S-P and Federal Reserve Board Regulation P) (collectively, the “GLB Act”).

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