General Terms and Conditions

1. TERMS AND DEFINITIONS

1. Account Details is the set of technical data attributes on the Customer which is obligatory to be stored by the Contractor and is used for Service rendering.
2. Agreement is the contract between the Customer and the Contractor for services rendering and/or software license provision.
3. Authentication Data is a set of non-personal data fields collected from Customer’s web- recourse and/or provided directly by the Customer including technical information about the device by which the User made the transition to the web site through the Internet; information about the
   User's actions on the web site and some other data attributes defined within the technical format.
4. Customer E-Mail Address (Customer E-Mail, E-Mail) is the email address, or the number of email addresses specified in the Agreement for respective information and notification purposes.
5. Data Policy is the public document, owned and managed by the Contractor, and describing the Contractors’ policy in respect of personal and user data processing. The most recent version of the mentioned document is available at https://jcsc.tech/en/privacy.
6. Effective Date is the date of Agreement signing by the Parties designated in the Agreement.
7. Minimum Validity Period is a period of 6 (six) month starting from the first Reporting Period, unless otherwise indicated in the Agreement.
8. Personal Account is a functionality within the secured part of the Services which is created for the Customer by the Contractor and allows receiving various technical information, statistics, and monitoring requests processing.
9. Product (or Web-Resource) is a web-resource and/or mobile application of the Customer or the Customer’s affiliates which is the subject of the Services, and which is used by Users to fulfill applications for financial products or other types of non-financial products and services.
10. Regular Maintenance (Technical) Works is a set of mandatory actions that the Contractor periodically runs during the term of the Agreement.
11. Reporting Period is a one calendar month period of Service rendering. The first Reporting Period shall be considered as the period from the date when the Contractor received the working (operation) Request until the last day of the first Reporting period, and the last Reporting period is the period from the beginning of the last month of service rendering / software license provision till the expiry date or termination of the Agreement.
12. Request (or Enquiry) is the set of Authentication data defined within the technical format that the Customer sends to the Contractor using Account details.
13. Request Response is a set of the resulting information provided within the technical format as the result of Authentication data processing. Request Response includes the number of device identifiers, score and vector of output attributes within the technical format. The set of data included in the Request Response depends on the package of Services rendering chosen by the Customer and specified in the Agreement.
14. Script (Data Collecting Script, JavaScript, SDK) is a reserved program code; this code is a mandatory component of the Services and is installed into Customer’s infrastructure for Service rendering.
15. Services are the information services rendered within the format described in the Technical Documentation and used to assess and evaluate credit risk, fraud risk or other type of risk on the applications for products based on device and virtual user behavior analysis; the data processed within the Services does NOT contain any types of direct consumer identifiers which may lead to unambiguous physical person identification. Services rendering includes the following stages: receiving Requests from the Customer, Requests processing and analysis, building Request Response and its provision to the Customer.
16. System (or Technological System) is a set of infrastructure components, server equipment, hardware and software tools ensuring Services provision for the Customer.
17. System Failure (or System Malfunctioning) is a set of circumstances that led to the failure of the System or to System Malfunctioning for more than 120 minutes, whereby the Contractor cannot provide the Customer with the Service or ensure the Properly Functioning of the System.
18. System Properly Functioning (or Properly Functioning): the System and corresponding services are considering properly functioning and properly provided if response time to the Request is not exceeding 30 seconds for 99% of Requests for any consecutive 720 hours with at least 1000 consecutive Requests.
19. Technical Documentation is the package of electronic documents which contain technical requirements for Parties infrastructure and software, service description, technical formats, input and output data vectors and other information needed for Services rendering.
20. User (or Virtual User) is an individual who intends to conclude an agreement for a loan, insurance policy or other type of financial or non-financial product or services with the Customer through the web-site or mobile application and whose Authentication data, if necessary, the Customer transfers to the Contractor for the provision of services according to the Contract terms.