Where we are operating in conjunction with third parties, crypto exchanges, third party APIs and/or any other third party systems, there is a risk of transactions being mistakenly or fraudulently signed for using your Keys as a result of the actions of the third party. The client accepts that in instructing us to deal with third parties they are aware of the risks involved, and that they, and not we, accept the risks involved in dealing with that third party.

Where the client utilises our API and custody their own instruction key they are responsible for the security of said key. Any instruction signed by that key will be considered valid and binding until they notify us of a breach and we confirm that their instruction key has been removed from the wallet policy.

Did this answer your question?