Safety center
Scam education, account security, moderation best practices, privacy guidance, suspicious link checks, reporting paths, and practical templates.
Core safety posture
Quick safety checks
Safety library
A calm way to inspect unexpected links before you click.
Review two-factor authentication, authorized apps, recovery options, and device hygiene.
What to document, where to report, and how to avoid escalating harm.
Recognize pressure tactics around free Nitro, fake giveaways, and urgent account claims.
Assign roles, preserve context, keep member updates short, and review after the incident.
Minimize personal data collection and make server expectations visible.
How to review a bot invite before adding it to your server.
A reusable announcement format for scams, incidents, and calm reminders.
A calm way to inspect unexpected links before you click.
Quick answer
Pause, inspect the domain, avoid shortened links, never enter credentials from an unsolicited message, and report suspicious messages.
Suspicious links often rely on urgency. The safest habit is to slow the interaction down and verify the destination before acting.
Do not paste tokens, passwords, backup codes, or private credentials into any site. Discord Wire News will never ask for those.
Review two-factor authentication, authorized apps, recovery options, and device hygiene.
Quick answer
Enable 2FA, review authorized apps, use unique passwords, and keep recovery details private.
Account security works best as a routine. A five-minute monthly review can catch old app authorizations and weak recovery habits.
Never share security codes or credentials with anyone claiming to help from a server.
What to document, where to report, and how to avoid escalating harm.
Quick answer
Use official reporting paths, preserve relevant context, avoid public callouts, and keep private details redacted.
A good report is specific and measured. Include relevant context without spreading harmful content further.
Moderators should document actions according to server policy and avoid collecting unnecessary private information.
Recognize pressure tactics around free Nitro, fake giveaways, and urgent account claims.
Quick answer
Unexpected gifts, shortened links, urgent claims, and credential prompts are all reasons to stop.
Scam education should be practical, not scary. Explain the pattern and the safe action members should take.
Legitimate gift flows should not require you to share passwords, tokens, or backup codes.
Assign roles, preserve context, keep member updates short, and review after the incident.
Quick answer
Use a documented escalation plan, communicate calmly, and avoid improvising policy in public.
Safety incidents are easier to handle when roles are clear. Name an incident lead, a communicator, and a documentation owner.
After the incident, review what worked and update templates rather than relying on memory.
Minimize personal data collection and make server expectations visible.
Quick answer
Collect less, disclose what you collect, limit staff access, and avoid private data in public channels.
Public servers can be welcoming without collecting sensitive details. Ask only for information you genuinely need.
Use staff-only spaces for sensitive moderation context and redact personal details when examples are shared.
How to review a bot invite before adding it to your server.
Quick answer
Check the bot's source, permissions, owner reputation, support site, and whether the invite asks for administrator access.
Do not invite bots just because a message promises a feature. Review the bot's purpose, website, support presence, and permission request.
Administrator access should be rare and justified. Most utility bots can work with narrower scopes.
A reusable announcement format for scams, incidents, and calm reminders.
Quick answer
State the behavior to avoid, the safe action to take, and where members can ask questions.
A good warning should be short enough to read and specific enough to act on. Avoid amplifying suspicious links.
Keep the tone calm. Members need a next step, not a panic spiral.