Privacy Policy & Telemetry Disclosure
GDPR & CCPA COMPLIANCE SPECIFICATION // LAST AUDITED: OCTOBER 2026
1. Zero-Retention of Private Keys and Trading Credentials
EMI operates with a strict zero-knowledge security standard regarding private trading credentials. Exchange API keys entered in your private institutional desk are never transmitted to external third-party servers or marketing trackers. They remain strictly confined to your self-hosted instance and environment variables.
2. Telemetry and Backtest Evaluation Data
When utilizing public Atlas comparison utilities or Symphony Studio simulations, anonymous execution metrics (such as backtest duration, simulated CAGR, Sharpe ratio, and asset ticker symbols) may be cached ephemerally in Redis to accelerate subsequent requests for identical parameter trees. No personally identifiable information (PII) is attached to these mathematical computation caches.
3. Cookies and Session Tokens
EMI utilizes secure, HTTP-only JWT cookies (access_token) strictly for session authentication and RBAC authorization verification. We do not use third-party advertising tracking cookies or behavioral profile aggregators.
4. Telegram Bot Alert Subscriptions
If you optionally configure Telegram regime flip alerts, your Telegram user ID or channel ID is stored solely for the technical delivery of the specific notifications you requested. You may cancel or remove your notification preferences at any time.