Security
Secure account connections and clear trading control.
TradeLuma uses clear user permission, limited broker data, secure connection methods, visible activity records, and controls that can pause live automation.
Encrypted transport
TradeLuma is designed for HTTPS-only access, secure browser sessions, and encrypted communication with supported infrastructure providers.
Limited credential exposure
Where supported broker connection providers are used, sensitive broker authentication steps are handled through provider or broker flows instead of being typed into TradeLuma pages.
Paper and live separation
Paper and live accounts are kept separate so testing cannot silently become live trading.
Clear activity record
Received alerts, blocked decisions, submitted orders, cancellations, fills, and broker account checks remain visible for review.
Pause controls
Live automation can be paused at the user, broker account, or platform level when a safety or connection issue appears.
Limited data use
Broker data is used for account connections, account checks, authorised orders, order updates, and position comparison—not to provide financial advice.
Security model
Protected access should remain clear to the user.
TradeLuma is designed so that secret handling, account permissions, activity records, and pause controls stay understandable to the user rather than hidden behind opaque security language.
Operational security
Secure automation continues after login.
TradeLuma also checks broker permissions, paper or live mode, order limits, connection health, data freshness, and the ability to pause trading when something is wrong.