Dadscord Ticket Bot — What Staff Actually See

dadscord · ticket bot · exposed

The Ticket Bot

What the Dadscord ticket system actually exposes staff to — and why nobody warned them before it was too late.

How It Works

The Dadscord ticket system operates through a direct message bot. Members open a ticket by DMing the bot — and from that point, they can send anything. Text, images, files. There is no content screening. There is no filter. Whatever gets sent appears immediately to whoever is handling the ticket.

For new staff with no prior warning, this means exposure to child explicit material, self harm imagery, and other graphic content with zero notice. No training. No preparation. Just access granted, and whatever comes next.

When this was raised with Ezy, it was shrugged off.

The Storage Problem

Ticket logs are stored. The images sent through those tickets are stored with them. Every bot in Dadscord is built and controlled by Ezy and his developers — all of whom are under NDA. There is no transparency into where that data lives, who has access to it, or how long it is retained.

The people who built the system and control the storage can't speak about it. There is no way to know what is being retained, who can access it, or what it is being used for.

The Human Cost

Dadscord staff are unpaid volunteers. They are not compensated, not trained, and not warned about what handling tickets may expose them to. There is no mental health support. No opt-out once you have access. No acknowledgment from leadership that this is even a problem.

Other large Discord servers have content warning systems, staff support resources, and moderation protocols specifically designed to protect the people doing the work. Dadscord has none of these. When the issue was raised, it was dismissed.

If you were a staff member at Dadscord and experienced this, you can submit your account anonymously through the tip form.

⚠ Pro Tip — From Someone Who's Seen It

As a staff member, several tickets involved active blackmail cases. From firsthand experience in that role: it is always in your best interest to not send images of yourself to anyone, for any reason. This includes verification systems, app connections, and direct messages.

Even indirect app connections can be traced back to you. Once an image is sent, you have no control over where it goes. No server, no person, and no verification system is worth that risk.