Secure Your Bot
Lower the risk of Discord restricting your custom RestoreCord bot: who should own it, what to use it for, and which branding and uses to avoid.
No checklist can guarantee that Discord will never restrict or disable an application. These practices reduce avoidable risk and make recovery easier if credentials or ownership need to change.
Security Principles
1. Do not let a personal Discord account own the production bot
- Avoid: A personal Discord account owns the production bot.
- Instead: A dedicated owner or Discord application team controls the bot.
Example to avoid: the application's team member list shows a single member, personal-owner, marked as Owner, who also owns personal servers.
2. Do not turn the RestoreCord bot into a general automation bot
- Avoid: The RestoreCord bot also runs giveaways, experiments, or public commands.
- Instead: The bot is used only for RestoreCord verification and recovery.
Example to avoid: the bot's slash command list shows /verify (RestoreCord verification) next to /giveaway (unrelated automation) and /ai-chat (experiment command).
3. Do not impersonate Discord or unrelated brands
- Avoid: The bot uses official-looking or unrelated branding.
- Instead: The bot uses a name and avatar your members recognize as yours.
Example to avoid: a bot profile named Discord Support (discordsupport) with a Discord-style "D" avatar and an App tag.
4. Do not use RestoreCord to sell members or evade policy
Selling members and evading Discord policy are prohibited.
- Avoid: Member authorizations are used for selling access or policy evasion.
- Instead: RestoreCord is used only for legitimate server verification and recovery.
Example to avoid: a message from member-market reading "Selling 10,000 verified members — DM for pricing".