Privacy Policy - Peacekeeper

## Peacekeeper Bot Privacy Policy

**Effective Date:** January 16, 2026
**Bot Name:** Peacekeeper (“Bot”)
**Provided By:** Code99 INC (“we,” “us,” “our”)
**Support Contact (Discord):** rcsgwayne (or use **`/help` → “Contact Developer”**)

This Privacy Policy explains what information the Bot processes, why it is processed, and the choices available to server operators and end users.

---

### 1) Scope

This Privacy Policy applies to information processed by the Bot when it is used in a Discord server (“Server”). It does not apply to Discord’s own processing of data. Discord’s policies apply to Discord’s services.

---

### 2) Information We Process

Depending on configuration and use, the Bot may process the following categories of information:

**A. Discord identifiers and configuration**

* User IDs, Server (guild) IDs, channel IDs, message IDs, role IDs
* Server configuration data (e.g., log channel IDs, ticket settings, onboarding settings, feature toggles)

**B. Operational content**

* Message content **only when needed** to provide a feature (for example: ticket transcripts, support messages within ticket channels, moderation triggers, command processing)

**C. Ticketing data (if tickets are enabled)**

* Ticket creator ID, ticket channel ID, ticket type, ticket number, timestamps (created/closed)
* Closure metadata (e.g., who closed the ticket, close reason if provided)
* Transcripts or logs generated from ticket channels (if enabled/configured)

**D. Enforcement and safety data (if enabled)**

* If enforcement is enabled, the Bot may process user identifiers in a privacy-preserving form (e.g., hashed/keyed identifiers) to evaluate whether automated safety actions should occur.

**E. Support contact data**

* If a user uses **`/help` → “Contact Developer”**, the Bot processes the submitted subject/message and the user’s ID in order to deliver the request to the Support Contact.

---

### 3) How We Use Information

We use information to:

* Provide and operate Bot features (onboarding, role menus, ticketing, logging, enforcement controls)
* Maintain service reliability (debugging, monitoring, rate limiting, abuse prevention)
* Respond to support requests and user/admin inquiries
* Enforce these policies and protect the Bot from misuse

---

### 4) When Information Is Stored

The Bot may store limited data necessary to function, including:

* Server configuration (to remember setup choices)
* Ticket metadata (to manage ticket state and numbering)
* Logs/transcripts **only if** the Server Operator enables or retains them
* Minimal operational logs for stability and abuse prevention

---

### 5) Data Retention

Retention depends on Server configuration and operational requirements:

* **Server configuration:** retained while the Bot remains installed in the Server, and deleted upon request or after removal where feasible.
* **Operational logs:** may be retained for a limited period for debugging and abuse prevention.
* **Tickets / transcripts:** retained according to Server Operator configuration and moderation practices (for example, posted into a ticket log channel that the Server manages).

If you want a strict retention period, publish it here (recommended):
**Retention Period:** [e.g., “Operational logs up to 30 days; ticket transcripts up to 90 days unless deleted sooner by Server staff.”]

---

### 6) How Information Is Shared

We do **not** sell personal information.

Information may be shared only as follows:

**A. Within the Server (as configured by Server Operators)**

* Posting logs to configured log channels
* Creating ticket channels visible only to authorized roles and the ticket creator
* Posting transcripts/log summaries to configured ticket log channels

**B. With the Support Contact**

* Messages submitted via **`/help` → “Contact Developer”** are forwarded to **rcsgwayne** to respond to the request.

**C. Service providers**

* The Bot may rely on infrastructure providers (hosting, databases, monitoring). They may process limited data strictly to provide their services to Code99 INC.

**D. Legal and safety**

* If required by law, legal process, or to protect users, our rights, or the public, we may disclose information as necessary.

---

### 7) User Choices and Controls

**Server Operators control** how the Bot is configured in their Server, including:

* Whether to enable ticketing and whether to retain transcripts/logs
* Which channels receive logs
* Whether enforcement features are enabled

**End users** can:

* Choose whether to submit information via ticket messages or via **Contact Developer**
* Ask Server staff about server-side retention (e.g., whether transcripts are logged)

---

### 8) Data Deletion and Requests

**Server Operators** may request deletion of their Server’s stored configuration and related data by contacting **rcsgwayne** on Discord or using **`/help` → “Contact Developer.”** We may require verification of admin rights.

**End users** should generally request deletion through the Server Operator first, because much of the data (e.g., logs/transcripts) may be stored in Server-owned channels under the Server’s control.

---

### 9) Security

We take reasonable measures to protect data processed by the Bot, including access controls and operational safeguards. However, no system is completely secure, and we cannot guarantee absolute security.

---

### 10) Children’s Privacy

The Bot is not directed to children under 13 (or the minimum age required by local law). If you believe a child has provided personal information through the Bot, contact **rcsgwayne** or use **`/help` → “Contact Developer.”**

---

### 11) Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Updates become effective when posted with a new Effective Date. Continued use of the Bot after changes means you accept the updated policy.

---

### 12) Contact

Questions or requests: contact **rcsgwayne** on Discord or use **`/help` → “Contact Developer.”**