Nelly floating next to a shield with a Discord logo.
Engineering & Developers

Updated Requirements to How Apps Access Data in Servers

Effective today, we're making changes for app developers that impact how their Discord apps access information from servers they’re added to, including information about server members, user presence, and message content. While most Discord apps and bots don’t use this information, we’re adding stronger protections for this data such as annual reviews and steeper thresholds for access. Continue reading to learn more about what’s changing and why.

These changes are primarily aimed at app developers (if you’re a developer, head to our Developer Help Center for a detailed guide). If you use apps on Discord, the short version is: most apps will continue working as they do today, but with more guardrails around what data they can access. An app that previously had access, but doesn't complete the new review process or is not granted access, may have functionality impacted as a result. For example, apps that previously relied on text commands (i.e. a bot that reacts to a particular word or phrase sent in a message) may be redesigned to operate with slash commands (where a user activates the bot by typing a /command) instead. To minimize disruption, developers will be notified and given 90 days to retain access while they make any needed changes or apply for continued access through the review process. Additionally, developers can resubmit at any time.

Today’s changes only affect how and when developers apply for access to certain user data, not what data is available. Read on for a full breakdown of what's changing.

What's Changing

There are two key changes to how apps request access to message content, server member lists, and user presence, such as online/offline status. Many Discord apps don’t use this data, so this change is only applicable to the small number of those that do. Here's what's changing and how often apps need to reapply for access. 

  1. User threshold change: Apps that reach 10,000 or more total users now need to go through a review process to keep accessing this data. Previously, we reviewed apps that reached 100 or more servers. In other words, we are changing the threshold based on how many total users it reaches, not just the number of servers the app is in. This means that apps with access to under 10,000 users will not experience any changes, while apps that reach a wider audience require review.
  2. Annual review change: Apps must now reapply for continued access every year. Apps change over time. Annual check-ins are an opportunity for developers to demonstrate that an app's data access still matches what it actually does. 
Chart that reads: “Updated Requirements for Discord Apps. Old: Based on servers, Apps in 100+ servers required a review, and submitted for review once. New: Based on users, Apps reaching 10,000+ users now require reviews, submitted for review annually.” 

Why We’re Making This Change

We love to see the ingenuity app developers use to create interactive minigame bots, apps that help moderate conversations, host giveaways and contests, and organize events. The original design for access requirements were based on what Discord and the app ecosystem looked like in 2020.

As Discord has grown, so has the number of apps accessing user data, and so does the importance of putting additional safeguards in place. Server administrators are in control of which apps they add, but we want to build additional protections that help Discord apps access the data they demonstrate that they need. 

Because the old threshold was based on server count, a Discord app added to a large community could have access to this kind of data without regularly going through the review process. These changes tie access to how many users an app can reach. Additionally, the original purpose of an app may evolve over time. An app with access from one year ago may serve a very different purpose today. Annual check-ins help reduce access that is not intended, necessary, or acceptable under our policies, which further strengthens protections for users.

Looking Ahead

As the app ecosystem continues to thrive (whether with purpose-built apps that exist in only one massive server, or public bots that wind up added in servers across Discord’s ecosystem), this data access will now be limited to clearer use cases.

Remember that server members can also review app profiles from the member list to learn more about the app and to help make informed decisions about the servers you participate in. 

We're continuing to invest in the tools and infrastructure that make Discord the best place to build and use apps. These changes will help ensure a safe, fun, and creative app ecosystem on Discord for years to come. 

Common Questions

  • Will I notice anything different as a user? In almost all cases, no. If an app you use hasn't applied for or maintained its access, some of its features that depend on this data (like reading message content) may stop working. The app itself won't disappear; it just won't be able to access that data until the developer reapplies.
  • What happens if an app developer misses the deadline to apply? If an app misses its deadline or doesn't meet our review criteria (which focuses on whether the app still actively uses the data it has access to, and whether that data is needed for its stated purpose), Discord may suspend its access to the relevant data, and developers can reapply at any time. The app will continue to function for features that don't require this access.
  • Does this mean apps get more access to my data? Apps can't access anything they couldn't before, and no new data is being shared. This is a change to the threshold for when apps have to apply for access, effectively increasing limitations on how the apps can access data.

If you have questions, our Support Center is here to help.

Tags
No items found.

related articles