Policy statement · Updated June 2026

Privacy Policy

This policy explains what CFBCBot stores and processes to operate Discord subscriptions, moderation safeguards, support, and service reliability.

Customer servers

Customer premium servers use slash commands, selected delivery channels, setup state, subscription status, and delivery logs so CFBCBot can post the sports features the customer configured. Customer commands do not use home-server moderation scanning, betting-spam analysis, image/OCR safety review, or community engagement processing.

CFBCBot stores Discord user IDs, usernames, guild IDs, guild names, selected setup state, configured channel IDs, command and delivery logs, and support records needed to operate the service.

Discord OAuth tokens used during customer setup are stored encrypted and are used to verify that the customer can manage the selected server.

Stripe processes payment details. CFBCBot stores Stripe customer, subscription, checkout, and billing event identifiers, but does not store raw card numbers.

Operational logs may include delivery failures, permission failures, entitlement changes, admin actions, rate-limit behavior, and support actions. Access to sensitive logs and review surfaces is limited to authorized operators and admins who need it to run, debug, secure, or support the service.

Contact support for account, setup, billing, or data questions.

Home community

In the CFBCBot home community server and other configured safety surfaces, CFBCBot may process message content, embeds, attachments, forwarded message snapshots, URLs, images, Discord invite links, and related metadata to enforce server rules, detect betting spam, block unsafe links, and protect users from abuse. Trivia sessions use slash commands and answer buttons rather than message-content matching.

For the CFBCBot home community server, CFBCBot may request the full member list to calculate aggregate member composition and server-tag adoption analytics, including how many members display the configured server tag or other visible server tags. These analytics are used for community operations and aggregate reporting, not customer-server scanning or cross-server member profiling.

When a message is flagged for safety review, CFBCBot may store short message excerpts, analyzed content, image or OCR signals, user IDs, guild and channel IDs, timestamps, violation reasons, actions taken, and admin review notes. Moderation violation records are configured for a default retention period of 7 days; false-positive notes, admin review records, support records, and security logs may be retained longer when needed to correct mistakes, investigate abuse, or comply with operational and legal obligations.

Some suspected spam, abuse, or safety-related content may be sent to service providers such as OpenAI for moderation, image, OCR, embedding, or classification analysis. Those processors are used to classify risk and protect Discord users, not to sell data or build advertising profiles.

CFBCBot may briefly keep recent activity signals from configured community channels so it can avoid repetitive promotional messages, choose relevant command guidance, and reduce bot spam. This engagement analysis is limited to service operation, does not sell personal data, and is not used for cross-server member profiling.