Privacy
TRON Checker screens public TRON addresses and stores account data only for authenticated features you enable.
Data we process
Screening sends public addresses to TRON data providers to compute blacklist, sanctions, balance, transfer, and risk signals. The service never asks for seed phrases or private keys.
Saved reports, cases, batch rows, watchlist items, API keys, usage counters, billing state, and alert delivery records are stored only for authenticated workflows and are visible through account export.
Analytics
We use privacy-conscious Google Analytics through Google Tag Manager and Vercel Analytics to understand aggregate product usage, page performance, and conversion paths.
Analytics events do not include wallet addresses, Clerk identifiers, emails, report IDs, search contents, or raw query strings. Page locations sent to analytics are sanitized before transmission: address query parameters and address fragments are removed, query strings and fragments are stripped, and report/case/history detail IDs are replaced with generic placeholders.
Wallet-check events use only anonymous operational fields such as elapsed-time bucket, result status, risk tier, and generic error category.
Controls
Report saving is opt-in. You can export account data or request deletion from Settings.
Retention caps are enforced when REPORT_RETENTION_DAYS, ALERT_EVENT_RETENTION_DAYS, or BATCH_RETENTION_DAYS are configured.