Privacy Policy
What we collect, and why
Effective November 8, 2026. Last updated November 9, 2026. This covers trenchlyfe.fun, launch.trenchlyfe.fun, the Trench iOS app, the Trench Telegram Mini App and bots, the Trench Score bot on X and the Trench Score browser extension (together, “Trench”, “we”).
1. What we collect
- AccountWhen you sign in, our sign-in provider Privy handles your email address or the Google, Apple, X, Telegram or wallet account you use. Our database keeps an account ID from Privy, the handle and avatar you choose, when you joined, and when you were last active. If you link a Telegram account, or open Trench inside Telegram, we keep its Telegram user ID and username. To match launches from a post and held fees to you, we read from Privy which X and Telegram accounts you have linked (their account IDs and usernames).
- WalletsWallet addresses you link, which one is primary, and the label your wallet app reports, plus the Trench wallet created for your account and, if you use perps, the address of your perps wallet (an Ethereum-style wallet). Linking uses a one-time code that your wallet signs; the code expires.
- ActivityCoins and wallets you follow and the labels you give them, your alert settings and alert inbox, chat messages, replies, reports and blocks, feedback and votes, orders, sell orders and event exits you set and how they filled, copy-trading settings and every copied trade, open-market trades you make through Trench (and the bagworker link they came from), the fee receipts we read from your trades, reward and bagworker records, the bagworker a trader is bound to for life, referral link counts, fee splits, Dev bonds, Dev pledges and other creator actions, revivals you start or claim from, airdrops you send, launch drafts made from a post, and the images and descriptions you upload when you launch a coin.
- Push alertsIf you turn on alerts, the push address your browser or phone gives us, so we can deliver them.
- Card purchasesBuying SOL with a card runs through MoonPay and is in test mode until MoonPay approves it. When you start a purchase we send MoonPay the linked wallet the SOL should land in, the amount, a purchase reference, and a keyed code made from your IP address that MoonPay uses to check the request came from you. MoonPay then tells us the purchase status, amounts and currencies, the network transaction and any failure reason, and we keep these with your account. MoonPay collects your card and identity details under its own privacy policy; we never see them.
- TechnicalOur servers log the IP address, country (from Cloudflare), page requested, referring page, browser type and time of each request. We use this for security, rate limits and traffic counts. The website also sends your device’s time zone with its requests to our servers, and the iOS app sends your device’s time zone and the country of your App Store account.
- Perps checksTo apply the perps location rules we compare the IP address of each request with public lists of VPN, proxy and data-center networks, record whether a Trench account has been used from the United States, and keep a log of perps eligibility decisions and of the orders Trench forwards to Hyperliquid. That log stores a one-way code made from your IP address, not the address itself.
- BlockchainPublic Solana data: trades, balances, hourly holder snapshots, the lots that set each wallet’s Hold Age, funding history (which wallet first funded which), and creators’ launch history across launchpads. We read it, for any wallet, to show coin pages, safety checks, Trench Score, dev records, wallet profiles, holder pay, the Diamond Hands Pool, Dev bonds and the bubble map, and to leave insiders out of holder pay. We keep hourly holder snapshots for 40 days and the trades of followed wallets for 30 days.
We do not collect government ID, payment card numbers or bank details, and we do not run identity checks. MoonPay may, for card purchases, under its own policy.
2. What is public
Some things on Trench are public by design:
- Your handle and avatar, your chat messages, and the coins you launched (shown on your profile and on each coin you created).
- Your bagworker handle on links you share and on the coins you bag work.
- Airdrops: the sending wallet, every recipient wallet, amounts, the note and each transaction, on the airdrop ledger.
- Rewards: every settled day and every payout, with the receiving wallet and transaction, on the rewards ledger.
- Dev records: for every coin creator, the record, its label and up to six wallets linked to the creator, each with how it is linked, including wallets on the same Trench sign-in. Anyone can look up a creator wallet’s record.
- Holder pay and the Diamond Hands Pool: each day’s ledger of reward rows (wallet, coin, kind, amount and vesting time) is fingerprinted by a Merkle root posted on chain, and anyone can look up any wallet’s rows and proof for a day. Each coin’s Diamond Hands Pool address, balance, payouts and per-wallet shares are public too.
- Dev bonds and Dev pledges: a bond’s evidence, wallet by wallet, and every pledge change with its date.
- Coins launched from a post: the X or Telegram handle of the person who posted, the post link, and what is held for and claimed by them.
- Trader profiles: any wallet’s profile, built from its on-chain swaps. Your own profile at /u/yourhandle, with your linked wallets and results, is public only if you make it public.
- Feedback you post, on the public board and in the Trench Telegram group, and the Score bot’s replies, which are public posts on X.
- Everything on the blockchain, including wallet addresses and trades. We do not publish which account owns a trading wallet, except as described above (a creator’s dev record and a profile you make public), but blockchain data can often be linked to people by others.
3. How we use it
- To run your account: sign-in, linked wallets, rewards, claims, creator tools, airdrops, orders and alerts.
- To keep Trench safe: rate limits, spam and seed-phrase filters in chat, reports and moderation, abuse prevention, the launch block list, grading dev records, leaving insiders out of holder pay, and applying the rules on where perps are offered.
- To count traffic. Our traffic stats store a one-way, keyed visitor code made from IP address, browser and month, not the IP itself, and stats records are deleted after 90 days.
- To improve Trench and fix problems.
We do not sell personal data, rent it, or use it for advertising. We do not use third-party advertising or tracking cookies.
4. Who we share it with
Only the service providers Trench needs to work, for that purpose:
- PrivySign-in (including X and Telegram), the Trench wallet, your perps wallet, the limited signing key used for one-click and orders if you turn them on, and, if you turn on copy trading, event exits or sell orders on other coins, the separate copy-trading key and its rules, which are owned by your Privy account.
- CloudflareDelivers and protects our sites. Your requests pass through its network, and it tells us the country and region each request comes from.
- Hyperliquid and RelayOnly if you use perps. Your perps wallet address and the orders, deposits and withdrawals you sign go to Hyperliquid, and bridge transfers go through Relay.
- HeliusOur Solana connection and data provider. Wallet addresses and transactions you send through Trench reach the network through it, with Helius’s sandwich protection and any rebate paid to your wallet. Wallets you follow, and wallets that Trench Score and dev records check, are watched or looked up through it. Before holder pay or a Diamond Hands Pool payout, the wallet addresses about to be paid are sent to Helius’s wallet identity service to check whether any of them is an exchange.
- JupiterMarket data, and routing for open-market trades (graduated coins and coins from other launchpads). When you make one, your wallet address and the trade go to Jupiter, which builds it, sends it after you sign, and keeps its share of the 0.5% Trench fee on outside coins. Copied trades, event exits and sell orders route through Jupiter the same way, and the iOS app asks Jupiter for coin prices and details directly from your device.
- Push servicesApple, Google or Mozilla deliver alerts to your device if you turn them on.
- XIf you sign in with X, through Privy. If you tag the Score bot or ask it to launch from a post, the bot reads, through X’s application programming interface (API), the post that tagged it, the post it replies under, quoted and linked posts, and the tagging account’s public profile, and posts its reply on X. If you tap “Post on X”, X handles that post.
- TelegramIf you use the Trench bot, the Mini App or the Trench channel and group, Telegram passes us your Telegram user ID, name and username and the messages you send the bot. If your Telegram account is linked, alerts for wallets you follow can also reach you as Telegram messages.
- AnthropicWhen the Score bot cannot find a coin in a post’s text, it may send the web address of up to two pictures from those public posts to Anthropic’s Claude service to read a contract address or ticker from them. Nothing about your Trench account is sent.
- MoonPayOnly if you buy SOL with a card, as described under Card purchases in section 1.
- Public Solana nodesThe website’s wallet connects to a public Solana node for live updates, and the iOS app uses public nodes (Solana’s mainnet node and PublicNode) to check a transaction before you sign it. They see your device’s IP address and, for those checks, the transaction.
We may also disclose information if the law requires it, to protect people from harm or fraud, or as part of a sale or reorganization of Trench, in which case this policy continues to apply.
5. Cookies and storage on your device
- trench_hint: a cookie with your handle and avatar so trenchlyfe.fun can show you as signed in. Display only, 7 days. It does not sign you in.
- Sign-in session: stored by Privy in your browser to keep you signed in.
- Preferences in your browser’s storage: filters, trade settings, layout, and the bagworker link that referred you to a coin (kept 7 days).
- Account cache: your handle and linked wallets, kept in your browser so the site can show you signed in quickly. Signing out clears it.
- Perps key: if you enable perps trading, the trade-only key that signs your orders is kept in that browser’s storage. It cannot withdraw.
- Cloudflare may set a security cookie to filter bots.
Trench Score browser extension and Score bot
The Trench Score extension for Chrome, Brave, Edge and Arc shows scores next to Solana contract addresses on X and DEX sites.
- What it sendsOnly the Solana addresses it finds in the page you are viewing (in text and links), sent to trenchlyfe.fun to look up their scores, plus the address of a coin when you open its Score card or paste it into the extension. Lookups are made only for addresses scrolled into view.
- What it never sendsThe page address, page content other than those addresses, your browsing history, cookies, your X account, wallet data or any identifier. It has no analytics or tracking, and it does not read or change anything on sites other than the ones listed in its store page.
- Stored on your deviceYour settings (Trench handle, default buy size, which sites show pills) in your browser's extension storage, and a short-lived cache of scores. Nothing is stored on our servers by the extension, apart from the normal request logs described in section 1.
- Buy on TrenchClicking Buy opens trenchlyfe.fun with the coin, your buy size and, if you set one, your handle as the referral (?ref=). Trades still need your confirmation on Trench.
The Trench Score bot on X (@ATrenchLyfeBot) answers only posts that tag it. It reads the post that tagged it, the post it replies to or quotes, and up to two posts linked from them, and looks for a contract address, a coin link or a $TICKER. If the text has none, it may send up to two of those posts’ pictures to Anthropic to read one (see section 4). It replies with the score under the coin post when that post mentions the bot, and otherwise to you. It keeps a log of the post IDs, the account ID that tagged it, how it found the coin, the coin and its reply, for rate limits and to avoid answering twice. It does not follow, like, message or reward anyone.
Launch from a post (the same bot on X, and @trenchlyfe_bot on Telegram). When you ask the bot to launch a coin from a post, it reads that post's text and picture and the account IDs and handles of the person who posted it and of you, and on X your account’s creation date (accounts under 3 days old are refused). These are kept with the launch draft and, if the coin launches, with the coin, so the poster's held share can only be claimed by that account. The picture is stored on our server and can become the coin's logo. Refused requests are logged with the reason.
6. Your choices
- Browse, read the guide and use Trench Score without an account.
- Change your handle and avatar, unlink wallets, turn alerts and push off, turn orders and one-click off, revoke copy trading and remove copy access, make your trader profile private, and remove your own chat messages from view at any time (we keep a hidden copy for moderation).
- Ask us to delete your account. We will remove your account data from our systems, except records we must keep for security or by law. We cannot change or delete anything recorded on the blockchain. Public ledgers (rewards, airdrops and the daily holder pay proofs) list wallet addresses rather than accounts and stay published, because others use them to check payouts.
- Depending on where you live, you may have rights to access, correct, delete or move your data, or to object to some uses. Contact us and we will respond.
7. Security and retention
Our internet-facing services run under a restricted, low-privilege account, and we never have access to your keys. Our database is copied continuously to a standby server we run, so Trench keeps working if the main server fails; the standby holds the same data under this policy. No system is perfectly secure. We keep account data while your account exists and server logs for as long as we need them for security and operations. Some records have set lifetimes: hourly holder snapshots 40 days, trades of followed wallets 30 days, traffic stats 90 days, open-market quotes 7 days and AI launch kit images 7 days.
8. Age
Trench is not for anyone under 18. We do not knowingly collect data from minors; if you believe a minor has an account, contact us and we will remove it.
9. Changes
If this policy changes, we will update this page and its effective date. Big changes will also be announced on X.
10. Contact
Questions, data requests or account deletion: message @TheTrenchLyfe on X.
Not financial advice
Trench is software. Nothing on Trench, in Trench Score, in the guide or from @TheTrenchLyfe is financial, investment, legal or tax advice, or a recommendation to buy or sell any coin. Memecoins are highly speculative and can lose all of their value. Do your own research and only risk what you can afford to lose.