API keys and exchange secrets are encrypted at rest at the point of intake, and access is isolated from any public-facing endpoint. When a bot needs to issue an order, the credentials are decrypted in a short-lived in-memory context and discarded immediately after the API call returns. Keys are never exposed through the product: no dashboard view, export, or support tool reveals them.
Every CEX integration requires API keys with trade scope only. No withdraw, no transfer, no internal-conversion permissions. We validate the scope at key intake and reject any key that includes restricted capabilities.
Practically, this means the worst-case impact of any breach (yours, ours, or the exchange's) is a bad trade. Not a missing balance. We cannot move your funds even if we wanted to.
On-chain bots run from a dedicated trading wallet, separate from your main wallet. You provide that wallet's key, which is encrypted at rest and used only to construct and execute the swaps you configure. We never ask for your primary wallet's key. Because the bot signs autonomously with this key, treat the DEX wallet as a hot trading wallet: fund it only with capital you're actively trading, and withdraw anytime.
Every order placed, every fill received, and every config change is recorded with a timestamp, source identifier, and full parameters. The audit log is visible in the dashboard in real time, filterable by bot, venue, time range, and event type, and we can share your full log file on request. There is no internal data we hide from the account that owns it.
The constraints we lock in are as important as the features we build.
Use this checklist before trusting anyone, including us, with your token's market.
Email contact@coinner.co or reach out on Telegram. We acknowledge security reports within 24 hours and work with researchers in good faith. We don't run a public bug bounty yet, but we credit responsible disclosures.