Information processed
Account data includes your email, display name, password hash, verification status and preferences. Workspace records include simulated orders, positions, balances, journal notes, risk limits, watchlists, alerts, agent analyses, chat messages and community activity. Security records may include sessions, request metadata and rate-limit information. Do not submit private keys, exchange secrets or sensitive personal information in posts or chat.
Why data is used
Data supports authentication, your saved workspace, paper-order execution, risk enforcement, research, notifications, moderation, troubleshooting and service security. Optional communications depend on your saved preference and the operator’s email configuration. Personal data must not be repurposed incompatibly without the notices and legal basis required for that deployment.
Cookies and browser storage
An essential HttpOnly session cookie keeps you signed in. A CSRF token protects authenticated changes. The connected application stores account and trading records on its backend rather than treating browser demo storage as an account. Old demo records may remain in your browser until you clear site data. This package does not install advertising or analytics trackers.
External providers and AI processing
The server requests market data from Binance, fundamental data from CoinGecko, and news from configured publishers. If a language-model service is configured, relevant account/portfolio context, agent research and your chat prompt may be sent to that provider to generate a response. Passwords and session tokens are not intended to be included in those prompts. Fonts may load from Google Fonts. Hosting, database and email providers process data according to the deployed configuration.
Community visibility
Posts, display names, likes and comments can be visible to other signed-in members. Reports are accessible to authorized moderators. Consider what you share; other people may retain copies of content they have seen.
Retention and deletion
The beta retains records while your account exists unless a specific cleanup or deletion applies. Paper-account reset retains historical trading records. Account deletion removes the account and its dependent beta records from the active application database. Hosting logs and backups may persist under the operator’s retention schedule; that schedule must be published for a public deployment.
Your controls and requests
You can edit your profile and preferences in Settings, edit journal notes, remove your own community content, export your journal, sign out or delete your account. Applicable law may provide additional access, correction, erasure, complaint and consent-withdrawal rights. Requests that are not supported in the interface should go to the operator’s published privacy contact.
Security and international processing
The application uses password hashing, authenticated sessions and access controls. Public deployments must use HTTPS and secure session cookies. No system is completely secure. Provider and hosting choices may involve processing outside your country; the operator must disclose relevant locations and use required safeguards.
Children and policy changes
The beta is intended for adults aged 18 and over. Do not create an account if you are under 18. Changes to data processing should be reflected in this notice and communicated where required. The date above identifies this version.