Privacy Policy

1. Information We Collect

When you interact with marketbot via Discord commands or slash interactions, the application processes only the operational metadata necessary to deliver requested market outputs:

• Discord Identifiers: Discord User ID, Guild (Server) ID, and Channel ID to route command responses and enforce rate limits.
• Command Input: User-supplied ticker symbols, intervals, or query prompts (e.g., /quote semis or .chart AAPL 1d).
• Watchlist Configurations: User-created basket lists (symbols, names, weights) explicitly stored to provide persistent portfolio comparisons.
• Operational Usage Metrics: Aggregated token accounting, daily turn counters, and admission timestamps used to prevent quota exhaustion and ensure fair system availability.

2. No Brokerage Credentials or Trade Account Storage

marketbot never requests, connects to, or stores brokerage accounts, exchange login credentials, API keys for financial institutions, credit card numbers, or bank routing details. We do not maintain or claim custody over any financial asset, and no brokerage accounts or trading authorizations are held on our systems.

3. How Information Is Used

Information processed by marketbot is used exclusively to:

• Fulfill requested market data queries, chart renderings, and research briefs.
• Maintain user and guild watchlist state.
• Enforce tier-based concurrency limits, burst control, and daily usage quotas.
• Diagnose operational errors and maintain system reliability.

4. Third-Party Upstream Processing

To produce research and charts, marketbot connects to upstream service providers:

• Discord API: Delivers messages, attachments, embeds, and slash interactions in accordance with Discord's Developer Terms.
• Market Data Providers: Ticker symbols are queried against market data sources (such as Yahoo Finance) to retrieve price history and fundamentals.
• Inference Providers: Conversational questions are processed through AI inference providers (such as OpenRouter) to produce cited synthesis. Prompts sent to inference providers are bounded to the specific user query.

5. Data Retention & Deletion

Watchlist definitions remain available until the owner deletes them through the supported delete_my_watchlist action. Operational usage metrics and log traces are retained only as needed for quota enforcement, error diagnosis, and system reliability, then cycled according to operational retention schedules.

6. Security and Tenant Isolation

Data stores are logically partitioned by Discord Guild and User identifiers. We apply defense-in-depth isolation to ensure one guild cannot access or view another guild's watchlists, settings, or private conversation context.

7. Project Information

This policy describes the data practices implemented by marketbot.