Privacy

Your account

Your email address and a bcrypt hash of your password, never the password itself. Also your role, whether the account is active, when you signed up and last signed in, when your email address was confirmed, whether you chose the email digest, how many AI calls your routes and backtests made this month, and which AI allowance notices you were sent this month. Signing in with Google stores the email address Google confirms and nothing else from Google.

Exchange connections

Each connection’s name, exchange and settings, and its API key and secret. Keys are encrypted (AES-256-GCM) before they are saved and are never shown back in the app, including to you. A Telegram bot connection stores the bot’s username and network. If an exchange refuses a connection’s key, the time it started refusing it is kept until the key works again or is replaced.

Telegram session

Mirrorpipe reads channels through its own Telegram account. That account’s login session and API credentials are stored encrypted. Mirrorpipe stores no Telegram login of yours.

Channels and their messages

The channels you add (Telegram id, title and username) and the messages posted in them: text, formatting, the sender’s Telegram id, which message it replies to, and when it was posted. Each message is stored once, even when several users’ routes read it.

Routes and trade records

Your routes’ settings, risk limits and rules. For each message a route reads: the signal found in it, each order request sent to your exchange with the exchange’s reply, and each trade (symbol, direction, entry, stop-loss, take-profits, size, status, profit and loss, and when it opened and closed). Paper and backtest trades are stored the same way.

Notifications

The notifications shown in the app’s notification inbox: your trades, an exchange refusing a connection’s API key, and your use of this month’s AI allowance at 80% and when it runs out. When it runs out, each admin is also notified, with your email address.

Security records

Password reset tokens, stored only as a hash and valid for one hour, and short-lived counters that limit sign-in and reset attempts, keyed by IP address or a hash of the email address.

Service logs

The app logs events and errors. Some entries include your email address or account id.

You see everything above that belongs to your account. Other users cannot see your account, connections, routes or trades.

Mirrorpipe admins see the user list in the admin area: each user’s email address, role, plan, status, sign-up and last sign-in times, and how many routes and recent signals they have. The people who run Mirrorpipe can also read the database directly. Encrypted keys and the Telegram session are decrypted only inside the service, to check and place orders and to read channels.

Services that do part of the work receive what that work needs. Your API key and secret travel with each order to Mirrorpipe’s order relay, which signs the order and sends it to your exchange. When AI parsing is on for a route, message text is sent to the AI provider that reads it (OpenAI, Google Gemini or Groq). A Telegram bot you connect receives the contract addresses your routes forward. Google handles sign-in if you use Google. When email is enabled, the email provider (Resend) receives your address to send reset links and digests.

To have your account and its data deleted, ask a Mirrorpipe admin.