What is Flake?
Flake operates entirely within the servers it is added to. It does not require you to authorize it against your personal Discord account (no OAuth login), and it does not redirect users to any external websites during normal operation. Flake's sole purpose is server protection: detecting and stopping raids, nukes, and alt/botted account activity.
Terms of Service
By adding Flake to your Discord server or otherwise using it, you agree to the following:
1. Purpose of the Bot
Flake is designed exclusively for server security purposes, including but not limited to raid detection, anti-nuke protection, and identification of alt or botted accounts. Server administrators are responsible for configuring Flake's protections appropriately for their community.
2. Closed Source Software
Flake's source code is proprietary and closed source. It is not available for self-hosting, modification, or redistribution. Flake is operated centrally and made available to servers by invite only.
3. Service Availability
Flake is provided on an "as is" and "as available" basis. While every effort is made to keep protections online and effective, no guarantee is made against downtime, false positives/negatives in detection, or evolving attack methods that may temporarily bypass protections.
4. No Account Authorization Required
Flake does not use Discord OAuth to access or act on behalf of individual user accounts. All of Flake's functionality operates through standard bot permissions granted at the server level by an administrator.
5. Prohibited Activities & Abuse
You are strictly prohibited from attempting to circumvent, exploit, reverse-engineer, or interfere with Flake's protective systems, including but not limited to:
- Evasion: Attempting to bypass raid, nuke, or alt-detection systems.
- Abuse of Permissions: Using Flake's granted permissions to harm the very server it is meant to protect.
- Reverse Engineering: Attempting to extract, decompile, or replicate Flake's closed-source detection logic.
- Platform Violation: Any use of Flake that breaches Discord's Developer Terms of Service or Community Guidelines.
6. Liability
The developers of Flake are not liable for damages resulting from server compromise, misconfiguration, or attacks that occur despite Flake's protections being active.
Privacy Policy
An explanation of what data Flake processes and how it's used to keep servers safe.
Server & User IDs
Stored to enforce security rules and recognize repeat offenders across protected servers.
Account Metadata
Account creation date, join patterns, and activity signals used to flag alts and botted accounts.
Security Event Logs
Raid, nuke, and moderation-action events logged for audit and detection-tuning purposes.
Server Configuration
Your chosen protection settings and thresholds, stored so Flake behaves as configured.
1. What We Don't Collect
Flake does not read or store message content, private messages, or personal account information beyond what is needed for security detection (such as account age and join behavior). Flake does not require or use OAuth, so it never gains access to your personal Discord account.
2. No External Redirects
Flake does not use external links or redirect users away from Discord during normal operation. All interactions stay within the Discord client.
3. Data Retention
Security-relevant data (such as flagged accounts or logged raid events) is retained only as long as necessary to provide effective protection, or until a server administrator removes Flake and requests deletion.
4. Data Sharing
Data collected by Flake is not sold or shared with third-party advertisers. Cross-server detection data (e.g. known raid/alt account signatures) may be used internally to improve protection across all servers using Flake, without exposing your server's private configuration to others.
5. Your Rights
Server administrators may request removal of their server's stored data by removing Flake from their server and contacting the developers.