The Complete Wiki to Discord Age-Restricted Activities

Discord's newer age-assurance system is changing how certain age-sensitive experiences are accessed across the platform.

For developers, one of the most important areas is Activities. An Activity can be subject to age gating when its Developer Portal configuration enables an Age Gate or when the Activity has an ADULT classification. In those situations, some users may need to confirm their Discord age group before they can launch the experience.

This does not mean every Discord app, bot, or Activity now requires age verification. Discord says that for most developers, existing apps, bots, games, Activities, and Social SDK integrations continue to work normally.

Quick Facts

Discord says users are generally placed into an age group automatically when its age-estimation system has enough confidence. Manual confirmation is mainly needed when the platform cannot confidently classify an account or when a user needs access to an age-restricted experience.

What Are Discord Age-Restricted Activities?

Age-restricted Activities are Discord Activities that have additional age-access requirements.

Activities are interactive experiences that can run inside Discord. Depending on their content and configuration, an Activity may be appropriate for general audiences or may require an age gate.

Discord's September 2026 developer guidance specifically says that Activities with the Developer Portal Age Gate enabled or an ADULT classification can require users to confirm their age group before launching.

The important distinction is that the age restriction applies to the experience, not automatically to every application on Discord.

A normal bot that provides moderation commands, for example, is not automatically turned into an age-restricted application simply because Discord has introduced age assurance.

What Is the Developer Portal Age Gate?

The Age Gate is a developer-facing control that allows an Activity to operate as an age-gated experience.

When an Activity has this type of restriction, Discord can prevent users who are not confirmed as eligible from launching it.

The platform handles the actual age-group determination. Developers do not need to build their own identity-verification system just to make Discord's age gate work.

This is an important architectural distinction:

Developer Portal: Determines that an experience requires age gating.

Discord: Determines whether the user is eligible based on their age group.

User: May need to confirm their age group if Discord cannot already establish that they belong to the adult group.

When Does a User Have to Confirm Their Age?

Most Discord users will not need to manually confirm their age simply to use Discord.

Discord says its age-estimation model can automatically place many accounts into an age group. Users generally encounter additional confirmation when they attempt to access age-restricted content, spaces, or settings without already being classified as adults.

For age-gated Activities, the same concept can apply.

A user may attempt to launch an Activity and encounter an age-confirmation requirement before Discord allows the Activity to start.

This means the first interaction with an age-restricted Activity can look different depending on the user's existing age-group status.

What Does Discord Mean by "Age Group"?

Discord currently uses age groups rather than simply exposing a user's exact birthdate to applications.

The important categories include:

• Teen: generally 13-17
• Adult: 18+
• Unclassified: Discord does not yet have enough confidence to place the account into an age group

Discord says the user's age group is stored in their Account Status and is not displayed publicly on their profile or to other members in a server.

This approach is designed to provide an age signal without giving developers or other users unnecessary personal information.

Why Would Discord Ask Users to Confirm Their Age?

Discord's age-estimation system does not always have enough information to confidently classify an account.

This can happen particularly with:

• Newer accounts
• Accounts where the age model is uncertain
• Users incorrectly classified into the wrong age group
• Users attempting to access age-restricted experiences
• Users in regions where additional age-assurance requirements apply

Discord says that when the model cannot confidently classify someone, the account can remain unclassified while receiving additional safety protections. The user can then confirm their age group if they need access to restricted experiences.

How Users Confirm Their Age Group

Discord's current process starts from:

User Settings → Account Status → Confirm Age

Users may also receive the confirmation prompt when attempting to access a restricted experience.

Depending on the user's region and device, available methods can include:

• Apple App Store age range
• Google Play age range
• Credit card confirmation
• Video selfie
• Government ID scan
• Google Wallet
• AgeKey

Not every method is available to every user.

Discord says the available options can vary depending on region, device, previous attempts, and local requirements.

Does Discord Receive the User's ID or Selfie?

According to Discord, its age-assurance system is designed to return an age signal, rather than the underlying identity information.

