Security & Transparency

Your wallet. Your control.

Understand exactly what Trenchers can access, how your trading data is handled, and what permissions are required.

We ask you to run an extension next to your trading terminal. You should be able to check what it does rather than take our word for it. This page states what is true in the code today, marks what is not built yet, and shows how to verify each point yourself.

Chrome permissionsEvery permission, and why

Extension source codeOpen source pending

Security audit reportsNo independent audit yet

How Trenchers works

Four parts, each with a narrow job. Data flows down; nothing in this chain holds your private key.

Your side
Trading terminal and public wallet
You trade on Terminal with your own wallet. Your wallet keeps your keys and asks you to approve every transaction.
Terminal's own order and price messages, read in your browser
Runs in your browser
Trenchers extension
Records your fills, runs Paper Trading on a virtual balance, and shows callouts. Data collection happens here, on your machine.
Your trades and callouts, over HTTPS, to your account only
Trenchers servers
Trenchers backend
Signs you in with X, stores your synced results and callouts left, and publishes callouts: sealed on the site the second they are sent, revealed 45 minutes later, and at once in the extension while you have callouts left.
Your own results, readable only by your session
trenchers.si
Analytics dashboard
Calculates PnL, win rate and sessions from your trades. Paper and Real have separate dashboards and are never added together.

Data collection

Happens in the extension, from what Terminal already shows you. It needs browser access to Terminal pages.

Blockchain verification

Solana is public: anyone can read a wallet's transactions from its address alone. For the wallets you add, your Real dashboard reads that public history; it needs no permission over the wallet.

Dashboard calculations

Done on your synced trades. Analysing a wallet's activity never requires its private key, only its public address.

What we can and cannot access

Four answers, not two. Not required: we have no use for it and never collect it. Technically inaccessible: the extension has no permission that reaches it. Reachable, deliberately not used: a permission could reach it, and the code does not. Used: we read it, for the reason given.

Data used for analytics

Data	Status	What happens	Detail
Public wallet address	Used	Read from Terminal, stored in your browser	Only the wallets you add on the Dashboard (you paste the address and prove it is yours) count. Terminal sends the extension the balance of every wallet on your account; the extension keeps only the wallets you added, adds up their balances and ignores trades from any other wallet. The extension does not send wallet addresses to Trenchers. Wallets you add are stored with your account.
Your trades on Terminal	Used	Read, stored in your browser, sent to your dashboard	Token, time, SOL in and out, fees, result. The transaction hash stays in your browser.
Trading timestamps and performance	Used	Computed in your browser and on your dashboard	PnL, win rate and sessions are calculated from the trades above.
Paper Trading activity	Used	Stored in your browser, sent to your dashboard	Virtual SOL only. Kept apart from Real results and never added to them.
Public blockchain transactions	Used	Read from public Solana data, for wallets you add	The swaps of the wallets you add to your Dashboard (up to 5), read from the public chain through our data provider. Anyone can read these; reading them needs no permission from you and cannot move funds.

Sensitive information

Data	Status	What happens	Detail
Device identifier and session	Used	Made by the extension, sent to trenchers.si	A random id created at install (not a fingerprint of your device) and your session start, heartbeat and stop, so an account works on one device with one active session and callouts reach you at once while you have callouts left. Our server records the IP address and country of the session. Nothing about your wallet.
Private keys	Not required, not collected	Never requested, never read	They stay in your wallet. Analytics only needs public data, and no part of Trenchers asks for a key.
Seed phrases	Not required, not collected	Never requested, never read	Nobody at Trenchers will ever ask for one. Anyone who does is not us.
Wallet signing (transactions)	Reachable, deliberately not used	Reachable on Terminal pages, never called	The extension contains no code that asks your wallet to sign or send a transaction.
Browser cookies and other sites	Technically inaccessible	No permission for them	The extension has no cookies, tabs, history or "all sites" permission, and runs only on the three sites listed below.
Terminal's session and storage	Reachable, deliberately not used	Reachable on Terminal pages, not read	The extension reads only its own saved settings on Terminal, never Terminal's login or wallet data.
Discord login token	Not required, not collected	Not read	Only the visible text of callout messages, in the channels you switch on.
Your X password	Technically inaccessible	Never seen	Sign-in happens on X. Trenchers receives your X profile, never your password.

