Last updated June 15, 2026
This policy explains what data lyra handles when you use the console, CLI, and SDK — and, just as importantly, what it never touches.
We never collect or store your private keys, seed phrases, or funds. The Service is non-custodial — keys stay in your wallet and signing happens on your device. There is no server-side key for the public console.
Wallet address. When you sign in, we verify a wallet signature over a server-issued nonce to establish a session. We store your public wallet address to scope your data to you.
Chat history. If you use the hosted console, your conversations are stored server-side, keyed to your wallet address, so they persist across devices. They are private to your session and not shared with other users.
Operational logs. Standard request and error logs (such as timestamps and status codes) used to keep the Service running and secure.
To answer you, the content of your messages and relevant context is sent to a large language model provider (for example OpenAI, Anthropic, or OpenRouter — or your own provider if you bring your own key). We do not use your conversations to train models. Review your chosen provider’s policies for how they handle requests.
Transactions you execute are recorded on public blockchains by their nature. Anything written to Sui (or any chain) is public and permanent, and outside our control.
We use a session cookie to keep you signed in after wallet-signature verification. We do not use third-party advertising or cross-site tracking cookies.
You can disconnect your wallet at any time, and you can clear your chat history from the console. Self-hosting the open-source CLI/SDK keeps data entirely on your own machine.
We may update this policy as the Service evolves; the “last updated” date reflects the latest version.
This document is provided for transparency and may be updated as the product evolves. It is not legal advice. Questions? Reach us at @lyraai_space.