Openfort Developer Terms of Service

Last Updated: January 16, 2026

PLEASE READ THESE DEVELOPER TERMS OF SERVICE ("DEVELOPER TERMS") CAREFULLY BEFORE USING THE SERVICES OFFERED BY ALAMAS LABS INC. D/B/A OPENFORT ("OPENFORT," "WE," "US," OR "OUR"). YOU ("DEVELOPER") HEREBY AGREE TO BE BOUND BY THESE DEVELOPER TERMS (TOGETHER WITH ANY DOCUMENTATION, ORDER FORMS, AND OTHER AGREEMENTS EXECUTED WITH OPENFORT RELATING TO DEVELOPER SERVICES, THE "AGREEMENT") TO THE EXCLUSION OF ALL OTHER TERMS. IF THE TERMS OF THIS AGREEMENT ARE CONSIDERED AN OFFER, ACCEPTANCE IS EXPRESSLY LIMITED TO SUCH TERMS.

BY EXECUTING AN ORDER THAT REFERENCES THESE TERMS, BY ACCESSING OR USING THE SERVICES, OR BY CREATING AN ACCOUNT, YOU ARE ACCEPTING AND AGREEING TO BE BOUND BY AND TO COMPLY WITH THESE TERMS. YOU AGREE TO THESE TERMS PERSONALLY AND ON BEHALF OF ANY COMPANY OR OTHER LEGAL ENTITY THAT YOU REPRESENT. YOU REPRESENT AND WARRANT THAT YOU HAVE THE RIGHT, AUTHORITY, AND CAPACITY TO ENTER INTO THIS AGREEMENT AND TO BIND ANY SUCH COMPANY OR LEGAL ENTITY.

ARBITRATION NOTICE: THESE TERMS CONTAIN AN ARBITRATION AGREEMENT IN SECTION 15, WHICH WILL REQUIRE YOU TO SUBMIT CLAIMS YOU HAVE AGAINST OPENFORT TO BINDING ARBITRATION. UNDER THE ARBITRATION AGREEMENT, YOU WILL ONLY BE PERMITTED TO PURSUE CLAIMS AGAINST OPENFORT ON AN INDIVIDUAL BASIS, NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS OR REPRESENTATIVE ACTION OR PROCEEDING.

1. Definitions

"API Keys" means the unique authentication credentials provided to Developer to access and use the Services.
"Authentication Credentials" means private keys, API key credentials, passkeys, email or SMS authentication codes, hardware authentication devices, or any other codes, secrets, or authentication methods that Developer or End Users utilize to access Wallets or any part of the Services.
"Authorized User" means an employee, contractor, agent, or representative of Developer who is authorized by Developer to access and use the Services on Developer's behalf.
"Confidential Information" means all non-public information disclosed by either party to the other, whether orally or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure.
"Delegated Actions" means functionality that enables Developer to sign transactions or perform actions on behalf of End Users who have granted explicit permission for such delegation through the Services.
"Developer Application" means any application, website, or service developed or operated by Developer that utilizes the Services to authenticate users, manage Wallets, or interact with blockchain networks.
"Developer Data" means any data, information, or other material provided, uploaded, or submitted by Developer or its End Users to the Services in the course of using the Services.
"Digital Assets" means digital currencies, cryptocurrencies, tokens, non-fungible tokens (NFTs), stablecoins, and other blockchain-based assets.
"Documentation" means the user manuals, specifications, API documentation, and implementation guides available at https://www.openfort.io/docs, as may be updated from time to time.
"End Users" means the users of Developer Applications who are authenticated or interact with Wallets via the Services.
"OpenSigner" means Openfort's open-source, client-side signing solution that enables self-custodial wallet implementation where private keys are generated and stored exclusively on the End User's device.
"Order Form" means any ordering document, online registration, or written agreement executed between Developer and Openfort that references these Developer Terms and specifies the Services, fees, and any additional terms.
"Private Key" means an asymmetric, cryptographic key that is secret and is used as part of a public-key cryptographic algorithm to sign transactions and control Digital Assets.
"Protocol" means a blockchain network or distributed ledger on which transactions with Digital Assets are recorded.
"Services" means Openfort's wallet infrastructure services, APIs, SDKs, and related tools as described in the Documentation and made available to Developer under this Agreement.
"TEE Backend Wallets" means server-side wallets secured via Trusted Execution Environment (TEE) technology, where cryptographic operations occur within isolated, secure enclaves and Openfort does not have access to raw Private Keys.
"Term" means the period during which Developer is authorized to access and use the Services under this Agreement.
"Wallet" means a digital wallet that secures cryptographic keys enabling the signing of messages and transactions, including control of Digital Assets on blockchain networks.

