CryptoScout
Privacy Policy
Overview
CryptoScout is a research Telegram bot that analyzes public blockchain and market data. This page describes what the bot database may store, what we never collect, and how to delete saved settings and history.
What data CryptoScout may store
- Telegram user id
- Telegram username (if available)
- Selected interface language
- History of public queries (for example, wallet / token / protocol checks)
- Favorite public wallet addresses and token contracts (and optional labels/symbols)
- Crypto Digest notification settings (timezone, schedule, thresholds, quiet hours, AI)
- Notification event keys for deduplication and retention
- Technical operational data: last-seen, cache records needed to run the service
Wallet and token addresses you submit
When you ask to analyze a wallet or token, you send a public address or contract. These public identifiers may be stored in query history and favorites if you use those features. They are not secret credentials.
Public blockchain and market data
Reports are built from third-party public APIs (for example DefiLlama, CoinGecko, DEX Screener, GoPlus, Honeypot.is, Etherscan, RugCheck, Alchemy, Moralis, TRONSCAN) and optional AI providers if the operator has enabled them. Those services process public requests under their own policies.
Website analytics
This marketing site may load analytics (Plausible, Umami, or GA4) if the operator
configures it. While values in config.js are null, third-party
analytics scripts are not loaded.
Logs
The bot and hosting environment may keep operational logs (errors, timings, service health). Logs are used for reliability and abuse prevention, not to collect private keys.
What CryptoScout does not collect
- Seed phrases / recovery phrases
- Private keys
- Passwords
- Banking details
- Wallet-connection sessions or transaction signatures
How to delete or manage data
- Favorites — manage / delete in the bot’s Favorites section
- Notifications — turn off all Digest alerts in Digest settings
- History / cache — use the matching clear actions in bot settings, if available
Data is stored in the bot’s local SQLite database in the operator’s hosting environment (for example Railway with a persistent volume).