1. Scope
This policy applies only to the PrismaBot software when it is installed and operated on infrastructure selected by the person or organization running that installation.
2. Self-hosted model
PrismaBot is designed to run entirely on the instance operator's own server or other chosen infrastructure. The PrismaBot project does not operate a central bot backend for self-hosted installations.
A standard installation does not send workspace information to the PrismaBot project. In particular, the project does not receive or have access to Discord messages, Twitch chat, platform identifiers, moderation records, workspace settings, credentials, API keys, overlay content, operational logs, or stored database records from an independently operated instance.
The standard software does not use PrismaBot-operated telemetry, analytics, advertising, licensing, crash-reporting, synchronization, or cloud-storage services. If an instance operator modifies the software or connects additional services, those changes may introduce separate data processing that is not covered by this policy.
3. Who is responsible
The instance operator is the person or organization that installs PrismaBot, supplies platform credentials, selects features and permissions, configures retention, and controls the server and database. The instance operator determines why and how information is processed and is normally responsible for that processing under applicable data-protection law.
The PrismaBot project is not the controller or processor for information that remains inside an independent installation because the project does not receive, host, or access that information.
Discord, Twitch, YouTube, news providers, and any other services connected by the instance operator process information under their own terms and privacy notices. Their role is separate from both the PrismaBot project and the instance operator.
4. Information an instance may handle locally
The exact information depends on which features the instance operator enables. A PrismaBot installation may process:
- Discord server, channel, role, message, interaction, member, and user identifiers, together with usernames, display names, avatars, permissions, reactions, and relevant message content.
- Twitch channel, user, chat, stream, follower, subscriber, reward, moderation, and EventSub information required for configured Twitch features.
- Commands, responses, reaction-role mappings, polls, giveaways, schedules, notification rules, moderation rules, blocked terms, and related execution records.
- YouTube channel and upload metadata, gaming-news and feed records, and other public provider data requested by configured notification features.
- Overlay Studio and Live Canvas documents, uploaded media, alert configuration, browser-source state, and workspace-specific visual assets.
- Bot tokens, OAuth access and refresh tokens, API keys, webhook addresses, encryption material, and other credentials supplied by the instance operator.
- Local operational information such as logs, job state, deduplication records, errors, security events, and configuration history.
PrismaBot is built around isolated workspaces so that the settings and operating records for separate Discord servers and Twitch channels remain separated inside the installation.
5. Why an instance processes information
Local information is used only to provide features selected by the instance operator, including authentication, commands, notifications, reaction roles, moderation, polls, giveaways, schedules, gaming news, Twitch events, overlays, workspace access control, security, troubleshooting, and reliable job execution.
The PrismaBot project does not sell instance data, use it for advertising, build advertising profiles, or train machine-learning models with it. An instance operator must establish its own lawful basis and provide any notices or consent required for the features it enables.
6. Storage and retention
Instance information is stored on infrastructure and in backups controlled by the instance operator. The operator chooses the server location, database location, backup system, log settings, access permissions, and retention periods.
The operator should retain information only while it is needed for an enabled feature, security, legal compliance, or a clearly stated community purpose. Disabling a feature may stop new collection without automatically removing existing database records or backups. The operator is responsible for completing any required deletion.
7. External connections and sharing
A self-hosted instance communicates directly with services configured by the operator. This may include Discord, Twitch, YouTube, content feeds, game-information providers, media providers, or custom APIs. Information is sent only as needed to perform the configured request or action.
The PrismaBot project does not receive that traffic. The instance operator is responsible for selecting external providers, reviewing their terms, limiting requested permissions, and disclosing any resulting transfers or recipients to affected users.
8. Automated moderation and actions
PrismaBot may apply rules configured by an instance operator, such as detecting blocked terms, limiting links, assigning roles, posting notifications, or taking moderation actions. These decisions are made by the operator's configuration within that instance, not by the PrismaBot project.
Operators should use proportionate rules, maintain human oversight, provide a way to challenge mistakes, and avoid using PrismaBot for decisions that produce legal or similarly significant effects on individuals.
9. Access, correction, and deletion
Requests concerning information handled by a particular installation must be sent to the instance operator. For a community installation, this will usually be the relevant Discord server administrator, Twitch channel owner, or organization operating the bot.
The PrismaBot project cannot search, export, correct, or delete records held by an independent instance because it has no access to that server or database.
Removing PrismaBot from Discord or revoking Twitch credentials stops or restricts future platform access, but it may not erase local database records or backups. The instance operator must perform any required local deletion and follow the connected platform's deletion requirements.
10. Security responsibilities
The instance operator is responsible for securing the host, restricting administrative access, protecting credentials and encryption keys, applying updates, configuring network access, maintaining safe backups, monitoring incidents, and notifying affected users or authorities when required.
No software or storage system can guarantee absolute security. Operators should grant PrismaBot and its platform applications only the permissions required for enabled features.
11. Children and age requirements
PrismaBot is not intended to bypass the minimum-age requirements of Discord, Twitch, or any connected provider. Instance operators must follow the age, consent, and child-safety rules applicable to their community and jurisdiction.
12. Changes to this policy
This policy may change when PrismaBot's architecture or features change. If a future version introduces project-operated hosting, telemetry, accounts, or other central services, the policy must be updated before those services begin processing information.
The effective date at the top of this page identifies the current version. Instance operators should review updates before installing a new release.