Privacy policy

Trenchpilot is software that watches new Solana launches and trades by the rules you set. This site is where you use it.

Questions, complaints and deletion requests about this policy go to @trenchpilotbot on X.

What we hold depends on how you signed up and how far you have progressed in the product.

If you sign in with Google

We ask Google for two permissions: openid and email. That gives us your Google account ID, your email address, and whether Google has verified that address. We don't request your name, profile picture, Gmail, Drive, Contacts, Calendar or anything else.

We store the ID because it doesn't change. Email addresses can be reassigned.

We use what Google gives us only to create your account, recognise you when you come back, and contact you about your account if we need to. Trenchpilot's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We don't use it for advertising, we don't sell it, and we don't use it to train any AI model.

If you sign up with an email address and password

We store your email address and a scrypt hash of your password. We never store the password itself and never write it to a log. Nobody at Trenchpilot can read it or recover it for you.

If you sign in with Phantom

We store your Solana address. To prove the wallet is yours, we send a one-time message for you to sign, check the signature, then discard the message. We never see or ask for your private key or your seed phrase. Nobody from Trenchpilot will ever ask you for either, on any channel, for any reason.

On every account, whichever way you joined

• When the account was created and when you last signed in.
• How you signed up and your access level, since registering and being let in are separate steps.
• The page you arrived from, taken from the referring URL your browser sends. It shows us whether people come from X, a friend or search.

While you are signed in

Each sign-in creates a session record: when it was created, when it expires, your IP address and your browser's user-agent string. We keep the IP and browser so we can tell one session from another.

We also log sign-in attempts: the email or wallet address that was tried, the IP it came from, and whether it worked. We use this to stop password guessing against your account, and for nothing else.

Once you have a trading wallet

We store your trading wallet address, the wallet address registered with it, whether it's in paper or live mode, and the internal identifiers needed to run it.

Once your bot is running

We record what your bot decided and did: the token, what made it look at that token, which of your rules passed or failed and the numbers it saw, and, for each position it opens, the entry, the exit, the size, the profit or loss, and the fees. This is your trading history. It powers the dashboard, we use it to investigate how a strategy behaved, and the aggregate figures shown on the website are built from it. Those figures contain no identifiers.

If you request access

The access form asks for your X handle, which is required, and optionally a wallet address, a Telegram or Discord handle, what you do, and a short note. We also record the page you came from and the two-letter country code our host works out from your IP. We use all of it to decide who to let in, and for nothing else.

• No analytics and no tracking. We use no analytics tools, no error-tracking services, no tracking pixels and no session recorders. The site loads no third-party analytics or advertising scripts.
• No advertising. We don't run ads, we don't share anything with ad networks, and we don't build advertising profiles.
• We don't sell or rent your data. That includes data brokers and any other third party.
• We don't train AI models on your data. The strategies are sets of rules you configure. Your email, your identity and your trading history are not training data, and nothing from Google is used for developing or improving any generalised or foundation model.
• We don't ask for identity documents. No passport, no driving licence, no selfie, no proof of address. If the law requires that to change, we will update this policy beforehand.
• We send transactional email only. That means a password-reset link when you ask for one, and a notice when your access is switched on. There is no mailing list and no marketing email. These messages go through our email provider, listed below, which sees your email address and the message and nothing else.

We set two cookies. Both are ours, both are strictly necessary, and neither tracks you. We show no consent banner because neither cookie needs consent.

• tp_session keeps you signed in. It holds a random token and nothing else. Our database stores only a hash of that token, so we can't rebuild the cookie. JavaScript can't read it, it isn't sent on cross-site requests, and it lasts 30 days.
• tp_goog exists only while a Google sign-in is in progress and expires after ten minutes. It carries one-time values that stop anyone else's sign-in being slipped into your browser.

These are the main services that handle your data.

We would hand data over if a court or other authority with the power to compel us issued a valid order. If we receive one, we'll tell you, unless we're forbidden to.

The database is in Frankfurt, Germany, and so is the website code that reads it. Account and trading records are stored inside the EU.

Some processing happens in the United States. Our trading engine runs there, Google handles the sign-in itself, and our wallet provider holds the wallet key material. Google and the wallet provider are US companies.

• Your account lasts until you ask us to delete it.
• Sessions expire 30 days after your last visit, and immediately when you sign out.
• The Google sign-in cookie expires after ten minutes.
• Sign-in attempt logs and trading history are kept for as long as the account exists.
• Access requests are kept for as long as we need them to review applications. Ask us at any time and we will delete yours.

Once you turn a strategy on, it trades without asking you first. In live mode that means software is making decisions with your real money, so you should know how it works and how to stop it.

A strategy is a set of rules you choose and can see. It watches new Solana launches and checks each coin against those rules. If a coin passes, it buys the size you set and exits on the plan you configured. The dashboard shows every decision, including each coin it skipped and why.

You can lose everything you put in. Trades happen without your approval, and memecoins are extremely volatile. You can pause or turn off any strategy at any moment, you can revoke our permission to swap altogether, and you can message @trenchpilotbot on X to challenge anything the system did.

Solana is a public ledger. Every trade your bot makes, including the amounts, the timing and the wallet addresses involved, is visible to anyone, permanently. Block explorers and analytics firms we have no relationship with already index it.

Nobody can delete that, us included. If you ask us to erase your data, we can remove everything on our side, including the link between you and your wallet address, but the chain keeps its own record and always will. A wallet address isn't anonymous. Anyone who learns that an address is yours can read everything it has ever done.

Depending on where you live, you may have legal rights to see your data, correct it, delete it, get a copy, restrict what we do with it, or object to it. We'll honour all of those for anyone who asks, wherever you are.

To delete your account, message @trenchpilotbot on X with the email or wallet address on your account. We will check it is yours, delete it by hand and confirm what was removed and what remains.

You can also withdraw access yourself, without asking us. Revoke Trenchpilot's access to your Google account at myaccount.google.com/permissions, and revoke our permission to swap in your wallet whenever you like. Neither affects your funds.

If you are in the EU or the UK and have a concern about how we handle your data, you can complain to your national data protection authority. You are welcome to contact us first, but you do not have to.

• Everything travels over HTTPS, and the session cookie is marked secure.
• Passwords are hashed with scrypt and a random salt for each one. We never store or log the plain password.
• Session tokens are stored only as a hash, so someone who read every stored session still couldn't sign in as you.
• The website holds no key that can touch your funds. The credential for our wallet provider lives in a separate service that serves no web pages.
• Sign-ins are rate limited, and every form checks that the request came from this site.
• The database cannot be queried through any public API. Only our own server code reads your data.

None of this makes a breach impossible. If one affects you, we'll tell you what happened, what was taken and what to do, as soon as we know the facts.

Trenchpilot is not for anyone under 18. We don't knowingly hold data about children. If you believe a child has created an account, message us and we'll remove it.

We update this policy when what the software does with your data changes. The date at the top shows when it was last updated.

If we ever want to use your data for something new, we'll ask you first.

Questions, corrections or deletion requests: @trenchpilotbot on X.