Our Data — Transparent by Design
Our core game metrics come from publicly available Roblox APIs. For brand intelligence, we also collect publicly available social and earned-media data. We never access private player data. Here is exactly how we collect, process, and serve our intelligence.
Roblox Public APIs
Concurrent players, total visits, likes, favorites, and game metadata. The primary source for all CCU tracking and engagement metrics.
Game discovery and recommendation feeds. Used to identify trending, rising, and newly popular games across the platform.
Gamepass listings, pricing, and purchase data. Powers monetization analysis, revenue estimation, and gamepass density calculations.
Game icons, place images, and creator avatars. Provides visual assets used across dashboards and game intelligence pages.
Creator profiles, display names, and account metadata. Used for creator attribution and studio identification.
Studio and group ownership data. Identifies which games belong to organized development teams versus solo creators.
Keyword and term search across the Roblox catalog. Supports keyword intelligence features and game discovery by name.
Platform Scale
Data Limitations
- CCU data is a periodic snapshot (every 5 minutes), not a continuous real-time stream. Brief spikes between samples may be missed.
- Revenue figures are model-based estimates, not actual Robux earnings. They should be used directionally, not as precise financial projections.
- Historical data is aggregated over time: hourly resolution for the first 3 days, then daily summaries. Intra-day patterns are lost after aggregation.
- Core game data comes from publicly available Roblox APIs. Private analytics (Developer Hub data, A/B test results, etc.) are not accessible to RoLearn.
- Brand-intelligence features additionally use publicly available social/earned-media data (e.g. YouTube, X, TikTok, Instagram, Twitch, Facebook), collected via official APIs and, where no public search API exists, third-party collection vendors. This covers public creator/post data only.
- Customers using the RoLearn SDK send us player telemetry about their own games. RoLearn processes this as a data processor under a Data Processing Agreement; it is not part of the public-data pipeline described here.
- ML model accuracy depends on data quality and market stability. Sudden platform changes or Roblox API modifications may temporarily affect predictions.
Privacy & Data Handling
Game data: RoLearn only collects publicly available game metrics — concurrent players, visits, likes, favorites, gamepass listings, and game metadata. We do not access any private player data, Developer Hub analytics, or personal Roblox account information.
User data: When you create a RoLearn account, we store your email address, a bcrypt-hashed password, subscription plan, tracked games, and UI preferences. Passwords are never stored in plaintext.
Authentication: Sessions are managed via cryptographically signed JSON Web Tokens (JWT) with short expiration periods. All traffic between your browser and our servers is encrypted with TLS 1.2/1.3.
For complete details, see our Privacy Policy.