HARD DRIVE SECURITY Sample Clauses

HARD DRIVE SECURITY. Vendor must properly format the hard drive, deleting all information, or replace the hard drive with a new hard drive prior to storing or re-selling the equipment. The Customer may request to retain the hard drive for a nominal fee. Vendor will supply written notification to the Customer that all data has been made inaccessible. This notification must be provided with forty-five (45) days of the equipment being returned to the Vendor.
AutoNDA by SimpleDocs
HARD DRIVE SECURITY. If ‘bizhub SECURE’ or a comparable option has been ordered, KMBS will provide advanced security Services at a fee. These Services include real-time hard-drive encryption (level 2 encryption – equivalent to current Department of Defense standards and US Air Force standards) and document data security through disk over-write as well as user mailbox data deletion, HDD encryption, HDD lock and administrative password (according to customer policy). At the Customers request, for an additional fee KMBS shall return the hard drive to the Customer for disposal. A replacement hard drive will be installed and re-initialized with the generic device control programs. Additional Services are subject to hourly fees plus the cost to replace the Hard Drive (availability of options depends on model and configuration).

Related to HARD DRIVE SECURITY

  • NOTE For Community-­‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-­‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]

Time is Money Join Law Insider Premium to draft better contracts faster.