PRIVACY

Privacy Policy

Project Shirohanal Discord bots — Susanoo (Verify), Hoshikaze (Tickets), Kurokami (Security), Setsuna (Welcome), Tsukihana (Music) and Izanagi

Last updated: 8 October 2026

สรุปภาษาไทย

บอททุกตัวของ Project Shirohanal ใช้นโยบายนี้ร่วมกัน เราเก็บเฉพาะข้อมูลที่จำเป็นต่อการทำงานของบอท (ไอดี Discord, การตั้งค่าเซิร์ฟเวอร์ และข้อมูลเฉพาะฟีเจอร์ตามตารางด้านล่าง) ไม่ขายข้อมูล ไม่เก็บ IP จริงของผู้ยืนยันตัวตน (เก็บเป็น hash) และไม่เก็บเนื้อหาข้อความ ขอลบข้อมูลได้ทุกเมื่อผ่านเซิร์ฟเวอร์ซัพพอร์ต

1. Who we are and scope

This policy applies to the Discord bots operated by Project Shirohanal ("we", "us"): Susanoo (verification), Hoshikaze (tickets), Kurokami (security / anti-raid), Setsuna (welcome messages), Tsukihana (music) and Izanagi (license bot), and to the verification page of this website (/verify/…). All of these bots use this one policy. Our community server is discord.gg/2GKjnxGKMR.

2. Data we process, per bot

BotDataWhy
Susanoo (Verify)Server settings (role IDs, channel IDs, limits, and a snapshot of the channel permissions the bot changed). For each member who verifies: Discord user ID, time of verification, and a salted SHA-256 hash of their IP address (truncated). Raw IP addresses are not stored. Single-use link tokens are remembered for 24 hours.Give the Verified role, limit accounts per IP, restore channels with /unsetup, stop link re-use.
Hoshikaze (Tickets)Server settings; for each ticket: ticket number, channel ID, the opener's user ID, category, the reason text the opener typed, the staff member who claimed it, status and creation time; a blacklist of user IDs. When a ticket is closed or a transcript is requested, the bot reads the messages in that ticket channel and sends them as a text file to the server's log channel and/or the opener; the transcript is not kept on our server.Run the ticket system and provide transcripts.
Kurokami (Security)Server settings, whitelists, locked channels, and warnings (user ID, reason, moderator ID, time). To detect spam, links, mass mentions and raids the bot analyses messages and join events (account age, join rate) in real time; this analysis is held briefly in memory and message content is not stored.Moderation, anti-spam and anti-raid protection.
Setsuna (Welcome)Server settings: welcome/goodbye channel and text, colour, optional background image URL, auto-role IDs. When a member joins or leaves, the bot uses their user ID, username, avatar and the member count to build the message; the welcome image is generated on the fly and not stored.Send welcome / goodbye messages and give auto-roles.
Tsukihana (Music)No personal data is stored. The playback queue, the songs/links you request and your voice-channel state are processed in memory only while music plays.Play music in voice channels.
Izanagi (License)Discord user ID, license / subscription records (e.g. expiry time), hardware ID (HWID) and IP address used for license checks, and ban-list entries (HWID, IP, reason, time).Check licenses and block abuse.

All bots also receive the IDs of servers, channels, roles and users involved in a command or event, because Discord sends them to the bot. We keep aggregate usage counters (for example how many times each command was used) and system metrics for our public status page; these do not contain user IDs.

3. What we do not do

We do not sell your data, we do not use it for advertising, and we do not build member profiles. We do not read direct messages. We do not store the content of server messages. We do not use Discord presence data. Some bots use Discord's Server Members and Message Content intents only for the features described above (for example assigning the Unverified role when a member joins, or building a ticket transcript).

4. Verification page and IP addresses

When you open a verification link on this website, your IP address is processed by our server to apply a short-lived anti-abuse rate limit (held in memory) and, if the server enabled it, to enforce the per-IP account limit. Only a salted hash is saved, never the raw IP address. The page asks a small human check and does not use advertising or tracking cookies.

4b. Logging in with Discord and the web dashboard

If you choose "Continue with Discord" or connect Discord in your account settings, Discord tells us your user ID, username, avatar and the list of servers you are in together with your permissions there (OAuth2 scopes identify and guilds). We use this only to log you in and to show the servers where you may change our bots' settings. We save your Discord ID, username and avatar on your website account while it is connected; you can disconnect at any time in your account settings, which removes them. We do not keep the Discord access token (it is revoked right after use) and your server list is kept only in memory for the dashboard session (up to 6 hours). Settings you save in the dashboard are stored in the same way as settings saved with the bots' commands (see the table above).

4c. Web music controller (/web)

The music bot's /web command gives you a personal link to a web page where you can add songs and control the player. The link contains a signed token with your Discord user ID and the server ID; it expires after 6 hours and is replaced when you run /web again. The page reads which voice channel you are in (to decide whether you may control the player) and the current playback queue. Nothing from this page is stored: the queue and playback state exist only in memory while music plays. Anyone who has your link can act as you on that page, so please do not share it.

4d. Whitelist (website)

If you create a Whitelist project we store the project's settings, the script files you upload (and the original if we obfuscated it for you), and your keys with their settings. When someone requests a script we log the result (accepted or the reason it was refused), the first characters of the key, a partly hidden IP address (for example 12.34.x.x) and a short hash of the device id (HWID); the last ~2,000 entries per project are kept for the project owner, who can also see the keys and device limits. Keys remember a hash of the device ids that used them (not the raw ids). The Getkey page keeps a temporary session in memory (up to 30 minutes) that includes the visitor's IP address to stop checkpoints being skipped, and a hash of the IP is stored with free keys to enforce daily limits. Project owners can blacklist IP addresses or device ids. Data of an expired project is deleted 33 days after expiry; deleting a project deletes its files, keys and logs.

4e. Music bot status

The music bot shows the title of the song most recently started on any server as its public Discord status ("Listening to …"). A server administrator can switch this off for their server in the website dashboard.

5. Where data is stored and who can see it

Data is stored on servers we operate. We do not share it with third parties except (a) Discord itself, which receives what the bots send to Discord, (b) our hosting provider, which only provides infrastructure, and (c) when the law requires it. Server administrators can see the information their own server's bot posts (for example verification and moderation logs, ticket logs and transcripts).

6. Retention and deletion

We keep a server's data while our bot is used in that server. You can ask us at any time to delete data about you, or all data for a server (for example after removing the bot), through our community server linked above; we will delete it within 30 days. Server administrators can also remove most data themselves: /unsetup restores the channels changed by Susanoo, and closing a ticket removes the ticket channel. Single-use verification tokens expire after 24 hours.

7. Security

Verification links are single-use, expire quickly and are signed (HMAC) so they cannot be forged. IP addresses used for the per-IP limit are stored only as salted hashes. Bot tokens and secrets are kept on the server and never shown to users.

8. Children

Our bots are used inside Discord and follow Discord's minimum age requirements. We do not knowingly collect data from people below the age allowed by Discord's Terms of Service.

9. Your rights

You can ask what data we hold about you, ask us to correct or delete it, or object to its use, by contacting us through the community server. Discord's own handling of your data is described in Discord's Privacy Policy.

10. Changes and contact

If we change this policy we will update the date above, and the new version applies from then on. Questions or requests: discord.gg/2GKjnxGKMR.