Enclave Privacy Policy

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

1 · Who we are

Enclave is operated by Enclave Host, Inc. (“we”). You reach us at support@enclave.host, and for security matters at security@enclave.host. This policy covers the website, the CLI, and the public API. It sits alongside our Terms of Service.

2 · The short version

Your wallet is your account. You use Enclave with a crypto wallet, and paying is an on-chain transaction. We do not run ad trackers, we do not build advertising profiles, and we never sell your data. Most of what the service touches is either already public on a blockchain or kept in your own browser. The parts a third party handles - card payments, sign-in wallets, bot checks - are described below by name.

3 · What we collect

We collect only what running the service needs.

Wallet addresses and public on-chain data. Deployments, payments, and app listings are records on public smart contracts on the Base network. Your wallet address and those transactions are public by the nature of a blockchain - anyone can read them, including us. This is inherent to a non-custodial, on-chain service, not something we choose to store about you.

Passkeys - public keys only, nothing to steal. If you sign in with a passkey, the private key is created and stored on your own device (your phone, laptop, or security key) and never leaves it. We store only the public key, a random credential identifier, and a signature counter - enough to recognize your passkey, never enough to impersonate it. No password, no email address.

Card details - handled entirely by Stripe, never by us. If you pay by card, checkout happens on a Stripe-hosted page. Your card number and payment details go to Stripe, not to Enclave; we never receive, see, or store them. We keep only the order and its payment status.

Kept in your own browser. A session token (proving you signed a wallet challenge) and your deploy narratives - the running log of what you deployed and its output - live in your browser's localStorage on your device. They are not uploaded to us as a profile; they stay client-side and you can clear them at any time.

Ordinary server logs. Like any web service, our infrastructure and the IPFS gateway/relay may briefly log request metadata (such as IP address and timestamps) to serve traffic, defend against abuse, and keep the system healthy. We keep these short and do not use them to build a profile of you.

4 · What we don't collect

We don't ask for your name, we don't run KYC on deployers, and we don't require an account to use the service. We don't hold your funds or your keys (see the Terms), and we don't sell, rent, or trade any data about you to anyone.

5 · Your workload's contents are not visible to us

Enclave runs your app on confidential-computing hardware. The app's memory and the data it processes are encrypted and isolated from the machine's operator - that is the point of the platform, and attestation lets you verify it. So the contents of what your app does (the data it handles, the requests it serves) are not visible to us as the operator, by design. What is public is the on-chain record that a deployment exists and what code it runs, and the metadata needed to route and bill it.

6 · Sub-processors

A few third parties process limited data on our behalf so the service can work, each under its own privacy policy: Stripe for card payments on its hosted checkout page (all card and payment data); and the IPFS gateway and relay infrastructure that serves the content-addressed site and app bytes and routes deployment traffic (ordinary request metadata as above).

Public blockchain networks (Base) and the RPC endpoints used to read and write chain state are not our sub-processors - they are public infrastructure your wallet talks to directly.

7 · How we use what we collect

We use the little we have only to run the service: authenticate you, place and bill deployments, process the payments you initiate, keep abuse off the platform, and answer your support requests. We do not use it for advertising or profiling, and we do not sell it.

8 · Retention

On-chain data is permanent and public - it lives on the blockchain, not on our servers, and cannot be deleted by us or anyone. Browser-side data (your session token and deploy narratives) stays until you clear it or it expires. Server and gateway logs are kept only as long as needed to operate and secure the service, then discarded. Payment data held by Stripe is retained under its own policies.

9 · Your choices

You can use a fresh wallet, sign in with a passkey or a wallet (never an email), pay from a wallet instead of by card, and clear your browser storage at any time to remove the client-side session and narratives. Because the service is non-custodial and account-free, there is little personal data for us to hold in the first place. For any privacy question or request, write to support@enclave.host and we will help.

10 · Changes and contact

We may update this policy; the date above changes when we do. Continuing to use Enclave after a change means you accept it. Questions or requests: support@enclave.host.