This project is not yet finished. Public release planned end of 2026.Contact us for details
Guides

Security & Data

What's encrypted, what stays on your instance, and exactly what Ionide-operated services ever see.

Ionide doesn't custody funds and isn't an exchange. Your assets stay on the exchange account you connect, and Ionide only ever gets trading-only API access to it. This page covers how your exchange credentials are stored, and precisely what data does or doesn't leave your own self-hosted instance.

How your exchange API keys are stored

  • Keys are encrypted with AES-256-GCM before being written to your instance's local database (a Docker volume, /app/data), using a key you generate yourself: the installer runs openssl rand -hex 32 for you and writes it to your local .env as SECRETS_ENCRYPTION_KEY.
  • The encryption key is independent of your Discord bot token, so rotating one never invalidates the other.
  • /secrets action:status shows which exchanges have credentials configured without ever decrypting them. Stored values are never echoed back in Discord, not even to the bot owner.
  • Decryption happens only in-memory, at the moment the bot places or checks on a trade for you. It's never part of any request to an Ionide-operated service.

What never leaves your instance

Your raw API key, secret, and (for BitgetBitget) passphrase are never transmitted anywhere once you've entered them via /secrets action:set: not to product-api, not to alpha-engine, not in logs. They are used only to authenticate your bot directly with the exchange you selected. If you lose your SECRETS_ENCRYPTION_KEY, those stored credentials can't be decrypted by anyone, including us. You'd need to run /secrets action:set again with a new key.

What Ionide receives automatically

On first start, the bot registers a generated installation ID so Ionide can create an instance identity, even before you run /setup. After setup, requests use that instance ID and an instance-specific access credential; your license key is not attached to every request.

  • Required heartbeat (every 5 minutes, while the bot is running): product version, deployment environment, per-exchange API latency stats, JVM memory/uptime/thread count, and cumulative trade entry/exit outcome counts (successful, failed, simulated). This lets us operate licensing and diagnose reliability issues across self-hosted instances.
  • Error reports (sent immediately, off the bot's main thread, for unexpected failures): redacted exception message, stack trace, short location label, correlation ID, and per-start run ID. This lets us catch and fix reliability problems without waiting for a manual report.

That's the complete list for required telemetry. No exchange credentials, wallet addresses, balances, positions, symbols, sides, notionals, PnL, funding, order details, or trade history leave your instance through it.

Support bundles: sent only when you ask

A support bundle is separate from required telemetry. It uploads only when a bot owner explicitly runs /share-support-bundle with a support-issued, single-use key. It can contain:

  • A sanitized rolling bot log.
  • A sanitized incident journal used to investigate a failure. It can include exchange names, symbols, prices, fees, and order/execution context needed to replay an incident.
  • Small runtime metadata: instance ID, bot version, uptime, memory/thread figures, and whether the incident recorder was enabled.
  • The note supplied with the command.

Known local secrets and common credential patterns are redacted before upload. This materially reduces exposure, but pattern matching over free-text logs cannot guarantee catching every unknown secret shape. If Ionide cannot resolve the local secrets needed for safe redaction, it aborts the entire upload. Support bundles are kept for up to 90 days, then deleted.

Permission scoping

Ionide only ever requests trading permissions on your exchange API key, never withdrawal access. See Adding Exchange API Keys for exact steps per exchange, and run /secrets action:test after setting a key: it checks the key works and, where the exchange's API exposes it, confirms withdrawal permission is actually off. Revoke a key from your exchange's own dashboard at any time: the bot loses trading access immediately but never had a way to move funds out in the first place.

Where your host has a stable public outbound IP, restrict the key with the exchange's IP allowlist. Without one, some exchanges expire API keys automatically. Ionide warns every bot owner in Discord before its conservative estimated expiry date and marks it in /secrets action:status; rotate the key with /secrets action:set. This is an estimate, not an exchange-reported expiry date.

Installer egress-IP check

After a successful install, the installer makes one optional IPv4-only HTTPS request to https://api.ipify.org and prints the address it observes to your terminal. ipify receives that request's source IP; Ionide receives nothing from this check. The result is never written to .env, the database, logs, telemetry, or a support bundle.

This is only a point-in-time observation. It cannot determine whether your IP is static or dynamic, and it does not guarantee that exchange traffic uses the same route. Add the displayed address to an exchange allowlist only when you know your outbound IP is stable. If lookup fails, is invalid, or your host has no IPv4 route, installation continues without displaying an address.

Your own infrastructure

Ionide runs as a container on infrastructure you control. Docker host security (OS updates, SSH access, who can reach your Docker daemon) is your responsibility, the same as any other self-hosted service. See Self-Hosting Ionide for what the installer does and where the encryption key and database live so you can back them up.

Questions?

Reach out on Discord or [email protected].