Your keys. Your money. Your control.
easiTrades is designed so the platform can watch the market and do the math — but never move your money without you.
Signals, not orders
In the default mode easiTrades only tells you what to do. It places no trades and moves no funds. Execution stays entirely at your broker, in your hands.
Encrypted credentials
Broker and market-data keys are encrypted at rest and scoped to your account. They're used only to read prices and — if you ever opt in — to place orders you've explicitly authorized.
Per-tenant isolation
Every account is a separate tenant. Your roster, rules, positions, and keys are partitioned and access-checked on every request — never mingled with anyone else's.
The control model
easiTrades separates watching from acting on purpose. The engine continuously reads market data and evaluates your rules. When a level is crossed it produces a signal — a recommendation with the exact ticker, shares, and price. Turning that signal into a trade is a human step you take at your broker.
Later, an optional execution mode can place your orders automatically through a connected brokerage API. It is off by default, opt-in per symbol, and begins in a paper-trading environment. The rules and guardrails are identical — only the final "act" step changes, and only when you deliberately enable it.
How your keys are handled
- Stored encrypted at rest and associated only with your tenant.
- Used for the minimum necessary scope — market data, and orders only in opt-in execution mode.
- Never written to logs, never exposed in the interface, never shared across accounts.
- Revocable at any time from your side at the provider — the platform degrades gracefully to signals-only.
What we store — and what we don't
To do its job the platform keeps your roster and rule settings, the positions and lots you record, the signals it generates, and a rolling log of prices for the names you watch. It does not need or store your broker password, your bank details, or the ability to withdraw funds.
Access to the account
Access is authenticated per request, and every write is checked against the tenant that owns the record — a signal, position, or setting that isn't yours is invisible, not merely restricted. Administrative actions are auditable.