aiFuzzBot Privacy Policy
Implementation information reviewed: 25 October 2026.
This page explains how information is used by the current aiFuzzBot service and the controls available to channel owners and their teams.
1. Information used by the service
Connected account identifiers, channel and server details, role information and OAuth credentials support sign-in and platform integrations. The service can store chat messages with viewer identifiers and timestamps, viewer activity, conversation memory and viewer profile context. This information is not necessarily anonymous.
Dashboard settings, device records, service logs and payment-related account or subscription references support the features you use. Optional visitor badge interactions use configured visitor information and short-lived sessions tied to a device.
2. Why information is used
Information is used to deliver chat commands, moderation, rewards, overlays, viewer statistics, chat replay and AI responses; to manage connected accounts and access; and to diagnose service problems. The information used depends on which features and integrations are enabled.
3. AI and connected providers
When AI features are enabled, messages, prompts and selected conversation or viewer context can be sent to the configured AI provider to generate responses. Speech features can send text to the configured speech provider. Twitch, Discord and optional StreamElements connections exchange information needed for the requested integration.
Provider processing and retention are governed by the provider and your configuration. Do not put sensitive personal information into public chat or prompts. This page does not promise that all stored chat is anonymised or that third-party providers never retain it.
4. Memory, chat history and deletion
The dashboard provides AI memory switches, configurable memory retention, and controls to clear conversation memory and viewer profiles. These controls concern AI context; they do not erase separate chat logs, payment records, operational logs or third-party records.
Chat replay depends on recorded sessions available for the channel. There is no universal 15-day or 30-day chat deletion promise on this page. Retention varies by data type and service configuration. Contact us for information about stored records or to request access, correction or deletion.
5. Security and access controls
Dashboard management flows use authenticated sessions, streamspace checks and team permissions. Session cookies are HTTP-only with SameSite protection, and production configuration uses secure cookies for HTTPS.
StreamElements connection credentials are encrypted at rest and scoped to the selected streamspace; saved credentials are not rendered back to the browser. This specific protection is not a claim that every stored record is encrypted.
Overlay imports enforce archive and path checks. External widget scripts are not executed by the importer, and supported conversions start as disabled private drafts for review. Hardware endpoints use device authentication; optional visitor sessions expire and are bound to the identifying device.
6. Payments and session cookies
Payment details are entered through Stripe Checkout. aiFuzzBot uses payment and subscription references to manage access. Dashboard sessions and package review flows use cookies to keep sign-in and order state. The package review step validates details and checks a request token before checkout.
7. Your choices and questions
Channel owners and authorised team members can manage enabled AI features, memory and connected services in the dashboard. Disconnecting an integration does not itself erase historical records or revoke data already held by another provider.
For privacy questions or requests concerning your information, email privacy@aifuzzbot.co.uk. Include the relevant channel or account so the request can be verified. Requests may require identity checks and review of records that must be retained.
See the Terms of Service for service terms and the security and privacy feature guide for a summary of controls.