Security
Draft · October 2026
These are the practices we follow when we build and hand over a system. They lower risk; they do not remove it. We have no third-party security audit or certification, and we don’t claim one.
Keys and wallets
- We never ask for seed phrases, private keys or exchange passwords via Instagram, TikTok or any DM.
- We recommend a dedicated trading wallet, separate from your main holdings, funded only with what you are prepared to lose.
- You create that wallet and enter its key into the system yourself. We document where and how it is stored.
- We don’t hold, pool or move your funds. There is no deposit to us other than the agreed invoice.
Built-in safety rails
- Position size, maximum open positions, exit rules and a wallet reserve are part of the configuration, not optional extras.
- A pause switch stops new trades immediately.
- Every decision is logged with the rule that caused it, so you can check what the system did and why.
Infrastructure
- The system runs on your computer or on a server in your name. You hold the logins.
- Secrets live in environment files or the platform’s secret store — never in source code or chat.
- Third-party services (RPC, server, Telegram bot) are registered to you, so you can revoke access at any time.
Handover
- Written documentation: what runs where, which keys and accounts it uses, and how to stop it.
- If we needed temporary access during setup, we list it — and you rotate those credentials after delivery.
- Code and dependency versions are pinned, so the delivered system does not change underneath you.
This website
- Static site. No accounts, no logins, no wallet connection, no payments.
- No cookies, no analytics, no third-party scripts.
Spotted an issue?
DM us on Instagram or TikTok. Please don’t post vulnerabilities publicly before we’ve had a chance to fix them.
