Acrobat Sample Clauses

Acrobat. The On-premise Software may include technology that allows Customer to enable certain features of PDF documents through the use of digital credentials (“Key”). Customer may not access, attempt to access, control, disable, remove, use, or distribute the Key for any purpose. Digital certificates may be issued by third party certificate authorities, or can be self-signed. Customer is solely responsible for deciding whether or not to rely on a certificate and for the purchase, use, and reliance upon digital certificates.
AutoNDA by SimpleDocs

Related to Acrobat

  • pdf The vendor must download the Vendor Agreement from the attachment tab, fill in the requested information and upload the completed agreement. DO NOT UPLOAD encrypted or password protected files.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Encryption The Fund acknowledges and agrees that encryption may not be available for every communication through the System, or for all data. The Fund agrees that Custodian may deactivate any encryption features at any time, without notice or liability to the Fund, for the purpose of maintaining, repairing or troubleshooting the System or the Software.

  • Workstation Encryption Supplier will require hard disk encryption of at least 256-bit Advanced Encryption Standard (AES) on all workstations and/or laptops used by Personnel where such Personnel are accessing or processing Accenture Data.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Counterparts; Facsimile Signature This Agreement may be executed by facsimile signature and in any number of counterparts, each of which shall be an original but all of which together shall constitute one and the same instrument.

  • Format The data will be provided in the format specified in Specification 2 for Data Escrow (including encryption, signing, etc.) but including only the fields mentioned in the previous section, i.e., the file will only contain Domain and Registrar objects with the fields mentioned above. Registry Operator has the option to provide a full deposit file instead as specified in Specification 2.

  • COUNTERPARTS; FACSIMILE/E-SIGNATURES This Settlement Agreement may be executed in counterparts and by facsimile or e- signatures, each of which shall be deemed an original, and all of which, when taken together, shall constitute one and the same document.

  • Facsimile Signatures The facsimile signature of any party to this Agreement shall constitute the valid and binding execution hereof by such party.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

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