> For the complete documentation index, see [llms.txt](https://suzuna.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://suzuna.gitbook.io/whitepaper/data-and-privacy.md). # Data & Privacy ### Designed around minimal data collection SUZUNA is built around a simple principle: collect and retain only the information required to operate the product and understand how it is being used. The core product does not require users to provide private wallet credentials or prove ownership of a wallet. #### Wallet Data SUZUNA works with **public BNB Chain wallet addresses**. A wallet address is used to identify the wallet represented by an agent and retrieve relevant on-chain information when a user asks a question. SUZUNA does not require: * Private keys * Seed phrases * Wallet passwords * Transaction signing * Wallet ownership signatures The agent is read-only and cannot move or control assets in the connected wallet. #### Product Data SUZUNA maintains only the product information required for operation and lightweight usage analytics. ### SUZUNA does not store raw Telegram user IDs. When a message arrives, the Telegram ID is hashed using HMAC-SHA256 with a server-side secret and discarded in the same operation. Only the resulting hash is retained. The hash is deterministic, so the same Telegram account always resolves to the same internal user, but it cannot be reversed without the secret. The database on its own cannot be linked back to Telegram accounts. The internal user record contains: Internal user ID \ Hashed Telegram identifier \ Created timestamp \ Last active timestamp No Telegram username, display name, or profile photo is requested or stored at any point. A consequence of this design is that SUZUNA can reply to a user but cannot initiate contact. There are no announcements, alerts, or notifications. **Agents** Each agent record contains: * Agent ID * Internal user ID * Wallet address * Chain * Created timestamp * Last active timestamp * Status An agent represents a specific wallet address and does not contain private wallet credentials. **Usage Events** SUZUNA records lightweight product events required to understand product usage. Supported event types include: * `AGENT_DEPLOYED` * `AGENT_USED` * `AI_QUERY` Each event can contain: * Event ID * Internal user ID * Agent ID * Event type * Timestamp * The content of a user's question is never stored. An event records that a query occurred, not what was asked. Question text is also excluded from application logs. #### Blockchain Data Blockchain information is retrieved when required for a user's query. SUZUNA does not need to permanently store the complete blockchain history of every wallet in its internal database. This approach keeps the product infrastructure focused on the information required to provide the service rather than unnecessarily duplicating public blockchain data. #### Product Metrics The usage events allow SUZUNA to measure product-level metrics such as: * Total Users * Agents Deployed * Active Agents * Weekly Active Users * AI Queries These metrics help the team understand product adoption and usage without requiring unnecessary personal profile information. #### A Read-Only Model SUZUNA is an analysis layer, not a wallet custody system. The platform does not request private keys or seed phrases, and agents do not receive permission to sign or execute blockchain transactions. The architecture is intentionally designed around: **Public wallet data → Analysis → Explanation** rather than: **Wallet access → Asset control** This separation keeps the core product focused on understanding blockchain activity while minimizing the information and permissions required from users. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://suzuna.gitbook.io/whitepaper/data-and-privacy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.