Creekbot Privacy Policy
Written by creekie
privacypolicy creekbot

Last Updated: July 6, 2026

This Privacy Policy explains how Creekbot ("we", "us", or "the Bot") collects, uses, and stores user data within the Discord platform. By using Creekbot or participating in the r/Steam Discord server, you consent to the data practices described in this policy.


1. What Data We Collect

Creekbot is designed to collect only the minimum amount of data necessary to perform its moderation and role-management functions. The data we collect includes:

  • Discord User IDs: We collect and store your unique Discord User ID to link your profile to server statistics, role applications, and moderation actions.
  • Message Activity Statistics: We record aggregate engagement data, which includes the timestamp of your first and last message, the total number of messages you have sent, and your total days active in the server. Note: We take a historical sample of these user message statistics at the exact time you apply for the "Regular" role.
  • Role Application & Review Data: When you submit an application for the "Regular" role, we store the textual reason you provide, the application timestamp, and the corresponding message ID. We also log internal review data associated with your application, including individual staff votes and the final decision status.
  • Application Restriction Data: If you are restricted from applying for server roles, we store your Discord User ID and the timestamp of the restriction to enforce this block.
  • Honeypot Message Content: If a user posts in the designated administrative "honeypot" channel, the Bot will capture and log the specific message content and any attached files. Note: Message content outside of this specific hidden channel is never logged or stored.

2. How We Use Your Data

The data collected is used strictly for internal server management and automated moderation:

  • Role Management: We use your User ID and activity statistics to determine eligibility for the "Regular" role and to automatically prune the role from inactive members.
  • Application Processing & Restrictions: Your submitted application data and internal staff votes are stored so our moderator team can fairly review, approve, or decline your request. We use restriction logs to automatically block blacklisted users from submitting new applications.
  • Automated Moderation: Your User ID is stored in our ban database to track and automatically lift 12-hour temporary bans triggered by the honeypot system. Captured honeypot message content is relayed to a secure logging channel solely for staff review.

3. Data Storage and Security

All collected data is stored securely in an external database. Crucially, message content is never stored inside any database. Any message content captured by the honeypot system is only temporarily held in memory to relay it to a secure Discord logging channel, after which it is discarded. We implement reasonable security measures to protect the database from unauthorized access. The data is strictly used for the functional operations of Creekbot and is only accessible by authorized server administrators.


4. Data Sharing

We do not sell, rent, or share your personal data with any third parties. Your data remains strictly within the infrastructure supporting Creekbot and the moderation team of the server.


5. Data Retention, Access, and Deletion

  • Activity Statistics: Engagement statistics remain in the database to maintain accurate server history and role eligibility.
  • Moderation & Restriction Logs: Honeypot ban records and application blacklists are kept in the database to distinguish between active and expired actions and to maintain server security.
  • Right to Access: You can request a copy of the data held about you at any time by using the /requestdata command in the r/Steam Discord server. Alternatively, reaching out via our privacy email will yield the same result.
  • Right to Deletion: If you wish to have your data removed from our database (including application history and message statistics), please contact [email protected] with your Discord User ID.

6. Contact

If you have any questions or concerns about this Privacy Policy or Creekbot's data handling practices, please contact [email protected]

This blog post does not have a PGP signature attached to it.
This blog post's original markdown can be downloaded here.

Comments

No comments... be the first?