Privacy Policy
Effective 16 November 2026
CommunityGames.io ("we", "us") runs games that viewers play by typing in a live stream's chat. This policy covers the website at communitygames.io and the app at app.communitygames.io. It says what we collect, why, who handles it for us, and how to get it deleted. Questions go to support@communitygames.io.
If you run a room
- Email address. We send your sign-in code to it and use it to identify your account. Supabase stores it with your sign-in history, and Resend delivers the code.
- Billing. Stripe takes your card and runs your subscription. We never see or store your card number. We keep your Stripe customer ID, your plan's status and the date you've paid through.
- Your room. Its name, your settings, the chat channels you connect, any logo and sponsor text you add, your colours, your ban list, the latest round's results and a history of your last 500 rounds.
- Your browser. The app keeps your sign-in session, your room's mod link and a few display preferences in your browser's local storage. The app sets no advertising or tracking cookies.
- Usage events. When you sign in, start a payment, subscribe or stop, create a room, connect a chat, or start or finish a round, the app sends PostHog a record of it with your account ID (not your email), your room's name, the game, the number of players, the chat platforms and the channels you connected (your Kick or Twitch channel name, your YouTube handle or stream link). PostHog keeps your room's name and channels on your account's record. If you opened the app from our website, your sign-in record also carries the site that sent you there (for example chatgpt.com or google.com) and the website page you first landed on. We use these to see how the service is used.
- Server logs. Our server records errors and request details, including IP addresses, so we can fix problems and keep the service secure. We keep them only as long as we need them for that.
If you play in a stream's chat
Viewers don't sign up. When a streamer connects their chat, the app reads the public chat messages on Kick, Twitch or YouTube to find join words, votes and answers. We don't store the text of chat messages.
For each player we keep the public username, name colour, platform and subscriber badge for the length of the round. When a round ends, we save each player's username, platform and finishing place to that room's round history, along with the game, the time and the round code. A room keeps its last 500 rounds, and older ones are deleted as new ones come in. YouTube usernames are removed 30 days after the round and replaced with "YouTube viewer"; the finishing place stays. The streamer sees this history in their dashboard and can download it.
Each saved round gets a verify ID, shown on the winner card. Anyone with that ID can look the round up at communitygames.io/verify and see the game, the time, the room name, the players' usernames and platforms, the finishing order and the round code. We publish this so viewers can check that a result wasn't changed. If a streamer bans a username, it stays on that room's ban list until the streamer removes it.
YouTube chat is read through the YouTube API Services, so Google's Privacy Policy also applies to it.
If you visit communitygames.io
- Vercel hosts the website and counts visits with Vercel Web Analytics, which doesn't use cookies.
- PostHog records page views and clicks on the website, also without cookies. It counts unique visitors from a hash of your IP address and doesn't keep the address itself.
- The website remembers, in your browser and for the open tab only, which site sent you and the page you landed on, and adds both to its links into the app.
- The website's fonts load from Google Fonts, so Google receives your IP address.
- The contact form sends what you type to Formspree, and booking a call sends your details to Cal.com.
Who handles data for us
Supabase (accounts and sign-in), Resend (email), Stripe (payments), PostHog (usage analytics), DigitalOcean (the app's server, in Toronto, Canada), Vercel (the website), Formspree (the contact form), Cal.com (bookings) and Google (YouTube chat and fonts). Each handles data only to provide its service to us. We read public chat from Kick, Twitch and YouTube.
We don't sell personal information, and we don't share it for advertising.
Where it's stored
In the United States and Canada. If you live elsewhere, your data is moved to those countries to run the service.
How long we keep it
- Account and billing records: while your account is open. We delete them within 30 days of your request, except for payment records Stripe and we must keep for tax and accounting law.
- Room data: until you delete the room or close your account.
- Players' names: in a room's last 500 rounds, until newer rounds push them out or the room is deleted. YouTube usernames, in round history and on the latest winner card, for 30 days at most. A player can ask us to remove their name from a round by emailing support@communitygames.io with the verify ID.
Your choices and rights
Email support@communitygames.io to get a copy of your data, correct it, delete it or close your account. We answer within 30 days. You can cancel your plan any time with Manage billing on the app's start page.
Depending on where you live, laws such as the GDPR or the California Consumer Privacy Act give you these rights, and we honour the same requests from everyone. Where the GDPR applies, we rely on our contract with you for your account and billing, on our legitimate interest in running streamers' games and keeping the service secure, and on legal obligations for tax records. You can also complain to your local data protection authority.
Children
The service isn't aimed at children under 13. If you believe a child under 13 has given us personal information, email us and we'll delete it.
Security
Everything travels over HTTPS. Secret keys stay on our server, and room links carry a secret key that only the owner can replace. No system is perfectly secure, and we'll tell affected users if a breach puts their data at risk.
Changes
If we change this policy we'll post the new version here with a new date. We'll email account holders about significant changes before they take effect.