Discord's Global Age Groups Are Live: What Bot and App Developers Should Check

On September 22, 2026, Discord started rolling out age groups to accounts worldwide. CTO and co-founder Stanislav Vishnevskiy announced it on the Discord blog, and the same day the developer team published an entry called "Age Assurance: What It Means for Discord Developers" in the developer change log.

The headline for builders is reassuring: Discord says most apps keep working as they are. But a few runtime behaviors change, and if you maintain a bot, an Activity or a Social SDK integration, an hour of checking now beats a confused support queue later.

What Discord shipped

Every account now falls into one of three groups:

• Adult (18+): nothing changes.
• Teen (13–17): extra protections are on by default.
• Unconfirmed: Discord doesn't have enough signal yet. These accounts get the same protections as teens, except their full profile and activity remain visible across shared servers.

Placement is automatic. According to the blog post, an estimation model looks at account signals such as account history, activity levels and the communities someone takes part in. Discord says it does not look at messages, calls or other content, and that more than 90% of users won't be asked to confirm their age. Confirmation options include a credit card check, app store age-range sharing, an on-device video selfie and an ID scan. The model is not currently available in the UK and Australia.

Teen protections route messages from non-friends to a message requests inbox, filter sensitive images, block age-restricted servers, channels and bot commands, and limit full profile details to friends and people in smaller shared servers.

Inven Global's coverage independently confirms the timing and the 90% figure.

Why it looks like this

This is Discord's second attempt. In February, the company pushed its planned March rollout to the second half of 2026 after a backlash. TechCrunch reported that many users expected mandatory face scans and ID uploads, and that a breach at a third-party vendor the previous October had exposed data from roughly 70,000 users, including government ID photos. The September version leans on automatic estimation and offers more ways to confirm.

The four runtime changes developers may see

The changelog is explicit that these are behaviors your app might encounter, not features you need to implement.

1. Custom statuses can vanish from presence

"Private Profiles limit the visibility of custom statuses from user presence." The mechanics were documented on September 17: custom status (activity type 4) is omitted from the activities array of Presence Update events dispatched to a guild when a user's profile privacy is set to Friends Only, or to Friends & Small Servers Only in a guild with more than 200 members. Playing, Streaming, Listening, Watching and Competing activities are not affected.

If your bot rewards people for repping your server in their status, or builds leaderboards from status text, treat a missing type 4 activity as "unknown" rather than "removed". Otherwise you may strip roles from members who only changed a privacy setting.

2. Age-restricted Activities may ask users to confirm their age group

If you ship an Activity marked as age-restricted, some players will now hit a confirmation step before they get in. Watch that point in your funnel so a drop-off there doesn't get misread as a bug.

3. Parent-set spending limits may block purchases

Apps with premium SKUs or other commerce flows may see some purchase attempts stopped by limits a parent has set. Make sure your UI handles a failed or abandoned purchase gracefully and doesn't leave entitlements in a half-granted state.

4. Social SDK DMs may land in Message Requests more often

Games that use the Social SDK for messaging should expect more DMs to be filtered into Message Requests instead of arriving directly.

Revisit your nsfw command flags

Age-restricted commands aren't new. Per the application commands docs, a command created with nsfw: true can only be used by someone 18 or older, from an age-restricted channel or from a DM with the app after they enable age-restricted commands in User Settings. What changes is that Discord now assigns age groups across its whole user base, and teen and unconfirmed accounts can't reach those commands. If a command carries the flag out of habit, reconsider it.

One more date: November 16

Separate from age assurance, the same changelog says channel obfuscation becomes mandatory for all bots on November 16, 2026. Channels a bot can't view will still arrive over the Gateway, but with the name ___hidden___, sensitive fields nulled and the CHANNEL_OBFUSCATED flag set. Over HTTP, GET /guilds/{guild.id}/channels will leave them out of the response entirely. You can test early with the "Private Channel Obfuscation" toggle in the Developer Portal.

A short checklist

• Make any logic that reads custom status (activity type 4) tolerant of absence.
• Audit which commands set nsfw: true.
• Exercise failed-purchase paths for any SKUs you sell.
• Turn on Private Channel Obfuscation for a test app before November 16.
• If something breaks, the changelog points to Developer Support and a developer help center article.

Changes like this hit community teams too: role rewards, onboarding flows and moderation habits all depend on what members can see and do. Disclosure: I'm Souvic Chakraborty, and I build Discorder.tools, tools that help Discord communities grow, engage members and run more smoothly, so I have a stake in this space.

Disclosure: this article was written with the assistance of AI tools.