Security is part of the architecture.

BXK Trader Pro is being designed so broker access, user isolation, and execution permissions are explicit parts of the system rather than conveniences added later.

Broker authorization

Where supported, broker connections use OAuth authorization. Broker tokens are associated with the individual BXK Trader Pro user and stored in encrypted form.

Account isolation

Broker connections and selected accounts are scoped per user. The application is designed to fail closed when a user does not have access to the requested broker connection or account.

Connection removal

Supported broker integrations include a user-controlled disconnect path. For Schwab, BXK Trader Pro removes the locally stored authorization tokens and linked account metadata when the user disconnects. Any separate broker-side revocation requirement depends on the final approved broker workflow.

Execution controls

Account-data access and trade execution are treated as separate capabilities. A broker being available as a data source does not automatically make it an execution broker.

Support safety

BXK support will not ask users to send brokerage passwords, access tokens, refresh tokens, API secrets, Social Security numbers, or payment-card numbers through support messages.

Responsible disclosure

Security information on this page describes the product design and is not a certification, warranty, or guarantee that a security incident cannot occur.