Privacy Policy
Purposes of processing
The Operator (the JonGem team, email [email protected]) processes personal information for the following purposes:
- Identifying members, signing in, and keeping a session
- Providing the game catalog, play, wishlists, and the library
- Keeping game score records and rankings, and preventing forged scores
- Receiving hosted uploads, links, and embeds, running security scans, and reviewing listings
- Operating the community (comments, reviews, likes, reports) and responding to abuse
- Remembering locale and similar preferences
- Complying with the law and handling disputes
No personal information is currently processed on the basis of consent. The Operator processes personal information on the grounds the Korean Personal Information Protection Act allows without consent. The legal basis for each purpose is:
- Performance of a contract (Article 15(1)(4) of the Personal Information Protection Act): signing up and signing in, keeping a session, two-step verification, the game catalog, play, wishlists and the library, game score records and rankings, receiving uploads, links and embeds and reviewing listings, private game invitations, the community (reviews, discussion posts, replies, likes and reports), remembering your language, and the information received from Google
- Legitimate interests (Article 15(1)(6)): security scans and bot checks, preventing forged scores and scores from many accounts, handling spam and abuse, the play count check, keeping access records (server logs), security alerts to the Operator, and handling disputes. This processing is done only as far as needed and reasonable to protect the Service and its users
- Legal obligations (Article 15(1)(2)): handling copyright notices and notifying the uploader (Article 103 of the Copyright Act), and keeping the access records of the Operator and reviewers who handle personal information (Article 8 of the Standards for Securing the Safety of Personal Information)
Personal information collected
The following information may be collected when you use the Service. The exact items depend on the features you use.
- Account: nickname (public), login subject identifier, login method (local or Google), and bio. If you sign in with Google, the email and display name provided by that account (private)
- Information received from Google: when you sign in with a Google account, Google sends the email address and name of that account through the sign-in service (Supabase Auth). The Operator uses them to identify and contact you and never shows them to other users. Google sign-in is not processing the Operator outsources to Google; the Operator receives this information from Google. The legal basis is performance of a contract (Article 15(1)(4))
- Two-step verification (only if you turn it on): when you turned it on, and a hash of each recovery code with when it was used. The recovery codes themselves are not stored. The authenticator app secret is kept by Supabase Auth, not by the Operator
- Usage records: sign-in times and similar access logs, play counts, wishlists, and the library
- Game scores (when you play a game that has scoreboards): for each play, the game, the version, when it started and when it ends, a hash of the play token (the token itself is not stored), and a random value used to replay the game for a check. When you submit a score, its value on each board, its status (public, held, removed and so on) and why it is held, when it was submitted, and the network it came from (the first part of the IP address, IPv4 /24 or IPv6 /48). Reports of score records a member makes (the reason and how it was handled)
- Community: reviews, comments, likes, and report contents
- Copyright notices (only people who send one): the name of the rightsholder or agent, the email for our reply, the work and why you hold the rights, what in the game copies it, and the statement. Under Article 41 of the Enforcement Decree of the Copyright Act, the notice is attached when the uploader is told that the game was taken down, so the name and contact of the person who sent it reach the uploader
- Uploads: game files and metadata, and security scan results
- Private games (only members who use them): the members a creator invited (nickname and when they joined), the members a creator removed (until let back in), and the passes made when a game is opened (a hash of a random value and when it ends)
- Cookies: the session cookie, sign-in flow cookies (Google sign-in and two-step verification), and the locale cookie. See the cookie notice for details
- Automatically generated data: technical information needed to operate and secure the Service, such as browser type, IP address, and logs
- Network data for scores: to keep the score request limits (a number per 10 minutes for a member in each game and across all games, and for each network of visitors who are not signed in), your member identifier or the network of your IP address is held in the memory of the hub server for 10 minutes. A request refused by a limit leaves one line in the access records (server logs) with the network (for a member, the member identifier and the game address name), kept for the same period as other access records. The network stored with a record is used only to see whether one network holds several top spots of a board, to find forged scores from many accounts
Public pages (games, reviews, discussions, replies and profiles) show only the nickname you choose. On your first sign-in you get a random nickname (for example 플레이어-1a2b3c) instead of your Google name, and you can change it in the account settings on your profile. Your email and Google display name are never shown to other users. The Google display name is stored once when the account is created and is not overwritten at later sign-ins. The email is refreshed at sign-in so it stays a working contact address.
Retention periods
The Operator keeps personal information only as long as needed for the purposes above. The periods for each kind of data are below.
- Account data (email, Google display name, login identifier, nickname, bio): until you close the account. It is erased at once when you do
- Community posts (reviews, discussion posts, replies): until the post is deleted. Posts stay after you close the account, shown as written by "Deleted user" so nobody can tell who wrote them
- Wishlist, library (play history) and helpful votes: deleted at once when you close the account
- Invitations to private games: deleted at once when the creator removes the member. A record that the creator removed them is kept so the same link does not let them back in, and is deleted when the creator lets them back in. Both are deleted at once when the creator or the member closes their account. When the game is deleted, they go when the game is destroyed. Each member has one pass per game, which works until 2 hours after they last opened the game; a pass that ended, or whose member can no longer open the game, is deleted the next time the game is opened or its state changes
- Uploaded game files, metadata and scan records: kept while you are a member. When you close the account, your games become unlisted and leave browse and play. They are kept for 1 year after you close the account, then destroyed. A game you delete yourself is unlisted at once and kept for 1 year from the day you delete it, then destroyed. This year is not a period any law requires; the Operator chose it to handle reports and disputes about the game. If a report on the game is still open, the game is destroyed after that report is handled
- Private game files: when a new version replaces an old one, the old version's files are deleted 7 days later. A private game that neither its creator nor the members they invited play for 90 days is archived and its game files are deleted (the creator is told 14 days before). While a report on the game is open, the game is taken down or the creator's account is suspended, its files are kept, and the 90 days start again when that ends. Version records, scan records, the game's details and its member list stay for the period above, and a new version from the creator opens the game again
- Session cookie (jongem_session): up to 30 days (ends after 3 days without use, up to 12 hours for reviewers), or until you sign out. The server keeps a hash of the session id with its created, last-used and expiry times for the same period
- Sign-in flow cookies (jongem_oauth_state, jongem_oauth_verifier, jongem_oauth_next, jongem_mfa): about 10 minutes
- Locale cookie (jongem_locale): about 1 year
- Score claim cookie (jongem_play_claim): up to 3 hours, or deleted once you sign in and take the score
- Game scores: a play token can submit a score, or be claimed after signing in, for 3 hours from the start of the play. After that, a play that left no score and the play of a visitor who did not sign in are deleted, with their scores, within 70 minutes. A member's plays and score records (value, status, why held, the network) are deleted at once when the member closes the account, or when the game is destroyed. A record a reviewer removed only leaves the rankings and is kept for the same period. Reports of score records are deleted with the record and remain after the reporter closes the account
- Two-step verification data (when it was turned on, recovery code hashes): erased at once when you turn two-step verification off or close the account. Making new recovery codes erases the hashes of the old ones
- Play count check: so that opening the same game many times in one day raises its play count once, the hub keeps a hash of the game, the date and the member identifier or IP address, made with a random key used for that day only. Neither the IP address nor the member identifier is stored, and hashes for different games or days cannot be linked to the same person. The key is kept only in the memory of the hub server, never in the database or backups, and is deleted within an hour after the day ends (Korea time). Once the key is deleted, not even the operator can tell whose hash it is. The hashes are deleted after 7 days
- Access records (sign-in session records, server logs) and audit records: 1 year. This year is not a period set by law; the Operator chose it to look into security incidents and misuse. Sign-in session records are kept for this period even after you close the account
- Access records of the Operator and reviewers (the audit records of the Operator and reviewers handling personal information): kept for at least 1 year under Article 8 of the Standards for Securing the Safety of Personal Information, and for at least 2 years once the system handles the personal information of 50,000 or more people
- Report records (the contents of game and post reports, including the name and contact a copyright notice gives): kept after they are handled, to deal with disputes and to judge repeat infringement, for as long as the reported game (for a post report, the game the post belongs to) stays on the Service, and deleted when that game is destroyed. They remain after the reporter closes the account
- After you close the account: your email, Google display name, nickname, bio and sign-in link are erased at once and every session ends. Signing in again with the same Google account creates a new account with no link to the old records. What is left of the account (such as the join date, which cannot identify you on its own) is kept while posts by that account remain
- Backups: an encrypted backup of the database is made every day, and up to 14 daily, 8 weekly and 12 monthly copies are kept. Deleted data can therefore stay inside backups for up to about 13 months, and disappears when the old backups are deleted. Backups are used only to recover from failures or incidents
- Data a statute requires to be kept: if there is any, this policy will state the statute and the items kept, and the data is kept for that period separately from other data
Provision to third parties
The Operator does not provide personal information to third parties unless you consent, a statute requires it, or it is necessary to protect a person's life, body, or property in an emergency. If a provision occurs, the recipient, purpose, items, and retention period will be stated in this policy and any required consent will be obtained. One provision a statute requires: a copyright notice (including the name and contact of the person who sent it) is attached when the uploader is told, under Article 41 of the Enforcement Decree of the Copyright Act.
Processors and outsourcing
The Service may use the following processors (or equivalent service providers). The actual contracts and scope must be confirmed before launch.
- Supabase: member authentication (including Google sign-in and two-step verification) and, when configured, database hosting. Kept in the Seoul region, Republic of Korea
- Cloudflare: file storage (R2) and, when used, content delivery or hosting
- Google: optionally, URL reputation checks (Web Risk) and a translation API. Google sign-in is not outsourcing, so what it sends is listed under "Personal information collected" above
- Cloudflare Turnstile: checks for automated requests (bots) on sign-in, game upload, a member's first community post, and when you submit a game score, or take one after signing in, that would enter a board's top 10. Those pages load Cloudflare's challenge script, and the hub sends your IP address to Cloudflare when it verifies the result. Used only when configured
- Resend: sends security alert mail to the Operator. An alert can include the internal id of the member involved and the first part of an IP address (an IP range), never an email address or name. Used only when configured
- Amazon Web Services Korea LLC (Amazon Lightsail): hosting of the hub and play servers. The servers are in the Seoul region (ap-northeast-2), Republic of Korea
- Malware scanning (ClamAV) is intended to be run by the Operator. If it is outsourced, that provider will be added to this list
International transfers
To outsource processing and storage needed to perform our contract with you, the Operator transfers personal information outside the Republic of Korea to the companies below. This includes access from abroad. The legal basis is Article 28-8(1)(3)(a) of the Korean Personal Information Protection Act, and the matters required by paragraph (2) of that Article are set out below. The database (Supabase) and the hub and play servers are in Seoul, Republic of Korea.
- Supabase Pte. Ltd. (Singapore, [email protected]): the database and member authentication (including Google sign-in and two-step verification). Data is stored in the Seoul region (ap-northeast-2), Republic of Korea, and Supabase and Supabase, Inc. (United States), which provides its support services, may access it from abroad. Countries: Singapore, the United States. Items: the information listed under "Personal information collected" above that is kept in the database (account, two-step verification, usage records, game scores, community, reports, upload information, sign-in session records and audit records)
- Cloudflare, Inc. (United States, [email protected]): content delivery and the server connection (CDN, Tunnel), file storage (R2), and bot checks (Turnstile). Countries: the United States, and the countries with a Cloudflare data center that handles the request (more than 100 countries, including the Republic of Korea; the list is at www.cloudflare.com/network). Items: requests and responses to and from the Service (including IP address, browser information, and cookies), uploaded game files, encrypted database backups, access logs (server logs), and the IP address and browser information sent for a bot check
- Google Asia Pacific Pte. Ltd. (Singapore) and its affiliates in the Google group, including Google LLC (United States) (contact: support.google.com/cloud/contact/dpo): URL reputation checks (Web Risk) and translation (Cloud Translation). Each is transferred only when turned on. Countries: Singapore, the United States, and the countries where Google or its subprocessors keep facilities (the list is at cloud.google.com/terms/subprocessors). Items: game link and embed addresses members submit and the outside addresses found in uploaded game files (Web Risk), and the published game description, reviews and discussion posts on a game page where someone pressed translate (translation)
- Plus Five Five, Inc. (operator of Resend, United States, [email protected]): sending security alert mail to the Operator. Transferred only when configured. Country: the United States. Items: the internal id of the member involved and the first part of an IP address (an IP range). Never an email address or name
- Amazon Web Services Korea LLC and its affiliate Amazon Web Services, Inc. (United States) ([email protected]): hosting of the hub and play servers (Amazon Lightsail). The servers are in the Seoul region (ap-northeast-2), Republic of Korea; AWS states that information may be stored in or accessed from multiple countries, including the United States. Country: the United States. Items: the requests and responses passing through the servers (IP address, browser information and cookies), the access logs (server logs) held on the servers for a short time, and uploaded files while they are scanned
- Purposes: the work stated for each company above
- Timing and method: sent over an encrypted network connection (TLS) each time you use the related feature or information is stored
- Retention: kept for the periods under "Retention periods" above. Google holds text to translate in memory only briefly while it translates, and Resend keeps alert mail for 30 days. When an outsourcing contract ends, each company deletes the information or returns it to the Operator under its data processing agreement
- How to refuse, and the effect: you may write to [email protected] or [email protected]. These transfers are needed to provide the Service, so if you refuse, you cannot use the features that need them. If you refuse the database and member authentication (Supabase), you cannot use member features, and you can close your account in account settings. Content delivery (Cloudflare) handles every visit, so if you refuse it you cannot reach the Service. Translation is transferred only when someone presses translate on a game page
Destruction
When the retention period ends or the purpose is fulfilled, personal information is destroyed without undue delay. Electronic files are deleted so they cannot be recovered, and paper records, if any, are shredded or burned. Information that must be kept under a statute is stored separately for that period.
Your rights and those of a legal representative
You and your legal representative may request access, correction, deletion, suspension of processing, or withdrawal of consent. Requests can be sent to [email protected] or [email protected]. The Operator will take the needed steps without undue delay and will tell you the result.
Deletion or suspension may be limited where a statute requires the information to be kept. For a child under 14, a legal representative may exercise these rights.
You can change your nickname yourself in the account settings on your profile page, and close your account there by typing a confirmation word. What happens after you close it is described under "Retention periods".
How to request access. To see the personal information the Operator processes about you (Article 35 of the Personal Information Protection Act), write to [email protected] and say what you want to see. So we can check it is you, members should write from the email address linked to their account. The Operator lets you see it within 10 days of receiving the request. If there is a good reason it cannot be shown within that time and it is postponed, or if access is limited or refused for a reason in Article 35(4) of the same Act, the Operator tells you the reason and how to object within 10 days of receiving the request. Once the reason for a delay is gone, you can see the information at once. You can object by writing to [email protected], and the Operator will look at it again and tell you the result. You can also ask the authorities under "Remedies in Korea" below for help.
Separately from an access request, "Download my data" in the account settings (/account/export) gives you a JSON file at once with your profile (including your private email and Google display name), reviews, discussion posts and replies, helpful votes, wishlist, play history, game score records with their plays, reports of score records you made, the details and status of games you uploaded, reports you made, signed-in sessions, whether two-step verification is on and how many recovery codes are left, and account security records such as sign-ins within the retention period. It is machine-readable, so it is easy to keep or take elsewhere.
The file leaves out values that could be used to sign in (session tokens, recovery codes, the authenticator secret), other users' information (for example who reported you, who replied to your posts, or which moderator acted), moderators' internal notes and detailed scan results. For security, it can be downloaded only from a recently signed-in session and only a limited number of times. To see information that is not in the file, use the contacts above.
The right under Article 35-2 of the Personal Information Protection Act to ask that your personal information be sent to you or to another controller does not apply to the Operator. Article 42-2 of its Enforcement Decree limits it to controllers with average sales above 180 billion won that process the personal information of a set number of people or more, and to controllers in healthcare, telecommunications and energy. The download above stays available all the same.
Children's information
The Service is intended for people aged 14 or older. Personal information of children under 14 is not collected without the consent of a legal representative. In the United States and similar jurisdictions, the Operator does not knowingly collect information from children under 13. If such information is found, it will be deleted without undue delay.
Security measures
The Operator takes steps such as access control, HTTPS in transit, HttpOnly and SameSite flags on session cookies, separating the hub origin from the play origin, and scanning uploads. These measures cannot remove all risk of transmission or storage over the internet.
Cookies
The Service uses essential cookies to keep you signed in, to secure the sign-in flow, and to remember your language. Cookie names, purposes, lifetimes, and how to refuse them are described in the cookie notice (/legal/cookies).
Privacy officer
For questions, complaints, or requests about personal information, contact:
- Team in charge of privacy: JonGem Privacy (the JonGem team)
- Email: [email protected]
- Operator contact: [email protected]
Notice for international users (GDPR, CCPA, and similar laws)
For users in the EEA, the United Kingdom, and Switzerland, the Operator processes personal information for the purposes in this policy. Legal bases may include performance of a contract (providing the Service), legitimate interests (security, abuse prevention, and improving the Service), consent where it applies, and compliance with legal obligations. You may request access, correction, erasure, restriction, portability, and objection, and you may lodge a complaint with a supervisory authority. No separate EU representative or formal data protection officer has been appointed; if one is appointed, this policy will be updated.
For users in California and certain other U.S. states, the Operator collects the categories of personal information described above to provide the Service. The Operator does not sell personal information and, as a rule, does not share it for cross-context behavioral advertising. You may request to know what has been collected, to delete it, and to opt out of sale or sharing where that right applies. Send requests to [email protected].
Remedies in Korea
You may also seek help from the following Korean authorities:
- Personal Information Infringement Report Center: privacy.kisa.or.kr, 118 (no area code)
- Personal Information Dispute Mediation Committee: www.kopico.go.kr, 1833-6972
- Supreme Prosecutors' Office Cyber Investigation Division: www.spo.go.kr, 1301 (no area code)
- Korean National Police Agency Cyber Investigation Bureau: ecrm.cyber.go.kr, 182 (no area code)
Changes to this policy
If this policy changes, the new version will be posted on this page with an effective date. For material changes, the Operator will try to give reasonable notice in the Service before the change takes effect.