The “reachable” rows matter: on Terminal pages, one extension script runs in the page's own context so it can read Terminal's market messages. Any script there could, in principle, see what the page sees. Ours reads only those messages. You can check this in the source: it wraps the page's WebSocket and nothing else.

Read-only analytics

Verified in code

Free Analytics observes and measures. It holds no authority over your funds, so it needs none.

Wallet tracking: You add a wallet by pasting its public address and proving it is yours, with a tiny transfer from it to any address of yours (0.001001 to 0.001999 SOL) or, if you prefer, a message signature. Neither gives Trenchers any power over the wallet: a public address lets anyone read, and lets no one spend. You can remove a wallet at any time.
Trade recording: Built from Terminal's own order confirmations as they arrive in your browser, not from your wallet.
History reconstruction: Buys and sells of the same token are grouped into one trade, with what it cost and returned, fees included.
Paper Trading: A virtual SOL balance kept in your browser. Paper Quick Buy changes that balance only; it sends nothing to Terminal or the blockchain.
Dashboard sync: Your trades go to your own account. Another member cannot read them: every read is tied to your session. The extension sends them straight to your account with its own key, which you can revoke from the Extension page.

Reading, recording and computing do not need a signature, so the analytics never ask for one. Callouts and top-ups are described below.

Callouts and top-ups

Free callouts liveSOL top-ups open

Trenchers does not trade for you and never takes anything from your wallet. You buy callouts by sending SOL yourself, and you trade on your own terminal, with your own wallets.

How a top-up works

Your browser prepares a plain SOL transfer to Trenchers for the plan you pick. Your wallet shows it and you approve it; Trenchers never signs.
The transfer carries a reference unique to your request. Our server finds it on-chain, checks the amount and the recipient, and adds the callouts once.
No permission over your wallet is ever requested: no key, no spending authorization, no recurring payment.
The SOL lands in a receive-only Trenchers wallet whose key is not on any server. Once a day it is moved by hand to a wallet created on a device that never connects to the internet, and any other transfer out of it raises an alarm.

How a callout is charged

0.015 SOL per callout, counted only if an on-chain trade reached ×1.4 the market cap at sending within 24 hours. Otherwise it comes back.
Every charged callout links the transaction that reached ×1.4. A charge is final; if you think one is wrong, write to support.
One device and one active session per account; each callout sent in real time carries an invisible mark of your account.

Top-ups are paid in SOL (plans on the Credits page); unused callouts never expire and are not refunded in SOL.

Sealed callouts: we cannot backdate a call

The second a callout is sent, the site posts its exact time, a market cap range and a fingerprint (SHA-256) of the token address with a secret salt. When the callout is revealed, the salt is published with it and your browser checks that it matches the fingerprint posted at the time of the call.

Chrome extension permissions

Documentation available

The full list from the manifest of the extension on the Chrome Web Store today (v0.19.8). There are no others: no cookies, tabs, history, downloads, scripting or “all sites” access, and no messages accepted from other extensions.

