Keep Factually independent
Whether you agree or disagree with our analysis, these conversations matter for democracy. We don't take money from political groups - even a $5 donation helps us keep it that way.
Fact check: How much data does discord collect on the user
1. Summary of the results
Discord collects extensive amounts of user data across multiple categories. According to their privacy policy, the platform gathers account information, user-generated content, payment information, and behavioral data from platform interactions [1]. The scope of data collection is particularly concerning as it includes IP addresses, connected accounts, Discord discriminator numbers, and payment information - much of which remains in Discord's databases even after account deletion [2].
Data usage patterns vary significantly depending on activity type. Text messaging consumes approximately 0.02 MB per message, voice calls use 0.15-0.5 MB per minute, and video calls can consume 5-20 MB per minute [3]. However, technical issues can cause extreme data consumption, with one documented case showing 1000GB usage in 24 hours due to potential malware, caching problems, or application bugs [4].
Security incidents have exposed the risks of Discord's data collection practices. In March 2023, a data breach through a compromised support agent affected 180 user accounts, exposing sensitive information including state ID numbers and driver's license numbers [5]. Additionally, fraudulent services claim to sell access to 600 million Discord users' message histories for $5, suggesting potential data scraping activities [6].
2. Missing context/alternative viewpoints
The original question lacks important context about Discord's data protection measures and user controls. Discord emphasizes that they do not sell user data and provide users with privacy controls including two-factor authentication, content filters, and customizable privacy settings [7]. This presents a more balanced view of Discord's data practices beyond just collection.
Financial incentives play a crucial role in data collection practices. Discord benefits from collecting extensive user data to personalize user experiences and improve platform functionality [1], which ultimately drives user engagement and revenue. The company's business model relies on this data to maintain competitive advantages in the gaming and communication platform market.
Technical infrastructure requirements also justify extensive data collection. Discord manages trillions of messages and faces significant database management challenges [8], suggesting that some data retention serves legitimate operational purposes rather than purely commercial exploitation.
Alternative viewpoints include privacy advocates who argue that Discord's data retention practices, particularly keeping data after account deletion, represent unnecessary privacy risks [2]. Conversely, Discord and similar platforms argue that data collection enables essential features like message history, friend connections, and platform security.
3. Potential misinformation/bias in the original statement
The original question itself is neutral and factual, seeking information rather than making claims. However, it lacks specificity about what type of data collection is being questioned - whether personal information, usage analytics, message content, or technical data.
Potential bias could emerge in how the question is interpreted. Privacy-focused perspectives might emphasize the extensive and persistent nature of Discord's data collection [2], while platform defenders might highlight user control features and data protection measures [7].
The question also doesn't acknowledge the legitimate operational needs for data collection, such as maintaining platform functionality, preventing abuse, and providing user-requested features like message history and cross-device synchronization [8].
Missing nuance includes the distinction between data Discord collects directly versus data that may be accessed through security breaches or third-party scraping operations [6] [5], which represents different categories of privacy risk that users should understand separately.