The finding
Hobby, city, language and gaming servers on Discord already organize real-life meetups. They use Discord's Scheduled Events, event bots and links to outside RSVP tools. Admins want correct time zones, reminders, capacity limits and no spam. They remove bots that ask for broad permissions, mass-message members or scrape member lists.
Discord's Developer Policy, effective 8 July 2024, draws the hard line. Developers must not mine or scrape data from Discord. They must not use API data to profile Discord users, their identities or their relationships with other users. A smart-match bot that reads who is in which server and suggests people to meet does exactly that.
Why it mattered to the design
The earlier plan dropped the Discord smart-match idea for this reason and kept only an RSVP bot that created events and synced RSVPs, with no profiling.
The current plan goes further: organizers are just members. Run clubs, language exchanges and Discord communities are invited to post their events and open seats on Peoplarium. The reward is reach and tools, never payment. The Phase 1 build has no Discord bot, nothing is inferred from server data, and open seats go to verified members.
How it was checked
Researched by AI research agents and checked against primary sources on 28 September 2026. The research cited an older copy of the policy kept in Discord's API documentation. The current policy on Discord's developer support site, effective 8 July 2024, still contains both rules: no profiling of users, identities or relationships, and no mining or scraping.
What admins want from bots comes from community practice and bot comparisons, not a survey, so no figures are given for it.
Sources
- Discord Developer Policy, Discord, published 2024-07-08. Checked 2026-09-28.