Monstra may collect account profile details, authentication identifiers, subscription records, product usage data, request logs, support messages, and bot interaction history needed to operate the service.

When you purchase a Premium subscription or consumable currency through Apple In-App Purchase or Stripe, Monstra may receive subscription status, entitlement information, purchase records, and billing metadata necessary to provide the features you purchased. This data is processed through RevenueCat.

If you connect Alpaca paper trading, Monstra may collect and process paper account metadata, holdings, balances, order status, rebalance previews, and audit events required to support user-initiated sync and operational safety checks.

Monstra may use collected data to authenticate users, deliver product functionality, improve system reliability, investigate abuse, support billing, maintain audit trails, and surface educational bot outputs and simulation experiences.

Brokerage sync data is used to display paper-only account views, build previews, and execute user-initiated paper sync workflows. It is not used to provide personalized financial advice.

Some data displayed in Monstra may come from third-party providers or integrations and may be delayed, stale, incomplete, or temporarily unavailable. Monstra cannot guarantee uninterrupted availability or perfect data accuracy across every provider dependency.

Payment, authentication, hosting, analytics, and brokerage connectivity may involve third-party service providers including Stripe (web billing), Apple In-App Purchase (iOS billing), RevenueCat (subscription management), Clerk (authentication), and Alpaca (paper brokerage connectivity). Each operates under its own terms and privacy practices.

Monstra retains operational records, audit logs, and safety telemetry for as long as reasonably necessary to support security monitoring, billing and fraud prevention, legal and regulatory obligations, operational support, and dispute resolution. Specific retention periods vary by data category and applicable law.

Because Monstra is educational and simulation-oriented, users should independently evaluate information before acting on it elsewhere. Bot outputs are algorithmic and not personalized recommendations.