Account email and login/session data
SignalTrades uses account email, username when present, password hashes, and session cookies to let users sign in and keep access scoped to their own account.
A practical summary of the data SignalTrades appears to use today, written for review before a broader launch.
SignalTrades uses account email, username when present, password hashes, and session cookies to let users sign in and keep access scoped to their own account.
The app uses a theme cookie and browser localStorage for dashboard preferences such as theme mode, default range, landing tab, compact rows, and price freshness visibility. These settings are stored in your browser.
Per-user watchlists, followed sources, and comments are stored so each logged-in user can maintain personal research views. Browser-only preferences are not stored in the database.
SignalTrades stores public-source call data such as source, asset, direction, thesis or quote, publication time, stored prices when available, calculated tracked outcomes when possible, and links back to original sources.
When a user chooses to request an AI Research Brief, the app sends relevant call information to the configured AI research provider to produce that brief. Briefs are research aids, not recommendations or investment advice.
The app can use third-party services to render market charts and process requested AI research. The current code includes a TradingView chart embed and an Anthropic client for AI research briefs.
Stored data remains in the app database until changed or removed by app operations. Security controls such as hashed passwords, HTTP-only session cookies, and scoped account queries reduce risk, but no system can be described as absolutely secure.
For privacy questions, use the Support page and choose the topic that best matches your request.