Trust
This page is maintained by the CW Trades team to answer common security and privacy questions about CW Trades. It describes controls that are in place today — it is not a certification, an audit report or independent verification.
Access requires an authenticated account. Every workspace is isolated at the database level with row-level security, so members only ever see data belonging to workspaces they have been granted access to. Workspace roles determine who can manage accounts, connections and settings.
CW Trades runs on Lovable Cloud managed infrastructure. Application traffic is served over HTTPS, and data is stored in a managed Postgres database with access controlled by policy rather than by application code alone.
Broker credentials are handled server-side and stored encrypted. They are never exposed to the browser and are not returned by any client-facing interface. Broker connections operate read-only by default; controls that change account state are separate, explicit and individually recorded.
CW Trades stores the trading data you import or synchronise, the journal and planning content you write, your workspace configuration and operational records such as import lineage, risk events and command history. Trade identities, risk events and lineage records are append-only.
CW Trades uses cookies and local storage necessary to keep you signed in and to remember workspace preferences. See the privacy policy for the current position on any analytics processing.
You can export your data from Settings at any time. You can also request account and workspace deletion from Settings; deletion removes your workspace data according to the process described in the privacy policy.
If you believe you have found a security issue, contact us through the support page with enough detail to reproduce it. Please do not test against other users' data.
Managed hosting, database isolation, encrypted storage of credentials and authenticated access.
Enforcing workspace isolation policies, keeping broker access read-only by default, and recording an audit trail for imports, risk events and broker commands.
Protecting your sign-in credentials, choosing who you invite to a workspace, and confirming any destructive broker control before you authorise it.
Questions about a specific requirement? Raise a support request from inside CW Trades and we will answer directly rather than guess in public copy.
