JAMONORI / Privacy Policy
Privacy Policy
JAMONORI (the “Operator”) handles information from users of the JAMONORI app and the jamonori.com information website as described below.
Effective date: 2026-11-06
1. Information and purposes
My Playground processes word input and scores on your device. Account nicknames, experience synchronization, Live Multiplay and Google sign-in use the information below. Unexpected-error reports may be sent whenever the server is reachable, regardless of play mode or sign-in status.
| Category | Information and purpose | Retention |
|---|---|---|
| Guest use | Random user identifier and hashed session information for joining and reconnecting to live play | Sessions: 7 days from issue. Identifiers attached to play and submissions are removed with the related records |
| Google sign-in | Google account identifier and hashed session information for account recognition and sign-in | Account identifier until account deletion. Sessions are valid for up to 180 days after the last session check and renew during use. Signing out revokes that session |
| Live Multiplay | Participation, submitted word paths and times, scores, ranks and nickname for score verification, results and abuse prevention | Records are cleaned up after 30 days from the end of the round; account deletion removes that account’s records |
| Account profile | Automatic or custom nickname, initial-choice state, change time, policy-consent version, change restriction, cumulative experience and profile revision for account display, levels, rewards and rename timing | Until account deletion |
| Solo experience verification | Account-bound random per-device sync stream ID, sequence and event ID, rules and dictionary versions, play type and vocabulary scope, tiles, accepted paths, start/end timestamps, elapsed times and finish type. The server recalculates scores; the entire history and wordbook are not uploaded | Raw round payloads are processed during verification and not saved in the server database. Receipt details expire at 30 days; physical removal proceeds in batches of up to 128 on subsequent activity and may take longer. Replay-prevention cursors, sync-limit state, cumulative experience and live-run continuity remain until account deletion |
| Nickname reports and hiding | Reporter and target IDs, server nickname snapshot, fixed reason, time, review state, minimal operator-action/review audit data and hidden target IDs for safe public names and moderation | Reports and audits expire logically at 30 days. Physical deletion removes up to 128 rows per table per maintenance call on activity or resumption; inactivity or backlog may delay removal, with no exact deletion deadline. Hiding lasts until removed or an associated account is deleted. Account deletion removes linked report, block and audit references |
| Request limits | IP address and account request counts/windows to limit excessive requests | IP is used in game-server limiting memory, not stored in the game database. Account nickname-limit windows are stored in the database and pruned after expiry on activity. Sync-limit state remains until account deletion. Provider processing is described in section 3 |
| Error reports | Error message and code location, app version and platform (Android, iOS or web) for diagnosis | Server error logs: up to 7 days. Account and device identifiers are not sent as separate fields |
| Email and deletion requests | Sender email, message and the minimum account-verification information needed to respond and handle rights requests | Deleted from the Operator’s mailbox within 90 days after resolution. Additional verification evidence is deleted as soon as its purpose is complete. Provider records and backups are described in section 3 |
When you sign in with Google, we may temporarily receive an authentication token containing your name, email address and profile-picture URL. After verifying your identity, we store only Google’s account identifier from Google data in account data. We do not save your Google name, email address or profile picture in account data or show them in rankings. If you email us, we separately process your sender address and message. Rankings show account nicknames and safe generated names for guests. Saving a custom name requires acceptance of our Nickname rules. Other players can report or hide names in the app.
On the web deletion page, Google verification loads after you choose Verify account. The selected Google email is temporarily displayed so you can check the deletion target; it is not stored in account data. The authentication token is used only for verification and deletion. The page clears its verification details when verification expires, is cancelled or finishes. This page does not create a JAMONORI account.
2. Information on your device
Game history (the latest 200 games per play type), settings, recovery data, saved and collected words, bests, legacy device experience and record-reset undo data stay on your device. Legacy experience is preserved separately; new account experience starts at zero. History import does not increase account experience.
Each signed-in account has a local profile cache, reward state and durable pending solo-experience queue. The queue holds its original account, random stream ID, sequence, completion ID, round payload, first-dispatch revision and retry state. It is separate from the 200-game history limit and has no expiry before acknowledgment. Completion IDs prevent duplicate registration for the local stream lifetime. Small batches are sent on Sync or live entry; continuation runs only while live. Switching accounts never transfers the queue. A guest-started round never becomes account experience after sign-in. We collect no hardware identifier or device fingerprint.
A local sign-in marker contains no name, email or authentication token and supports startup prompts. Sign-out or account deletion in the app clears it. Ordinary sign-out retains account queues and reward caches.
After server account deletion, the app signs out and clears that account's profile, queue, completion IDs, reward caches and account link in recovered play. Other accounts, local history, wordbook, collected words, bests, settings and legacy experience remain. If cleanup fails, Device cleanup offers a local-only retry. Each recovery key (jamonori-account-cleanup:<encodeURIComponent(subjectId)>) contains only the deleted random account ID and flag 1. It has no expiry until cleanup succeeds and is then removed immediately. It contains no profile, experience or round payload. If even this marker cannot be saved, a warning asks you to retry before closing because recovery may not be remembered after restart.
After successful cleanup, a separate minimal IndexedDB deletion tombstone prevents late writes for 48 hours and is removed on the next local access after expiry. It contains the account key, expiry and empty queue state, with no profile, experience or round contents. Deletion also removes the original stream, so an old open round cannot register account experience again.
Use the app's record controls or device/browser data controls to remove local records. Delete exported files separately. Deleting an account on the website cannot remotely erase storage on other devices.
3. Providers and international processing
The Operator runs JAMONORI from the United States and entrusts the providers below with processing and storage needed to deliver the service and support you request. We distinguish game storage, web and API delivery and security, and email forwarding and storage. App and website connections to the game server use HTTPS.
For overseas processing and storage necessary to enter into or perform our service contract with you, we rely on Article 28-8(1)(3)(a) of Korea's Personal Information Protection Act. This policy discloses recipients and contacts, processing countries and regions, data, timing and methods, purposes and retention, and how to refuse the transfers. We distinguish the Operator's direct collection from the United States from processing entrusted to external providers. Operating from the United States does not mean all information is stored only there.
| Provider and service | Data, purpose and transfer timing | Processing locations and retention |
|---|---|---|
| Cloudflare, Inc. — game processing and storage (Durable Objects) | Account identifiers, sessions, nicknames, profiles, experience, sync identifiers, verification payloads, reports, blocks, moderation audits, participation, submissions, scores and ranks from section 1 travel over HTTPS during account, sync and live features. Account and experience management, gameplay, verification and nickname moderation | Northeast Asia is requested as a preferred location; storage is not restricted to a specific country. See Cloudflare's published countries and regions below. Account, session and game data: section 1; storage recovery history: up to 30 days |
| Cloudflare, Inc. — web and API delivery, security and error logs | IP, requested URL, access time, browser information and the relevant request data are transmitted and processed when you connect to the website or game server. Error reports from section 1 arrive when unexpected errors occur. Page and API delivery, connection protection and troubleshooting | Cloudflare's global network processes requests separately from the game storage placement. App error logs: up to 7 days. Cloudflare's own security and network records follow its processing rules |
| Cloudflare, Inc. — email forwarding (Email Routing) | When you email us, addresses, messages and attachments travel over the network to Gmail. Processing of sender, recipient, subject, message ID and delivery-result metadata | Cloudflare's global infrastructure. Delivery analytics metadata: 31 days |
| Google LLC — support email storage and replies (Gmail) | Email addresses, messages and attachments travel over the network when support mail is received or answered. Support and rights requests, correspondence storage, spam and security processing | Google servers worldwide, including the United States. The Operator deletes correspondence from its mailbox within 90 days of resolution and additional verification material as soon as it is no longer needed. See below for removal from provider systems and backups |
We describe processing countries and regions using official provider documents and our current service settings. The published scope below applies according to the type of information and feature used; it does not mean all information is copied to every country.
- Cloudflare's South Korea addendum lists affiliate processing in the United States, United Kingdom, Singapore, Australia, Germany, Portugal, France, Japan, Canada, Netherlands, United Arab Emirates, India, Mexico, Malaysia and Sweden. Its service-specific subprocessor list lists Google for the Developer Platform in the United States, European Economic Area, Australia and India, and Oracle in the United States, European Economic Area, United Kingdom, Japan, Australia, Canada and Singapore. Requests travel through its global network; these affiliate and subprocessor lists are not a complete list of network countries.
- Google's Privacy Policy describes processing on servers worldwide, outside your country of residence, and it publishes data center locations. We have not applied a country restriction to our operational Gmail account. The data center list does not specify where an individual support message is stored.
Provider privacy contacts are privacyquestions@cloudflare.com for Cloudflare and googlekrsupport@google.com for Google in South Korea. Contact privacy@jamonori.com about JAMONORI's international processing, access, deletion or restriction of processing. If you do not want the processing required for an online feature, stop using that feature. Account deletion removes information linked to your existing Google account; playing live as a guest afterwards processes new guest information. Not sending a support email avoids forwarding and storage of that correspondence. Solo play requires no Google sign-in, but error reporting may still occur when the server is reachable, as described in section 1.
Google sign-in and Google verification for web account deletion connect to Google when you start the corresponding feature. Google's own processing of account and authentication information follows the Google Privacy Policy. Section 1 describes what JAMONORI receives or stores.
See the Cloudflare Privacy Policy and Data Processing Addendum for its processing practices, and the Email Routing analytics documentation for delivery records. Google's retention guidance says deletion generally takes around two months, and data may remain in encrypted backups for up to six months.
We do not sell personal information or use it for personalized advertising. Apart from providing the services above and complying with legal requirements, we do not disclose it to third parties for other purposes.
4. Account deletion and your rights
You may request access, correction, deletion or restriction of processing, and contact us with privacy questions.
- In the app: From any app screen, select your nickname in the header (Sign in before signing in), open the account dialog, then choose Delete account. During Live Multiplay, wait until the round has ended before deleting. Your account, Google link, sessions, nickname, profile, experience, sync cursors, receipts, limit state, live-run continuity, linked report/block/audit references and associated live participation, submissions, scores and ranks are removed from the server. Your Google account itself is not deleted.
- Outside the app: verify with Google and delete your account on our account and data deletion page, or email privacy@jamonori.com. Reinstalling the app is not required. For email requests, we explain the minimum information needed to verify ownership; an email address or display name alone is not proof of ownership.
- We aim to handle email requests within 7 days of receipt. If more verification or time is needed, we explain why and provide an expected timeline. A shorter legally required deadline takes precedence. Do not send passwords, sign-in verification codes or identity documents.
We remove expired data from active storage using the cleanup process stated above; activity-driven batch deletion may lag logical expiry. Account deletion removes the linked data. Cloudflare recovery history may retain earlier states for up to 30 days and is not used for normal service operation. Error logs without an account-identifier field may remain for up to 7 days. Email and provider records follow sections 1 and 3. If the law requires separate retention, we explain its basis, data and duration and limit it to what is necessary.
5. Security
Server session values are hashed. Android sign-in data is encrypted using Android Keystore. Web-game sign-in cookies use HttpOnly, SameSite and Secure attributes. Operational access is restricted, and the service is configured not to put authentication-bearing request bodies or headers into ordinary access logs.
6. Website, cookies and advertising
The jamonori.com website provides Google verification for account deletion and uses no advertising or visitor-analytics tools of its own. Starting verification connects to Google and the game server. The game server's jamonori_challenge cookie binds the verification request for up to 5 minutes. The deletion page does not create a new sign-in session. Blocking this may prevent web verification; email support remains available. Fonts and illustrations are served by the site. Cloudflare processes network information to deliver and protect the site and may use security-check cookies when needed.
When web-game sign-in is available, jamonori_session maintains the session and jamonori_challenge verifies Google sign-in for 5 minutes. Guest sessions last 7 days; account sessions last 180 days after the latest check and renew during use. Blocking them may prevent web-game sign-in and live features. The current app does not provide advertising SDKs or payment features.
7. Age
JAMONORI is intended for users aged 15 and over in South Korea. In other countries, the minimum age is 14 or the age required by the local app store content rating, whichever is higher. A parent or guardian who believes information about a child under 14 has been processed may contact us for review and deletion.
8. Privacy contact
- Privacy and rights-request contact: JAMONORI Privacy
- Email: privacy@jamonori.com
- The Operator handles these inquiries and requests directly.
9. Changes
We update this page and its effective date when the policy changes. Important changes to information use or your rights will be announced on the website or in the service before taking effect, with separate consent where required.