Security & Reliability
Security controls built for live trading automation
This page summarizes how TradeDupe protects credentials, monitors execution health, and responds to incidents. Last updated on March 3, 2026.
Credential security
Credentials are encrypted at rest using AES-256-GCM before storage.
Encryption keys are managed separately from credential records.
Plaintext credentials are never written directly to the database.
Access to production data is restricted to authorized operational workflows.
Reliability controls
Persistent account health checks monitor websocket and session state.
Automatic reconnect and retry workflows recover from transient failures.
Rogue-trade protection flattens unauthorized follower fills to restore alignment.
Execution and recovery events are journaled for post-session auditability.
Telemetry methodology
Latency metrics are measured server-side from the timestamp where a leader execution report is ingested to the timestamp where follower orders are dispatched to the broker API.
Copy success rate is calculated as successful follower placements over expected follower placements for enabled accounts. Disabled followers are excluded from the denominator.
Uptime reflects availability of the copy worker infrastructure and its execution pathways. Degraded periods are captured in operational logs and reviewed for remediation.
Incident response standards
Severity-based response: service-impacting incidents are triaged immediately.
Investigation includes scope, root cause, and remediation documentation.
Post-incident improvements are prioritized to reduce repeat failure modes.
Customers receive status communication when issues affect execution quality.
Need help or have due-diligence questions? Contact us through the help page.