For example, Discord says that with facial age estimation, processing occurs on the user's device and the selfie is not shared with Discord.

For ID-based verification, the verification provider handles the document and Discord receives the resulting age information rather than the user's ID itself.

Discord's Safety Library describes this approach as "age signal, not identity."

This distinction is important for developers because applications should not need access to a user's government ID simply to determine whether an age-restricted Activity can be launched.

What Happens When an Age-Gated Activity Is Blocked?

Discord's developer documentation describes a specific runtime behavior.

If a user is not eligible to launch an age-gated Activity, the launch can fail with:

HTTP 403

and:

Error code 50165

Discord describes this as a possible result when a user has not completed the required age-group confirmation.

For developers, this means an Activity should not assume that every user who can see or interact with its launch surface will successfully enter the experience.

Should Developers Handle Error 50165?

Yes.

Discord says developers generally do not need to make integration changes because of the age-assurance rollout, but they should account for users who may not be eligible to launch an age-gated Activity.

A well-designed Activity should therefore handle a blocked launch gracefully.

Instead of treating the failure as:

"The Activity is broken."

the experience should recognize that the user may simply be ineligible or unconfirmed.

A useful error experience can explain that:

1. The Activity has an age restriction.
2. Discord requires an eligible age group.
3. The user may need to complete Discord's age-confirmation process.
4. The Activity cannot bypass Discord's restriction.

Developer Portal Classification Matters

Discord's Developer Policy already places responsibilities on application developers regarding age suitability.

Developers must not direct applications toward users below Discord's minimum age requirements, and applications must be appropriately rated based on their content when required.

Discord's policy also states that applications distributing adult content must follow the platform's age-restriction requirements. Applications that are not labeled age-restricted must remain appropriate for users under 18 and comply with applicable laws.

This makes accurate classification important.

Developers should not attempt to label an adult-oriented experience as general-audience content simply to reduce friction during launch.

Age Gate vs Application Age Rating

These concepts are related but not identical.

Age Gate is the access-control mechanism.

Age classification describes the suitability of the application or experience for a particular audience.

A developer should therefore think about two separate questions:

1. Is the content appropriate for minors?

If yes, the experience may not require an adult-only classification.

2. Does the experience contain adult or age-restricted material?

If yes, the application may need the appropriate age-restricted classification and access controls.

Discord's developer policies place responsibility on developers to ensure applications are appropriately rated and comply with the platform's rules.

What Does This Mean for Discord App Integrations?

The impact depends heavily on what the application does.

A standard:

• Moderation bot
• Utility bot
• Music application
• Community management tool
• General-purpose integration

does not automatically become age-restricted.

However, an integration that launches an age-sensitive Activity can encounter Discord's age-gating behavior.

This distinction prevents a common misunderstanding:

Discord's age-assurance rollout is not the same thing as forcing every developer to implement age verification.

Discord explicitly says most developers will see no changes to existing integrations.

Testing Age-Restricted Activities

Testing is one area where developers need to be careful.

Discord specifically warns that development-team accounts may bypass the age gate.

That means testing an age-restricted Activity only with the account that owns the application can produce misleading results.

A developer might see:

Developer account → Activity launches successfully

while a normal user sees:

User account → Age confirmation required or launch blocked

Discord recommends using a non-development-team account when testing age-gated experiences.

This is particularly important before publishing or distributing an Activity.

Recommended Testing Checklist

Developers building age-restricted Activities should test at least these scenarios:

Adult, already confirmed

The Activity should launch normally if the account is eligible.

Adult, unconfirmed

The developer should verify what happens when Discord requires age confirmation.

Teen account

The Activity should not assume that a teen account can access an adult-only experience.

Unclassified account

The Activity should handle the possibility that Discord has not yet assigned an age group.

Non-development account

Testing should be performed outside the application development team because development accounts can bypass the age gate.

Can Developers Build Their Own Age Verification System?

