Doc Scan specific Clause Samples

Doc Scan specific terms 2.1. You must display on all Doc Scan screens the phrase “powered by Yoti” reasonably prominently to Individuals, unless otherwise agreed by Yoti. 2.2. If we have agreed with you that you are using the Yoti App in addition to Doc Scan, it is a condition of this Agreement that you integrate and maintain throughout the Term the Yoti App in a prominent position alongside the Doc Scan product. If you fail to do so then we reserve the right to ▇▇▇▇ you for Doc Scan at the Pricing Schedule rates instead of any rate we have agreed with you. 2.3. Any biometric template received by you through Doc Scan must be deleted within three years of the initial purpose being satisfied or the last interaction with the user, whichever occurs first. You indemnify us against all losses (including damages, settlement costs, defending lawsuits and regulatory action against us) for any failure to comply with this requirement.
View Source

Related to Doc Scan specific

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-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.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Core Profession Specific Provide nationally consistent legal advice and management to support effective and lawful registration, notifications and compliance procedures, and hearing panels processes Profession-specific services, as listed in the National Board’s regulatory plan and annual budget.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.