SP TRADE

Privacy Policy

A code-based description of information stored in the browser, processed on the server, or handled by external services. Controller details and retention periods still need to be completed.

Document status: transparency draft · Updated August 5, 2026 · No binding effective date has been set

What is verified and what remains open

The technical description is based on SP TRADE's active code. The operating entity, official address, registration details, privacy contact, governing law, and retention policy have not been provided, so they are not presented as facts.

1. Information in your browser

  • Interface preferences: Reduced motion and larger text preferences are stored in localStorage.
  • Device choices: Cookie consent and dismissed prompts may be remembered in localStorage.

Clearing browser data may reset these device-specific choices.

2. Information processed by the SP TRADE server

  • Account: When authentication is enabled, the system processes an email address, profile details, permission roles, authentication, and sessions.
  • Trading journal: Trades, prices, fees, dates, setups, notes, behavior fields, and goals are stored in PostgreSQL under the authenticated account so they can sync across signed-in devices.
  • Bot Builder: Conversation messages, generated Pine Script, the selected model, token-usage metadata, and timestamps are stored in PostgreSQL under the authenticated account so sessions can be resumed.
  • Analysis and portfolio: A symbol, asset selection, and questionnaire answers are sent to server routes to create a result. Portfolios saved by the user are stored under the authenticated account.
  • Blog: Articles, drafts, and publishing runs are stored in PostgreSQL.
  • Rate limiting: The authenticated account ID is used as a temporary in-memory key for Bot Builder request limits.

3. External services

Market queries, model-backed features, optional Google sign-in, and account email delivery may use external services when those features are configured.

Saved Bot Builder sessions are available to their account through the product. Operators with direct database access can technically access stored conversation records for system operation and support. The active hosting location and final service inventory require verification in production.

4. Cookies and sessions

Authentication uses technical cookies to maintain a session. The code configures a session for up to seven days and refreshes it every twelve hours. Cookie names, their actual production duration, and possible cookies from sign-in services have not yet been verified for a final policy.

5. Purposes, security, and deletion

Information is used to operate accounts and tools, generate results, provide security, limit usage, and run the blog. Admin permissions and authentication controls exist, but no system is completely secure. A complete account-deletion process, backup and log retention, and legal exceptions have not yet been documented for a final policy.