What this policy covers
This Privacy Policy explains how BrewBot collects, uses, stores, and shares information when you use brewbot.dev, the BrewBot dashboard, the Discord bot, public pages, overlays, support tools, and related services.
The information we process depends on which features you use. Many BrewBot features are optional, and some public-facing features intentionally publish information you choose to make visible.
Information we collect
We collect information you provide directly, information available through connected platforms, and technical data generated when the service is used.
- Account and team data, such as your Clerk user ID, name, email address, avatar, organization memberships, and related authentication/session data.
- Discord server data, such as server IDs, names, icons, channel IDs, role IDs, feature settings, and configuration for moderation, welcome messages, reaction roles, custom commands, birthdays, reports, and similar tools.
- Content and activity data used by enabled features, such as AI conversation memory, AI usage records, moderation and audit-log message snapshots, ticket submissions, ticket messages, transcript events, and ticket attachments.
- Community profile data entered into server tools, such as speed-dating profile fields, birthdays, public support portal submissions, and creator account usernames for alerts or live monitoring.
- Integration data, such as Twitch authorization tokens, custom bot credentials, and other connected-service metadata needed to run the integrations you enable.
- Billing and subscription data, such as Stripe customer and subscription identifiers, plan information, billing status, and limited payment-related metadata.
- Technical and security data, such as request logs, user agent strings, cookies, OAuth state values, and limited network metadata used for fraud prevention, debugging, and service protection.
How we use information
- To authenticate users and manage team or server access.
- To operate BrewBot features, including Discord automations, creator alerts, AI tools, live monitoring, overlays, support portals, and billing features.
- To store server settings and remember user preferences.
- To process support requests, investigate issues, and respond to abuse or security incidents.
- To monitor reliability, prevent fraud or misuse, enforce limits, and improve the service.
- To send requested outputs to connected services such as Discord, Twitch, TikTok, YouTube, or voice providers.
AI, voice, and connected-service processing
If you enable AI features, BrewBot may send prompts, message content, conversation history, and related metadata to AI providers used by the service, including HiCap AI and xAI Grok, in order to generate responses or other outputs.
If you enable voice features, BrewBot may send text and related settings to ElevenLabs to generate speech or voice responses.
If you connect Twitch, TikTok, YouTube, Discord, or other platforms, BrewBot may exchange data with those services to authenticate accounts, fetch creator or live-status information, deliver alerts, or perform actions you request.
Sensitive connected-service credentials such as custom bot tokens and certain OAuth tokens are stored in encrypted form when BrewBot needs to retain them for the feature to work.
How we share information
We do not sell your personal information. We share information only as needed to run BrewBot, comply with law, protect the service, or complete transactions you request.
- Service providers and infrastructure partners such as Clerk, Stripe, AWS, hosting vendors, database providers, and customer support or analytics tools we use to operate BrewBot.
- AI and voice providers when you use features that require them, including HiCap AI, xAI Grok, and ElevenLabs.
- Connected platforms such as Discord, Twitch, TikTok, and YouTube when the integration requires information exchange.
- Authorities, regulators, or other parties when required by law or when reasonably necessary to enforce our terms, protect users, or respond to security issues.
- A successor entity if BrewBot is involved in a merger, acquisition, financing, or asset sale.
Public features and user-visible content
Some BrewBot features are intended to be public or semi-public. That can include portfolio listings, Brewlinks pages, overlay pages, public ticket submission forms, and public ticket status links.
Only submit information to those features that you are comfortable making available to the intended audience. Anyone with the relevant page or link may be able to view information you choose to publish there.
Data retention
We retain information for as long as needed to provide BrewBot, maintain security, comply with legal obligations, resolve disputes, and enforce agreements. Retention can vary by feature.
Some records may be removed automatically through maintenance jobs, feature-specific cleanup routines, or user-initiated deletion. Residual copies may remain in backups, logs, or disaster-recovery systems for a limited period.
Security
We use reasonable administrative, technical, and organizational safeguards designed to protect information processed by BrewBot. That includes access controls and encrypted storage for certain sensitive credentials used by integrations.
No service is completely secure, and we cannot guarantee absolute security.
Your choices
- You can manage many server settings directly in the BrewBot dashboard.
- You can disable optional features such as AI memory, alerts, birthdays, public portals, or other stored feature modules when they are not needed.
- You can disconnect integrations and remove configured credentials from the dashboard where supported.
- You can cancel paid subscriptions through the available billing workflow.
- If you need help accessing or deleting information that is not self-service, contact BrewBot through the support links or community contact methods listed on brewbot.dev.
Children's privacy
BrewBot is not directed to children under 13, and the service is intended for users who meet Discord's minimum age requirements and any higher local age requirement that applies to them.
Changes to this policy and contact
We may update this Privacy Policy from time to time. When we do, we will post the revised policy here and update the effective date.
If you have questions about this policy, contact BrewBot through the support links or community contact methods listed on brewbot.dev.