Help Center for setup, billing, exchanges, and Ultra operations.
Start with the operational basics, then move into exchange permissions, billing, security controls, and Ultra execution rules.
A practical knowledge base for setup, safety, and daily operation.
Support command
Categories
Getting started
Account setup, onboarding order, and what to prepare before connecting an exchange.
Billing
Plans, renewals, invoices, and what happens during grace or cancellation windows.
Exchanges
API key scope, safe permissions, revalidation, and exchange-specific operational rules.
Security
2FA, session invalidation, email verification, account recovery, and privacy controls.
Ultra
Signal fanout, risk limits, cooldowns, partial fills, and futures-specific guardrails.
Getting started
Account setup, onboarding order, and what to prepare before connecting an exchange.
Account setup checklist
The minimum safe sequence before you connect capital: verify email, enable 2FA, review risk profile defaults, then connect trade-only exchange keys.
- Use a unique password and verify the inbox before doing anything exchange-related.
- Enable TOTP 2FA and store backup codes offline before your first live session.
- Connect only exchange keys with withdrawals disabled and trading permissions enabled.
Billing
Plans, renewals, invoices, and what happens during grace or cancellation windows.
Billing lifecycle basics
Subscriptions move through activation, renewal, grace, and expiry states. Operational access follows the recorded plan state instead of optimistic payment assumptions.
- Invoices and renewals are idempotent; the current plan changes only after verified payment transitions.
- Grace windows keep access temporary, but expiry is enforced if payment does not recover in time.
- Unsubscribe and notification preferences are applied before lifecycle email delivery.
Exchanges
API key scope, safe permissions, revalidation, and exchange-specific operational rules.
Exchange permissions and safe mode
CryptiDex treats exchange connectivity as fail-closed. If permissions, balances, or network reachability cannot be proven, the connection stays unsafe and trading does not proceed.
- Withdrawal-enabled keys are rejected even if trading permissions look valid.
- Revalidation can downgrade a previously safe connection when exchange proofs fail later.
- Multi-exchange portfolios rebalance per exchange; balances can still be aggregated for reporting.
Security
2FA, session invalidation, email verification, account recovery, and privacy controls.
Security and recovery controls
Security controls are designed to be usable: email verification, pending-email swaps, session invalidation, backup-code recovery, and privacy-driven deletion all follow explicit server checks.
- Email changes are completed only after the pending address is verified.
- Force logout and deleted-user lockout are enforced at the session layer.
- GDPR export, recovery windows, and hard-delete anonymization are part of the same privacy system.
Ultra
Signal fanout, risk limits, cooldowns, partial fills, and futures-specific guardrails.
Ultra risk operations
Ultra uses one master signal, fans it out across eligible users, and still applies per-user risk gates before any execution helper can open or manage a position.
- Probability, spread, cooldown, weekly loss, and stop-trade gates can all convert a signal into NO_SIGNAL.
- Partial fills, double-fill prevention, and BE+/TP handling are deterministic and logged.
- The journal and dashboard reflect the execution state instead of pretending every signal becomes a trade.