Privacy Policy
BuildOS is non-custodial. In plain terms: we never see, request, or store your private keys or seed phrase — ever, under any circumstance.
How wallet connections work
When you connect MetaMask or OKX Wallet, the browser extension shares only your public wallet address with BuildOS. When you sign a transaction, the signing happens entirely inside your wallet extension — the private key never leaves it and never touches our frontend or servers. We only ever receive the signed transaction hash after you've approved it.
What we do store
- Your public wallet address (already public on the blockchain)
- The natural-language description you type in and its compiled agent config
- Transaction hashes and agent status, once committed on X Layer testnet
All of the above is inherently public, pseudonymous blockchain data. None of it identifies you personally unless you choose to make that link yourself.
What we never do
- Ask for or accept a pasted private key or seed phrase, anywhere in the product
- Sign transactions on your behalf without an explicit wallet approval popup
- Sell, share, or monetize wallet or usage data with third parties
- Track you across other sites
Escrow & onchain data
If you use escrow, your deposit amount, unlock time, depositor address, and recipient address are recorded on the EscrowVault smart contract, permanently and publicly visible on the X Layer blockchain — this is inherent to how public blockchains work, not something BuildOS separately stores or controls. We don't attach names or off-chain identity to this data.
Demo Mode
Demo Mode lets judges and visitors explore BuildOS using an account we control, pre-seeded with real testnet agents, so you don't need to install or fund a wallet to see it work. See our Demo Mode disclosure for details.
Contact
Questions about this policy — reach out via the GitHub repo.