2. Access to Services

2.1 License Grant

Subject to Developer's compliance with the terms and conditions of this Agreement, Openfort grants Developer a non-exclusive, limited, personal, non-sublicensable, non-transferable right and license to internally access and use the Services during the applicable Term for Developer's internal business purposes, only as provided herein and only in accordance with the Documentation.

2.2 API Keys and Authentication

To access the Services, Developer will receive API Keys. Developer is responsible for:

Maintaining the confidentiality of all API Keys and Authentication Credentials
All activities that occur using Developer's API Keys, whether or not authorized by Developer
Implementing appropriate security measures to protect API Keys in accordance with industry best practices
Notifying Openfort immediately of any unauthorized use or security breaches at security@openfort.io

2.3 Service Updates

Openfort may provide updates, patches, enhancements, or fixes for the Services without additional charge. Developer understands that Openfort may make improvements and modifications to the Services at any time; provided that Openfort shall use commercially reasonable efforts to give Developer reasonable prior notice of any material changes that might adversely impact Developer's use of the Services.

3. Wallet Services

Openfort provides non-custodial wallet infrastructure services. Developer acknowledges and agrees that Openfort does not store, manage, or control any Private Keys, funds, or Digital Assets on behalf of Developer or End Users except as expressly described in this Section 3.

3.1 OpenSigner (Client-Side Wallets)

OpenSigner is Openfort's open-source, client-side signing solution. When implementing OpenSigner:

Non-Custodial Nature. Private Keys are generated and stored exclusively on the End User's device. Openfort never has access to, stores, or transmits End Users' Private Keys.
Developer Responsibilities. Developer is responsible for properly implementing OpenSigner in accordance with the Documentation, including implementing appropriate key backup and recovery mechanisms as needed for the Developer Application.
End User Responsibilities. End Users are solely responsible for safeguarding their Authentication Credentials, Private Keys, and recovery phrases. Developer shall inform End Users that loss of these credentials may result in permanent loss of access to their Wallets and Digital Assets.
No Recovery Capability. Openfort cannot assist with recovering Private Keys or Authentication Credentials for OpenSigner implementations, as Openfort does not have access to this information.

3.2 TEE Backend Wallets

Openfort offers server-side wallet functionality secured via Trusted Execution Environment (TEE) technology powered by Google Cloud Platform Confidential Computing infrastructure. When using TEE Backend Wallets:

TEE Isolation. All cryptographic operations, including key generation and transaction signing, occur within secure, isolated TEE enclaves. Openfort does not have access to raw Private Keys at any time.
Non-Custodial Architecture. While Private Keys are generated and stored within Openfort's TEE infrastructure, Openfort cannot access, view, or extract the raw Private Keys due to TEE isolation. Developer retains control through authenticated API access.
Use Cases. TEE Backend Wallets are suitable for backend automation, programmatic signing, and scenarios where server-side key management is required.
Developer Configuration. Developer is solely responsible for configuring access controls, permissions, and security policies for TEE Backend Wallets in accordance with the Documentation.

3.3 Delegated Actions

Delegated Actions enable Developer to sign transactions on behalf of End Users who have granted explicit permission.

IMPORTANT: IF DEVELOPER ENABLES DELEGATED ACTIONS, DEVELOPER ASSUMES FULL RESPONSIBILITY FOR THE FOLLOWING:

User Disclosure. Developer is responsible for providing all necessary notices and disclosures to End Users regarding Delegated Actions. Developer must describe to End Users—in a manner that is accurate, clear, and concise—exactly how Delegated Actions will function, including the specific rights that Developer will have to sign transactions on behalf of the End User.
Consent Acquisition. Developer must obtain explicit, informed consent from End Users before enabling Delegated Actions. Such consent must clearly specify the scope and limitations of the delegation.
Scope Limitations. Developer shall not exceed the scope of permissions granted by End Users and shall implement appropriate controls to prevent unauthorized actions.
Revocation Mechanisms. Developer must provide End Users with clear mechanisms to revoke Delegated Actions at any time.
No Openfort Responsibility. Openfort is not responsible for providing notices to, or obtaining consents from, any End User in connection with Delegated Actions. Openfort makes no guarantee regarding the configuration of Delegated Actions and disclaims all liability arising from Developer's implementation or use of Delegated Actions.
Regulatory Considerations. Developer acknowledges that depending on the configuration of Delegated Actions, such services may or may not be deemed self-custodial under applicable law. Developer is solely responsible for ensuring compliance with all applicable laws and regulations regarding custody and control of Digital Assets.

