Privacy Policy

Signing in with your wallet doesn't give us your email, name, or any identity information — just your public wallet address. When you place an order, we also store:

• The plan you ordered and its price.
• Your Telegram user ID (so your agent knows who to talk to) and your Telegram bot token (encrypted at rest).
• Your OpenRouter API key, encrypted at rest.
• The on-chain transaction hash for your payment, and your order's provisioning status (VPS IP, install progress).

Strictly to run the service: verifying your payment on-chain, provisioning your VPS, wiring your agent up to OpenRouter and your Telegram bot, and showing your order status in your dashboard. We don't sell your data, and we don't use it for advertising or marketing.

No email address, no password, no name or physical address, and no third-party analytics or ad-tracking scripts run on this site. See our Cookie Policy for the two cookies we do use — both are functional, not tracking.

Order data lives in a Postgres database (Supabase). Your OpenRouter key and Telegram bot token are encrypted before they're stored, and are only ever decrypted server-side when needed to provision or run your agent. Row-level security is enabled on every table — nothing is reachable directly from a browser, only through our server-side code.

A few services are load-bearing for the app to work:

• Reown / WalletConnect — powers the wallet connection modal.
• Robinhood Chain RPC — used to verify your on-chain payment.
• Telegram — your agent messages you through the bot you provide; we don't use Telegram for anything else.
• Supabase — hosts our database.

You can ask us to delete your order history and stored credentials at any time — message us on Telegram or X from the wallet address on the account.

If this policy changes in a material way, we'll update the date at the top of this page.