Protect your account and research.
Use private account flows, separate public evidence and contact the published security channel.
Owner-bound private flows and security checks are implemented. These guides do not replace current terms/privacy policy or establish an independent security certification.
Entry points
/support/channelsUse personal/account commands in your private Bookie chat. Placeholders are not actual market, account or destination identities.
Keep account journeys private
Public groups can discuss market information, but they are not account-management screens. Balances, research records, drafts, linking and money actions belong in your private chat or authenticated app. Old or forwarded buttons still require the original owner/context.
Public thesis evidence is a sanitized projection. It excludes private owner, wallet, order and recommendation identifiers. Evidence labels do not certify the opinion's accuracy.
Do not send secrets to support
Never post a seed phrase, private key, session token or provider credential. The app copies only the wallet reference actually supplied by the server; it does not export keys. A support agent cannot safely bypass custody, identity or execution gates.
Report a problem with useful evidence
Use the published security disclosure contact on Trust for vulnerabilities. For ordinary help, use /support or the site's contact link. Include the action, approximate time and a non-secret receipt/reference; redact account tokens and private personal data from screenshots.
The current legal pages describe their stated scope. They do not by themselves prove a completed launch account/privacy acceptance review.