3.4 Implementation Requirements

Developer must implement the Services in accordance with the Documentation to ensure security and proper functioning. This includes:

Following Openfort's security protocols for key management and API integration
Implementing proper user authentication flows
Maintaining appropriate error handling and user notifications
Handling End User data securely and in compliance with applicable privacy laws

3.5 Risk Acknowledgment

Developer acknowledges and agrees that using blockchain technology and Digital Assets involves significant risks, including: (i) price volatility and potential total loss of value; (ii) irreversibility of transactions; (iii) regulatory uncertainty; (iv) technological failures in blockchain networks; (v) smart contract vulnerabilities; and (vi) loss of access due to lost credentials. Openfort shall not be liable for any losses arising from these inherent risks, and Developer agrees to communicate these risks to End Users.

4. Developer Obligations

4.1 General Obligations

Developer shall:

Use the Services in compliance with all applicable laws, regulations, and this Agreement
Ensure that all Authorized Users comply with this Agreement
Be responsible for the accuracy, integrity, and legality of all Developer Data
Prevent unauthorized access to or use of the Services and notify Openfort promptly of any unauthorized access
Obtain all necessary consents and provide all necessary notices to End Users as required by applicable law and this Agreement

4.2 Security Requirements

Developer must maintain appropriate security measures, including:

Secure storage and transmission of API Keys and sensitive data
Regular security updates and vulnerability patching
Monitoring for and responding to security incidents
Compliance with industry security standards appropriate to the nature of the Developer Application

4.3 End User Notification Requirements

Developer is responsible for informing End Users about:

The non-custodial nature of the Wallet services
End User's sole responsibility for safeguarding Authentication Credentials and Private Keys
The risks associated with Digital Assets and blockchain technology
If applicable, the scope and operation of any Delegated Actions
That Openfort cannot recover lost Private Keys or Authentication Credentials

4.4 Compliance Requirements

Developer represents and warrants that:

Developer, its Authorized Users, and its End Users are not located in, organized in, or residents of any country subject to comprehensive U.S. economic sanctions or an arms embargo (including Cuba, Iran, North Korea, Syria, and the Crimea, Donetsk, and Luhansk regions of Ukraine)
Developer will comply with all applicable anti-money laundering (AML), counter-terrorism financing, and economic sanctions laws and regulations
Developer will not use the Services for any illegal activities or to facilitate illegal transactions
Developer will implement appropriate compliance controls proportionate to the nature and risk profile of the Developer Application

4.5 Data Protection

Developer shall comply with all applicable data protection and privacy laws in connection with Developer's use of the Services, including obtaining all necessary consents from End Users for the collection and processing of their personal data. Developer shall maintain a privacy policy that clearly discloses to End Users what data is collected and how it is used.

5. Fees and Payment

5.1 Fees

Developer shall pay Openfort fees for the Services as set forth in the applicable Order Form or Openfort's pricing page at https://www.openfort.io/pricing ("Fees"). All Fees shall be invoiced monthly in arrears unless otherwise specified. All Fees paid are non-refundable except as expressly provided in this Agreement.

5.2 Payment Terms

Unless otherwise specified in an Order Form:

All invoices are payable in U.S. dollars within thirty (30) days from the date of invoice
Openfort may use a third-party payment processor, and Developer agrees to the terms and conditions of such payment processor
Past due invoices are subject to interest at the rate of 1.5% per month, or the maximum rate permitted by law, whichever is lower
Developer shall maintain accurate and current billing information

5.3 Taxes

