zipguard

The Discord security bot real members never notice.

Zero IP. No web page. No ads. Free for every server, open source.

Join the pilot Read the data statement

Why it exists

Most verification bots send every new member to a web page that records their IP address, browser and device. In October 2026 one of the largest leaked IP-derived locations for millions of Discord accounts. Data you never collect cannot leak.

zipguard works only from what Discord already sends every bot when someone joins, plus what happens inside your server afterwards. Nobody clicks a link. Nobody switches off a VPN.

How it works

Every join: silent scoreAccount age, avatar, public badges, the invite used, timing against other joins, creation-date clustering. Low risk passes with zero clicks.
Medium risk: one clickThe member sees one button inside Discord. Click it and they are in. A click faster than a person can click is held instead.
High risk: a human decidesHeld in a quarantine role until a moderator approves, kicks or bans with one button. The member can appeal from inside Discord.
After the join: anti-nukeThree channel or role deletes by one account inside a minute get reverted, and that account loses its roles. The server owner is never touched.

Every verdict lists the rules that fired, in plain words. Moderator overrides feed the false-positive rate in /zipguard stats. New servers run in shadow mode for 7 days: everything is logged, nothing is enforced, so you can see what it would have done before it does anything.

What we store, what we never store

Stored (90 days, deleted on request)Never stored
Your Discord user ID and when you joinedIP addresses
The risk score and the reasonsBrowser or device fingerprints
Moderator actions and appealsEmail or phone
Server settingsConnections, other servers, message content

Members run /my-data to see their rows and /forget-me to delete them at once. The data statement is generated from the database schema, so it cannot drift from what the code stores.

Honest limits

Without IP addresses or fingerprints, zipguard will not unmask a patient person on a five-year-old second account. Nobody does that without invasive data. zipguard raises the cost of alts and raids; it does not identify people. Servers that want more can turn on Discord's own verified-phone level. Discord holds the phone number; zipguard never sees it.

Setup

  1. Invite the bot.
  2. Run /setup. It creates #zipguard-log, #verify and a quarantine role, and hides your channels from that role. Under 60 seconds.
  3. Drag the zipguard role above the quarantine role in Server Settings, Roles.
  4. Watch #zipguard-log for a week. End shadow mode early with /zipguard shadow on:false.

Commands

CommandWhoWhat
/setupAdminSafe defaults in one step
/zipguard shadowManage ServerLog only, or enforce
/zipguard thresholdsManage ServerScores for the challenge and the high action
/zipguard actionManage ServerHigh risk: flag, timeout, kick or ban
/zipguard antinukeManage ServerAnti-nuke on or off
/zipguard statsManage ServerZero-click rate, completion, false positives, time to verdict
/my-dataAnyoneEverything zipguard holds about you
/forget-meAnyoneDelete it now
/privacyAnyoneLink to the data statement

Pilot

zipguard is in a private pilot with a small group of servers before the public launch. Invites open as the hosted bot comes online. If you run a server and want in, email help@myagents.email with your server name and size.

The source code becomes public at launch, so anyone can check what zipguard collects. There is no paid tier and there never will be ads on a security flow.