Developers should not treat Discord's age gate as something to circumvent with their own logic.

If Discord determines that an Activity is age restricted, the platform controls whether the user can launch it.

A third-party verification flow might be useful for a separate business requirement, but it should not be used as a way to bypass Discord's platform-level access restrictions.

The safer architecture is:

Developer classification → Discord age gate → Discord eligibility → Activity launch

rather than:

Developer verification → Ignore Discord restriction → Activity launch

Why Age Assurance Is Important for Activities

Activities can provide more immersive experiences than ordinary text commands.

They can include:

• Games
• Interactive experiences
• Social activities
• Media experiences
• Commerce-related interactions
• Other embedded experiences

Because these experiences can potentially expose users to content beyond normal server messages, platform-level age controls provide another safety layer.

Discord's September 2026 developer update describes the changes as primarily a Trust & Safety platform update, rather than a major developer-platform rewrite.

Age Assurance Is Broader Than Activities

Developers should also understand that Discord's age-assurance system affects more than Activities.

Discord says age confirmation can be relevant to situations such as:

• Accessing 18+ channels and servers
• Viewing certain sensitive media
• Changing certain safety settings
• Speaking in Stage channels
• Enabling age-restricted command settings
• Accessing certain NSFW-related settings on iOS

The exact requirements can vary by region.

Therefore, the Activity age gate is one component of a broader platform-level age-safety system.

How Discord's Age Estimation Works

Discord says it can estimate a user's age group using account-level and behavioral signals.

Its technical explanation says the model considers factors such as:

• How long an account has existed
• The communities associated with the account
• Broader account-level behavioral patterns

Discord says it does not read users' messages in servers or DMs to determine their age group, and no single server determines the classification.

If the model is sufficiently confident that an account belongs to an adult, Discord can automatically place it into the adult group.

If confidence is insufficient, the account can remain unclassified.

What Developers Should Not Assume

There are several common misconceptions around the new system.

"Every Discord app now needs age verification."

False.

Discord says most existing apps, bots, Activities and Social SDK integrations continue working normally.

"Developers receive the user's ID."

False.

Discord's stated system is designed around returning an age signal rather than exposing underlying verification data to Discord applications.

"A developer can bypass the age gate."

No.

The platform determines whether the user is eligible to launch the restricted Activity.

"Testing with the developer account proves the Activity works for everyone."

Not necessarily.

Discord says development-team accounts may bypass the age gate.

"Age confirmation reveals a user's age to everyone."

No.

Discord says the user's age group is not displayed on their profile or to other server members.

Age-Restricted Activities and App Discovery

Discord's App Directory has its own requirements.

Apps seeking discoverability must comply with Discord's Developer Policy and Developer Terms, while public discoverable apps must be suitable for Discord's 13+ audience. Discord's App Directory guidelines specifically prohibit graphic or sexual content in public spaces.

This creates an important distinction:

An age-restricted Activity is not automatically equivalent to an App Directory-friendly experience.

Developers need to consider both:

• Whether the Activity can legally and technically be launched for eligible users.
• Whether the overall application qualifies for public discovery.

How This Changes the Developer Workflow

For developers building Discord Activities, the process now looks more like a safety-aware launch pipeline.

Step 1: Determine the content classification

Decide whether the Activity is suitable for general users or contains age-restricted material.

Step 2: Configure the application correctly

Use the relevant settings and classifications in the Discord Developer Portal.

Step 3: Test with normal accounts

Do not rely exclusively on development-team accounts.

Step 4: Test blocked access

Make sure the application behaves properly when Discord refuses an Activity launch.

Step 5: Handle age-gate errors

Account for 403 / error 50165 where applicable.

Step 6: Keep user messaging clear

Tell users that Discord's age requirements are preventing access rather than presenting the situation as an application failure.

Privacy Considerations

Age assurance inevitably raises privacy questions.

Discord's current approach emphasizes data minimization.

