Read-only platform design
The public service is not designed to place, route, copy, cancel, or modify orders. Connector and API event types are allowlisted.
Security is an ongoing operational program. No system is completely immune to defects, attacks, provider failures, or human error.
The public service is not designed to place, route, copy, cancel, or modify orders. Connector and API event types are allowlisted.
Account and journal data is separated by workspace so one customer cannot access another customer’s records.
Platform secrets are excluded from browser storage, email, logs, exports, and user backups. Connector device credentials are revocable.
HTTPS is required. Managed infrastructure encryption, signed links, secret management, and restricted storage access protect data.
Verified email, secure sessions, optional TOTP multifactor authentication, recovery codes, active-session review, and login alerts are supported.
Structured logs, audit events, rate limits, webhook verification, idempotency, backups, restore procedures, and incident response support reliability.
Send a clear report to security@tradechrona.com. Include affected URL or component, reproduction steps, impact, and a safe proof of concept. Do not access other users’ data, disrupt the service, or include secrets in the initial email.
A formal coordinated-disclosure and safe-harbor policy must be reviewed before public launch.
Read the Privacy PolicyChoose a manual calendar plan or connect the accounts and research tools that fit your process.