SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Performing Agency by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Performing Agency in the course of providing data processing services in connection with Performing Agency’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
Agency Disclosure Auctioneer and all licenses employed by or associated with auctioneer represent the Seller in the sale of these properties. DISCLAIMERS: SAMPLE
Agency Shop It is mutually agreed by the parties that this Unit is an agency shop Unit. It is the intent of the parties that the agency shop provisions in the Memorandum of Understanding comply with applicable state law (Government Code Section 3502.5).
Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, VarTec 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.
Processing of Deposit files The use of compression is recommended in order to reduce electronic data transfer times, and storage capacity requirements. Data encryption will be used to ensure the privacy of registry escrow data. Files processed for compression and encryption will be in the binary OpenPGP format as per OpenPGP Message Format -‐ RFC 4880, see Part A, Section 9, reference 3 of this Specification. Acceptable algorithms for Public-‐key cryptography, Symmetric-‐key cryptography, Hash and Compression are those enumerated in XXX 0000, not marked as deprecated in OpenPGP IANA Registry, see Part A, Section 9, reference 4 of this Specification, that are also royalty-‐free. The process to follow for the data file in original text format is: