Privacy Policy

Hi, darling. This policy explains what ZeroTwo Plush (“ZT Plush”, “the bot”, “we”) collects when you use the Discord bot, the dashboard at dashboard.zt-bot.com or the website at zt-bot.com, why, how long we keep it, and what you can do about it. ZT Plush is run by one developer (Doog) in the State of Florida, United States.

The short version: we store what the features you use need to work. We don’t sell data, show ads, or use your messages to train AI. You can download or delete your personal data yourself with /privacy export and /privacy delete.

1. Who decides what gets stored

Most data exists because a server’s staff turned a feature on (for example Message Logger, tickets or welcome messages) or because you used a command (for example /birthday set or /remind). Server staff can see the records the bot keeps for their server, such as warnings, tickets and logs. If you have questions about a specific server’s logs, its staff are often the right people to ask; we can help too.

2. What we collect

Discord identifiers

Server, channel, role, message and user IDs, so settings and records stay attached to the right server and person. Some records also save a username or tag as it was at the time (for example the author of a deleted message, or the staff member who sent a Mass-Tag).

Server settings

Everything staff configure: welcome and goodbye messages, custom commands, embeds, scheduled messages, reaction roles, permission tiers, AutoMod lists, giveaway defaults, the server’s language and so on. Text staff write is stored as written and is never translated.

Data about members

• Moderation: warnings (severity, reason, who issued and who removed them), AutoMod hits (including the link that was posted) and verification attempts.
• Tickets: who opened a ticket, its category, and the subject and details you typed.
• Things you set: your birthday (month and day only), AFK reason, reminders, saved playlists, your personal language and your privacy opt-outs.
• Activity in features: giveaway entries and wins, poll votes, boost history for booster rewards, counting and word-chain progress, and how many translations you used each day.
• Plush+: when a license is redeemed, we store the license key, the server, who redeemed it, and the purchase ID and email address Gumroad returns for that key.

Message content

The bot uses Discord’s message content access for these features only:

• Aurora AutoMod (on by default) reads messages, edits and forwarded messages to find scam and phishing links. Messages are checked on our server against threat lists and are not stored; when a bad link is found, the link and a warning are saved.
• Message Logger (off by default; staff turn it on) saves deleted messages: the text, the author and attachment links. Free servers keep 1 per channel for 5 minutes; Plush+ servers keep 10 per channel for 1 hour. Bot messages and DMs are never logged. Unless staff switch it off, a copy of each deleted message is also posted to the server’s mod-log channel, where it stays until staff delete it.
• Overseer Logs (Plush+, off by default; staff turn it on) posts log entries to channels the server’s staff choose. Depending on what they switch on, an entry can include the text of a deleted or edited message (before and after), its images (re-uploaded as files, since Discord removes them once the message is gone), a text file of messages removed in a purge, voice channel joins, leaves and moves, member joins and leaves, nickname and role changes, channel and role changes, and who did it, read from the server’s Discord audit log. The bot only stores the settings; the entries stay in those channels until staff delete them. Bot messages are skipped, and members who used /privacy optout never have their message text included.
• Tickets: when a ticket closes, a text transcript of the ticket channel is posted to the server’s transcript channel (if set) and sent to the server owner. The transcript itself is not stored by the bot.
• Commands and features you use: reminders, AFK reasons, polls, quotes, counting and word-chain channels, Mass-Tag and scheduled messages store or repost the text that was typed for them.
• /translate sends the text you choose (including a message you point to by ID) to DeepL.

We never read DMs sent to the bot (it doesn’t receive them) and never record voice: in voice channels the bot only plays audio and joins deafened.

The dashboard and website

• Discord sign-in asks only for your profile and the list of servers you’re in (the identify and guilds scopes). Your Discord access token is kept in an encrypted sign-in cookie and is only used on our servers to talk to Discord and the bot.
• Cookies: sign-in cookies (needed to stay signed in), zt_lang (your language), and a passcode cookie on the owner-only ops panel. Your browser also remembers which site announcement you dismissed. There are no advertising or analytics cookies.
• Like any website, our hosts process technical request data such as IP addresses to deliver pages and stop abuse (see section 4). The bot itself never receives your IP address, email address or phone number from Discord.

3. How we use it

• To run the features you and your server use.
• To enforce limits and keep the bot safe: rate limits, translation caps, AutoMod, abuse protection and server standing.
• To check and support Plush+ licenses.
• To fix problems: error reports and logs may include server and user IDs (never passwords or tokens).

We do not sell or rent data, use it for advertising, build profiles of people, or use message content to train AI or machine-learning models.

4. Services we share data with

Only what each service needs to do its job:

• Discord — the platform the bot runs on, and the sign-in for the dashboard.
• Hetzner — hosts the bot and its database (Hillsboro, Oregon, USA).
• Vercel — hosts the website and dashboard. Cloudflare — DNS and email routing.
• DeepL — receives the text you ask /translate to translate. Translations are cached in the bot’s memory for up to 24 hours and never written to disk.
• Gumroad — processes Plush+ payments. We never see your card details; we check license keys with Gumroad.
• Music sources — song searches go through our own Lavalink server to SoundCloud, YouTube and similar sources; LRCLIB receives the song title and artist when you ask for lyrics.
• Link fixers — for content extraction the bot rewrites social links to embed-friendly services (fxtwitter, rxddit, kkinstagram, tnktok); Discord then loads the preview from them.
• Threat lists — the bot downloads phishing lists from URLhaus (abuse.ch) and a public GitHub list. Nothing about you is sent to them.

We may also disclose information if the law requires it, or to protect people from harm or abuse of the bot.

5. How long we keep it

• When the bot leaves a server: that server’s data is deleted 30 days later, unless the bot is added back first. We keep the server’s standing record, including its name (so blocked servers stay blocked), and any Plush+ license record.
• Plush+ license records (key, server, who redeemed it, Gumroad purchase ID and email) are kept for as long as the license exists, so we can support and verify purchases.
• Message Logger: 5 minutes (Free) or 1 hour (Plush+), as above.
• Translation counters: 30 days. AutoMod hit records: 90 days. Verification attempts: 90 days. Reminders: deleted 7 days after they fire.
• Warnings: kept while the bot is in the server. When a member leaves, their low and medium warnings are marked as cleared but remain in the server’s history; staff can remove warnings at any time.
• Everything else (settings, tickets, giveaways, polls, birthdays, playlists and so on) is kept until it’s deleted by you, by staff, or by the 30-day server purge.
• Backups: we keep copies of the database on our server, readable only by the bot’s system account, so we can recover from failures. Copies are deleted within 90 days, so deleted data can remain in a backup until then. Backups are never published or shared.
• Logs: technical logs rotate and are deleted after about 14 days. Error reports are kept until the problem is fixed.

6. Your choices and rights

• /privacy export — get a file with the data the bot holds about you (also on the dashboard).
• /privacy delete — delete your personal data: birthdays, reminders, AFK, playlists, language, poll votes, giveaway entries, logged messages, counters and similar (also on the dashboard).
• /privacy optout — stop Message Logger and Overseer Logs from recording the text of your messages in every server. Mass-Tag DMs can be turned off per server with /masstag optout.
• Remove single items yourself, such as /birthday remove or deleting a playlist.

What delete keeps: records that belong to a server’s safety and history — warnings, AutoMod hits, tickets you opened, Mass-Tags you sent, giveaways you hosted and anything you created for a server (custom commands, scheduled messages). Your opt-outs are kept too, so logging and DMs stay off. If you want any of these removed, email us and we’ll review it with the server.

Depending on where you live (for example the EU, UK, California or other US states), you may have rights to access, correct, delete or port your data, to object to or restrict processing, and to complain to your data protection authority. We honor these requests wherever you live. Email darling@zt-bot.com with the subject Data Request and your Discord user ID; we reply within 30 days (sooner if your law requires).

EU/UK legal bases: performance of the service you or your server asked for (contract), our legitimate interests in running and protecting the bot (for example AutoMod and abuse prevention), and consent where a feature is opt-in. We may transfer data to the United States, where our hosting providers are.

7. Children

ZT Plush is not directed at children. You must meet Discord’s minimum age (13, or older where your country requires). We don’t knowingly collect data from children under that age; birthdays are stored without the year, and if we learn we hold data about a child under the minimum age we delete it.

8. Security

We use encrypted connections, a firewall, restricted access to the server and database, strict limits on dashboard requests, and regular updates. The bot has a built-in lockdown mode for suspected security incidents. No system is perfectly secure: if we believe data has been accessed without permission, we will lock things down, notify Discord, and tell affected users and servers through the support server and this website as quickly as we can.

9. Changes

We’ll update this policy when the bot changes. The date at the top shows the latest version, and important changes are announced in the support server.