Privacy and data use
Updated 13 October 2026
What the bot stores
The bot stores your Telegram user ID and, during wallet verification, your Telegram name/username and linked public wallet address. It also stores verification nonces, cached balance and tier, usage counters, AIF price alerts, private research notes, token observations and change events. Selected networks, temporary menu input state, and your private per-network wallet nicknames, tags, notes and bookmarks are saved for the bot menu. Nicknames are not passed to blockchain or AI providers; Telegram receives them in your private notifications. AIFOLD does not request seed phrases or private keys.
What is sent to providers
Telegram handles bot messages. Blockchain RPC, explorer, market-data, security and historical-price providers receive public addresses or transaction queries. Abacus.AI provides hosting and AI completions. Your /ask question, retrieved public token/wallet/portfolio facts, and project research question with retrieved page text can be sent to the AI provider. When configured, Brave receives your public project search query. Private token-watch notes, wallet nicknames, tags and notebook notes are not included in public shared reports or group summaries and are not sent for grounded explanations. Short-lived address context and your explanation-mode choice are stored privately. Project questions should not contain private information. AIFOLD cannot delete provider-held records through /forget; provider retention follows their separate policies.
Public cards, group mode and API
Shared report pages and images contain only cached public token observations. Group scanning requires a group administrator to enable it; the queue stores group chat ID, token address, network and public report text, not the sender’s private notebook. Queued group cards are removed after seven days when the worker runs. Read-only API keys are stored as SHA-256 digests with expiry and revocation state. A key is displayed once in your private Telegram chat when you explicitly request /api on; do not forward that message. The research API returns public token or shared P&L data, never private nicknames or notes.
Visibility
Research notes, history, wallet status and data-deletion commands work only in a private chat with the bot. Commands posted in a group are visible to that group. A public wallet is on-chain data; linking it to a Telegram account is a separate record stored by the service. The public activity panel exposes only service timestamps, not account identities.
Retention and deletion
Account records, watch labels, documentary claim results, and wallet performance history remain until you remove them. /unwatch, /unwallet, /unclaim and /pnlremove delete their corresponding records and events. Stopping an alarm keeps your nickname; /forgetwallet removes that private notebook entry; /forget DELETE also removes nicknames, tags, notes, API keys and selected networks. Pending input expires after 15 minutes and is cleared by cancellation or network changes. /digest off removes your daily briefing preference. /unlink disconnects the wallet and pauses all monitoring but retains research. Shared wallet analyses contain public addresses and calculations, with no Telegram identities or private nicknames; the directory job removes analyses not requested for 30 days. Shared source caches contain public research or prices rather than Telegram identities. Monthly project knowledge retains its last reviewed public summary through outages. Anonymous cost estimates contain no questions, wallet links or Telegram IDs. Scheduled jobs remove sent events after 30 days, expired quotas after seven days and other research caches one day after expiry. Cleanup requires the jobs to run. Backups and provider records follow separate retention arrangements.
Questions
Contact the project through the official Telegram community t.me/AIFOLDAI or X account @AIFOLDAI. Do not include a seed phrase, private key or API credential in any message.