Product Terms – Data Service
1. Introduction
1.1. These product terms apply whenever we agree to provide you with any of the following services:
1.1.1. the provision of CeFi data collection which includes data collection and normalization for all queries made during a period;
1.1.2. collection of Wallet and DeFi data which includes all blockchains and protocols supported by the Hash Data platform; and
1.1.3. Data consulting services, including but not limited to pulling data manually form protocols that we currently do not support in our tool.
together, the Data Services.
1.2. Definitions used and rules of interpretation set out in our General Terms available at hashdata.co are treated as incorporated into these product terms.
1.3. The Engagement Terms regarding Data Services are made up of:
1.3.1. an engagement letter or service agreement between you and us (the EL);
1.3.2. these product terms;
1.3.3. the Cayman Islands jurisdiction terms;
1.3.4. our General Terms and any document referred to in it that is not already mentioned in this Clause 1.3; and
1.3.5. any other document that expressly forms part of the Engagement
1.4. If there is any conflict or ambiguity between those various parts of the Engagement Terms, a term contained in a document higher in the list above has priority over a term contained in a document lower in that
1.5. We may change these product terms at any time. We will notify you of changes in line with Clause 33 (Notices) of our General
2. Data services
2.1. Through our unique data structure and data segregation, we are able to perform pricing on a per client basis.
2.2. Our charges are easy to understand with no hidden additional costs. Fees include all exchanges, blockchains and protocols supported by the tool including new integrations added in future.
2.3 A minimal monthly maintenance fee is charged to maintain the organization’s unique environment where data is stored and is all encompassing of the funds/entities created on your profile.
2.4. Hash Data pricing is calculated based on the complexity of the query.
2.4.1Historical queries:
Historical queries are queries which are run over a set historical period. Our tool has a set base cost per API/wallet and variable cost based on the number of transactions. Therefore, costs per API/Wallet decrease as more queries are run. Hash Data pricing is calculated based on the complexity of the query. Hash does not limit the API’s/wallets that you are allowed per tier, rather we charge a base cost per API/wallet per month for the specific fund and only charge for transactions that were run for that month in order to give our clients more flexibility.
2.4.2. Continuous queries
Continuous queries are queries which are run on a set interval as defined by the client. Continuous queries are priced monthly based n a tiered fee structure, the number of API’s/wallet address and number of transactions per fund/entity on our platform. Continuous queries are set on our platform where all new data in an exchange account, address or DeFi protocol is populated to the platform throughout. Pricing is calculated on a monthly basis based on the activity of that specific fund/entity registered under a client in that month.
Data is retained until deleted by the client or when the contract with Hash is terminated. Let us know if you have specific extended data retention needs and we can discuss facilitation.
3. Supply of information and documents
3.1. You acknowledge that our ability to perform the Data Officer Services depends on timely receipt of all necessary information from all relevant persons including you and any other relevant service providers (for example, any investment manager, fund administration or custodian).
4. Your undertakings
4.1. You undertake for the duration of the Data Services that:
4.1.1. (if applicable) your administration will be undertaken by persons of sound reputation who have sufficient expertise to administer you;
4.1.2. your administrator will keep and maintain data policies and procedures on your behalf in line with applicable laws and rules in the Cayman Islands regarding data processing.
5. Availability
5.1. The Hash shall use reasonable endeavors to ensure that the uptime for the Data Services is at least 99% during each calendar month.
5.2. Hash shall be responsible for measuring uptime, and shall do so using any reasonable methodology.
5.3. Downtime caused directly or indirectly by any of the following shall not be considered when calculating whether the Provider has met the uptime guarantee:
5.3.1. a Force Majeure Event;
5.3.2. a fault or failure of the internet or any public telecommunications network;
5.3.3. a fault or failure of the Provider’s hosting infrastructure services provider, unless such fault or failure constitutes an actionable breach of the contract between the Provider and that company;
5.3.4. a fault or failure of the Customer’s computer systems or networks;
5.3.5. any breach by the Customer of this Agreement; or
5.3.6. scheduled maintenance carried out in accordance with this Agreement.
6. Schedule maintenance
6.1. Hash may from time to time suspend the Data Services for the purposes of scheduled maintenance to the Platform, providing that such scheduled maintenance must be carried out in accordance with this clause.
6.2.Hash shall ensure that all scheduled maintenance is carried out outside Business Hours.
7. Support services
7.1. Hash shall provide the support services with reasonable skill and care and in accordance with the following:
7.1.1. Hash shall make available to the Customer a helpdesk
7.1.2. The Customer may use the helpdesk to request and, where applicable, receiving the support services; and the Customer must not use the helpdesk for any other purpose.
7.1.3. Hash shall ensure that the helpdesk is accessible by email.
7.1.4. Hash shall ensure that the helpdesk is operational and adequately staffed during Business Hours during the Term.
7.1.5. The Customer shall ensure that all requests for support services that it may make from time to time shall be made through the helpdesk.
7.1.6. Hash may suspend the provision of the support services if any amount due to be paid by the Customer to the Provider under this Agreement is overdue, and the Hash has given to the Customer at least 30 days’ written notice, following the amount becoming overdue, of its intention to suspend the support services on this basis.
8. Ending the data services
8.1. Despite the longer notice of termination period specified in our General Terms, any party may end the Data Services at any time by giving not less than 60 days notice to the other party.
8.2. Despite the longer notice of termination period specified in our General Terms, any party may end the Data Services with immediate effect in the event that:
8.2.1. the other party commits any material breach of its obligations under this Agreement; and
8.2.1.1. such breach is not capable of remedy; or
8.2.1.2. where such breach is capable of remedy fails, within fourteen days of receipt of notice served requiring it so to do, to make good such breach; or
8.2.1.3. any regulatory action is taken against the other party; or
8.2.1.4. any proceedings are commenced against or in respect of the other party.
Dated: 15 November 2021