Privacy

Browser data

The web app does not require a ProtoRadar account. It uses browser localStorage to keep your selected theme, saved token identifiers, and locally created alert rules, including their names, thresholds, state, and timestamps. That data stays in the browser unless you clear site data or your browser synchronizes it under its own settings.

Browser watchlists and alert rules are separate from Telegram and do not create server-side subscriptions.

Telegram bot data

When you use the production Telegram bot, ProtoRadar processes your numeric chat ID and command so it can respond. The durable store keeps subscription status and timestamps, watched contract addresses, Telegram update IDs and processing leases, and alert delivery state such as attempts, errors, and delivery timestamps. ProtoRadar does not intentionally persist the text of your bot commands in those application tables.

Sending /stop deactivates that chat and deletes its watched-address rows. It does not erase already-created update-processing records, alert-delivery history, general radar scans, or data retained independently by Telegram. Do not send wallet seed phrases, private keys, credentials, or other sensitive material to the bot.

Public MCP

The public MCP is read-only. It receives the searches, addresses, and filters submitted by your MCP client, processes ordinary connection and rate-limit metadata, and reads ProtoRadar's public APIs. It cannot create a Telegram watch or change your browser data. Your MCP client or its operator may separately keep prompts, tool calls, and results under its own privacy terms.

Infrastructure and external providers

Hosting and database providers may process standard request data such as IP address, user agent, requested route, timestamp, and operational logs. ProtoRadar also queries public chain RPCs, market-data services, reviewed launchpad APIs, and optional social data providers to build research results. Those providers receive server requests needed for the query; opening an external link sends you to that provider directly.

Telegram processes bot messages under Telegram's own terms. Public blockchains remain public, so contract addresses and transactions cannot be made private by ProtoRadar.

Retention and choices

• Clear this site's browser storage to remove the theme, watchlist, and local alert rules from that browser.
• Use /unwatch for one Telegram contract or /stop for the deletion boundary described above.
• Operational records are retained only as needed for deduplication, delivery, abuse prevention, debugging, and service integrity, subject to the infrastructure in use.

Questions and requests

ProtoRadar currently has no private support intake. For a general privacy question, open a minimal GitHub issue (opens in a new tab) asking for follow-up, but do not post a chat ID, IP address, secret, or other personal data in the public issue. See Support for safe reporting guidance.