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.
Use of Past Record In imposing any discipline on a current charge, Management will not take into account any prior infractions which occurred more than one (1) year previously nor impose discipline on an employee for falsification of the employee's employment application after a period of one (1) year from the employee's date of hire.
Use of Customer Statements The Contractor shall not use any statement attributable to the Customer or its employees for the Contractor’s promotions, press releases, publicity releases, marketing, corporate communications, or other similar communications, without first notifying the Customer’s Contract Manager and securing the Customer’s prior written consent.
Use of Project Issuer does hereby covenant and agree that it will not take any action during the term of this Agreement, other than pursuant to Article IX of this Agreement or Article IX of the Indenture, to interfere with Company's ownership of the Project or to prevent Company from having possession, custody, use and enjoyment of the Project.
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.
No Unauthorized Use of Prospectus The Company has not distributed and, prior to the later to occur of (i) the Closing Time and (ii) completion of the distribution of the Securities, will not distribute any prospectus (as such term is defined in the 1933 Act and the 1933 Act Regulations) in connection with the offering and sale of the Securities other than the Registration Statement, any preliminary prospectus, the Prospectus or other materials, if any, permitted by the 1933 Act or by the 1933 Act Regulations and approved by the Representatives.
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.
Use of Summary Prospectuses (i) The Company shall ensure that an Initial Summary Prospectus is used for each currently offered Variable Contract described under the related registration statement, in accordance with paragraph (j)(1)(i) of Rule 498A.
Identification of Data a. All Background, Third Party Proprietary and Controlled Government Data provided by Disclosing Party shall be identified in the Annex under which it will be provided. b. NASA software and related Data provided to Partner shall be identified in the Annex under which it will be used. Notwithstanding H.4., Software and related Data will be provided to Partner under a separate Software Usage Agreement (SUA). Partner shall use and protect the related Data in accordance with this Article. Unless the SUA authorizes retention, or Partner enters into a license under 37 C.F.R. Part 404, the related Data shall be disposed of as instructed by NASA.
Use of Proceeds The Company will use the net proceeds received by it from the sale of the Securities in the manner specified in the Prospectus under “Use of Proceeds.”