Permission	Why it is needed	What it technically allows	How Trenchers uses it	Optional
`storage`API	Keep your sessions, paper balance, settings and the callout list between browser restarts.	Read and write the extension's own storage area. It cannot read other extensions' or websites' storage through this permission.	Trading state, paper trades, callouts (kept 8 days), chart cache, preferences.	Required
`unlimitedStorage`API	The price-chart cache can outgrow the default quota.	Lifts the size limit of the storage above. Grants no access to anything new.	Chart cache. Under review: we plan to prune the cache and drop this permission.	Required today
`alarms`API	Run periodic tasks while Terminal is open.	Schedule timers that wake the extension. No data access.	Refreshing prices and callouts, expiring old data.	Required
`api.geckoterminal.com`Host	Price history for the charts.	Send requests to GeckoTerminal from the extension.	Token and pool addresses only. No account or wallet data.	Required
`api.dexscreener.com`Host	Current market cap of called tokens.	Send requests to DexScreener from the extension.	Token addresses only (up to 30 at a time); on Axiom and GMGN, the coin or pool address of the page you open.	Required
`padre.gg (Terminal)`Site access	The Trenchers panel, trade tracking and paper trading run inside Terminal.	Run scripts in Terminal's pages, including one script in the page's own context. That context could technically reach anything the page can, including a connected wallet's provider object.	Reads Terminal's own market and order messages to record prices, plus the fills and balance of the wallets you added on trenchers.si. No call to the wallet provider, no signing, no clicks on Terminal's buttons.	Required
`axiom.trade, gmgn.ai`Site access	The Trenchers panel (callouts, top-ups, paper trading) on Axiom and GMGN.	Run scripts in these sites' pages, in the extension's own isolated context only.	Reads only the coin address in the page URL; its price comes from DexScreener. No script in the page's own context, so nothing of these sites' traffic, wallet or session is read, and real trades are not tracked there.	Required
`discord.com/channels`Site access	Pick up callouts from Discord channels you choose.	Read and change Discord pages under /channels.	Only in channels you switch on, and only messages containing a Solana token address. Your Discord login is never read.	Reads nothing until you switch a channel on
`trenchers.si`Host + site access	Link the extension to your Trenchers account and sync your results to your dashboard.	Send requests to trenchers.si, and run a script on its pages.	The extension sends your trades, trading sessions and paper fills to your own account with a key you can revoke, and reads your access level and the callout feed. The page script only marks that the extension is installed and starts the account link from the Extension page.	Required for dashboard sync

The extension's own pages run under a content security policy that only allows its own scripts: it cannot load or run code from the internet. Learn what each permission means in Chrome's documentation.

Don't trust us. Verify us.

The extension’s public repository goes online in the coming days. The parts that make Trenchers a business stay private, and we say which.

Public

The Trenchers extension you install from the Chrome Web Store: every file of it.
Its permissions and how each one is used.

Repository not visible yet

Private

The Trenchers backend and website code.
How callouts are found and reviewed, and the internal review tools.

Never shipped inside the public extension

Reviewed and published on the Chrome Web Store. Every release goes through Google’s review before it reaches you: the Trenchers.si listing ↗. Chrome installs it from there and keeps it up to date; there is no other download.
Inspect it. It is plain, readable JavaScript, with no minification and no third-party libraries.
Review its permissions. Open chrome://extensions → Trenchers → Details, and compare with the table above.
Watch it work. In chrome://extensions, open the service worker's DevTools and its Network tab: every request the extension makes is listed there.
Report what you find. See Report a vulnerability.

Chrome installs updates from the Chrome Web Store on its own, after Google’s review, and this page always describes the version on offer. Beyond that review, no independent party has audited the source yet.

Data privacy

What we collect: Your X profile (ID, handle, picture, and the email X shares; at sign-up we also check public facts about the X account, its age, to grant free credits), synced trades and paper trades, the wallets you add and their public swap history, your credits and how they were used, promo codes you redeem, referrals (who invited you, the members you invite, commissions and the payout address you give), the extension's device id with the IP address and country of each session, and support messages. For extension connections, we store a fingerprint (hash) of each connection key, never the key itself.
Why: To show your dashboards, run callouts and the one-device rule, prevent abuse of free callouts, and answer support.
Where: In our database and file storage at Supabase. Every table has row-level security switched on.
Who can access it: You, through your session. Trenchers administrators, through server tools, to run the service and support. Not other members.
Retention: Kept while your account exists, and erased within 30 days of a deletion request (server logs are kept briefly by our host for security).
Account and data deletion: Request it from Settings → Security & data; the team erases the account and its data. Download your data from the same place. Deletion is handled by hand today, not instantly.
Processors: Supabase (database, sign-in), Vercel (hosting, anonymous visit statistics without cookies), X (sign-in), Helius (reads the public history of the wallets you add). Market data comes from GeckoTerminal and DexScreener, which receive token addresses only.
In transit: HTTPS everywhere, with HTTP Strict Transport Security. Extension connections use a key you create from your account and can revoke at any time; we keep only its hash.

Read the Privacy Policy and Terms of Service. Both were updated on October 23, 2026 to cover the extension, synced trades, callouts and credits.

Security audits

Independent auditNot yet audited

