Keep your Discord verification bot safe from being disabled

Your custom bot is where your verified members live. These habits lower the everyday risks that can take a bot, and the members behind it, offline.

Short answer

Give the bot a dedicated owner account with 2FA that joins no servers, use it only for RestoreCord verification and recovery, brand it as clearly yours, keep the token private, and audit its servers in Manage Bot Guilds.

Why the bot deserves this much care

RestoreCord can only pull members back through the bot they verified with. Their authorization belongs to your Discord application, so if Discord ever restricts or deletes that application, those members are lost with it. The setup wizard makes you acknowledge this before you start, and it's worth taking literally.

No checklist can guarantee Discord will never act on an application. The practices below reduce avoidable risk and make recovery far easier if ownership or credentials ever need to change.

1. A dedicated owner account

Don't let your personal account own the production bot. Create a fresh Discord account just for it, or hand ownership to a Discord application team, and enable two-factor authentication immediately. Then follow the wizard's second warning: don't join Discord servers with the owner account. An account that never joins servers can't be phished through a DM from one.

2. One job per bot

It's tempting to bolt giveaways, AI chat or test commands onto a bot that's already in your server. Resist it. RestoreCord's own guidance is that the bot should run verification and recovery and nothing else. Anything experimental belongs on a second bot that holds no member authorizations.

3. Branding that is honestly yours

Use a name and avatar your members know from your server. Never imitate Discord or another brand, and never use member authorizations to sell access or get around platform policy. That last one is the fastest way to lose a bot entirely.

4. Treat the token like a vault key

  • Keep it in a password manager, not in a DM, a screenshot or a shared doc.
  • Never commit it to a code repository, public or private.
  • If it leaks, reset it in the Developer Portal and paste the new value into RestoreCord before doing anything else.
  • Rotate during a quiet period, then test verification with a staff account.

5. Audit where the bot lives

Open the bot in the dashboard and choose Manage Bot Guilds. It lists every server the bot is installed in, with owner and member counts. Spot an install you don't recognise? Select it and leave. You can tick several at once, though you'll need to re-invite the bot to rejoin any you leave by mistake.

Bot Guild Management

View and manage Discord servers your bot is currently in

Search guilds...
A

Aurora Community

Owner
12.4K members
A

Aurora Staff

Owner
38 members
O

Old Test Server

4 members
1 of 3 selectedLeave Selected

Sharing access without sharing the token

Bringing in staff? On Premium and above, sub-users can help manage your servers. Bots shared through sub-user access appear in their bot list without exposing the token or the edit actions, so helpers never need the credentials at all.

RiskHabit that lowers it
Owner account phished or bannedDedicated account, 2FA, joins no servers
Bot flagged for unrelated activityVerification and recovery only
Token in the wrong handsPrivate storage, immediate reset
Unknown installsRegular Manage Bot Guilds review

Setting up from scratch? Follow the custom bot setup guide with these habits in mind, or go back to RestoreCord Bot.

Harden a custom bot in four moves

  1. Make a dedicated owner

    Create a new Discord account just for the bot and enable two-factor authentication on it before anything else.

  2. Keep the bot single-purpose

    Use it only for RestoreCord verification and recovery, with a name and avatar your members recognise as yours.

  3. Guard the token

    Store the token somewhere private, never paste it in chat or a repository, and reset it straight away if it leaks.

  4. Audit installs regularly

    Open Manage Bot Guilds in the dashboard and leave any server you no longer run.

Monthly bot safety review

Run through these whenever staff changes or once a month, whichever comes first.

Owner account is not your main

A separate account owns the application, so losing your personal account never takes the bot with it.

Owner account joins no servers

It exists to hold the application and nothing else.

Token lives in one private place

A password manager, not a Discord DM, a screenshot or a code repository.

No unrelated commands

Giveaways, AI chat and experiments run on another bot.

Branding is clearly yours

Nothing that resembles Discord staff or an unrelated brand.

Guild list reviewed

Every server in Manage Bot Guilds is one you actually manage.

Bot security questions

Protect the bot that protects your server

Review your custom bot's owner, token and installs in the RestoreCord dashboard today.