Privacy · current product
Your trading record should stay yours.
Signal Bridge is being built around private member records. This page describes the data the current community and member tools may handle today, without pretending every future feature already exists.
What the current system may store
- Discord account identifiers and membership/access information needed to connect a member to the workspace.
- Journal text, trade details, tags, strategy/version metadata, session events, and review records you submit or create.
- Chart screenshots, evidence references, or trade-import data when you choose to add them.
- Technical records needed to operate sign-in, event history, reliability, and troubleshooting.
Why it is used
The data is used to provide member access, preserve your journal and strategy history, connect live-session events to later review, operate the product, and diagnose failures. Signal Bridge does not need your brokerage password to provide the current product.
Where the current product runs
The community and identity layer uses Discord. The public website is published from GitHub Pages. Current hosted member and session services run on Cloudflare infrastructure. Those services have their own platform policies in addition to this notice.
Private versus public
Member journal records and workspace data are intended to remain private unless a record is deliberately selected for sharing or publication. Public research/examples should be treated separately from a member’s private operating record.
Data requests
Self-service deletion is still being improved. For the current product, request access, correction, or deletion through the Signal Bridge Discord so the request can be tied to the correct member identity.
Open Signal Bridge Discord →