Enclave Terms of Service

Last updated: July 14, 2026 · applies to enclave.host and the Enclave public API

1 · The service

Enclave (operated by Enclave Host, Inc., “we”) lets you deploy WebAssembly apps to confidential-computing hardware, paid for per unit of runtime. Deployments are records on public smart contracts on the Base network; independent enclave machines claim and run them. By creating, funding, or operating a deployment - from this site, the CLI, or the API - you agree to these terms.

2 · Eligibility and sanctions

To use Enclave you must be old enough to form a binding contract where you live - at least the age of majority in your jurisdiction. Each time you deploy, you represent that you are not on any sanctions or denied-party list; that you are not located in, ordinarily resident in, or acting on behalf of anyone in a country or region subject to comprehensive sanctions or embargo; and that you will not use the platform in violation of applicable export-control or sanctions law. We may refuse, suspend, or stop serving deployments to comply with those laws.

3 · Payments are crypto-only

Runtime is paid for in one of two ways, both up front: USDC on the Base network, sent from a wallet you control straight to our treasury, or by card on a Stripe-hosted checkout page. There are no subscriptions and no stored payment methods on our side. Card payments buy a specific order of runtime; they never buy, hold, or convert cryptocurrency for you, and we never send cryptocurrency to customers.

4 · Payments are non-custodial

You pay directly from your own wallet by signing on-chain transactions. We never hold your funds and never have access to your keys. Funding a deployment forwards your payment in the same transaction; nothing is escrowed or held on your behalf. The “balance” a deployment shows is prepaid runtime - an accounting number on a public smart contract - not money in an account.

Some catalog apps charge a publisher fee, set by the app's publisher and shown in the hourly rate before you sign. When you fund a deployment of such an app, the publisher's share of that payment forwards directly to the publisher's wallet in the same transaction. That share is a payment from you to that publisher - an independent third party - not to us; we never hold it either, and it is as final as every other payment here.

5 · Payments are final

Blockchain transactions are irreversible, and so are payments here: all payments are final. There are no refunds, chargebacks, or reversals, and prepaid runtime cannot be converted back into funds. Runtime you have paid for is consumed as your deployment runs; if a runner fails mid-lease, up to one lease interval of prepaid time can be lost. Double-check the app, the shares, and the amount before you sign - the chain will not give it back.

6 · No guarantee of uptime or availability

The service is provided “as is” and “as available”, with no guarantee of uptime, availability, or performance and no service-level agreement. Enclave hardware can fail, restart, or be withdrawn; the platform, its APIs, and this site can be interrupted, degraded, or discontinued at any time. The failover design lets another enclave take over a funded deployment, but we do not promise that one will be available, that takeover will be timely, or that your app will run continuously. Do not run anything here whose downtime you cannot tolerate, and keep your own copies of anything you cannot afford to lose.

7 · Your apps and your use

You are responsible for what you deploy and for the traffic it serves. Do not use the platform for anything unlawful, for attacking others, or for content or workloads you do not have the rights to run. Apps in the catalog are published by third parties: a catalog listing (or approval) means the record is well-formed, not that we endorse the app or vouch for what it does - attestation lets you verify what code runs, and that is the guarantee on offer. If you publish an app that charges a publisher fee, the price you set is yours, and so are any obligations that come with receiving it (including taxes); we route your share of each funding to your wallet, we never hold it, and payments to you are as final as every other payment here. We may refuse, suspend, or stop serving deployments that break these terms or threaten the platform.

8 · Privacy and data

Enclave is crypto-native and non-custodial, so there is very little personal data for us to hold. What the service does touch - wallet addresses and public on-chain records, passkey or wallet sign-in, card payments handled entirely by Stripe, and browser-side session state - is set out in our Privacy Policy. Because your app runs on confidential-computing hardware, the contents of what it processes are not visible to us as the operator; see the Privacy Policy for the details.

9 · Disclaimers and liability

To the maximum extent permitted by law, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement; and our total liability to you for any claim arising out of the service is limited to the amount you paid for the deployment giving rise to the claim in the thirty days before it arose. Nothing here limits liability that cannot lawfully be limited. You use public blockchains, cryptocurrency, and confidential-computing hardware at your own risk.

10 · Governing law and disputes

These terms are governed by the laws of the State of Delaware, without regard to its conflict-of-laws rules. Before starting any formal proceeding, you agree to first try to resolve the dispute informally: email support@enclave.host with a short description of the issue and give us at least 30 days to work it out. If it cannot be resolved that way, the dispute will be settled by binding arbitration on an individual basis, administered by the American Arbitration Association (AAA) under its Commercial Arbitration Rules, seated in Wilmington, Delaware, rather than in court - except that either party may still bring an individual claim in small-claims court, or seek injunctive relief to stop misuse of the platform.

11 · Changes and contact

We may update these terms; the date above changes when we do, and deploy surfaces will ask for your agreement again. Continuing to deploy after a change means you accept it. Questions: support@enclave.host.