Privacy Policy

Effective 9 October 2026. Blockle is non-custodial, open-source software. This policy explains the little data the Blockle website and apps touch. It is written in plain language and is not legal advice.

The short version

We never hold your keys, seeds, funds, or wallet passwords. They are generated and stored on your device, encrypted (scrypt + AES-256-GCM), and are never transmitted to us.
We do not perform KYC and do not collect your name, email, or identity to use the wallets or the non-custodial exchange.
Your AI-agent provider key (if you connect one) stays in your device's encrypted vault and is sent only to the AI provider you chose (e.g. Anthropic/OpenAI), never to us.

What is processed

Public blockchain data. Transactions you broadcast are recorded on public ledgers (BLOCK and the chains you use). That data is public and permanent by design — not controlled by us.
Server logs. Like any website, blockle.org and exchange.blockle.org web servers log standard request metadata (IP address, timestamp, user agent, URL) transiently for security and operations.
Node / RPC / indexer calls. To show balances and tokens the apps query configurable providers (public RPCs, Esplora, and — if you enable it — Alchemy). Those third parties receive the addresses/requests you look up under their own policies. You can change or self-host every endpoint in settings.
Optional, anonymized agent telemetry. The in-wallet agent can send anonymized, bucketed performance stats (strategy, venue, P&L %, size bucket) to improve the product. It is off by default, contains no keys, seeds, credentials, or raw addresses, uses a rotating pseudonymous id, and you can leave it off.

What we do NOT collect

Private keys, seed phrases, wallet passwords, AI provider credentials, and personal identity information. There is no account to create to use the wallets.

Cookies

The marketing site uses only essential cookies/local storage needed for the pages to work. The exchange uses a session cookie after you sign in with your wallet signature.

Your choices

Use your own RPC/indexer endpoints, keep agent telemetry off, and remember that on-chain activity is public. You control your keys and data on your device.

Contact

Questions: Discord or GitHub.