Privacy Policy
Last updated: November 2026
Data We Collect
Solcurity is designed to be privacy-first. We collect minimal data:
- ▸ Public wallet address: Only when you submit a scan. This is public blockchain data.
- ▸ Telegram alerts: If you create an alert, the wallet address and Telegram user/chat IDs are stored in Supabase so scheduled checks can notify you. They remain until you remove the alert.
- ▸ Scan results: Generated from public blockchain data. Cached temporarily for performance.
- ▸ IP address: Only for rate limiting (in-memory, not stored permanently).
Data We Do NOT Collect
- ▸ Seed phrases, private keys, or wallet passwords
- ▸ Email addresses or phone numbers
- ▸ User accounts or authentication tokens
- ▸ Advertising or cross-site tracking identifiers
- ▸ Analytics or behavioral data
How Data Is Used
- ▸ Public address → Query Solana RPC for public blockchain data
- ▸ Generate security report → Return to you
- ▸ Cache result (TTL: 5 min) → Avoid duplicate RPC calls
- ▸ IP → read for scan rate-limit checks; reports use an HMAC hash for persistent rate limiting (the raw IP is not stored in the report database)
Data Sharing
We do not sell your data. Requests to external services required for the features you use are:
- ▸ Solana RPC endpoint: To fetch public blockchain data (configurable via SOLANARPCURL).
- ▸ Supabase threat database: When configured, the scanner sends the scanned address and observed counterparties/program IDs to the project’s Supabase service for matching. These identifiers are not inserted as scan records by Solcurity; service-provider request logs may be subject to Supabase’s policies.
- ▸ Groq AI (optional): If you request an AI explanation, Solcurity sends the scan risk level, checks, and up to eight findings to Groq. The scanned wallet address is redacted from these fields before sending. Groq's own data handling and retention policies apply.
- ▸ Claude connector (optional): If you use the remote MCP connector, the public wallet address and resulting scan report are sent between Solcurity and Claude so Claude can use the tool and explain its results. Anthropic's data handling policies apply to that use.
- ▸ Telegram (optional): Bot commands and alert notifications are sent through Telegram. If you enable alerts, the wallet address and Telegram user/chat IDs are stored in the project's Supabase database until you remove the alert; Telegram's data handling policies also apply to your chats.
- ▸ Community reports: If you submit a report, the identifier, evidence, and explanation are stored in Supabase for moderation. The submission is retained until an operator deletes it under their retention policy.
Your wallet address is sent to the Solana RPC endpoint you configure (or the default public endpoint) and, when Supabase threat screening is configured, to that database for matching. Scanner results are not intentionally stored as scan records by Solcurity. We do not send addresses to third-party threat intelligence APIs. AI features are optional and only run when you request them; using the Claude connector sends the requested public address and scan output to Claude for processing.
Data Retention
- ▸ Scan results: Cached in-memory for 5 minutes (configurable via CACHE_TTL_SECONDS)
- ▸ Rate limit data: In-memory, expires after 60 seconds (configurable)
- ▸ Telegram alert subscriptions: Retained in Supabase until removed using the bot's alert controls
- ▸ Scan results are not stored as records; Telegram alert subscriptions are stored until removed
Your Rights
Scans are not stored as scan records. If you create Telegram alerts, you can remove their stored subscription data using the bot's alert controls:
- ▸ You can clear your browser cache to remove any client-side data
- ▸ Server-side cache expires automatically
- ▸ Use the bot's /alerts menu to remove individual subscriptions
Security
- ▸ All communication over HTTPS
- ▸ No private keys ever transmitted
- ▸ Rate limiting prevents abuse
- ▸ Input validation on all endpoints
Contact
Questions about this policy? Open an issue on our GitHub repository.
