Privacy Policy

This policy applies to the 302 Mod Discord Application and the moderation, safety, welcome, logging, and server-administration features it provides in the 302 Community. The Application is operated by 302 Development in Canada and is not affiliated with or endorsed by Discord, Inc.

302 Mod is configured for the 302 Community Discord server. It may send welcome or moderation-related direct messages, but it does not use incoming direct-message content for server moderation or profiling.

Depending on the event or feature, 302 Mod may process:

• Account and membership information: Discord user ID, username, display name, avatar, account creation time, server join/leave events, nickname, and server roles.
• Server information: server, channel, role, message, invite, and interaction IDs and related Discord metadata.
• Message information: content, attachments, mentions, links, author, channel, timestamps, and edit or deletion events.
• Voice information: voice-channel joins, leaves and moves, plus server mute/deafen and self-mute/deafen changes used for staff logs.
• Invite information: invite codes and available creator, channel, usage, or expiration details used for invite logs.
• Moderation information: warned or banned user IDs, moderator IDs, case IDs, reasons, proof attachment names/URLs, warning counts, action timestamps, deleted-warning details, chat-ban roles, and expiration times.
• Operational information: errors and service events needed to troubleshoot and maintain the Application.

Message Content Intent. 302 Mod uses message content to:

• detect configured banned words, prohibited links, mass mentions, restricted GIFs, Zalgo or styled text, and other server-rule violations;
• run staff prefix commands such as warning, ban, and warning-history commands;
• record edited or deleted message content and relevant attachments in staff-only Discord log channels;
• create moderation evidence for messages that trigger automated warnings or punishments.

Server Members Intent. 302 Mod uses member information to:

• send welcome messages and record member join and leave events;
• record nickname and role changes;
• maintain an accurate member cache and evaluate staff, exemption, and restricted-feature roles;
• apply moderation actions, including warning escalation, temporary chat-ban roles, timeouts, and bans.

Information is used only as reasonably necessary to:

• enforce published community rules and detect configured violations;
• delete violating content and notify affected members;
• create, review, update, and display moderation cases to authorized staff;
• apply progressive warning consequences and restore expired chat restrictions;
• record message, member, voice, nickname, role, and invite events in configured Discord staff channels;
• send server welcome messages and relevant moderation direct messages;
• maintain server rules, protect the community, prevent abuse, and troubleshoot the service.

Message content is not used for targeted advertising, user profiling, eligibility decisions outside server moderation, or training artificial-intelligence or machine-learning models.

Persistent off-platform records. The Application stores moderation cases and configuration needed across restarts. These records may include Discord IDs, action types, staff-provided reasons, proof URLs/names, warning counts, timestamps, chat-ban expiration data, and IDs of rules messages managed by the bot.

Temporary message cache. Recent messages may be kept in server memory so edited or deleted content can be recorded accurately. This cache is size-limited, is not written to the moderation database, and is cleared when the Application restarts.

Discord staff logs. Message edits/deletions, moderation evidence, member events, voice events, and invite events may be posted to access-controlled staff channels within Discord. Those messages and attachments are then stored by Discord according to Discord’s systems and policies.

We do not sell or rent user information. Information may be shared only:

• with Discord as necessary to receive events, send logs and notices, manage roles, and perform moderation actions;
• with authorized 302 Community staff through access-controlled Discord moderation and logging channels;
• with hosting or infrastructure providers that help operate and secure the Application;
• when reasonably necessary to protect users, investigate abuse, comply with applicable law, or respond to valid legal process;
• when the affected user directs or consents to the disclosure.

Discord’s handling of data is governed by Discord’s own terms and privacy policy.

• Moderation cases may be retained longer than 30 days while needed to maintain warning history, document staff actions, enforce progressive consequences, resolve appeals, or protect the community.
• Active chat-ban records are retained until the restriction expires or is removed; the related moderation case may remain afterward.
• Recent message cache entries remain only until evicted by newer entries or the Application restarts.
• Discord staff-log messages and evidence remain until deleted under community procedures or Discord’s retention practices.
• Operational logs may be retained for a limited period reasonably necessary for debugging, safety, and reliability.

Information will be deleted when it is no longer necessary for the Application’s stated moderation functions, when Discord validly requests deletion, or after a valid user request unless retention is required by law or necessary to address an active safety matter.

Members may request access to, correction of, or deletion of their stored 302 Mod data by contacting us below and providing their Discord user ID. We may request verification that the requester controls the relevant account before acting.

Because message scanning is an essential server-safety function, members cannot opt out of moderation processing while continuing to post in areas monitored by the Application. A member may stop new processing by not posting or participating, or by leaving the server. This does not automatically erase an existing moderation record.

A deletion request may be limited where retaining a record is reasonably necessary to protect the community, resolve an active appeal or safety issue, comply with law, or document enforcement against abuse. We will explain any applicable limitation when responding.

We use reasonable technical and administrative safeguards intended to prevent unauthorized access, alteration, or disclosure. Access to Discord moderation logs is limited through server permissions. No internet transmission or storage system can be guaranteed completely secure.

Users must meet Discord’s minimum age requirements. If you believe information was processed for someone who is not permitted to use Discord, contact us so we can review it.

We may update this policy when the Application, its moderation practices, or legal requirements change. The “Last updated” date identifies the current version.

For privacy questions, moderation-data requests, or deletion requests, contact:

• Operator: 302 Development / Brandon302
• Email: [email protected]
• Discord server: 302 Community Discord