Privacy Policy

Effective Date: October 1, 2026 • Version: 1.1 Enterprise

At Werrberus, we consider user privacy and confidentiality paramount. Unlike conventional commercial bots that log conversations, harvest user graphs, and monetize data through external databases, Werrberus was built from the ground up on a strict Zero Data Retention & Stateless Architecture.

1. The Zero-Retention Principle

        Guaranteed Stateless Operation: Werrberus never stores, sells, monetizes, or profiles personal user data. All threat evaluations occur strictly in volatile memory (RAM) utilizing local CPU mathematical equations. Once an event (join, message, or update) is evaluated, its raw data is discarded immediately from memory.
      

2. Data Processed in Volatile Memory (Transient RAM Only)

To protect Discord servers against botnet swarms, zero-day phishing, and malicious Web3 drainers, Werrberus inspects the following event data in volatile memory (RAM) exclusively during real-time event processing:

Discord Snowflake IDs: Evaluated using GAP-0331 Z/9Z ring algebra invariants (residue congruences in I₃ = {0, 3, 6}) and account creation epoch deltas (Δt < 48h) to detect coordinated Sybil botnet swarms.
Account Metadata: Account creation timestamp and avatar existence flags to determine account freshness and join burst anomalies.
Message & Attachment Content: Inspected transiently to detect dangerous URLs, typosquatting domains, crypto drainers, high-entropy Base64 token grabbers (H > 4.70 bits/char), and QR code login hijack traps.
Audit Log Records: Inspected strictly during rapid channel or role deletion spikes to identify compromised administrator accounts (Anti-Nuke protection).

3. Data Stored Persistently on Disk

The only information saved persistently on the host machine is non-personal server configuration settings stored in a local guild_settings.json file:

Guild ID: The numeric Discord snowflake identifying the server.
Configured Log Channel ID: The channel where security alerts and review cards are dispatched.
Security Thresholds: The active profile (balanced, strict, or relaxed) and user-adjusted numeric boundaries (e.g. join burst threshold, spam limits, feature toggles).
Quarantine Role / Channel IDs: Optional role and channel IDs designated for the containment jail module.

No usernames, avatar graphics, user messages, IP addresses, or conversation histories are ever recorded to persistent storage or uploaded to cloud databases.

4. Privileged Gateway Intents Transparency

In accordance with the Discord Developer Policy, Werrberus requires two Privileged Gateway Intents:

Server Members Intent (GuildMembers): Required strictly to receive real-time join events (on_member_join), assess account age, and prevent join-flood raids.
Message Content Intent (MessageContent): Required strictly to evaluate message structures for phishing links, crypto drainer patterns, and high-entropy token grabbers in real time.

Neither intent is ever used to log, harvest, or aggregate user conversations.

5. Third-Party Sharing and Analytics

Werrberus operates 100% self-contained without external API dependencies, tracking pixels, or third-party analytics services. We do not sell, share, or disclose user data to advertisers, brokers, or external AI platforms. All calculations occur locally on the bot's host CPU.

6. Data Subject Rights & Data Erasure (GDPR / CCPA)

Because Werrberus retains no personal user data, there are no personal records to query, rectify, or export under GDPR or CCPA. For server administrators wishing to erase their guild configuration record:

Execute the /werr reset slash command to restore all configuration values to defaults.
Evict or kick Werrberus from the server. Upon removal, all volatile tracking queues and active counters for that server are immediately purged from RAM.
Server owners may also contact the developers to request immediate manual deletion of their guild configuration entry.

7. Policy Updates & Contact

We may update this Privacy Policy periodically to reflect technological advancements or Discord policy changes. Revisions will be published on this page with an updated effective date. For any privacy inquiries, please contact our team via Discord.