A community moderator receives the same question from twenty members: “Do I have to send you my ID?” The answer must be immediate and precise. A server team should never collect identity documents, selfies, credit cards, or birthdays in DMs. The safest rollout points members to Discord's in-app flow and explains what the community can and cannot see.
Discord's September announcement, Safer for Teens, Same Discord for Adults, describes its age-group approach and added teen protections. Discord's current help article, How to Confirm Your Age Group on Discord, explains Account Status, confirmation methods, privacy handling, device requirements, and scam warnings. Availability can vary by region and app version.
Growit o1 is an expressive pocket AI device in development. Its current Sight workflow is an owner-triggered connected beta that requires a compatible connected service after setup. Final capabilities, supported services, pricing, and availability will be announced before sales open. In this guide, o1 is a deliberate review prompt rather than an autonomous publisher, account operator, or source of guaranteed performance.
The server's job is communication and moderation. Discord and its approved in-app process own age assurance; volunteer moderators should not recreate it.
Publish a boundary card
| Member question | Community answer |
|---|---|
| Where do I check? | User Settings, then Account Status in the current app |
| Can moderators see my age? | The age group is not displayed on the member profile |
| Should I DM an ID? | No; never send identity documents to moderators or bots |
| Will Discord email a link? | Discord says confirmation happens in the app, not by email or text |
| What if it is wrong? | Use the retry or support route in the official help article |
| What changes here? | Only the channels, permissions, and safety rules named by the server |
Pin the card in a read-only updates channel and link the official Help Center directly. Avoid screenshots from unofficial accounts because interface labels and available methods can change.
Audit channels and roles
List age-restricted channels, stage permissions, bot commands, onboarding questions, and moderator escalation paths. Confirm that server labels reflect the actual content. Do not mark an ordinary support channel as age-restricted merely to force verification.
Review bots that request personal information. Remove commands that ask for birthdays, IDs, selfies, addresses, or payment data unless a documented legal and security review establishes a valid need. Discord says the age group is handled through Account Status; community bots should not duplicate that signal.
Use Growit's community post generator to draft a short notice, then rewrite it against Discord's current help language. Read o1 privacy guidance before using an owner-triggered connected review with moderation logs.
Explain privacy facts without guarantees
Discord says most users will not need an additional confirmation step and that age-group information is not visible to other server members. Its help article describes privacy-forward methods, on-device processing for facial age estimation, document deletion, and a returned age signal rather than identity details.
Quote those boundaries accurately and link the source. Do not promise that any online system is risk-free or describe a vendor process more broadly than Discord does. Never ask a member to prove completion with a screenshot containing account details.
Prepare moderators for scams and distress
Give moderators one response template: do not click verification links sent by email, text, DMs, or bots; open Discord directly and check Account Status. Create a separate escalation for members who report account suspension, an incorrect age group, harassment, or exposure to sensitive content.
Avoid debating a member's age in public. Move support to a private ticket that records only the minimum operational detail, then route the person to official Discord support. Delete unsolicited identity documents according to a written incident procedure and restrict access immediately.
Measure the rollout safely
Track questions by category, broken official links, permission mistakes, and moderation workload. Do not build a spreadsheet of members' inferred ages. The useful signal is whether people can find the official process and whether server permissions behave as documented.
Update the pinned message when Discord changes its help article, app version requirement, or regional process. Name a reviewer and date the notice.
A good rollout reduces panic and data collection. Members learn where to act, moderators stay inside their role, and the server keeps sensitive verification out of community workflows.