According to Discord, verification vendors are required to collect only what is necessary for the age check and delete verification data after the process is completed. Discord receives an age signal rather than the user's underlying ID or biometric information in the standard flows described by Discord.

For developers, this means an application should avoid requesting additional personal information simply because it wants to know whether a user is an adult.

If Discord already provides the necessary access control, developers should use the platform's mechanisms rather than creating unnecessary data-collection requirements.

Age-Restricted Activities vs Normal Discord Bots

The key difference is that an age-restricted Activity has an additional access layer controlled by Discord.

Why This Matters for Game Developers

Game developers are likely to be among the most visible users of this system because Discord Activities can provide interactive experiences directly inside communities.

For a game with mature themes, gambling-like mechanics, sexual content, extreme violence, or other age-sensitive material, developers need to consider:

• Content classification
• Age-gate configuration
• User eligibility
• Regional legal requirements
• Activity launch failures
• User messaging
• Testing with non-development accounts
• App Directory requirements

The goal is not simply to make the Activity launch.

It is to make sure it launches only for the audience it is intended for.

Timeline

2022

Discord introduced dedicated age-restricted channel settings, allowing servers to identify spaces containing age-restricted content.

February 2026

Discord described plans for a technical approach to estimating age without collecting user identity information.

2025-2026

Discord expanded age-assurance technology in response to legal requirements in certain regions.

September 2026

Discord expanded additional teen safety protections globally and published developer guidance explaining how age-gated Activities can behave at runtime.

September 2026

Discord also published updated user guidance covering age-group confirmation methods, including Apple and Google age ranges, video selfie, ID scan, credit card confirmation, Google Wallet and AgeKey.

FAQ

Do all Discord Activities require age confirmation?

No. Only experiences subject to relevant age restrictions may require users to confirm their age group.

Does every Discord app need an Age Gate?

No. Discord says most existing apps and integrations continue working normally.

What is Discord error 50165?

It is an error associated with a blocked launch of an age-gated Activity when the user is not eligible to access it. Discord documents the response as 403 / error code 50165.

Can teenagers use Discord Activities?

Yes, where the Activity is appropriate for their age and does not have an adult-only restriction. An adult-classified or age-gated Activity can restrict access.

Does Discord show my age to other users?

No. Discord says your age group is not displayed on your profile or visible to other server members.

Do developers see my ID?

Discord's stated age-assurance design provides developers with access decisions rather than exposing users' verification documents.

Why does my development account launch an Activity when another account cannot?

Development-team accounts may bypass the age gate. Discord recommends testing age-gated experiences with a non-development-team account.

Can I confirm my age without an ID?

Depending on your region and device, Discord may offer alternatives such as Apple or Google age ranges, video selfie, credit card confirmation, Google Wallet or AgeKey.

Do I have to confirm my age just to use Discord?

Generally, no. Discord says most users are automatically placed into an age group and do not need to manually confirm their age.

Can an app bypass Discord's age restrictions?

Developers should not design an application around bypassing Discord's platform-level age controls.

Current Status

Discord's age-restricted Activity system is active as part of the platform's broader 2026 age-assurance rollout.

The biggest change for developers is not that every Discord application suddenly requires age verification. Instead, developers need to understand that age-gated Activities can now encounter platform-level eligibility checks before launch.

The most important points are:

• Developer Portal Age Gate can make an Activity age restricted.
• An ADULT classification can also trigger age-gated behavior.
• Users may need to confirm their Discord age group before launching.
• Blocked Activity launches can return 403 / error 50165.
• Development-team accounts may bypass the age gate, so testing must include normal accounts.
• Developers generally do not need to rebuild their integrations because of the rollout.
• Discord's system is based around an age signal rather than exposing users' identity documents.
• Developers remain responsible for properly classifying and operating their applications under Discord's Developer Policy.

For Discord developers, the practical takeaway is simple: classify age-sensitive experiences correctly, test them with ordinary accounts, handle blocked launches gracefully, and treat Discord's age-assurance layer as a platform requirement rather than something an app should attempt to reproduce or bypass