No independent firm has audited Trenchers yet. When one does, this section will show the auditor, the date, the scope, the full report and what was fixed. We will not show a badge or score in its place.

We do run our own internal security reviews of the extension, website and backend, and fix what they find. An internal review is not an independent audit, and we do not present it as one.

Security FAQ

Can Trenchers steal my wallet?

The analytics features have no way to move your funds: they never hold your private key and never ask your wallet to sign anything. The extension does run on Terminal pages, where a wallet may be connected, so in principle a malicious update could misuse that position. That is why we publish the exact build's SHA-256, keep the permissions minimal, and are publishing the source so anyone can check what each release does. No software is risk-free; keep your wallet's own confirmation prompts on and read what you sign.

Does Trenchers need my private key?

No. Nothing in Trenchers asks for a private key or a seed phrase, and nobody from Trenchers will ever ask for one.

Can the extension execute trades without my permission?

The extension contains no code that signs or sends a transaction, and it does not click Terminal's buy or sell buttons. Paper Quick Buy only changes a virtual balance stored in your browser. Your wallet would still ask you to approve any real transaction.

Does Trenchers trade for me?

No. Trenchers selects the callouts; you buy and sell on your own terminal, with your own wallets. There is no Trenchers wallet and no automated bot. On the site, each callout is posted blurred the second it is sent and revealed 45 minutes later; with credits, the extension gets it at once during your session.

Can I use Trenchers without connecting a wallet?

Yes. Callouts and Paper Trading work without any wallet, and you can look around without an account. Adding a wallet to your Real dashboard is optional: you paste its public address and prove it is yours with a tiny transfer to yourself or a message signature. Neither can move your funds for Trenchers.

Can I use Paper Trading without risking SOL?

Yes. Paper trades use a virtual balance in your browser. They never reach the blockchain and are shown on their own dashboard, never added to your Real results.

How are callouts counted?

You get 25 free callouts when you sign up. A callout sent to you in real time is counted only if it reaches ×1.4 within 24 hours; otherwise it comes back. You can buy more callouts with SOL: you send it yourself from your own wallet, and Trenchers never takes funds from it. See Callouts and top-ups.

How do I revoke trading permissions?

Today there is nothing to revoke: Trenchers holds no trading permission over any wallet. You can disconnect the extension from your account on the Extension page, sign out on every device from Settings, and remove a tracked wallet from your Dashboard.

What data does the extension collect?

Your fills on Terminal (token, time, amounts, fees, result), your paper trades, prices, and callouts from the channels you choose. It sends your trades, your trading sessions (start, pause and end times) and callouts to your own dashboard, and token addresses to GeckoTerminal and DexScreener for prices. See What we can and cannot access.

Is the extension open source?

Its public repository is ready and goes online in the coming days, under the MIT licence; this page will link to it the day it is visible. Until then, the installed extension is its own source: plain, unminified JavaScript you can read in Chrome.

Where do I get the extension?

Only from the Chrome Web Store, where Google reviewed and published it. Chrome installs it and keeps it up to date; there is no other download.

How can I verify the extension's safety?

It is plain, unminified JavaScript with no third-party libraries, reviewed by Google before it was published on the Chrome Web Store. Check its permissions on chrome://extensions and compare them with the table below. See Verify us.

What happens if Trenchers is compromised?

An attacker could read what the platform stores: your X profile, synced trades, tracked wallet addresses, callout history, session IP addresses and support messages. They would find no private keys, because we do not hold any, and no way to move funds from your wallets. A compromised release of the extension is the bigger risk, which is why every release goes through Google’s Chrome Web Store review before it reaches you, and why its permissions are listed here.

Report a vulnerability

How to reach us

Email contact@trenchers.si with “Security report” in the subject. Please don't post the issue publicly until we have fixed it.

Include

What you found and where (page, extension version, endpoint).
Steps to reproduce, and what an attacker could do with it.
Screenshots or a proof of concept, if you have them.

What happens next

We reply to confirm we received it.
We investigate, fix, and tell you when the fix is live.
We credit you here if you want to be named.

Please don't

Access or change other members' data.
Run denial-of-service or spam tests.
Test against wallets or funds that are not yours.