Secure Files Containers. A secure files container includes any filing equipment that can be locked during non-duty hours (e.g., Power Files and Lektrievers, filing cabinets and shelf units).
Secure Files Containers Sample Clauses
Related to Secure Files Containers
Quality control records and Documents The Contractor shall hand over a copy of all its quality control records and documents to the Authority’s Engineer before the Completion Certificate is issued pursuant to Clause 12.2. The Contractor shall submit Road Signage Plans to the Authority Engineer for approval at least 6 (six) months prior to expected completion of Project Highway.
Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:
DOCUMENTATION; RECORDS OF PROCESSING Each party is responsible for its compliance with its documentation requirements, in particular maintaining records of processing where required under Data Protection Law. Each party shall reasonably assist the other party in its documentation requirements, including providing the information the other party needs from it in a manner reasonably requested by the other party (such as using an electronic system), in order to enable the other party to comply with any obligations relating to maintaining records of processing.
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:
Operator’s Security Contact Information Xxxxxxx X. Xxxxxxx Named Security Contact xxxxxxxx@xxxxxxxxx.xxx Email of Security Contact (000) 000-0000 Phone Number of Security Contact
Files and Records A. An employee will have the right to review the contents of files concerning the employee, excluding initial references of the district pertaining to said employee or other items statutorily exempt from disclosure originating after initial employment, and to have a representative of the Association accompany him/her in such a review.
Telephone Monitoring/Recording From time to time we may monitor and/or record telephone calls between you and us to assure the quality of our customer service or as required by applicable law.
Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts. Contractor shall maintain all Records, fiscal and otherwise, directly relating to this Contract in accordance with generally accepted accounting principles so as to document clearly Contractor's performance. Following final payment and termination of this Contract, Contractor shall retain and keep accessible all Records for a minimum of three years, or such longer period as may be required by law, or until the conclusion of any audit, controversy, or litigation arising out of or related to this Contract, whichever date is later.
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.
REMOVAL OF RECORDS FROM PREMISES Where performance of the Contract involves use by the Contractor (or the Contractor’s subsidiaries, affiliates, partners, agents or subcontractors) of Authorized User owned or licensed papers, files, computer disks or other electronic storage devices, data or records at Authorized User facilities or offices, or via remote access, the Contractor (or the Contractor’s subsidiaries, affiliates, partners, agents or subcontractors) shall not remotely access, modify, delete, copy or remove such Records without the prior written approval of the Authorized User. In no case, with or without the written approval of the Authorized User, can the Authorized User data be accessed, moved or sent outside the continental United States.
