Yoti IDV specific terms Sample Clauses

Yoti IDV specific terms. 2.1. If using IDV SDK or a direct API, you must display on all Yoti IDV screens the phrase “powered by Yoti” and the Yoti logo reasonably prominently to Individuals, unless otherwise agreed by Yoti. If using the IDV Portal you must not amend or remove the Yoti branding.
AutoNDA by SimpleDocs

Related to Yoti IDV specific terms

  • Product Specific Terms these terms apply to specific Products referenced in this section.

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

  • Specific Terms Whenever used in this Agreement, the following words and phrases, unless the context otherwise requires, shall have the following meanings:

  • CLOUD SPECIFIC TERMS AND CONDITIONS To the extent that Contractor has received an award for Lot 3, Cloud, the following terms and conditions apply to Lot 3, Cloud. For the duration of an Authorized User Agreement, the Cloud Solution shall conform to the Cloud Solution Manufacturer’s specifications, Documentation, performance standards (including applicable license duration, warranties, guarantees, Service Level Agreements, service commitments, and credits). PROTECTION OF DATA, INFRASTRUCTURE AND SOFTWARE Contractor is responsible for providing physical and logical security for all Data, infrastructure (e.g. hardware, networking components, physical devices), and software related to the services the Contractor is providing under the Authorized User Agreement. All Data security provisions agreed to by the Authorized User and Contractor within the Authorized User Agreement may not be diminished for the duration of the Authorized User Agreement without prior written agreement by the parties amending the Authorized User Agreement.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Vendor’s Specific Warranties, Terms, and License Agreements Because TIPS serves public entities and non-profits throughout the nation all of which are subject to specific laws and policies of their jurisdiction, as a matter of standard practice, TIPS does not typically accept a Vendor’s specific “Sale Terms” (warranties, license agreements, master agreements, terms and conditions, etc.) on behalf of all TIPS Members. TIPS may permit Vendor to attach those to this Agreement to display to interested customers what terms may apply to their Supplemental Agreement with Vendor (if submitted by Vendor for that purpose). However, unless this term of the Agreement is negotiated and modified to state otherwise, those specific Sale Terms are not accepted by TIPS on behalf of all TIPS Members and each Member may choose whether to accept, negotiate, or reject those specific Sale Terms, which must be reflected in a separate agreement between Vendor and the Member in order to be effective.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Country-Specific Provisions The Award shall be subject to any special provisions set forth in Exhibit A for your country, if any. If you relocate to one of the countries included in Exhibit A during the life of the Award or while holding Shares acquired upon vesting of the Restricted Share Units, the special provisions for such country shall apply to you, to the extent the Company determines that the application of such provisions is necessary or advisable in order to comply with applicable laws with regard to the acquisition, issuance or sale of the Shares or facilitate the administration of the Plan. Exhibit A constitutes part of this Agreement.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.

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