1. DEFINITIONS
“Errors” shall have the meaning ascribed to it in Section 3.b) below.
“Package” shall have the meaning ascribed to it in Section 2.a) below. For greater certainty, a Package may consist of one document uploaded that contains twelve financial statements, or up to twelve individual documents containing monthly financial statements through Flinks Connect.
Unless otherwise defined herein, all capitalized terms carry the definitions ascribed to them in the Master Terms, or Order Form, as applicable.
2. UPLOAD SERVICE
Pursuant to the Flinks Master Terms and Conditions set forth at https://flinks.com/terms-conditions, and the applicable Order Form between Flinks and Client, Flinks shall provide Client with the following Service:
a) The Upload Service will allow Client’s End-Customers to upload their financial document(s), that are in a portable document format (i.e., .pdf) or acceptable scanned image format (e.g., .png, .jpeg) through Flinks Connect, which Flinks shall thereafter Process to derive certain standardized insights on such financial document(s) through the use of a Flinks optical character recognition and data-refining tool, and provide those insights back to Client. An End-Customer may upload a maximum of twelve (12) months of financial documents per account, per financial institution (collectively, a “Package”).
b) The Upload Service does not include the Processing of file formats that are machine-readable by default (e.g., .csv, .xls, .json); these file formats are subject to pricing under Flinks’ Enrichment Service.
c) The above Services do not include any professional, technical, consulting or integration services.
3. SERVICE TERMS
a) Operational Metrics
Connection Method Availability and Flinks Connect Availability are monitored on a 24/7 basis and assessed on a monthly basis. Flinks commits to deploy its best efforts to ensure 99% Connection Method Availability and Flinks Connect Availability, excluding Scheduled Maintenance, Emergency Maintenance and any Data Source malfunction outside of Flinks’ control.
b) Technical Support
In the event that any bugs, defects, delays, hindrances, or other errors (collectively, “Errors”) occur, Client will report to Flinks the Error in accordance with the Severity Levels (to be reasonably determined by Client) as set forth in Schedule A hereto. Flinks commits to deploy its best efforts to respond to an Error, depending on the Severity Level, within the time frames set forth in Schedule A entitled “Schedule A – Support”, starting from the time Client notifies Flinks of the Error.
SCHEDULE A – SUPPORT
Technical support times for the Service described in this Service Schedule are as follows during the Term: