Insider MEVINSIDER

Privacy Policy

Privacy Policy

LAST UPDATED — AUGUST 2026

Insider is built to know as little about you as possible. This policy explains what the Service processes, what it never touches, and the choices you have.

01

What we never collect

Your private keys never leave your side: they are generated client-side or imported by you and are used only to sign the transactions you configure. We do not collect names, emails, phone numbers, government IDs, or payment card data. There is no KYC.

02

What the bot processes

To operate, the Telegram bot processes your Telegram user ID and username, the wallet addresses you create or import, your strategy settings (chains, caps, slippage, stops), and the on-chain activity of those addresses. On-chain data is public by nature.

03

What the website processes

insidermev.com serves static pages and keeps standard, short-lived server logs (IP address, user agent, requested path) for security and abuse prevention. The site sets no advertising trackers and runs no third-party analytics.

04

How data is used

Operational data is used to run your configured strategies, route transactions through private relays, show you your own history, and keep the Service safe. It is not sold, rented, or used for advertising.

05

Third-party infrastructure

Executing on-chain requires third parties: RPC node providers, private relay operators, and the Telegram platform itself. They see the data inherent to their role (e.g. a relay sees the transactions it lands). Their processing is governed by their own policies.

06

Retention and deletion

Operational records are kept while your wallet is active and for a reasonable period afterwards for security and dispute purposes. You can stop using the Service at any time; contact support to request deletion of the off-chain records tied to your Telegram account. On-chain history is permanent by design and outside anyone's control.

07

Contact

Privacy questions and deletion requests go to the support channel linked below.

Questions about this document?

Contact support