Privacy Policy
Last updated: March 2026 · Effective immediately
01 Overview
Bloo is a Fluxer bot that operates on servers ("guilds") and stores data to provide its features. This policy explains what data we collect, why we collect it, how it is stored, and the rights you have over it.
We collect only what is necessary to make Bloo work. We do not sell your data, run advertising, or share it with third parties for commercial purposes.
02 What We Collect
The following table outlines the categories of data Bloo may store for a given server:
| Data Type | What It Includes | Why |
|---|---|---|
| Server configuration | Prefix, enabled features, channel/role IDs, mod settings | Required to operate commands and features |
| User IDs | Fluxer user IDs of members who interact with Bloo | Required to associate records (XP, balance, warnings) with the correct user |
| Moderation records | Warnings, bans, kicks, mutes, and mod log entries | Moderation history and staff accountability |
| XP & level data | XP total, level, last activity timestamp per user per server | Leaderboard and level reward functionality |
| Economy data | Wallet balance, bank balance, inventory, transaction log, job history | Virtual economy functionality |
| Giveaway data | Prize, entry lists, winner IDs, host ID, configuration | Running and recording giveaways |
| Ticket data | Ticket open/close events, associated user IDs | Ticket system functionality |
| Reaction role config | Message IDs, emoji mappings, role IDs | Reaction roles functionality |
| Watchlist entries | User IDs flagged by staff, with optional notes | Moderation watchlist feature |
| Scheduled actions | Reminder contents, user ID, scheduled time | Personal reminder feature |
| Dashboard session data | Fluxer user ID, username, session token | Dashboard authentication |
| Message log metadata | Deleted/edited message content (if logging is enabled by the server owner) | Message audit logging — only if explicitly enabled |
We do not collect: message content unless message logging is explicitly enabled by the server owner, passwords or credentials, payment information, or persistent device identifiers.
03 How We Use Your Data
Data collected by Bloo is used exclusively to:
- Provide the features you or your server administrators have enabled
- Maintain moderation records for server staff
- Display leaderboards, economy balances, and other user-facing information
- Authenticate dashboard users and enforce permission levels
- Diagnose errors and improve reliability
We do not use your data for advertising, profiling, or any purpose beyond operating Bloo's features.
04 Data Storage & Security
All data is stored in an SQLite database on a private server located in the EU. The server is not publicly accessible. Data is stored in WAL mode with regular backups.
Dashboard sessions are stored server-side using signed, encrypted session cookies. OAuth2 tokens are stored only for the duration of the session and are not logged permanently.
While we take reasonable precautions to protect your data, no system is completely immune to security breaches. In the event of a breach affecting user data we will notify affected server owners via the support server as soon as reasonably possible.
05 Data Retention
Data is retained for as long as Bloo is present in a server and the features that generated it are active. Specifically:
- While Bloo is in your server: All configuration, XP, economy, and moderation data is retained.
- After Bloo is removed: Data is not automatically deleted. Server owners may request deletion at any time via the support server.
- Moderation records: Retained indefinitely by default, as they may be relevant to future moderation decisions. Server owners can purge specific records.
- Dashboard sessions: Automatically expire after 30 days of inactivity.
- Ended giveaways: Retained in history for up to 90 days, then eligible for cleanup.
06 Data Sharing
We do not sell, rent, or share your data with third parties. The only exceptions are:
- Fluxer API: Bloo communicates with Fluxer's API to send messages, manage roles, and read server information. This is subject to Fluxer's Privacy Policy.
- Legal obligations: If required by law or a valid legal process, we may be required to disclose certain information. We will make reasonable efforts to notify you if this occurs, where legally permitted.
No analytics services, advertising networks, or data brokers receive any data from Bloo.
07 Dashboard & OAuth2
The Bloo dashboard at bloo-bot.xyz/dashboard uses Fluxer's OAuth2 system to authenticate users. When you log in, Bloo receives:
- Your Fluxer user ID
- Your Fluxer username
- The list of servers you share with Bloo
This information is used only to verify your identity and determine which servers and permission levels you have access to. Your OAuth2 access token is stored in your session and is not logged permanently.
You can revoke dashboard access at any time by removing the authorisation in your Fluxer account settings. This will invalidate your current session immediately.
08 Cookies & Sessions
The Bloo dashboard uses a single session cookie to maintain your login state. This cookie is:
- HTTPOnly and Secure — not accessible to JavaScript and only sent over HTTPS
- Scoped to
bloo-bot.xyz - Automatically expired after 30 days of inactivity
We do not use tracking cookies, advertising cookies, or any third-party cookies. The session cookie is the only cookie set by bloo-bot.xyz.
09 Your Rights
Depending on your location, you may have certain rights regarding your personal data. Regardless of jurisdiction, we offer the following to all users:
- Access: Server owners can view data stored for their server via the dashboard.
- Correction: Staff can correct or remove individual moderation records via the dashboard.
- Deletion: Server owners can request full deletion of their server's data at any time via the support server. Individual users who wish to have their personal records deleted should contact us through the support server.
- Portability: If you need an export of your server's data, contact us and we will do our best to provide it in a reasonable format.
10 Children's Privacy
Bloo is not directed at children and does not knowingly collect data from individuals below the minimum age required by Fluxer's Terms of Service. If you believe a minor has submitted data through Bloo, please contact us and we will take appropriate steps to remove it.
11 Changes to This Policy
We may update this Privacy Policy from time to time. The "last updated" date at the top of this page will reflect any changes. Continued use of Bloo after an update constitutes acceptance of the revised policy.
Material changes — particularly those that affect how your data is used or shared — will be announced in the support server.
12 Contact
For any privacy-related questions, data access or deletion requests, or concerns about how your data is handled, please reach out through the support server. We take privacy seriously and will respond as promptly as possible.
Privacy questions or data requests?
Join the support server and we'll handle any data access, correction, or deletion request directly. We aim to respond within 14 days.
💬 Join Support Server