Privacy policy
Last updated October 2026
Short version: free scanning is anonymous. We count visits as daily totals with no cookies. We only hold personal data if you sign in, ask for email alerts or buy Pro, and then only what's needed to run them. We never sell or share it.
Free scanning
When you look up a token, your browser asks DexScreener, RugCheck and GoPlus directly: those requests do not pass through us. Your watchlist and settings are stored in your own browser. If you open a token page at trenchreports.com/t/…, our server fetches public data about that token and counts how many times the page was viewed; it does not record who viewed it.
To decide whether to show paid trade links (they are hidden in the UK), the page asks our server which country the request comes from. Cloudflare provides that; we do not store it.
Visits and page views
When one of our pages loads, it tells our server which page it is, which site linked to it (the site's name, such as google or x.com, not the page you were on) and any campaign tag in the link (such as ?src=tiktok). The server adds these to daily totals, together with the country Cloudflare reports and whether the device is a phone, tablet or computer and its operating system. We use no cookies for this and store nothing in your browser.
To count each visitor once per day without cookies, the server combines a one-way hash of your IP address and your browser's user-agent with a random value that is replaced every day. The result can't be turned back into your IP address, and because the random value changes daily, you can't be recognised from one day to the next. These daily keys are deleted within about two days; only the totals (for example, "412 visitors from the US on 3 October") are kept, for up to 400 days. Our legal basis is our legitimate interest in knowing how many people use the site and where they find it.
Links from Telegram groups
Referral rewards: if you sign up through someone's referral link (?r=…) or enter their code, we keep which account referred yours and when, so your fee discount and their reward can be worked out. Your browser keeps the code from a link for 30 days (local storage, not a cookie). The person who referred you sees only counts and totals, never your email, name or trades. If you set a payout wallet, we keep its address to send rewards to it.
Trading results on your profile are off unless you switch them on; then your public profile shows totals, ratios and a calendar of daily results from trades made here, never which tokens you hold.
Links our bot posts in a Telegram group carry that group's code (?src=g-…). If you arrive through one, your browser keeps that code for 30 days (in local storage, not a cookie; the first group link wins). If you then sign in or trade on the site, your account or the wallet you traded with is credited to that group, once. This is how we see which groups the bot is useful in, and how a group's owner who joined our partner program earns a share of our fee on trades credited to the group. The owner sees only totals (number of trades, amounts traded, what they earned), never who you are or your wallet. To clear the code, clear this site's data in your browser. If you're a group owner who joined the partner program, we store your Telegram user ID, your group's ID and name, the payout wallet you set, and a record of each payout we sent you, for as long as you're a partner and then as long as tax and accounting rules require. Our legal basis is our legitimate interest in knowing where our users come from and paying our partners correctly.
The Telegram bot in groups
When a group adds our bot, we store the group's ID, name, type and member count, when the bot was added or removed, which of its switches the group's admins turned on (auto-scan, scam protection, follow-ups), and how many checks the bot answered there. We don't store the group's messages or its member list. For each token checked in a group we keep the token, the risk read shown, when it was first and last checked there and how many times, for 60 days, so the bot can post a follow-up if the token rugs and answer /stats. We never record who asked.
With auto-scan on, the bot reads each new message only to look for a token contract address, and keeps nothing else from it. To skip repeats, it remembers which address it checked in which group for about 10 minutes.
With scam protection on, the bot reads each new message only to check it against a few scam patterns (requests for seed phrases or private keys, wallet "verify" links, fake "support" accounts), and checks the names of people who join against the group's admins. To do that it keeps the admins' Telegram IDs, names and usernames, refreshed every few hours. If a message matches, the bot removes it or replies with a warning; it keeps nothing from the message, only a daily count of how many it caught. It never bans or mutes anyone.
An admin can turn any of this off with /autoscan off, /protect off or /followups off, or remove the bot at any time.
The Telegram bot in private chats and inline
If you sign in with Telegram, /watch adds a token to your account's watchlist from the chat, the same as doing it on the site. When you type @TrenchReportBot and a contract in any chat, Telegram sends us what you typed and your Telegram user ID so we can answer; we use the ID only as a short-lived rate-limit counter key, and keep nothing else.
Feedback
If you send feedback from /feedback, we store what you wrote, the category you picked, the page you came from, the contact you typed (only if you left one) and your country as Cloudflare reports it. A one-way hash of your IP address is used only as a rate-limit counter key and deleted within a few hours; it isn't stored with your message. Feedback is used to fix and improve the site and is kept until it has been dealt with. To have yours deleted, email us.
The status bar
The bar at the bottom of each page asks our server whether each chain's data sources are answering. That request carries nothing about you, and nothing is stored about it.
The public track record
When you open a token's report, the page sends our server that token's chain and contract address. If the token isn't on the track record yet, the server makes its own risk read and logs it publicly, with the time. The same happens for tokens checked with our Telegram bot. What's logged is about the token only: nothing that identifies you, your wallet or your chat. To stop one visitor flooding the record, a one-way hash of your IP address is used as a counter key and deleted within about three hours. Track-record entries are permanent by design and are not personal data.
Free email alerts
We store your email address, the tokens you chose, and the fact that you confirmed. While a request is unconfirmed we also keep a one-way hash of your IP address to stop abuse; unconfirmed requests are deleted after 7 days. Our legal basis is your consent, which you can withdraw with the unsubscribe link in every email.
Early-access accounts
While Pro is free in early access, you can sign in to get alerts, saved scans and a synced watchlist. If you sign in by email we store your email address; if you sign in with Telegram we store your Telegram user ID and the ID of your private chat with our bot, and nothing else from your Telegram account (not your name, username, phone number or contacts). Either way we also store the tokens you watch, your alert rules and saved scans, a log of alerts sent to you (kept 30 days) and a login session, kept as an HttpOnly cookie for up to 30 days (we store only a hash of it). While a Telegram sign-in is in progress, a random code and a hash of a secret held in a short-lived cookie are kept for about a day. To stop abuse, a one-way hash of your IP address is used as a rate-limit counter key and deleted within a few hours. Our legal basis is providing the service you signed up for. No card or payment details are collected.
Pro accounts
We store: your email address; your Stripe customer ID and subscription status (never card or bank details: Stripe handles those); the tokens you watch, your alert rules and saved scans; a log of alerts sent to you (kept 30 days); your Telegram chat ID if you link Telegram; your referral code and referral records; and a login session, kept as an HttpOnly cookie for up to 30 days (we store only a hash of it). Our legal basis is performing the contract you entered into.
Accounts and passwords
Anyone can make a free account with an email address and a password, or with Telegram. For an email account we store the address and a salted, one-way hash of your password (PBKDF2), never the password itself. Until you confirm your address, the sign-up waits for up to an hour and is then deleted. To slow down password guessing, a one-way hash of your IP address and of the email address being tried are used as rate-limit keys and deleted within a few hours. Changing your password signs out your other devices.
Public profiles
A profile is optional. If you make one, its handle, display name, bio, avatar and background choices and the month you joined are public at trenchreports.com/u/your-handle, and so are the tokens on your watchlist, with the date you added each one, but only if you switch that on (it is off by default). Your email address and Telegram details are never shown. We count views of each profile as a plain number. If someone reports a profile, we keep the reason, any note they add and a one-way hash of their IP address (to limit repeat reports), and delete handled reports after 180 days. If you have Pro, a ★ PRO badge shows next to your name on your profile and in search; you can switch it off on your account page. Who you follow and who follows you is public on profile pages: accounts that follow without a profile are counted but never named. You can delete your profile at any time from your account page; your watchlist then becomes private again, and the follows to your profile are removed.
Wallets
Scan my wallet: the address you scan is sent to our server, which reads that wallet's public token balances from the Solana network (through Helius, or Solana's public servers) and prices them on DexScreener. The result is kept in memory for about a minute so a reload doesn't repeat the work, and is not stored. A one-way hash of your IP address (or your account, if signed in) is used as a rate-limit key.
Linking a wallet to your account means signing a message with it, which costs nothing and gives no access to your funds. We store the wallet's address, your account and when you linked it. Wallet addresses are public on the blockchain; linking connects one to your account, and we never show that link to anyone.
Your trading wallet and Quick trade use Privy (privy.io). When you open your trading wallet, we give Privy a short-lived token with your Trench Report account ID (not your email) so it signs you in, and Privy creates your Solana wallet. Privy holds the wallet's key under its own privacy policy; we never see it. We store your Privy user ID, the wallet's address and Privy's ID for it, your account, whether Quick trade is on, and your limit per buy. When you open the Wallet panel, our server reads the wallet's public balances (through Helius) and prices them; that isn't stored. Deposits and withdrawals you make there are passed to the Solana network and are public on the blockchain; we don't keep a separate record of them. Trades made with it are recorded like other trades (wallet, token, amounts, fee, transaction). Turning Quick trade off keeps this record so your trade history stays; ask us to delete it.
Copy trading. When you follow a wallet we store its address, the nickname you give it (only you see it), where its alerts go, your copy amount, and when you accepted the risk notice. The followed wallet's trades are public chain data; we keep 30 days of them and your alerts for 7 days. If you list one of your own wallets on Top traders, its trades and results are shown publicly next to your profile handle until you unlist it. Copied trades are recorded like other trades, with the wallet they copied.
Wallet alerts (Pro) are off until you switch them on for a linked wallet. While they're on, our server reads that wallet's balances about every 30 minutes and keeps its largest holdings (which token, how much, and its dollar value at the time) so it can alert you when one of them changes for the worse. That list is replaced on every read, and deleted when you switch alerts off, unlink the wallet, or your Pro ends (within two days). Unlinking a wallet deletes the link and that list.
Who processes it
- Stripe: payments, receipts, billing portal.
- Cloudflare: hosting, the database that holds the visit totals above, and the country lookup.
- Resend: sending login links and alert emails.
- Telegram: delivering alerts and bot replies to chats you choose.
- Helius: reading public Solana wallet balances for wallet scans and wallet alerts.
- Helius (copy trading): watching the wallets people follow or list, for their trades, their 30-day history and public identity labels.
- Privy: email sign-in and the embedded wallet for Quick trade, and signing the trades you start with it.
- Jupiter: routing swaps.
We use no advertising trackers and we do not sell, rent or share personal data. Aggregate counters (for example, how many token pages were viewed per day) contain no identifiers.
Keeping and deleting it
Data is kept while your account is active. Email support@trenchreports.com to get a copy of your data or to have it deleted; we reply within 30 days. Stripe keeps payment records it is legally required to keep.
If you are in the EU or UK
You can ask to access, correct, delete or export your data, and object to or restrict processing; you can also complain to your data-protection authority. Your data is processed in the United States.
Age
Trench Report accounts are not for anyone under 18.
Contact and changes
Lincoln Smith, Texas, USA · support@trenchreports.com. If we change this policy, the date above changes; material changes are emailed to account holders.