Privacy Policy
The operator of Gemoim ("we") runs Gemoim (https://gemoim.com, the "Service"): party and classroom games played on phones, the word-guessing game "Chammallo", and information pages (kids' activities, places, festivals, quizzes, tools and a mobile game ranking). The Service can be used without signing in, and we handle as little personal information as possible, in accordance with the Personal Information Protection Act of Korea.
1. What information we access, collect, store and use
| Category | Items | Purpose |
|---|---|---|
| Playing a game | The nickname the player types | Showing names on the game screen, scoring |
| Input during a game | Answers (text, choices, drawings); Chammallo chat and descriptions (including text being typed) | Running the game, showing results, live relay to other players, checking for inappropriate language |
| Google Sign-In (optional) | Google account unique identifier; email address (only if verified by Google) | Identifying the member and keeping them signed in. Google Sign-In uses only the basic sign-in scopes (openid, email, profile); of these we store only the identifier and email. We do not access the user's YouTube account, YouTube data or any other Google data. |
| Signed-in users' records | Nickname; game records (scores, ranks, rating points, win history, Gemoim level, experience, daily stamps, chosen character, name tag frame, skin); leaving-game and chat sanction records | Providing records and rankings, preventing abuse |
| Question sets (optional) | Question sets a signed-in user creates | Using them in games; visible to others only if the creator turns on sharing |
| Classes (optional, teachers) | Class name and roster entered by the teacher (student number and a display name chosen by the teacher); class session records (attendance, per-game scores and ranks, answers to the teacher's own question sets) | Letting the teacher see participation and results. Co-teachers invited by the class owner (up to 5) see the same roster and records and each other's account email. |
| Business information change request (optional, business owners) | Sender's email address, business name, request, attached photos, business website or phone given for verification | Changing or removing a business photo or listing. Sent through the user's own email app; not stored on our servers. |
| Comments and likes on information pages (optional, signed in) | Comments and replies with time, nickname, likes and "want to go" marks, time of confirming age 14 or older | Publishing comments (public, with nickname), reply notifications, saved list |
| Direct messages (optional, signed in) | Message content and time, blocked users | Communication between users. We do not read messages; if a message is reported, only the reporter's last 5 received messages from that person are passed to the report. |
| Email updates (optional consent) | Google account email, time of consent, type and time of emails sent | Weekly email about weekend festivals and alerts for saved events. Not sent at night (21:00–08:00); stops immediately on unsubscribe. |
| Generated automatically | A random per-browser connection identifier | Returning to the same seat after reload or reconnection |
| Collected automatically | IP address, access time, browser information (web server access logs) | Service stability, handling outages and abusive access |
| Reports | Reported person's nickname and account (if signed in), reason, game, room number, time, the reported Chammallo message, reporter's account (if signed in) | Review and action by the operator. The reported person is not told who reported. |
| Usage statistics | Page visits, screens viewed and time spent, type of referral (search, KakaoTalk, invite link, etc. — not the address), device type and environment (operating system, browser or in-app browser type, screen size range, language, installed as home-screen app, 3D support), page load time, how far an information page was scrolled (range), game progress (start, finish, left midway), words typed into the site search box (words that look like numbers, emails or links are discarded; only the number of people per day is counted, IP is not kept). The browser stores the first and last visit dates to count return visits. | Improving the Service. The server keeps only daily and hourly totals and never receives or stores who did what. Search words are deleted after 30 days (after 7 days unless searched by 3 or more people). |
| Service operation logs | Room number, random connection identifier, room and game stages, join and disconnect times, class student numbers, server and screen errors with browser type, the screen flow just before a screen error (game stage and kind of action), device type and screen size, text the user writes with "Report a problem" (no nicknames, answers or chat) | Finding and fixing errors and outages |
Guests (not signed in) have only their nickname and temporary identifier handled in server memory; these disappear when the room closes or the server restarts. We do not collect resident registration numbers, phone numbers, real names, school names or location. We do not use third-party advertising or analytics tools or cookies; usage statistics are calculated directly on our server. The Google Sign-In button is provided by Google and works under Google's policies.
2. Processing of in-game input
- Party and classroom game nicknames, answers and drawings are handled only in server memory while the room is open and are not stored. They are checked by an automatic filter on our server before being shown; this check is not sent outside.
- Comments, direct messages and nicknames on information pages are checked by the same on-server filter before publishing or sending. Links, phone numbers and messenger IDs are not allowed.
- Chammallo chat is handled in server memory only during the match and not kept afterwards. Some messages (a random sample, reported messages, messages of warned users) are sent to Anthropic (section 5) for AI review. Review results are used to improve the filter in a form that does not identify who wrote them (sentence, game topic and verdict only).
- To improve the Chammallo bot, description sentences are kept without identifying the writer (sentence, topic and answer word only). They may be used as bot lines after 24 hours; sentences judged inappropriate are not used.
3. Retention and deletion
- Game room nicknames, answers, drawings and scores: deleted when the room closes.
- Class rosters and records: until the teacher deletes them or the account, and automatically at the end of the school year (end of February). Teachers can extend by one year from 90 days before deletion.
- Question sets: until the creator deletes them or the account.
- Account information, game records, sanction records: until the account is deleted. "Delete account" on "My info" (gemoim.com/me) deletes them immediately. If deleted during an active sanction or matchmaking wait, a one-way hash of the Google identifier and the end time are kept only until that period ends.
- Chammallo chat (original): deleted when the match ends.
- Non-identifying review records and bot sentences: until the purpose of improving the filter or bot is achieved.
- Reports: 90 days.
- Comments and likes: until the writer deletes them or the account.
- Direct messages: 1 year after sending; deleted from both inboxes when either account is deleted.
- Notifications: latest 100 per person.
- Email consent: until withdrawn or the account is deleted; sent-email records 400 days.
- Business change request emails: 1 year after handling.
- Web server access logs: 14 days. Service operation logs: 14 days. Screen error records and "Report a problem" texts: 90 days.
- Database backups: made daily and deleted after 14 days.
- Usage statistics: non-identifying totals only.
- Sign-in tokens: revoked on sign-out; only hashes are stored on the server.
- The browser stores the sign-in token, connection identifier (deleted when the tab closes), last nickname, first and last visit dates and, for guests, level, stamps and chosen character. These can be cleared in browser settings.
4. Provision to third parties
We do not provide users' personal information to third parties, except where required by law.
5. Processors and transfers abroad
| Recipient | Task | Items | Country · method |
|---|---|---|---|
| Amazon Web Services, Inc. | Server and database hosting; email sending (Amazon SES, only with email consent) | All items in section 1 (for email: recipient address, nickname and content) | Stored and sent in Korea (Seoul region) |
| Anthropic, PBC (privacy@anthropic.com) | AI review of Chammallo chat | Messages under review and game context; no user identifiers | USA, via API during use; not used to train models |
| Google LLC | Sign-in authentication | Google account authentication | USA, the user authenticates directly with Google |
Party and classroom game input is not sent outside. Chammallo games opened in school mode are not sent to Anthropic or used for bot training.
5-1. Use of YouTube API Services
The mobile game ranking information page uses YouTube API Services.
- What we access: once a day our server, using an API key (not any user's account), searches for public videos about each game published in the last 7 days and reads their public view counts.
- What we store and display: only the aggregate per game — total view count and number of videos, with the date it was measured. We do not store or display any video, title, channel, comment or other YouTube data.
- User information: we do not access, collect or store any user's YouTube or Google account data through the YouTube API Services, do not send information about users to YouTube or Google, and do not use cookies or device information for this feature. Google Sign-In (section 1) is separate and does not request YouTube access.
- Refresh and deletion: aggregates are refreshed daily. Each aggregate is stored and displayed for at most 30 days from the day it was measured and is then deleted automatically, even if the daily update stops. Deletion requests sent to the contact in section 9 are handled within 7 days.
- By using that page you agree to be bound by the YouTube Terms of Service. See the Google Privacy Policy. Permissions given to Gemoim through Google Sign-In can be revoked at any time at Google security settings.
6. Users' rights
Users may request access, correction, deletion or suspension of processing of their personal information at any time. Accounts and records can be deleted directly with "Delete account" at gemoim.com/me; other requests can be sent to the contact below with the Google account email used to sign in, and are handled without delay.
7. Children under 14
Children under 14 cannot create accounts. They may join games without signing in, in which case no information identifying the child is collected. In classes, students join without signing in by choosing their number from the teacher's roster. If we learn that account information of a child under 14 has been collected, we delete it immediately.
8. Security
- All communication is encrypted with HTTPS.
- Sign-in tokens are stored only as hashes, and server access is limited to the operator.
- Other players see only nicknames, not account information.
9. Privacy officer
Gemoim operator · hamlee9@gmail.com
10. Changes
Changes to this policy are announced on this page at least 7 days before they take effect.