Security baseline
The service uses encrypted HTTPS connections, verified email authentication, optional authenticator-app verification, private user-scoped data, server-side authorization, rate limits on sensitive actions, anti-automation checks, hardened browser security headers, signed Stripe webhook verification, and security-event logging.
- Authentication and authorization are enforced on the server.
- User records are queried within the authenticated user scope.
- Sensitive actions are subject to validation, rate limits, and event logging.
Integration security model
Planned platform connections begin with the least privilege necessary for account visibility. Where supported, KR Control Tower will use provider-hosted OAuth or another documented, revocable authorization method.
- Read-only access is the preferred initial scope.
- Live trading-platform passwords are not collected. The restricted Rithmic Test review uses explicitly consented, temporarily encrypted Test credentials.
- Execution or order-management permissions require separate provider approval, security review, and testing.
- Connection, expiry, error, and revocation states will be visible to the user.
Payment protection
Stripe hosts payment collection and billing management. KR Control Tower receives subscription status and identifiers but does not store full card numbers or card security codes.
Trading credentials
Never send passwords in support tickets or enter live broker or prop-firm credentials. The Rithmic Test form is restricted to the owner and verified provider reviewers, accepts Test credentials only, uses user-bound AES-GCM encryption for up to eight hours, and removes stored credentials on disconnect. Expired credentials cannot be used and expired ciphertext is removed on the next status check. Other connections use provider authorization where available.
Data handling
KR Control Tower limits collection to information needed to operate the service, maintain account records, provide support, prevent abuse, and meet legal or operational requirements. Future integration data will be documented by provider, scope, and purpose before activation.
- Data in transit is protected through HTTPS.
- Administrative access is restricted to operational need.
- Provider tokens are treated as sensitive and must remain server-side.
- Manual, delayed, live, and unavailable data are labeled distinctly.
User responsibilities
Use a unique password, activate authenticator protection in My Profile, secure the email account connected to KR Control Tower, sign out on shared devices, and report unexpected activity immediately. Support will never ask for your password, authenticator code, or complete payment-card number.
Reporting a concern
Report suspected account compromise, exposed data, abusive activity, or a security weakness through the Help Center using the Technical category. Include steps to reproduce but do not include passwords, private keys, or full card data.
Continuity and recovery
Operational health checks, audit history, user data exports, and administrator backup exports support troubleshooting and recovery. External monitoring checks the public application and health endpoint. Additional recovery automation will be expanded before a full public launch.
Responsible disclosure
Security researchers and users should submit a concise report through the Help Center. Do not access another user’s information, disrupt the service, expose a vulnerability publicly before coordinated review, or include secrets in the report.