The Fees are exclusive of, and Developer will be solely responsible for, all applicable taxes, including any sales, use, excise, value-added, goods and services, consumption, and other similar taxes or duties (excluding taxes based on Openfort's net income). If any payment is subject to withholding tax, Developer will reimburse Openfort for such withholding tax.

6. Enterprise Services

6.1 Enterprise Agreements

For Developers requiring custom terms, enhanced support, or volume pricing, Openfort offers enterprise agreements. Enterprise terms are established through separate Order Forms that reference these Developer Terms. In the event of any conflict between an Order Form and these Developer Terms, the Order Form shall control with respect to the specific Services covered by that Order Form.

6.2 Managed Services

Openfort may offer managed services, including custom development, dedicated support, and implementation assistance, as specified in an Order Form. Such managed services are subject to additional fees and terms as set forth in the applicable Order Form.

6.3 Service Level Agreements

Custom service level agreements (SLAs) may be negotiated and included in an Order Form for enterprise customers. In the absence of a custom SLA, Openfort will use commercially reasonable efforts to maintain the availability of the Services.

7. Restrictions

Developer shall not (and shall not allow any third party to):

Reverse engineer, decompile, disassemble, or otherwise attempt to discover the source code, object code, or underlying structure, ideas, or algorithms of the Services (except to the extent applicable laws specifically prohibit such restriction)
Modify, translate, or create derivative works based on the Services
Copy, rent, lease, distribute, pledge, assign, or otherwise transfer or encumber rights to the Services
Use the Services for the benefit of a third party other than End Users of the Developer Application
Remove or alter any proprietary notices or labels from the Services
Use the Services to build a competitive product or service
Interfere with or disrupt the Services or attempt to gain unauthorized access
Use the Services for any illegal activities or to facilitate illegal transactions
Share API Keys or access credentials with unauthorized third parties
Exceed any rate limits or usage restrictions specified in the Documentation
Configure Delegated Actions in a manner that is misleading or intended to divert, misappropriate, or otherwise obtain unauthorized access to Digital Assets

8. Intellectual Property

8.1 Openfort Property

All rights, title, and interest in and to the Services, including all intellectual property rights therein, remain with Openfort and its licensors. Developer's use of the Services does not grant Developer ownership of any intellectual property rights in the Services. No rights are granted to Developer except as expressly set forth in this Agreement.

8.2 Developer Data

As between Developer and Openfort, Developer shall retain all right, title, and interest in and to the Developer Data, including all intellectual property rights therein. Developer grants Openfort a non-exclusive, worldwide license to use, copy, and process Developer Data solely as necessary to provide the Services and as otherwise described in Openfort's Privacy Policy.

8.3 Feedback

If Developer provides suggestions, comments, or other feedback regarding the Services ("Feedback"), Developer grants Openfort a non-exclusive, worldwide, perpetual, irrevocable, transferable, sublicensable, royalty-free license to use and incorporate such Feedback into the Services without obligation to Developer.

8.4 Marketing Rights

Developer grants Openfort a license to use and display Developer's name and logo for marketing purposes, including identifying Developer as a customer of Openfort. Developer may revoke this license by providing written notice to Openfort.

9. Confidentiality

9.1 Definition

"Confidential Information" means all non-public information disclosed by either party (the "Disclosing Party") to the other party (the "Receiving Party"), whether orally or in writing, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. Confidential Information includes business plans, technical data, product roadmaps, pricing, customer information, and trade secrets. Confidential Information does not include information that: (a) is or becomes publicly available without breach of this Agreement; (b) was known to the Receiving Party prior to disclosure; (c) is received from a third party without breach of any confidentiality obligation; or (d) is independently developed by the Receiving Party without use of the Confidential Information.

9.2 Protection

The Receiving Party shall:

Use the same degree of care to protect the Disclosing Party's Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care
Not use Confidential Information for any purpose outside the scope of this Agreement
Limit access to Confidential Information to employees, contractors, and agents who need such access and who are bound by confidentiality obligations at least as restrictive as those herein
Promptly notify the Disclosing Party of any unauthorized disclosure

9.3 Compelled Disclosure

The Receiving Party may disclose Confidential Information if required by law, provided that the Receiving Party gives the Disclosing Party prompt notice (to the extent legally permitted) and reasonable assistance if the Disclosing Party wishes to contest the disclosure.

10. Third-Party Services

The Services may operate with or utilize third-party services, including cloud infrastructure providers. Openfort's TEE Backend Wallets utilize Google Cloud Platform Confidential Computing infrastructure. Developer acknowledges that: (a) Openfort is not responsible for the operation of any third-party services; (b) the availability of the Services may depend on third-party services; and (c) Developer is solely responsible for complying with any applicable terms of third-party services that Developer chooses to integrate with the Developer Application.

11. Warranties and Disclaimers

11.1 Mutual Warranties

Each party represents and warrants that: (a) it is duly organized and validly existing under the laws of its jurisdiction; (b) it has full power and authority to enter into this Agreement; and (c) this Agreement constitutes a valid and binding obligation.

11.2 Developer Warranties

Developer represents and warrants that: (a) Developer has all rights and consents necessary to provide Developer Data to Openfort; (b) Developer's use of the Services will comply with all applicable laws; and (c) the Developer Application will not infringe or misappropriate any third-party rights.

11.3 Disclaimer

THE SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. OPENFORT DOES NOT WARRANT THAT THE SERVICES WILL BE UNINTERRUPTED OR ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT THE SERVICES ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. OPENFORT SPECIFICALLY DISCLAIMS ANY AND ALL LIABILITY FOR OR IN CONNECTION WITH: (A) THE SECURITY, VALUE, OR CONTROL OF ANY DIGITAL ASSETS; (B) ANY BLOCKCHAIN NETWORK OR PROTOCOL; (C) ANY ACTIONS OR INACTIONS OF END USERS; OR (D) THE CONFIGURATION OR IMPLEMENTATION OF DELEGATED ACTIONS BY DEVELOPER.

12. Indemnification

12.1 Developer Indemnification

Developer shall defend, indemnify, and hold harmless Openfort and its officers, directors, employees, and agents from and against all claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising from or related to: (a) Developer's breach of this Agreement; (b) Developer's violation of any applicable law; (c) Developer Data; (d) the Developer Application; (e) Developer's configuration or implementation of Delegated Actions; (f) any claim by an End User relating to Developer's services; or (g) any negligence or willful misconduct by Developer.

12.2 Openfort Indemnification

Openfort shall defend, indemnify, and hold harmless Developer from and against all claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising from any third-party claim that Developer's use of the Services as permitted under this Agreement infringes or misappropriates such third party's intellectual property rights, provided that Openfort shall have no liability to the extent the claim arises from: (a) Developer Data; (b) Developer's modification of the Services; (c) Developer's combination of the Services with other products or services not provided by Openfort; or (d) Developer's use of the Services in violation of this Agreement.

12.3 Procedures

The indemnified party shall: (a) provide prompt written notice of the claim; (b) grant the indemnifying party sole control of the defense and settlement; and (c) provide reasonable assistance at the indemnifying party's expense. The indemnifying party shall not settle any claim without the indemnified party's consent if the settlement would impose any liability or obligation on the indemnified party.

13. Limitation of Liability

13.1 Exclusion of Damages

IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, REVENUE, DATA, OR BUSINESS OPPORTUNITY, ARISING OUT OF OR RELATED TO THIS AGREEMENT, REGARDLESS OF WHETHER SUCH DAMAGES WERE FORESEEABLE OR WHETHER EITHER PARTY WAS ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

13.2 Liability Cap

EXCEPT FOR EACH PARTY'S INDEMNIFICATION OBLIGATIONS AND DEVELOPER'S PAYMENT OBLIGATIONS, IN NO EVENT SHALL EITHER PARTY'S TOTAL AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT EXCEED THE TOTAL FEES PAID OR PAYABLE BY DEVELOPER TO OPENFORT IN THE TWELVE (12) MONTHS PRECEDING THE DATE ON WHICH THE CLAIM AROSE.

13.3 Digital Asset Disclaimer

OPENFORT SHALL HAVE NO LIABILITY FOR ANY LOSS, THEFT, OR COMPROMISE OF PRIVATE KEYS, AUTHENTICATION CREDENTIALS, OR DIGITAL ASSETS, EXCEPT TO THE EXTENT CAUSED BY OPENFORT'S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT. DEVELOPER ACKNOWLEDGES THAT OPENFORT IS A NON-CUSTODIAL SERVICE PROVIDER AND DOES NOT HAVE ACCESS TO OR CONTROL OVER END USERS' PRIVATE KEYS OR DIGITAL ASSETS.

14. Term and Termination

14.1 Term

This Agreement commences upon Developer's acceptance and continues until terminated in accordance with this Section 14. Unless otherwise specified in an Order Form, the Term consists of successive one (1) month periods unless either party provides written notice of non-renewal at least thirty (30) days prior to the end of the then-current period.

14.2 Termination for Cause

Either party may terminate this Agreement: (a) upon thirty (30) days' written notice if the other party materially breaches this Agreement and fails to cure such breach within the notice period; or (b) immediately upon written notice if the other party becomes insolvent, makes an assignment for the benefit of creditors, or becomes subject to bankruptcy proceedings. Openfort may also suspend or terminate Developer's access immediately upon notice if Developer's use of the Services poses a security risk or violates applicable law.

14.3 Effect of Termination

Upon termination or expiration of this Agreement:

All rights granted to Developer under this Agreement will immediately cease
Developer must cease all use of the Services and delete all API Keys and cached data
Developer remains liable for any outstanding fees
Openfort will make commercially reasonable efforts to enable Developer and End Users to export their data and Wallet access credentials for a period of thirty (30) days following termination, provided Developer has properly implemented such export functionality in accordance with the Documentation

14.4 Survival

The following Sections shall survive termination: Definitions, Intellectual Property, Confidentiality, Warranties and Disclaimers, Indemnification, Limitation of Liability, Effect of Termination, and General Provisions.

15. Dispute Resolution

15.1 Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of Delaware, without regard to its conflict of laws principles.

15.2 Arbitration

Any dispute arising out of or relating to this Agreement shall be resolved by binding arbitration administered by JAMS under its Streamlined Arbitration Rules and Procedures. The arbitration shall be conducted by a single arbitrator in Wilmington, Delaware. The arbitrator's decision shall be final and binding, and judgment on the award may be entered in any court having jurisdiction. Each party shall bear its own costs, and the parties shall share equally the fees of the arbitrator and JAMS.

15.3 Class Action Waiver

DEVELOPER AND OPENFORT AGREE THAT EACH MAY BRING CLAIMS AGAINST THE OTHER ONLY IN AN INDIVIDUAL CAPACITY AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY PURPORTED CLASS OR REPRESENTATIVE PROCEEDING.

15.4 Equitable Relief

Notwithstanding the foregoing, either party may seek injunctive or other equitable relief in any court of competent jurisdiction to protect its intellectual property rights or Confidential Information.

16. General Provisions

16.1 Entire Agreement. This Agreement, including any Order Forms, constitutes the entire agreement between the parties regarding the subject matter hereof and supersedes all prior agreements, proposals, and communications. In the event of a conflict between these Developer Terms and an Order Form, the Order Form shall control.
16.2 Modifications. Openfort may modify these Developer Terms at any time by posting the modified terms on the Openfort website or by providing notice to Developer. Material changes will become effective thirty (30) days after notice. Continued use of the Services after the effective date constitutes acceptance of the modified terms.
16.3 Assignment. Developer may not assign or transfer this Agreement without Openfort's prior written consent. Openfort may assign this Agreement in connection with a merger, acquisition, or sale of all or substantially all of its assets. This Agreement shall bind and inure to the benefit of the parties and their permitted successors and assigns.
16.4 Notices. All notices under this Agreement shall be in writing and shall be deemed given when delivered by email to the address associated with Developer's account or, for notices to Openfort, to legal@openfort.io.
16.5 Waiver. No failure or delay by either party in exercising any right under this Agreement shall constitute a waiver of that right.
16.6 Severability. If any provision of this Agreement is held to be invalid or unenforceable, such provision shall be modified to the minimum extent necessary to make it valid and enforceable, and the remaining provisions shall continue in full force and effect.
16.7 Force Majeure. Neither party shall be liable for any failure or delay in performance due to causes beyond its reasonable control, including acts of God, natural disasters, war, terrorism, labor disputes, government actions, internet or telecommunications failures, or blockchain network failures or congestion.
16.8 Independent Contractors. The parties are independent contractors. This Agreement does not create a partnership, joint venture, agency, or employment relationship between the parties.
16.9 No Third-Party Beneficiaries. This Agreement is for the sole benefit of the parties and their permitted successors and assigns. Nothing in this Agreement shall confer any rights upon any third party.

17. Contact Information

For questions about these Developer Terms or the Services, please contact:

Openfort (Alamas Labs Inc.)
Email: legal@openfort.io
Website: https://www.openfort.io
Documentation: https://www.openfort.io/docs