- We store your account email, your synced workspace and your alert settings, so the Service works across your devices.
- We never ask for, and never store, private keys, seed phrases or wallet connections.
- We don't sell personal data, and we don't use it for advertising.
- You can export your data or delete your account at any time from Settings.
1.Who we are
This policy covers trenchsight.xyz, its web app, emails, notifications and shared receipts (the "Service"), operated by TrenchSight ("we", "us"). For any privacy question or request, contact [email protected].
2.Information we collect
| Category | What it includes | Source |
|---|---|---|
| Account details | Email address, username, and a securely hashed password. We never see or store your password in plain text. | You, when you sign up |
| Telegram and follows | If you connect Telegram (Max): your Telegram chat id, used to send you alerts and, unless you turn it off, the daily brief. If you follow other traders: who you follow, used only to send you their new calls. Disconnect or unfollow at any time in Watchtower. | You |
| Telegram bot and groups | When you message the TrenchSight bot or add it to a group: the chat id, the group's name, its automatic-check setting and a daily count of quick checks. In groups the bot reads messages only to spot token addresses; it doesn't store message text. The token addresses it checks are sent to the market and blockchain providers below. | You and the people in your group |
| Sign-up source and invites | When you create an account: where you heard about TrenchSight (if you answer), the invite handle in your link, the campaign tags in the link you used and the site that linked to us. If you invite friends: how many joined and upgraded. Used to see what brings people to TrenchSight and to credit invite rewards. | You and the link you arrived from |
| Error reports | When something breaks in the app or on our servers: the error message and technical trace, the page path, your browser and device type, and your account id if you are signed in. No scan contents or wallet data. Used only to fix bugs. | The app, automatically |
| Profile | Display name, bio, avatar colour and icon, if you add them. Your public profile also has a handle based on your username and, if you add them, wallet addresses and (with Max) coin badges, a banner, and a profile photo and banner picture you upload. Uploaded pictures are public, like the rest of a public profile. | You |
| Calls | When you scan a token while signed in: the token, its TrenchScore, its price at the time and the date, linked to your account. | Automatically |
| Workspace | Chats and the messages you send, scanned tokens, your Watchtower list and alert rules, watched wallet addresses, deleted-alert preferences, currency and default chain. | You, as you use the Service |
| Alert settings | Whether email and push alerts are on, your browser's push subscription (an endpoint and keys issued by your browser), and the alerts we've sent you. | You and your browser |
| Max payments | Your plan and Max end date, and for each payment the plan, amount, coin, network, transaction ID and the sending wallet address. Transaction details are also public on their blockchain. | You and the blockchain, when you pay |
| Usage records | The number of scans made each day, linked to your account, or for visitors without an account, to a one-way hash of the IP address (never the IP address itself). | Automatically |
| Anonymous scan records | For the public track record: a scanned token's address, chain, TrenchScore and its market data at the time and afterwards. These contain nothing about you. | Automatically |
| Technical data | Standard request data such as IP address, browser type and pages visited, processed by our hosting provider to deliver and protect the Service, and aggregated, cookie-free page statistics. | Automatically |
Token contract addresses and public wallet addresses are public blockchain information. When you ask TrenchSight to scan a token or watch a wallet, we process those addresses to provide the Service.
3.How we use information
| Purpose | Information used |
|---|---|
| Providing the Service: scans, reports, AI analysis, chats and syncing across devices | Account details, workspace, token and wallet addresses |
| Running Watchtower and sending the alerts you ask for, by email or push notification | Watchlist, alert rules and settings, email address, push subscription |
| Providing Max, confirming payments, sending renewal reminders and keeping payment records | Account details, Max payment records |
| Applying fair-use limits and preventing abuse | Usage records, hashed IP addresses for visitors without an account |
| Publishing the public track record | Anonymous scan records |
| Showing your public profile at trenchsight.xyz/u/your-handle, and your calls in the track record's feed and top callers | Profile and calls. Profiles are public by default: anyone can see your display name, handle, bio, avatar, the wallet addresses you add (marked “not verified”) and your calls. Turn this off in Settings → Profile → Public profile and they're hidden straight away; your calls then only count in the anonymous statistics. |
| Keeping the Service secure, reliable and working, and understanding overall usage | Technical data, usage records |
| Responding to your messages and requests | What you send us |
Where data-protection laws such as the GDPR apply, we rely on these legal bases: performing our contract with you (providing the Service you sign up for), our legitimate interests (security, abuse prevention, improving the Service and publishing anonymous statistics), and your consent (push notifications, which you can withdraw at any time).
4.What we don't do
- We don't sell, rent or trade personal data.
- We don't use advertising or cross-site tracking cookies, and we don't build advertising profiles.
- We don't ask for private keys, seed phrases or wallet connections. Anyone asking for these in our name is attempting a scam.
5.Service providers we share data with
We share only the minimum information each provider needs to perform its role for us:
| Provider | Role | Data involved |
|---|---|---|
| Supabase | Authentication and database | Account details, workspace, alert settings, usage records |
| Cloudflare | Hosting, security, server functions and aggregated page statistics | Technical data, requests to the Service |
| AI model provider (Groq) | Writing analyses | Your messages, attached files and scan results for the request |
| Helius and Solana RPC | Solana blockchain data | Token and wallet addresses |
| DexScreener and GeckoTerminal | Market and trending data | Token addresses |
| pump.fun | Who created a token and their other launches (Sonar) | Token and wallet addresses |
| Telegram | Delivering bot replies, alerts and the daily brief | Your chat id and the message content |
| GoPlus Security and Honeypot.is | EVM contract security checks | Token addresses |
| Etherscan, Blockscout and public EVM nodes | EVM contract, creator and wallet data | Token and wallet addresses |
| Resend | Sending account, alert, daily brief and Max reminder emails | Your email address and the email content |
| Helius, mempool.space, Etherscan and Blockscout | Confirming Max payments on-chain | The receiving address and the payment amount; no personal data |
| Coinbase, Kraken and Jupiter price APIs | Converting Max prices into SOL, BTC or ETH | None: only public price requests |
| Your browser's push service (e.g. Google, Apple, Mozilla) | Delivering push notifications | Push subscription; notification content is fetched securely by your device |
Blockchain and market-data providers receive token or wallet addresses, never your name or email. We may also disclose information if required by law, to protect the rights and safety of users or the Service, or as part of a merger or transfer of the Service, in which case this policy will continue to apply.
6.International transfers
Our providers may process data in countries other than yours, including the United States and the European Union. Where required, we rely on appropriate safeguards such as standard contractual clauses offered by those providers.
7.How long we keep information
| Information | Kept for |
|---|---|
| Account, profile, workspace and alert settings | Until you delete them or your account |
| Push subscriptions | Until you turn push alerts off, the subscription expires, or you delete your account |
| Sent alerts | Until you delete your account; you can hide alerts at any time |
| Usage records | As long as needed to apply limits and prevent abuse; they contain no name or email |
| Max payment records | While your account exists, and deleted with it. The payments themselves remain public on their blockchains. |
| Anonymous scan records | Indefinitely, as part of the public track record |
| Profile and calls | While your account exists, and deleted with it |
When you delete your account, your account, profile and public profile, calls, workspace, alert settings, push subscriptions, alerts and Watchtower state are permanently deleted. We may keep limited records where required for security or legal reasons.
8.Your rights and choices
- Access and portability: export your data as JSON or CSV from Settings → Data & privacy.
- Correction: update your profile and preferences in Settings.
- Deletion: delete your account from Settings → Account, or ask us to.
- Notifications: turn email or push alerts off at any time in Settings → Notifications or Watchtower.
- Other rights: depending on where you live, you may have the right to object to or restrict processing, to withdraw consent, and to complain to your local data-protection authority.
To make a request, email [email protected]. We'll respond within the time required by applicable law and may need to verify your identity first.
9.Security
We protect your information with industry-standard measures: encrypted connections (HTTPS), hashed passwords, database row-level security so that only you can read your workspace, server-side storage of private API keys, and strict content-security rules in the browser. No system is perfectly secure, so please use a strong, unique password and tell us immediately if you suspect unauthorised access.
10.Cookies and local storage
TrenchSight uses your browser's local storage to keep you signed in, to cache your workspace so the app loads quickly, and to remember small preferences such as the chain selected in the trending panel. A service worker is used to receive push notifications if you enable them. We don't use advertising or cross-site tracking cookies. Our page statistics are aggregated and cookie-free.
11.Children
The Service is intended for adults aged 18 and over. We don't knowingly collect information from anyone under 18. If you believe a minor has created an account, contact us and we'll delete it.
12.Changes to this policy
We may update this policy as the Service evolves. We'll change the effective date above and announce significant changes in the app.
13.Contact
Questions, requests or concerns about privacy: [email protected].