When you hand your Binance API key to a web-based trading bot, you are making a significant trust assumption: that their servers will never be hacked, their employees will never go rogue, and their infrastructure will never suffer a breach. History shows this assumption fails regularly.
The Web Bot Attack Surface
A typical web trading bot collects:
- Your Binance API key and secret (with trade permissions)
- Your strategy parameters
- Your trade history
- Your email and payment details
All of this sits on a central server. One successful attack on that server compromises every user simultaneously.
PumpTraderCEX's Approach
PumpTraderCEX is a desktop application. It installs on your machine and runs there. The Paper Trade version uses only Binance's public, unauthenticated market data endpoints — no API key required at all.
When the Pro Live Trader module launches, your Binance API key will be stored in an encrypted local config file on your own machine — never transmitted to or stored on our servers. The live engine communicates directly between your machine and Binance's API, with no middleman.
Your strategy configuration, trade history, session data, and filters are stored in local SQLite databases on your own machine throughout both tiers.
What We Do Receive
When you activate a license, we verify the license key. That is the only network request our infrastructure processes. We do not receive trade data, strategy parameters, API keys, or any market activity from your session.
The Practical Implication
Even if our entire website went offline tomorrow, your installed PumpTraderCEX application would continue to function exactly as before. Your data is yours — in paper mode and in live mode.
