Access Protection with Fireblocks Terms and Conditions

19. Third party rights  

The Contract does not give rise to any rights under the Contracts (Rights of Third Parties) Act 1999 to enforce any term of the Contract.

20. Governing law

The Contract, and any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with it or its subject matter or formation, shall be governed by, and construed in accordance with the law of England and Wales.

21. Jurisdiction

Coincover and the Customer irrevocably agree that the courts of England and Wales shall have exclusive jurisdiction to settle any dispute or claim (including non-contractual disputes or claims) arising out of or in connection with the Contract or its subject matter or formation.

1. Service Activation Requirements

The Customer acknowledges that Coincover is unable to commence provision of the Services until such time as:

1. the Customer has furnished Coincover with the Access Control List and all such evidence of the identity of the Access Control Members as may reasonably be required by Coincover;
   
   
2. the identity of the Access Control Members has been verified by Coincover;
   
   
3. the key pairs created by Coincover in accordance with this Service Schedule have been validated by the Fireblocks for use in connection with the workspace named in the Order Form; and
   
   
4. any initial invoice rendered by Fireblocks under the Contract has been paid in full by the Customer.

2. Services Description

As soon as reasonably practicable following the Service Activation Requirements being met, and in accordance with the applicable Service Level, Coincover shall:

1. create a public and private key pair using the Rivest-Shamir-Adleman (“RSA”) scheme for use by the Customer in connection with the workspace named in the Order Form which is provided by Fireblocks;
   
   
2. encrypt a copy of the RSA private key (which may only be decrypted by the Customer) for back-up and disaster recovery purposes in accordance with FIPS 140-2 level 3 standards;
   
   
3. store a copy of the encrypted RSA private key for the term of the Contract; and
   
   
4. subject to the remaining provisions of this Service Schedule, Coincover shall recover a copy of the encrypted RSA private key upon request by the Customer (“Recovery”).

3. Recovery Conditions

The Customer acknowledges that Coincover shall not be required to commence a Recovery until any request by the Customer is verified to Coincover’s reasonable satisfaction by a simple majority of the Access Control Members.

4. Other Conditions

Coincover shall be required to complete no more than the Maximum Number of Recoveries during any consecutive twelve (12) month period during the term of the Contract.

5. Timescales

Coincover shall use reasonable endeavours to complete all recovery requests within the agreed Recovery SLA below following the conditions in paragraph 3 of this Service Schedule being met by the Customer.