Privacy Policy

1. Scope and responsibility

This policy covers Security Guardian, its moderation and appeal features, and the Security Hub website. Hood Team operates the bot. Server administrators choose the honeypot, log and appeal channels, exemptions and configured punishment. They control access to the channels and must inform their community about these settings and evidence handling.

Security Guardian is independently operated. It is not operated, sponsored or approved by Discord merely because it uses Discord APIs.

2. Information processed

• Discord identifiers and context: user, server, channel, role and message IDs; usernames or display information; message timestamps; and member permissions or role information needed for exemptions and moderation.
• Honeypot evidence: the triggering message's text, attachment names, attachment metadata and file URLs. Where available within the bot's limits, attachment copies are downloaded and sent to the configured Discord log channel with incident and action details.
• Appeals: the user and server IDs, punishment, appeal reason, optional evidence links or submitted DM attachments, submission source, status, timestamps and review-message ID.
• Operational records: channel and punishment configuration, whitelist role IDs, moderation and appeal counters, and appeal-cooldown records.
• Website and technical data: the website uses the request IP address and entered user ID for temporary submission rate limits. The hosting service may process request and error logs. Diagnostic notifications may contain identifiers and error context needed by the developer to investigate failures.

Do not submit passwords, Discord tokens, one-time codes, identity documents, payment credentials, health information or other unnecessary sensitive information in appeals or evidence.

3. How and why the data is used

Data is used to apply the administrator's configured honeypot rule, check exemptions, preserve incident evidence before message removal, notify affected users, remove recent messages where permitted, process appeals, reverse a ban or timeout where an administrator approves, prevent repeated appeal submissions, show operational statistics and investigate failures.

The current trigger is a non-exempt user posting in the configured honeypot channel. It does not classify the wording as phishing or use an AI model to decide whether the user is a scammer. Other channel histories may be fetched during recent-message cleanup; that cleanup identifies the user's messages by author ID and timestamp.

Message Content access is used for guild-message text and attachments needed as evidence. DM messages sent to the bot are also used to process appeals. The bot does not track users' online activities for this workflow. Message content is not used to train AI or machine-learning models, to build advertising profiles or to sell personal data.

4. Storage, recipients and visibility

The production application stores its configuration, appeal records, cooldowns and counters in a SQLite database on its Railway persistent data volume, outside Discord. Appeal text and web-submitted evidence links may therefore be stored outside Discord.

The triggering honeypot evidence is assembled in memory and uploaded to the configured Discord moderation-log channel. Downloaded attachment copies are not deliberately saved as separate files in the bot's database directory by this evidence routine. Its download limits are 20 MiB in total and a 10-second deadline, so missing, inaccessible or oversized files may be recorded as unavailable.

People allowed to view the server's log or appeal-review channels can see the evidence and appeal information posted there. Administrators must restrict those channels appropriately. The operator and necessary hosting providers may process operational data for running and supporting the service.

The website can display appeal status and punishment information when a Discord user ID is entered, and lists configured servers and aggregate statistics. Entering an ID is not proof of ownership of that Discord account. The public lookup response is not the full appeal reason or the copied evidence files.

This policy does not claim that Security Guardian has Celestia's separate encrypted GitHub backup system. Copies independently made by the operator or hosting provider must be accounted for when processing data requests. Discord and Railway process data under their own services and policies.

5. Retention and removal

Appeal records are kept while needed for the moderation and appeal workflow. After a successful administrator approve or reject operation, the current implementation deletes that appeal row from the operational SQLite database. The Discord review message is updated with the outcome; the message and its evidence are not automatically erased by that database deletion.

Configuration, whitelist settings, counters and cooldown records have separate lifecycles. There is currently no uniform automatic expiry that deletes every record, moderation-log message or evidence copy within 30 days. Removing the bot, leaving a server or resolving an appeal does not automatically erase all copies.

Data that is no longer necessary for the stated service will be removed or de-identified. Verified requests will be handled promptly, subject to applicable legal requirements. Requests must consider operational records and copies under the operator's control. For records controlled by a server administrator, Discord or another provider, we will explain the scope and coordinate as appropriate.

6. Security and user choices

Administrative appeal decisions require Discord Administrator permission. The hosting platform protects its infrastructure; the running service must be able to read its operational SQLite database, which is not separately encrypted by the reviewed database code. Access to hosting accounts, credentials and server log channels must be limited to authorized people. No system can guarantee complete security.

Administrators can disable the honeypot feature, change its channels or manage whitelist roles. Users can avoid the restricted honeypot channel and choose whether to submit an appeal. These options are not a universal per-user switch that prevents every API event or moderation record from being processed. Data access and deletion requests are available through the contact below.

7. Requests, corrections and contact

For access to, correction of or deletion of your data, or to report a privacy or security concern, contact Discord: uluvjeffy or the Hood Team support server. State “Security Guardian — data request”, your Discord User ID, the relevant server ID/name and the records concerned.

We will verify identity only as necessary through the relevant account. We do not ask for passwords, tokens or one-time codes. We will explain any information needed to process the request, any portion outside our control and any lawful reason a particular record must be retained. Deleting data can remove the ability to retrieve the affected record later.

8. Eligibility, providers and changes

Use the service only if you meet Discord's minimum age and other eligibility requirements and those of applicable law. Report data submitted by an ineligible user to the contact above. Third-party services apply their own policies: Discord Privacy Policy and Railway Privacy Policy.

The date on this page will change when the policy is updated. Material changes will be communicated through the website or support channel. This policy does not override applicable law or Discord's requirements.