Security
Built so we can't touch your capital.
Institutional security isn't a feature — it's the foundation. Zephirex is non-custodial, read-only by design, and engineered so that even we cannot move your funds.
Security architecture
Application-Layer Credential Isolation
AES-256 · at rest
API keys and credentials are encrypted at rest using AES-256. The encryption key is derived from your account credentials and is never stored in plaintext on Zephirex servers. During live strategy execution, the Order Execution Service accesses encrypted credentials within a strictly isolated, audited runtime. No credential value is ever exposed to user-facing services, logged, or readable outside this boundary.
Read-Only API Enforcement
Scope · read-only
Exchange connections are scoped to read-only permissions wherever the venue allows. Keys that include withdrawal or transfer scopes are rejected at the integration layer before they are ever stored on your account.
Withdrawal Restriction
No custody · ever
Zephirex is non-custodial. We never hold, transfer, or withdraw your capital. Even if a key were mistakenly granted withdrawal scope, our platform has no mechanism to initiate a withdrawal — the capability does not exist in our codebase.
Sandboxed Strategy Execution
Isolated · per strategy
Every strategy runs in an isolated runtime with bounded resources and no access to other strategies, your raw credentials, or the host environment. A runaway strategy cannot escape its sandbox or touch another portfolio.
Mandatory TOTP 2FA
TOTP · enforced
Time-based one-time passwords are required for every account and for every privileged action — API key management, strategy deployment, and settings changes. Password-only access to sensitive operations is not supported.
Audit Logging
Immutable · per action
Privileged actions are recorded in an append-only audit log — who did what, when, and from where. You can review the history of access and changes on your account at any time.
Phased Secrets Management
Vault-ready · Phase 2
Credential storage is architected for migration to HashiCorp Vault in Phase 2, providing hardware-grade secret isolation, dynamic credential rotation, and scoped access tokens per execution context.
Read-only API connections
We connect to read. We cannot move.
When you link an exchange, Zephirex requests the narrowest scope the venue offers — read access to balances, positions, and trade history. That data powers your analytics, PnL, and simulation without granting any ability to act on your account.
Keys that include withdrawal or transfer permissions are rejected before they're stored. If a venue cannot provide a read-only scope, we default to the most restrictive scope available and surface the limitation clearly in your dashboard.
connection_policy
- scope
- read-only
- withdrawal
- rejected
- trade
- opt-in only
- storage
- encrypted
- logging
- no secrets
- custody
- none
Risk disclaimer
ZephirexULTRA is a software tool and does not constitute financial advice. All trading involves risk. Past performance does not guarantee future results. You are solely responsible for all trading decisions and for the security of your own exchange credentials.