Data request · current Beta process
Know what is self-service and what still needs verification.
Signal Bridge links private member records to a Discord identity. The current process uses that identity to avoid deleting or exposing the wrong member’s data.
Delete an individual Journal record yourself
In the protected member Journal, move the record to Trash, then choose Delete permanently. The current member workflow requires the record to be archived first and then permanently removes that Journal record and its linked strategy observation. This action cannot be undone.
Request broader access, correction, or deletion
For a broader request covering your member identity, workspace records, or a private support ticket that was actually created for you, use the Signal Bridge Discord from the same Discord account tied to your workspace. State whether you want access, correction, or deletion and identify the scope as clearly as you can. A private /help ticket may be included in that scope when that path accepted the request and returned a ticket reference.
What not to send
Do not post passwords, brokerage credentials, API keys, authentication codes, one-time login links, session cookies, bot tokens, or other secrets in a data request or support request. The operator may ask you to confirm the Discord identity already associated with the data, but should not need your brokerage password to process a Signal Bridge data request.
Current limitation
Broader account-level deletion is not yet a one-click self-service feature. It is a verified operator process during the validation Beta. Signal Bridge should not claim a broader deletion request is complete until the relevant active stores — including private support storage when a support ticket exists — have actually been checked and the requested data has been removed or an applicable retention reason has been explained.