Product Specific Terms
Effective Date: April 17, 2026
These Product Specific Terms govern Client’s use of each feature set out herein and are incorporated by reference to the Master Service Agreement by which Client subscribed to the Fireblocks’ Service (the “Agreement”), and form an integral part of that Agreement. Capitalized terms not defined herein shall have the meaning assigned to them in the Agreement. In the event of any conflict between the Product Specific Terms and the Agreement, the Product Specific Terms shall govern.
BY EXECUTING AN ORDER FORM OR OTHER DOCUMENT THAT REFERENCES THESE TERMS OR USING (OR MAKING ANY PAYMENT FOR) THE PLATFORM OR ANY PORTION THEREOF, YOU: (A) HEREBY AGREE TO THESE TERMS ON BEHALF OF THE ORGANIZATION, COMPANY OR OTHER LEGAL ENTITY FOR WHICH YOU ACT; AND (B) REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUBSCRIBER AND ITS AFFILIATES TO THESE TERMS.
The Platform Services.
The Platform Services as described in this Section I are available to all Fireblocks’ clients and enable Client to securely store, manage and administer holdings of digital assets by using its Private Key Share.
Client Keys.
a. Client Keys.
Client Keys. Fireblocks will enable Client to access and use the Service in accordance with any usage and time limitations set forth in the applicable Order Form. Upon onboarding, the Service will cause the Client Device to generate a Private Key Share which will be stored on Client’s Device. Client may use the Recovery Passphrase to recover a Private Key Share in the event a Client Device containing a Private Key Share is lost, stolen, damaged, or otherwise inaccessible.
b. Disaster Recovery Kit.
In addition, Fireblocks will provide Client with a Disaster Recovery Kit which contains an encryption code, which will allow Client access to the set of keys required to access the digital assets in the Client Workspace without any involvement from Fireblocks. Collectively, Client’s Private Key Share, Recovery Passphrase, and/or the Disaster Recovery Kit as the “Client Keys”.
Client Obligations.
Client acknowledges and agrees that:
a. Client will appoint an Owner for each Workspace who will have control over such Workspace. Fireblocks will follow Owner’s instructions as a designated decision maker on behalf of the Client, and the Owner will be responsible to set up Client’s Workspace settings, including, without limitation, the Transaction Authorization Policy, administrative permissions and approval flows to operate the Workspace and Fireblocks will not be liable for any losses (including, but not limited to, digital assets) related thereto.
b. only Client’s Owner and/or Users are permitted to use the Client Keys and Client will prevent any unauthorized access to, or use of, the Client Keys;
c. it is solely responsible and liable for the establishment of the appropriate technical, organizational and security measures to ensure that Client’s Users safeguard access to their individual Client Keys, and Client will notify Fireblocks promptly upon becoming aware of any unauthorized access to or use of the Client Keys;
d. Client is solely responsible for any consequences, losses, expenses, costs, and claims arising from or related to any incorrect, neglectful, or unauthorized use of the Client Keys and Fireblocks has no responsibility for any loss or damage due to Client’s failure to secure the Client Keys as required by this Agreement, including, but not limited to, a failed recovery of a Client Workspace, loss of data, erroneous transmission of digital assets, loss of digital assets, and/or hacking by any Third Party;
e. Fireblocks does not have the ability to recreate or access the Client Keys and Fireblocks cannot assist in their retrieval in the event of loss by Client;
f. it is Client’s sole responsibility to back up its Client Keys;
g. Client must: (i) store the applicable Disaster Recovery Kit and Recovery Passphrase in a secured, offline location, with strict protocols setting adequate security measures to protect the Client Keys; and (ii) from time to time, perform a recovery test to ensure the Disaster Recovery Kit operates in accordance with Client’s recovery procedure; and,
h. any loss of the Client Keys could lead to permanent damage and complete loss of control over and inability to recover its digital assets.
API Co-Signer Service.
These terms apply to Client’s use of an API co-signer. Fireblocks shall provide the relevant specifications, deployment instructions and security recommendations for the installation and operation of the API co-signer (the “Co-signer Specifications”) to Client via the Fireblocks Console or Fireblocks’ Help Center, as applicable.
a. Key Management System and Access Management.
Client hereby acknowledges and agrees that it will install and operate the API co-signer in accordance with the Co-signer Specifications.
b. Security Measures.
In addition to ensuring its compliance with the Co-signer Specifications, Client is solely responsible for ensuring the security of its configuration in accordance with the recommendations on the Fireblocks Console and/or Fireblocks’ Help Center, and including updating and patching from time to time according to instructions from an applicable Third Party (e.g. a cloud provider) and/or Fireblocks.
c. FIREBLOCKS DISCLAIMERS.
CLIENT ACKNOWLEDGES AND AGREES THAT FIREBLOCKS WILL NOT BE LIABLE FOR ANY MALFUNCTIONING, LOSS OR DAMAGE DUE TO CLIENT’S FAILURE TO INSTALL THE API CO-SIGNER IN ACCORDANCE WITH THE CO-SIGNER SPECIFICATIONS WHICH MAY LEAD TO A FAILURE TO PROTECT ITS PRIVATE KEYS AT RUNTIME.
AI Services.
a. Usage.
Usage. These terms apply to Client’s use (including use by its Users) of any artificial intelligence (“AI”) powered generative experiences within the Fireblocks platform, including the Fireblocks’ Genie chatbot service or the agentic policy analyzer within FSPM (“AI Services”).
b. The AI Services may assist Users by answering questions, providing information, and supporting interaction with the Service.
c. Client’s use of the AI Services is entirely optional and completely within Client’s control; Client may choose not to utilize or engage with the AI Services, notwithstanding their availability in the platform.
d. The AI Services are powered by technology from Third Party providers, based on generative AI. Should Client choose to access and/or make use of any AI Services, they may be subject to, and (where applicable) the Client shall comply with, the relevant Third Party’s terms and conditions for such access and use. Further information, and applicable Third Party’s terms and conditions, are available for review in the relevant Help Center articles for the relevant AI Services.
e. Client is solely responsible for its use of the AI Services, including any inputs or prompts provided, as well as reliance on any outputs generated (which Client acknowledges may not be accurate). Client shall not use the AI Services in any way that violates or facilitates the violation of applicable law (including the Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence (the “EU AI Act”)), or violates Fireblocks’ intellectual property rights or otherwise competes with Fireblocks.
f. Client recognizes that AI, particularly generative AI, is a novel and evolving field. There may be unknown risks, and the technology’s safeguards may not be comprehensive. Client is fully responsible for ensuring the AI literacy of its Users.
g. Content and Output.
In certain cases, the AI Services may allow Users to submit various forms of input—including text, natural language statements, prompts, SQL requests, or other queries (“Input”). Based on this Input, the AI Services generate responses such as text, images, or other formats (“Output”). Collectively, Input and Output are referred to as “Content” and form part of Client’s Usage Data. Client assumes full responsibility for any risks arising from its, and its Users, use of such AI Services, including but not limited to accepting that Outputs may not always be accurate or appropriate. Client is responsible for verifying the suitability and correctness of Content for its intended use. Client will promptly stop using, displaying, or distributing any Output if it receives a claim that such Output violates a third party’s intellectual property rights, or notice that such a claim has been made. Content is and remains the property of the Client, with the understanding that the Client bears all responsibility for its legality (including, among others, compliance with intellectual property, copyright and trademark laws), accuracy, and appropriateness.
h. Client must not use AI Services without first determining if its use of the AI Services is legal, effective, safe, and appropriate for it. The AI Services and/or any components thereof are not intended to be used for and Client shall not use the AI Services for: (i) prohibited AI practices under the EU AI Act or other applicable law (ii) any use that would result in the AI Services being declared a high-risk AI system or that otherwise qualifies as “high-risk” or functionally similar under applicable law, (iii) any purpose that would violate applicable data protection, privacy, or intellectual property laws, or (iv) any use that is illegal, sensitive, critical, unsafe, high-risk, or hazardous (including any use that could result in death or serious bodily injury, catastrophic damage, warfare, or the operation of critical infrastructure). Client is responsible for any decisions, actions, and/or inactions arising from its use of AI Services, including ensuring compliance with applicable laws, regulations, and other legal requirements.
i. In addition to generating informational Outputs, the AI Services may, where expressly authorized by the User, execute certain actions on the User’s behalf (for example, activating APIs or initiating other permitted functions). Any such execution is strictly subject to the permissions granted by the User. For the avoidance of doubt, User’s actions shall not result in the use of the AI services for high-risk, prohibited or restricted AI purposes under applicable law.
j. WITHOUT LIMITATION, THE AI SERVICES AND ANY OUTPUT IS PROVIDED “AS-IS” AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, FIREBLOCKS DISCLAIMS ANY AND ALL RESPONSIBILITY WITH REGARDS TO THE CURRENCY AND ACCURACY OF OUTPUT PROVIDED THROUGH THE AI SERVICES, AND WILL NOT BE LIABLE FOR ANY LOSS OR DAMAGE (DIRECT OR INDIRECT) ARISING FROM USE OF THE AI SERVICES OR OUTPUT.
k. Client will promptly report any violations of these terms of use, or any issues with any of the AI Services, to Fireblocks’ Legal department at [email protected].
l. Client will use commercially reasonable efforts to cooperate with Fireblocks in any audit, investigation or regulatory inquiry with respect to Client’s use of the AI Services.
The Dynamic Platform services described in this Section II are available to all Fireblocks clients who subscribe to the Dynamic embedded wallets software-as-a service platform (the “Dynamic Service”). The Dynamic Service enables the Client to access the Dynamic Platform and provide embedded digital wallet and wallet connection functionality to its End Users, granting End Users the ability to securely manage cryptographic keys or shares, and securely store, manage and administer holdings of digital assets or automate on-chain activities.
Definitions.
Solely in relation to the Dynamic Service, the following capitalised terms shall have the meanings set out below:
a. “Access Credentials” means login information, passwords, security protocols, and policies through which End Users access the Dynamic Service.
b. “Client Application” means an application or web-based service developed or used by Client and/or its Affiliates (including its APIs), and which leverages the Dynamic Service.
c. “Dynamic Client Data” means all data, content, and information submitted to the Dynamic Service by or on behalf of Client or its End Users, or otherwise made available to Dynamic for use in connection with the Dynamic Service, and any Client-specific output that is generated by End Users through their use of the Dynamic Service.
d. “Dynamic Documentation” means the user guides, technical specifications, and other materials made available by Dynamic from time to time, including on the dynamic.xyz website, that describe the functionality, features, operation, or use of the Dynamic Service.
e. “Dynamic Platform” means the computer software applications, code (in source code, executable code or other machine-readable format), tools, application programming interfaces (APIs), software development kits (SDKs) connectors, programs, networks and equipment that Dynamic uses or makes available from time to time, to make the Dynamic Service available to its clients.
f. “End Users” means the Client’s customers who access and/or use a Client Application.
License Grant.
In addition to the Usage Rights set out in the Agreement, Dynamic grants Client a revocable, limited, non-exclusive, non-sublicensable, non-transferable, worldwide, and royalty-free license to (i) access and use the Dynamic Service; and (ii) access the Dynamic Platform solely for Client’s internal business purposes and to enable End Users to access and use the Dynamic Service through a Client Application, pursuant to the terms of the Agreement, these Product Specific Terms and the Dynamic Documentation. Client shall be responsible and liable for any use of the Dynamic Service by End Users.
Dynamic Responsibilities.
Dynamic shall have the following responsibilities to Client:
a. Provision of the Dynamic Service.
Dynamic will enable Client to access and use the Dynamic Service in accordance with any usage and time limitations set forth in the applicable Order Form. Client acknowledges and agrees that unless expressly stated otherwise herein, the Dynamic Platform and Dynamic Service are non-custodial. Unless specifically mentioned otherwise herein, Dynamic does not store, manage, or control any private keys, funds, or other assets on behalf of Client or Users. Dynamic shall not be liable for losses arising from any risks associated with digital assets and blockchain technology, and Client agrees that it is solely responsible for whether and how it communicates these risks to End Users.
b. Protection of Client Data.
Dynamic will maintain commercially reasonable administrative, physical, and technical safeguards designed to prevent unauthorized access to or use of Client Data under the control of Dynamic.
c. Support.
As part of the Dynamic Service, Dynamic will provide Client with Dynamic’s standard support, Documentation, and other online resources to assist Client in its use of the Dynamic Service, all as set forth in the applicable Order Form.
Access to and Use of the Service.
In addition to the obligations set out in the Agreement, Client will:
a. Client Responsibilities.
Client is and will be responsible for the accuracy, integrity, appropriateness, and legality of the Client Data as necessary for Dynamic to provide the Dynamic Service and obtaining any consents and providing any notices, as necessary, to enable Dynamic to perform its obligations under the Agreement, including, without limitations, accessing and processing any Personal Data for the purpose of providing the Dynamic Service.
b. Client Applications.
Client is responsible for the development, implementation, operation, support, maintenance, and security of each Client Application, including the processes by which End Users accept the terms and conditions of such Client Applications. Dynamic and its licensors bear no liability for any services Client provides to End Users, including Client Applications. Client represents and warrants that it shall comply with all applicable privacy laws and regulations including those applying to personal data, including without limitation, the personal data of the End Users using a Client Application.
c. Sandbox Services.
From time to time, Dynamic may offer potential new products, services or features in a sandbox environment (“Sandbox”) that allows Client to test the functionality, user interfaces, and security measures of the Client Application, without the risk of testing in a production environment. Dynamic provides access to the Sandbox solely for experimental and educational purposes. It is not intended for and should not be used by Client for any live offering. Dynamic does not guarantee the functionality, security, or uninterrupted access to the Sandbox. Client understands and agrees, and shall ensure any End User it permits to access the Sandbox understands and agrees, that any cryptocurrency or tokens used or stored in the Sandbox are subject to risk of loss for which Dynamic shall in no circumstance be liable.
d. Third Party Services.
Client acknowledges that certain Third Party Services are made available to the Client and/or the Client’s End Users through the Dynamic Platform, including specific features and functionality as listed here: https://www.dynamic.xyz/third-party-services.
e. Embedded Wallets.
Dynamic uses Multi-Party Computation (“MPC”) technology to help Client and its End Users secure digital wallets, as more particularly described in the Dynamic Documentation. Dynamic embedded wallets are non-custodial, meaning they are always owned and controlled by the End User (or Client, at Client’s option) and not controlled by Dynamic. Only the End User or Client (as applicable) has ownership and access to their controlling key share. For the avoidance of doubt, Dynamic never generates or stores any complete private keys or key shares in an unencrypted form on its servers, nor does it have access to or visibility of the underlying keyshares (whether encrypted or decrypted) at any time. Clients and End Users are responsible for securing authentication credentials and their respective shares, including any optional backup shares generated by the Dynamic Service at Client’s request. Dynamic is not responsible for any activities that End Users or Clients engage in when using End Users’ key shares, or when reconstructing full private keys during key exports or key imports. Dynamic further offers advanced wallet services, including backup share management hosted on Client’s site, For those and any other services offered as part of the Dynamic embedded wallet solution, Client agreed and affirms Dynamic is a non-custodial solution. In the event that an End User creates an embedded wallet and the embedded wallet is unfunded (i.e. the wallet contains no assets) for a period of six (6) months from the time of creation, Dynamic has the right to disable functionality of the embedded wallet through its interfaces which will delete all data associated with the account.
Dynamic Client Data
Client retains all rights, title, and interest in and to the Dynamic Client Data. Client grants to Dynamic and its Affiliates a worldwide, limited, revocable, non-exclusive, license to access, use, copy, distribute, perform, and display Dynamic Client Data, and provide necessary access to Third Party Services providers acting on Dynamic’s behalf, such as Dynamic’s hosting services provider, only: (a) as necessary to provide maintain, monitor, analyze, improve, promote, protect, document and update the Dynamic Service in a manner that is consistent with this Agreement and Dynamic’s Privacy Policy; (b) to prevent or address service or technical problems or at Client’s request in connection with support matters; or (c) as expressly permitted in writing by Client. Subject to the limited licenses granted herein, Dynamic acquires no right, title, or interest under this Agreement in or to any Dynamic Client Data. Client grants Dynamic a non-exclusive, royalty-free, worldwide license to use Client’s name and logo solely to identify Client as a user of the Dynamic Service on Dynamic’s website, marketing materials, and in public statements.
Data Processing Approvals.
Except to the extent otherwise specified in the applicable Order, Client is solely responsible for providing all necessary notices and obtaining, and represents and covenants that it has obtained or will obtain prior to processing by Dynamic, all necessary consents, licenses, and approvals for the processing of any Client Data (and any Personal Data) as part of the Service in a manner that is consistent with this Agreement and Dynamic’s Privacy Policy.
These features are available to all clients who have subscribed to the Pro, Enterprise and Enterprise+ tiers (collectively and individually “Premium Tiers”).
Gas Station Service and Gasless Relay Service.
All blockchains require a fee to be paid in the base asset of the blockchain to execute a transaction. This fee is referred to as gas.
The Gas Station Service allows the Client to automate the fueling of transactions with gas from a wallet designated by the Client. Clients can also utilize the Gasless Relay Service to pay gas fees through a workspace owned by a Third Party or Fireblocks.
a. Pricing and Fueling.
i. Gas Station Service: Client is solely responsible for setting price parameters and ensuring there are sufficient funds available for executing Client’s desired transactions. Gas prices shall be denominated in Gwei, unless otherwise mutually agreed in writing.
ii. Gasless Service: The Gasless Service allows Clients to centralize gas payments from a dedicated vault, known as a relay. The relay can be a local relay, i.e., a vault within a Client’s workspace pays the gas fees for all other vaults in that workspace; or, an external workspace relay, i.e., a vault in a separate workspace B, pays for the gas fees of the vaults in workspace A.
iii. The Fireblocks Gasless Relay Service is where the external workspace relay is within a Fireblocks-owned and controlled workspace, and in respect of the Fireblocks Gasless Relay Service:
- The gas price for such transactions will be calculated based on the gas paid converted to USD at the time the Client broadcasts the transaction.
- The gas rate for the Fireblocks Gasless Relay Service is fixed and Fireblocks will not be liable for any transaction failure due to gas prices.
- Client is solely responsible for determining the appropriate Fireblocks Gasless Relay Service tier for its needs and hereby acknowledges that if its usage exceeds this tier there may be insufficient gas available to execute transactions.
b. Client acknowledges that all block-based transactions are probabilistic and subject to failure and operations can be unsuccessful in being added to the blockchain for several reasons, including network congestion and insufficient funds in the Client’s gas station wallet.
c. CLIENT ACKNOWLEDGES AND AGREES THAT FIREBLOCKS DOES NOT GIVE ANY RECOMMENDATIONS REGARDING THE GAS PRICE NEEDED TO ACHIEVE A PARTICULAR TRANSACTION SPEED NOR DOES IT MAKE ANY GUARANTEES REGARDING THE EFFECTIVENESS OF ANY PARTICULAR GAS PRICE IN COMPLETING ANY PARTICULAR TRANSACTION OR SET OF TRANSACTIONS. ANY FEE ESTIMATES THAT THE GAS STATION SERVICE MAY PROVIDE ARE FOR INFORMATIONAL PURPOSES ONLY AND CLIENT ACKNOWLEDGES AND ACCEPTS THAT IT IS SOLELY RESPONSIBLE FOR DETERMINING THE GAS PRICE NEEDED TO ACHIEVE ANY PARTICULAR OUTCOME. CLIENT UNDERTAKES TO USE THE GAS STATION SERVICE THE GASLESS SERVICE AND/OR THE FIREBLOCKS GASLESS RELAY SERVICE AT ITS OWN RISK, AND CLIENT ASSUMES FULL RESPONSIBILITY FOR THE CONSEQUENCES OF ANY AND ALL UNSUCCESSFUL TRANSACTIONS AND ANY AMOUNTS THAT ARE DEBITED IN CONNECTION WITH SUCH TRANSACTIONS.
A client who has subscribed to a Premium Tier, may subscribe to these Add-On Features for an additional fee(s), as set out in the applicable Order Form.
Business Continuity Management System.
The Business Continuity Management System or “BCM” allows Client to ensure operational continuity by facilitating payload signing for the blockchain independent of the Fireblocks platform. It is intended for use when the Fireblocks Services are unavailable (for example, in temporary outage scenarios) and is built on top of Hosted MPC (another Add-on Feature, described below).
a. Installation.
In order the use BCM, Client acknowledges:
i. it must provide, set up and configure its infrastructure so that it complies with the functional requirements stated by Fireblocks, including, but not limited to: ensuring it has an active Hosted MPC subscription with Fireblocks; its own blockchain node(s) to broadcast transactions; and, a properly configured Hosted MPC Environment;
ii. it must download and properly install the relevant software (the “BCM Software”) made available by Fireblocks in accordance with the requirements provided by Fireblocks; and,
iii. it is solely responsible for broadcasting transactions signed via BCM to the relevant blockchain.
b. Client acknowledges and agrees:
i. Notwithstanding any recommendations Fireblocks may make with respect to the setup of BCM, Client bears sole responsibility for appropriately configuring, patching, and utilizing the necessary infrastructure, including but not limited to any security measures Client, in its sole discretion, deems are necessary (e.g. the required firewall setup, network routing setup, access list setup, RPC authentication methods);
ii. No Transaction Authorization Policy functionality will be available as part of BCM and Client will be solely responsible for putting in place compensating controls to ensure that transactions are appropriately authorized.
iii. While Fireblocks will use commercially reasonable efforts to notify Client when an update or upgrade to the BCM Software is available, Client will be solely responsible for installing this update in a timely manner to ensure it is running the latest version of the BCM Software.
c. DISCLAIMER
CLIENT ACKNOWLEDGES AND AGREES THAT CLIENT IS SOLELY RESPONSIBLE FOR THE SETUP, CONFIGURATION, MANAGEMENT, MAINTENANCE AND SECURITY OF THE CLIENT’S INFRASTRUCTURE AND ITS BCM INSTANCE. FIREBLOCKS WILL HAVE NO RESPONSIBILITY OR LIABILITY FOR ANY LOSSES INCLUDING LOSS OF DIGITAL ASSETS) AS A RESULT OF ANY DELAYS, FAILURES, OR OTHER MISBEHAVIOR RESULTING FROM SLOW, UNRESPONSIVE, MISCONFIGURED OR MALFUNCTIONING BCM.
d. SLA Exclusion
Given that it facilitates transaction signing without the use of the Fireblocks platform, Client acknowledges that Fireblocks’ SLA shall not apply to any use of BCM.
Cold Wallet.
The Cold Wallet offering allows Client to create a Workspace for which the relevant Private Key Share is stored offline.
a. Warranties.
Client represents, warrants, and undertakes that it: (i) will ensure that it procures and provisions any Cold Wallet Device appropriately and in accordance with the specifications set out in the Help Center and the Documentation; and (ii) is solely responsible for ensuring the security of the Cold Wallet Device, as well as the Recovery Passphrase and Disaster Recovery Kit with respect to the Cold Wallet (as provided in the Agreement).
b. Fireblocks Disclaimers.
Client acknowledges and agrees that Fireblocks is not liable for any loss, including any loss of any digital assets, arising from or relating to the provisioning and security of the Cold Wallet Device.
Embedded Wallets.
Subject to these terms, Client may provide its clients (each an “End User”) access to the Services through a white-labeled Client application (the “Client App”) in the form of an embedded wallet (the “Embedded Wallets”).
a. Client App.
i. To develop the Client App, Fireblocks will make a software development kit (“SDK”) available to Client, in addition to documentation in the Fireblocks developer portal (the “Portal”). Client acknowledges and agrees that it is solely responsible for monitoring the Portal for any updates and upgrades to the SDK that Fireblocks may make available during the Term.
b. Usage Rights to Service; End User Keys.
Through the Client App, Client will:
i. Provide the End User with the capability to generate a Private Key Share which enables the End User to independently execute transactions (the “End User Private Key Share”);
ii. allow the End User to generate a method to recover the End User Private Key Share in the event the End User’s Device containing the End User Private Key Share is lost, stolen, damaged, or otherwise inaccessible (the “End User Recovery Passphrase”); and,
iii. advise the End User of the availability of a Disaster Recovery Kit through which End User may access the digital assets in the End User’s Wallet(s) without any involvement from Fireblocks (the “End User Disaster Recovery Kit”).
Collectively, the End User Private Key Share, End User Recovery Passphrase and End User Disaster Recovery Kit shall be referred to as the “End User Keys”.
c. End User Key Obligations.
Client acknowledges and agrees that:
i. only End Users are permitted to use the End User Keys, and Client will advise End User of the best practice to prevent any unauthorized access to, or use of, the End User Keys;
ii. it is solely responsible and liable for the establishment of the appropriate technical, organizational and security measures to ensure that End Users safeguard access to the End User Keys, and Client will notify Fireblocks promptly upon becoming aware of any unauthorized access to or use of the End User Keys;
iii. Client is solely responsible for any consequences, losses, expenses, costs, and claims arising from or related to any incorrect, neglectful, or unauthorized use of the End User Keys or Client App and Fireblocks has no responsibility for any loss or damage due to Client’s or the End User’s failure to secure the End User Keys or Client App as required by this section, including, but not limited to, a failed recovery of an End User wallet, loss of data, erroneous transmission of digital assets, loss of digital assets, and/or hacking by any Third Party;
iv. Fireblocks does not have the ability to recreate or access the End User Keys and Fireblocks cannot assist in their retrieval in the event End Users lose their End Users Keys;
v. it is Client’s sole responsibility to ensure: (i) End Users backup their End User Keys; (ii) store the End User Disaster Recovery Kit and Recovery Passphrase in a secured, offline location, with strict protocols setting adequate security measures; and (iii) from time to time, perform a recovery test to ensure the Disaster Recovery Kit operates in accordance with Client’s recovery procedure;
vi. any loss of the End User Keys could lead to permanent damage and complete loss of control over and inability to recover any digital assets and Client represents that it will advise End Users of the same;
vii. Client shall enter into an agreement with the End User related to its use of the Client App and the Embedded Wallets that contains terms not less restrictive than the terms set forth herein; additionally Client shall advise End User of the End User Keys and their various functionalities; and,
viii. nothing in these Product Specific Terms shall be construed to create a relationship, contractual or otherwise, between End User and Fireblocks.
d. Client’s Liability and Indemnification of Fireblocks.
Client is solely responsible for its internal policies and procedures with respect to delegating use of the Embedded Wallets to End Users, including any consents required from its End Users to share any Usage Data. Client will be liable for all actions taken by its End Users, including any breach by End Users of these terms. Without derogating from the above, Fireblocks is not responsible or liable in any way for any of the following:
i. the development of the Client App, including its functionality and security;
ii. any unauthorized access to or use of the Embedded Wallets, including by any Third Party and/or in case of theft, embezzlement or similar cases;
iii. Client’s failure to enable the End User Disaster Recovery Kit;
iv. storage of the End User Keys; and/or,
v. any failure by Client to obtain any consents required by End User with respect to Usage Data. Client will fully indemnify Fireblocks for any losses, damages, or claims made by End User, or any Third Party, arising from the Client’s and/or End User’s use of the Embedded Wallets.
e. Representations and Warranties; Disclaimers.
i. Client represents and warrants that: (i) it has explained to End User the implications of and the obligations associated with using the Embedded Wallets, in accordance with the terms of the Agreement; (ii) it is solely responsible for ensuring that its activities on the Fireblocks platform, including the Embedded Wallets, are in compliance with any regulatory obligations, notwithstanding any use-cases proposed by Fireblocks.
ii. THE EMBEDDED WALLETS SERVICE IS PROVIDED “AS IS” AND FIREBLOCKS AND ITS SUPPLIERS, IF ANY, MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, REGARDING THE EMBEDDED WALLET SERVICE, AND SPECIFICALLY DISCLAIM THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE, TO THE MAXIMUM EXTENT POSSIBLE BY LAW. FIREBLOCKS DOES NOT WARRANT THAT THE EMBEDDED WALLETS SERVICE WILL MEET CLIENT’S REQUIREMENTS, OPERATE WITHOUT INTERRUPTION OR BE ERROR FREE.
f. Term and Termination.
i. Termination for Breach. If Client and/or End User commits a material breach of these terms, or if Fireblocks reasonably believes that Client and/or End User is in violation of these terms or any applicable law, Fireblocks may immediately terminate End User’s access to the Embedded Wallets and/or terminate Client’s Agreement upon written notice to Client.
ii. Effect of Termination. Upon termination, Client shall immediately deactivate any End User wallet(s).
Hosted MPC
Fireblocks hosted multiparty computation (MPC) allows Client to host its Private Key, as well as the two MPC cloud key shares typically held by Fireblocks in its cloud environment (the three key shares collectively referred to as the “Key Shares”) in the Client’s controlled environment either on-premise or in the cloud, in Client’s discretion (“Hosted MPC”). Client is solely responsible for any fees charged by participating third parties and any hardware required by Client to enable Hosted MPC.
a. Installation. In order to use Hosted MPC, Client acknowledges:
i. it must provide, set up and configure its infrastructure so that it complies with the functional requirements stated by Fireblocks; and,
ii. it must download and properly install the relevant software made available by Fireblocks (the “Hosted MPC Software”). While Fireblocks will use commercially reasonable efforts to notify Client when an update or upgrade to the Hosted MPC Software is available, Client will be solely responsible for installing the latest version of the Hosted MPC Software.
iii. Client Keys. Client acknowledges and agrees that by virtue of using Hosted MPC it will have sole responsibility for the security and integrity of the Key Shares. Notwithstanding any recommendations Fireblocks may make with respect to the setup of Hosted MPC, Client bears sole responsibility for appropriately configuring, patching, and utilizing the necessary infrastructure, including but not limited to any security measures Client, in its sole discretion, deems are necessary (e.g. the required firewall setup, network routing setup, access list setup, RPC authentication methods,);
iv. DISCLAIMER. CLIENT ACKNOWLEDGES AND AGREES THAT CLIENT IS SOLELY RESPONSIBLE FOR THE SETUP, CONFIGURATION, MANAGEMENT, MAINTENANCE AND SECURITY OF THE CLIENT’S INFRASTRUCTURE AND HOSTED MPC. NOTWITHSTANDING ANY RECOMMENDATIONS THAT FIREBLOCKS MAY MAKE IN ITS INSTALLATION GUIDE OR ELSEWHERE, FIREBLOCKS WILL HAVE NO RESPONSIBILITY OR LIABILITY FOR ANY LOSSES (INCLUDING LOSS OF DIGITAL ASSETS) AS A RESULT OF ANY DELAYS, FAILURES, OR OTHER MISBEHAVIOR RESULTING FROM SLOW, UNRESPONSIVE, MISCONFIGURED OR MALFUNCTIONING HOSTED MPC SOFTWARE ON CLIENT’S SERVERS.
iv. SLA Exclusion. Client acknowledges that Fireblocks’ SLA shall not include any Downtime Incidents (as defined in the SLA, fireblocks.com/sla) that are caused by or attributable to the Client’s infrastructure, including its use of Hosted MPC and/or Client’s own act or omission.
Key Link Solution
These terms govern Client’s use of Fireblocks’ solution through which the Client’s private key material (“Private Key(s)”) is entirely managed and controlled by the Client (“Key Link Solution”).
a. Installation. Client acknowledges: (i) it must provide, set up and configure its infrastructure (including, but not limited to, deploying the Fireblocks Key Link agent and integrating it with the Client key management system) so that it complies with the interface and functional requirements stated by Fireblocks; and (ii) this proper installation is necessary to enable the Client to use its Private Keys to execute transactions when using the Service.
b. Client Keys. Client acknowledges that, by virtue of its use of the Key Link Solution, the Client generates and stores its Private Keys within its own infrastructure.
c. Client acknowledges and agrees:
i. Fireblocks does not generate, nor does it have access to, the Private Keys and therefore Client shall be solely responsible for the security of the Private Key, including making any backups; viii. only Client’s Owner and/or Users are permitted to use the Private Key and Client will prevent any unauthorized access to, or use of, the Private Key;
ii. in the event of any unauthorized access to or use of the Private Key the Client bears sole responsibility for any mitigation efforts it deems necessary to prevent the loss of its digital assets;
iii. Client bears sole responsibility for appropriately configuring, patching, and utilizing the infrastructure in which it stores its Private Key, including any required firewall setup, network routing setup, access list setup, RPC authentication methods, and any other security measures deemed necessary, in the Client’s sole discretion;
iv. Fireblocks does not have the ability to recreate or access the Private Key and Fireblocks cannot assist in its retrieval in the event of loss by Client; and,
v. any loss of the Private Key could lead to permanent damage and complete loss of control over and inability to recover its digital assets.
d. DISCLAIMER. CLIENT ACKNOWLEDGES AND AGREES THAT CLIENT IS SOLELY RESPONSIBLE FOR THE SETUP, CONFIGURATION, MANAGEMENT, MAINTENANCE AND SECURITY OF THE CLIENT’S INFRASTRUCTURE. FIREBLOCKS WILL HAVE NO RESPONSIBILITY OR LIABILITY FOR ANY LOSSES (INCLUDING LOSS OF DIGITAL ASSETS) AS A RESULT OF ANY DELAYS, FAILURES, OR OTHER MISBEHAVIOR RESULTING FROM SLOW, UNRESPONSIVE, MISCONFIGURED OR MALFUNCTIONING HARDWARE ON WHICH THE PRIVATE KEY IS STORED.
e. SLA Exclusion. Client acknowledges that Fireblocks’ SLA shall not include any Downtime Incidents (as defined in the SLA, fireblocks.com/sla) that are caused by or attributable to the Client’s infrastructure, including its key management system and/or Client’s own act or omission.
Node Router
Fireblocks’ Node Router allows Clients to use their own blockchain node(s) when using the Service. When a Client purchases Node Router, Fireblocks’ support team will collaborate with the Client to provision the necessary connection and establish a link to the Client’s dedicated blockchain node (the “Client Node”).
a. Maintenance and Security of Nodes. Client acknowledges and agrees that it is solely responsible for the setup, configuration, management, maintenance and security of the Client Node. Fireblocks will have no responsibility or liability for any losses (including digital assets losses) as a result of Client’s use of Node Router services, howsoever arising, including any delays, drops, failures, stuck, or any other misbehavior resulting from a slow, unresponsive, misconfigured or malfunctioning Client Node. Additionally, the Client acknowledges that Fireblocks will not engage Fireblocks’ own node infrastructure in the event Client Node is inactive or otherwise malfunctions, whether as a backup or for any other means of recovery.
b. Security Measures. The Client bears sole responsibility for appropriately configuring, patching, and utilizing the Client Node, including firewall setup, network routing setup, access list setup, RPC authentication methods, and any other security measures deemed necessary, in the Client’s sole discretion.
c. SLA Exclusion. Client acknowledges that Fireblocks’ SLA shall not include any Downtime Incidents (as defined in the SLA at fireblocks.com/sla) that are caused by or attributable to the Client Node and/or Client’s own act or omission.
Raw Signing
The Raw Signing feature allows Client to sign transactions on non-supported blockchains or to use features or functionality that are not natively supported by the Fireblocks platform. If the Client chooses to enable Raw Signing in its Workspace(s), Client acknowledges and agrees that it is solely responsible for its setup and implementation and for ensuring the security of the Raw Signing feature, including using the Transaction Authorization Policy to determine and/or limit the range of derivation paths, vault accounts and digital assets available for Raw Signing. In addition, Client acknowledges that once a blockchain or feature is natively supported by the Fireblocks platform, Fireblocks strongly encourages Client to use the native integration, instead of using Raw Signing. FIREBLOCKS WILL HAVE NO RESPONSIBILITY OR LIABILITY FOR ANY LOSSES (INCLUDING LOSS OF DIGITAL ASSETS) AS A RESULT OF CLIENT’S USE OF RAW SIGNING. ON NOTICE TO CLIENT, FIREBLOCKS RESERVES THE RIGHT TO DISCONTINUE CLIENT’S USE OF RAW SIGNING IF, IN FIREBLOCK’S SOLE DISCRETION, SUCH USE WOULD RESULT IN SECURITY RISKS TO THE SERVICE OR OTHER CLIENTS.
Fireblocks Security Posture Management
a. The Fireblocks Security Posture Management (“FSPM”) solution allows Client to continuously monitor its security posture by identifying potential security flaws for review and action.
b. Client acknowledges and agrees:
i. The FSPM solution is based on industry-recognized information security principles, evolving threat intelligence, recommended best practices, and the Client’s configurations and uses of the Fireblocks’ platform. FSPM findings are for informational purposes only and do not constitute legal or security advice, or an assurance that the Client’s environment is free from risks.
ii. The FSPM solution may categorize identified risks as “High,” “Medium,” “Low”, or “Info”. These categorizations are indicative only and may not align with Client’s internal risk management framework, policies, or risk tolerance. Client is solely responsible for reviewing, validating, and addressing any findings, including any actions to be taken. Client is solely responsible for maintaining its own security controls and should not rely solely on the solution’s outputs to assess or manage security within its environment.
iii. The FSPM solution is not intended to replace or substitute Client’s own security reviews, assessments, audits, or other independent evaluations. Client should continue to maintain appropriate procedures to monitor, assess, and manage its security posture in line with any applicable standards and regulatory obligations.
iv. The FSPM solution’s scope is limited to the Fireblocks platform and it may not assess or detect potential security flaws in third-party products or services (including any Third Party Services) used by the Client to access or integrate with the platform.
v. The FSPM solution may uncover risks using an agentic policy analyzer, which is an AI-based attack simulator, and to which the AI Services terms within these Product Specific Terms apply.
c. Disclaimer. THE FSPM SOLUTION IS PROVIDED “AS IS” AND FIREBLOCKS AND ITS SUPPLIERS, IF ANY, MAKE NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, REGARDING THE FSPM SOLUTION, AND SPECIFICALLY DISCLAIM THE WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE, TO THE MAXIMUM EXTENT POSSIBLE BY LAW. FIREBLOCKS DOES NOT WARRANT THAT THE FSPM SOLUTION WILL MEET CLIENT’S REQUIREMENTS, OPERATE WITHOUT INTERRUPTION OR BE ERROR FREE, OR THAT ALL THREATS, VULNERABILITIES, MISCONFIGURATIONS OR OTHER SECURITY FLAWS WILL BE DISCOVERED, REPORTED OR REMEDIED. FIREBLOCKS HAS NO RESPONSIBILITY FOR ANY DAMAGE, INCLUDING ANY LOSS OF DIGITAL ASSETS AND/OR DAMAGE TO THE WORKSPACE, IN THE EVENT OF ANY CLIENT ACTION OR INACTION TAKEN DIRECTLY OR INDIRECTLY AS A RESULT OF THE OUTPUTS PROVIDED BY THE FSPM SOLUTION.
- General Terms.
- Accessing Third Party Service(s). Fireblocks may resell, and/or enable access through the Fireblocks platform to, certain optional service(s) provided to the Client, by external and independent Third Party providers (“Third Party Service(s)”). Client hereby acknowledges and agrees:
- Third Party Service(s) are provided to the Client directly by the Third Party, within that Third Party’s control, and Fireblocks is not responsible for the quality of, or the content available on, any Third Party Service(s), including whether it is accurate, complete, reliable, current or error-free;
- Fireblocks is not liable for any acts or omissions of such Third Party, including failure of such Third Party Service to perform to any particular standard;
- Third Party Service(s) are provided pursuant and are subject to the Third Party’s applicable terms and conditions, which the Client accepts and agrees to in using such Third Party Services;
- Client is engaging directly with that Third Party by using such Third Party Services, regardless of whether such Third Party Service was purchased through Fireblocks or accessed via the Service;
- Client’s ability to access Third Party Service(s) via the Service in no way constitutes a recommendation or endorsement of those Third Party Service(s) by Fireblocks; and,
- Fireblocks may present “click-license(s),” “EULAs”, “shrink-wrap” terms, or the like, on behalf of such Third Party, and it is Client’s sole responsibility to review such agreements prior to using such Third Party Service. Additionally, certain Third Parties and their associated terms and conditions are available for review in the Help Center.
- Third Party access to Usage Data. If Client elects to use Third Party Service(s) via the Fireblocks platform, Fireblocks may need to provide certain data to the relevant Third Party Service(s) provider. Client acknowledges and agrees that Fireblocks may share the necessary data (including without limitation, Usage Data) for the purpose of facilitating the integration of Service with the Third Party Services, including enabling, using or accessing such Third Party Services (the “Purpose”). Client hereby authorizes Fireblocks to share such data for, and to the extent necessary to fulfil, the Purpose.
- Disclaimer of Errors Attributable to Third Party Service(s). In the event that a transaction is not completed due to a Third Party, or an error occurs as a result of a Third Party (including, without limitation, errors on any supported blockchain), Fireblocks is not responsible for any claim, liability, expenses, losses, costs, and/or claims resulting from such Third Party content or act.
- End User Consent. To the extent Client is offering access and use of the Service (and/or Third Party Service(s)) to End Users, and Usage Data of such End Users is shared with Fireblocks, Client will notify the End User of this, and obtain all required consents from End User to such sharing of its Usage Data. Client will indemnify and hold Fireblocks harmless from any and all claims and liability arising from such sharing of Usage Data, and any Client failure to obtain the required consents.
- Disclaimer. FIREBLOCKS HAS NO CONTROL OVER OR RESPONSIBILITY FOR, AND MAKES NO GUARANTEES ABOUT THE THIRD PARTY SERVICES AND/OR PROVIDERS THEREOF. CLIENT IS SOLELY RESPONSIBLE FOR, AND ACCEPTS ANY AND ALL RISKS FROM, ITS CHOICE AND USE OF, THIRD PARTY SERVICES PROVIDED TO THE CLIENT BY THE THIRD PARTY, THROUGH THE SERVICE, AND FIREBLOCKS DISCLAIMS ALL LIABILITY FOR SUCH THIRD PARTY SERVICES.
- Accessing Third Party Service(s). Fireblocks may resell, and/or enable access through the Fireblocks platform to, certain optional service(s) provided to the Client, by external and independent Third Party providers (“Third Party Service(s)”). Client hereby acknowledges and agrees:
- Specific Third Party Service Terms.
- DeFi Applications, DeFi Lending Protocol, Staking Services, AI Agent and Network for Payments Connectivity
- Third Party decentralized finance applications (“DeFi Applications”), and/or any staking activity on proof of stake blockchains (“Staking Service(s)”), and/or any decentralized lending, borrowing, or credit protocol, including without limitation protocols that enable deposits into lending vaults, the supply or borrowing of digital assets, and the earning of yield or interest (each, a “DeFi Lending Protocol”), are Third Party Service(s) Client may access through the Service.
- AI Link and Remote MCP (collectively, “AI Agents”) enable the Client to connect and interact with its Workspace(s) via the Client’s applicable AI agents (individually or collectively Third Party Service(s)).
- Network for Payments enables the Client to access certain Third Party Services which may provide Client access to payments services, including fiat on or off ramp services, via the Service (collectively and individually, “NP Provider”).
- FIREBLOCKS RESERVES THE RIGHT TO TERMINATE CONNECTIVITY WITH ANY DEFI APPLICATION, STAKING SERVICE, DEFI LENDING PROTOCOL, AI AGENTS OR NP PROVIDER OR MODIFY THE RULES FOR CONNECTIVITY, IF FIREBLOCKS, IN ITS SOLE DISCRETION, DETERMINES THAT SUCH THIRD PARTY SERVICE: (i) IS MALICIOUS OR POSES A RISK TO FIREBLOCKS’ CLIENTS AND/OR FIREBLOCKS PLATFORM INFRASTRUCTURE; AND/OR (ii) COULD BE INCOMPATIBLE WITH FIREBLOCKS’ COMPLIANCE WITH APPLICABLE LAWS AND/OR REGULATORY OBLIGATIONS.
- No Guarantee by Fireblocks. Any representations or guarantees regarding the operation of any DeFi Application, Staking Service, DeFi Lending Protocol, AI Agents or NP Provider are made by the Third Party and Fireblocks makes no statements, claims, representations or warranties about the security, functionality, or accuracy of representations regarding any of these Third Party Service(s), including in circumstances where a transaction to or from any such Third Party Service originates or terminates from a Fireblocks Workspace. FIREBLOCKS DOES NOT REPRESENT, WARRANT OR GUARANTEE: (i) THE RETURN OF ANY PRINCIPAL AMOUNT OF DIGITALASSETS TRANSFERRED TO A DEFI APPLICATION STAKING SERVICE OR DEFI LENDING PROTOCOL.
- ANY PROCEEDS, RETURNS, INTEREST, YIELD, OR REWARDS OFFERED OR ADVERTISED IN CONNECTION WITH ANY DEFI APPLICATION OR STAKING SERVICE; NOR THAT (iii) ANY FIAT OR DIGITAL ASSETS WILL BE TRANSFERRED OR OTHERWISE PROVIDED TO CLIENT AS A RESULT OF THE ACTIVITIES OF THE NP PROVIDER.
- DeFi Lending Protocol Specific Risks.
(1) Fireblocks does not control, endorse, or assume responsibility for any DeFi Lending Protocol, and does not act as lender, borrower, financial institution, custodian, or counterparty in connection therewith. DeFi Lending Protocols operates in a decentralised and autonomous manner, governed solely by its underlying smart contracts and, where applicable, its protocol governance mechanisms. Unless otherwise expressly stated, Client is at no time transacting with, or transferring assets to or from, Fireblocks or any of its Affiliates when interacting with a DeFi Lending Protocol. Client’s use of any DeFi Lending Protocol may be subject to additional terms imposed by the relevant third party, which it is Client’s sole responsibility to review and comply with.
(2) Fireblocks does not make any representation or warranty with respect to the safety, legitimacy, or regulatory status of any DeFi Lending Protocol or any of the services any DeFi Lending Protocol provides. It is Client’s responsibility to ensure that Client fully understands the nature of the services being provided by any DeFi Lending Protocol, including the financial, technical, and regulatory risks to which Client may be exposed, and the decentralised and autonomous nature of such protocols and the risks of interacting with them. Client is solely responsible for determining whether any DeFi Lending Protocol is appropriate for their use, financial circumstances, or risk tolerance.
(3) Fireblocks provides no guarantee of returns, yields, or interest in connection with any DeFi Lending Protocol. All aspects of lending and borrowing, such as interest rates and liquidation thresholds, are determined entirely by the smart contracts of the applicable DeFi Lending Protocols, which operate outside Fireblocks’ control. Client assumes full responsibility for assessing and accepting all associated risks before initiating any transaction.
(4) Client acknowledges that participation in DeFi Lending Protocols involves inherent and significant risks, including but not limited to: (a) smart contract vulnerabilities, bugs, or exploits that could result in loss of deposited assets; (b) blockchain network failures or congestion; (c) oracle failures or manipulation that may trigger erroneous liquidations or mis-pricing of collateral; (d) market volatility causing collateral to be liquidated at a significant loss; (e) borrower defaults creating protocol-level shortfalls that may not be fully recovered; (f) illiquidity or high-utilization periods during which withdrawals may be delayed or restricted; (g) variable and unpredictable interest rates, yields, and rewards, governed entirely by protocol smart contracts and governance mechanisms over which Fireblocks has no control; (h) unilateral changes by protocol governance participants to parameters such as collateral factors, liquidation thresholds, fee structures, or supported assets; (i) regulatory actions, sanctions designations, or legal proceedings that could restrict Client’s ability to access a DeFi Lending Protocol or withdraw assets; (j) protocol upgrades, forks, or migrations that may alter functionality or require Client to take affirmative action to preserve access to deposited assets; and (k) the irreversible nature of transactions executed on DeFi Lending Protocols, which, once submitted to the applicable blockchain network, cannot be cancelled, reversed, or modified, and are subject to on-chain conditions outside the control of Fireblocks and the relevant protocol. Client acknowledges and agrees that Fireblocks is not responsible for any losses, liabilities, costs, or damages that Client may incur in connection with or as a result of such risks. - Associated Fee(s). Client acknowledges that Staking Services, DeFi Applications, DeFi Lending Protocols, and NP Providers may charge fees, which may be deducted directly from any proceeds, staking rewards, yield, interest, or fiat or digital payments, and/or invoiced separately by the Third Party or by Fireblocks on behalf of the Third Party (“Associated Fee(s)”). Notwithstanding that in certain cases Fireblocks may receive a revenue share, the Associated Fee(s) are determined in the sole discretion of the relevant Third Party.
- Complaints. Any complaint regarding the calculation or distribution of proceeds, yield, interest, or staking rewards, or fiat or digital currencies, including the calculation and/or deduction of any associated fees, should be directed to the Third Party providing the relevant DeFi Application, Staking Service, DeFi Lending Protocols, or the NP Provider. Any complaint regarding the AI Agents, should be directed to the Third Party providing the AI Agents. Fireblocks has no obligation or responsibility to act as intermediary if any complaint or dispute arises between Client and such Third Party in any circumstances. UNDER NO CIRCUMSTANCES WILL FIREBLOCKS BE RESPONSIBLE FOR ANY LOST DIGITAL ASSETS, INCLUDING IF A CONVERSION OR UPGRADE FAILS FOR ANY REASON.
- Content Providers. Various information which is available through access and use of the Services may be obtained and provided from professional businesses or organizations, such as exchanges, market data providers and other content providers (including CoinmarketCap and CoinGecko) (“Content Providers”). Fireblocks and/or such Content Providers are not responsible for, and cannot guarantee, the quality of, or the content available through access and use of the Service, from such Content Providers, including whether it is accurate, complete, reliable, current or error-free. Fireblocks is not liable for any acts or omissions of such Content Providers, including failure to perform to any particular standard.
- DeFi Applications, DeFi Lending Protocol, Staking Services, AI Agent and Network for Payments Connectivity
- Digital Asset Listings.
Digital assets and associated transactions are only reflected in the workspace for those digital assets that Fireblocks has globally or locally listed, or the Client has self-listed. As such, if a digital asset is not listed by Fireblocks, Clients must explicitly self-list in order for them to appear in their asset searches. Where Fireblocks lists a digital asset it does so for Client convenience, saving them having to undertake self-listing. Fireblocks may list (or remove listing of) digital assets in its absolute discretion, and may receive payment from applicable digital asset issuers/foundations for listing their digital asset(s). Notwithstanding, Fireblocks listing of any given digital asset does not constitute an endorsement, promotion, recommendation, or warranty by Fireblocks. Digital assets are highly volatile and may lose value rapidly or become illiquid. Fireblocks makes no representation or warranty as to any digital asset’s value, utility, legality, performance, or suitability for the Client (as listed by Fireblocks or otherwise). The Client is solely responsible for its own assessment of digital assets, and its decisions in relation to them, and should conduct its own independent due diligence. - Blockchain Infrastructure Providers.
Fireblocks may engage with, and procure the services of, blockchain infrastructure service providers in the provision of the Services (including but not limited to node providers, RPC (remote procedure call) providers and MEV (maximal extractable value) protection services). Client acknowledges and understands that Fireblocks may receive a commercial or other benefit (for example, via a revenue share or other means) from such service providers. Notwithstanding, Fireblocks may in its absolute discretion, elect to make use of the services of any such provider over another, for example, in directing transaction(s) to a particular node services provider at any given time. In certain cases, such as MEV protection services (for example) the Client may be able to disable this feature themselves from within the Workspace. - Content Providers.
Various information which is available through access and use of the Services may be obtained and provided from professional businesses or organizations, such as exchanges, market data providers and other content providers (including CoinmarketCap and CoinGecko) (“Content Providers”). Fireblocks and/or such Content Providers are not responsible for, and cannot guarantee, the quality of, or the content available through access and use of the Service, from such Content Providers, including whether it is accurate, complete, reliable, current or error-free. Fireblocks is not liable for any acts or omissions of such Content Providers, including failure to perform to any particular standard.
- Blockchain/Node Errors/Failures. In the event that the Service does not accomplish a transaction due to an error or failure related to any Third Party Service, including the operation of the underlying blockchain or protocol of any supported digital asset (including delays caused by “hashing” and other blockchain errors), Fireblocks is not responsible for any claim, liability, expenses, losses, and/or costs related thereto. Fireblocks shall have no responsibility for any damages caused by a blockchain and/or node downtime or failure.
- Additional Risk Disclosures. Fireblocks has no control over and makes no representations regarding the value of any digital assets, or the security of the underlying networks or protocols. Fireblocks does not own or control the underlying software protocols which govern the operation of digital assets.
- Monitoring. Fireblocks enables Client to utilize its digital assets while stored in the Workspace; however, Fireblocks is an automated platform and does not manually monitor or control the status of transactions or balances within the Workspace. Client must review its own internal ledger and Client Wallet balances to ensure that the transaction is reflected in accordance with the notification provided by the Service prior to reattempting a “FAILED” transaction or crediting an end user if using a reconciliation process following a notification of a “COMPLETED” transaction.
- Deposit Control Feature. Client may customize the number of confirmations required from a blockchain before funds will be credited to Client Wallet by customizing various logical rules within the Service (the “Deposit Control” feature). Client is solely responsible in the event a transaction is unsuccessful in being added to the blockchain in the event it configures the Deposit Control feature to a threshold below the recommended value.
- Supported Tokens & Forks. Fireblocks supports only Supported Tokens. Client shall not attempt to receive, request, send, store, or engage in any other type of transaction involving any token other than a Supported Token. Fireblocks will have no responsibility or liability if Client loses, burns, or otherwise cannot access or control any token that Fireblocks does not support. Additionally, Client acknowledges and agrees that: (i) Fireblocks is not responsible for and makes no representation or warranty with respect to the operation or failure, functionality, security or availability of the underlying digital asset protocols (including but not limited to delays caused by “hashing” and other blockchain errors); and (ii) if a Fork occurs, Fireblocks will not support the forked protocol unless officially announced by Fireblocks, but will allow Client to transfer the affected asset within a commercially reasonable period of time.
- Sanity Testing. Following the setup of each Workspace(s), development or deployment of a new smart contract, minting of a new token, creation of a new Client App, or connection to a new exchange or counterparty, Client must test each such new Workspace(s), smart contract, token, or connection before executing a live transaction to ensure that the functionality is working as intended.
- Privacy. To the extent that Fireblocks processes Personal Data in connection with the provision of the Services under this Agreement, the Parties agree that such processing shall be subject to the terms of our Privacy Policy, available at https://www.fireblocks.com/privacy-policy/ and the Data Processing Agreement (“DPA”) available at: https://www.fireblocks.com/data-processing-agreement, which is hereby incorporated into and made part of this Agreement by reference. In the event of a conflict between this Agreement and the DPA with respect to the processing of Personal Data, the terms of the DPA shall prevail.
From time to time, Fireblocks may make early availability, in-development Services or features (the “Beta Services”) available to Client at no charge. Client may choose to try such Beta Services at its sole discretion. Client acknowledges that the Beta Services may contain bugs or errors and any participation in or use of the Beta Services is at Client’s sole risk. Client acknowledges that Fireblocks may discontinue the Beta Services at any time in its sole discretion, and may never make the Beta Service generally available.
DISCLAIMER OF WARRANTY AND LIABILITY. THE BETA SERVICES ARE PROVIDED “AS-IS,” EXCLUSIVE OF ANY WARRANTY WHATSOEVER WHETHER EXPRESS, IMPLIED, STATUTORY OR OTHERWISE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, FIRBLOCKS DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, AND, NOTWITHSTANDING THE LIMITATION OF LIABILITY SET FORTH IN THE AGREEMENT, FIREBLOCKS DISCLAIMS ALL LIABILITY WITH RESPECT TO ANY BETA SERVICES.
Except to the extent expressly precluded by applicable law, Fireblocks may update these Product Specific Terms from time-to-time. Fireblocks shall notify Client of the change by reasonable means, including posting the revised version at https://www.fireblocks.com/product-specific-terms/ and Client is responsible for regularly visiting the site to review the most current version. Client agrees that its continued use of the Service after the changes become effective shall constitute Client’s acceptance of the revised Product Specific Terms.
- “Beta Services” shall have the meaning prescribed to it in Section VII(1).
- “Cold Wallet” shall have the meaning prescribed to it in Section IV(2).
- “Client Wallet” means wallets that Client creates in the Client Workspace for the purpose of storing Client’s digital assets.
- “DeFi Applications” shall have the meaning prescribed to it in Section V(2)(a)(i).
- “Device” means any supported device controlled by the Client, Users, or End User.
- “Disaster Recovery Kit” means encryption code, which will allow Client or End User unilateral access to the set of keys required to access the digital assets in the Client or End User wallets, without any involvement from Fireblocks.
- “Embedded Wallets” shall have the meaning ascribed to it in Section IV(3).
- “End User” shall have the meaning prescribed to it in Section IV(3).
- “End User Disaster Recovery Kit” shall have the meaning prescribed to it in Section III(3)(b)(iii).
- “End User Keys” shall have the meaning prescribed to it in Section IV(3)(b).
- “End User Private Key Share” shall have the meaning prescribed to it in Section IV(3)(b)(i).
- “End User Recovery Passphrase” shall have the meaning prescribed to it in Section IV(3)(b)(ii).
- “Fork(ed)” refers to a change in protocol rules affecting a digital asset.
- “Help Center” refers to Fireblocks’ Client Help Center:https://support.fireblocks.io/hc/en-us.
- “Owner” means the administrative user appointed by Client as the designated decision maker with ultimate authority over the administration of such Workspace. The Owner will be responsible to set up Client’s Workspace settings unless a different arrangement is agreed between the parties in writing.
- “Personal Data” means any information which is related to an identified or identifiable natural person who can be identified directly or indirectly.
- “Private Key Share” means the key generated by the Service and stored on the Device which is required for the execution for each transaction.
- “Product Specific Terms” shall have the meaning prescribed in the preamble.
- “Recovery Passphrase” means encrypted keys provided to the Client or End User to restore the Private Key Share if the Device is lost or damaged.
- “Staking Service” shall have the meaning prescribed to it in Section V(2)(a)(i).
- “Supported Tokens” are those tokens that may be displayed in the Web Console and listed in the Help Center from time to time.
- “Third Party Services shall have the meaning prescribed to it in Section V(1).
- “Transaction Authorization Policy” is a set of logical rules and controls defined by the Client to govern transaction activity from its Workspace(s).
- “Web Console” is the user interface and information contained there that are made available as part of the Service. “Workspace” means an administrative environment on the Fireblocks platform that enables Client to securely store, manage and administer its holdings of digital assets directly on various blockchains.