On this page
1. Data acquisition and telemetry logging
To facilitate 24/7 low-latency order routing, AxiomTrigger systematically collects, encrypts, and stores specific operational datasets. This includes, but is not limited to: user profile identifiers, IP addresses, Binance API keys, API secrets, and granular trade telemetry (execution timestamps, slippage metrics, funding-rate payments, order states, and WebSocket error logs).
2. Cryptographic security
Binance API credentials are encrypted at rest using industry-standard AES-256-GCM with per-user keys (the user_id is bound as Additional Authenticated Data, so a leaked ciphertext cannot be moved between user rows). AxiomTrigger uses these credentials strictly to:
- Execute your algorithmic perpetual-futures trades.
- Query live Level-2 order-book data, klines, and funding-rate metadata.
- Verify position states against our local database via synthetic state-reconciliation loops.
- Place and cancel protective stop-loss / take-profit reduce-only orders on your behalf.
3. International data compliance and sharing
AxiomTrigger acts as a Data Processor regarding your operational information. We do not aggregate user data for sale to third-party marketing or data-brokerage entities. Trade execution data is shared exclusively with your connected exchange (Binance) to fulfil order routing.
Telemetry may be utilised internally on an aggregated, pseudo-anonymised basis for the empirical optimisation of our execution algorithms and fault-tolerance regression testing. Such aggregate data cannot be reverse-engineered to identify individual users.
Payment information (card / UPI / cryptocurrency transaction hashes) is handled entirely by our payments partner and never touches AxiomTrigger servers.
Privacy questions or data-deletion requests: [email protected].