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.
Private support request text, a ticket reference/status, and member-linking metadata if the Discord /help path accepts your request and returns a ticket reference.
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, follow up on private support requests, 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 current public Beta site is distributed through Cloudflare Pages. The current v2 session-event and Journal service uses Supabase-hosted database and Edge Function infrastructure. Legacy and auxiliary Signal Bridge routes may continue to run on Cloudflare Workers during the staged cutover. These providers operate under their own platform policies in addition to this notice.

Private versus public

Member journal records, workspace data, and accepted private support requests are intended to remain private unless a record is deliberately selected for sharing or publication. Raw private help-request text is not sent to the public product-analytics funnel. Public research/examples should be treated separately from a member’s private operating record.

Deletion and data requests

Individual Journal records can be moved to Trash and then permanently deleted from the protected member Journal. Broader access, correction, or deletion requests can include member identity, workspace records, and any private support ticket that was actually created for that member. Those broader requests still require identity verification during the current Beta so the wrong member’s data is not changed or removed.

See the current Data Request process →

Signal Bridge should only promise deletion that the active storage paths can actually perform. No fixed support-record retention promise is being made here. This notice will be updated as durable evidence storage, account controls, AI features, business identity, support operations, and infrastructure change.