MOMOKOO MERGE
About this translation. This English text is provided for convenience only. The binding version of this Policy is the Korean original at nos.zone/privacy. If the two differ in meaning, the Korean version prevails.
N.O.S (the “Operator”) treats the personal information of users of the web game MOMOKOO MERGE (the “Game”) with care, and collects only the minimum information necessary to provide the Game.
The Game has no sign-up procedure and does not collect information that directly identifies a user, such as a real name, email address or phone number.
When a user's game ends and the score is submitted to the ranking, the following is sent to the server.
| Item | What it is | Purpose |
|---|---|---|
| Player ID | Random string generated on the device (momokoo_ + 16 random characters) | Anonymous identifier linking ranking records to the same player |
| Display name | Name entered by the user (up to 16 characters) or an auto-generated name (MOMO-XXXX) | Shown on the ranking screen |
| Display name type | Whether the name was entered by the user or generated automatically | Applying the display-name policy |
| Play record ID | Random identifier created for each round | Preventing duplicate submission of the same record |
| Score | Final score for that round | Calculating and displaying the ranking |
| Platform | Runtime identifier such as web | Diagnosing environment-specific problems |
| Distribution channel | Delivery-route identifier such as cloudflare | Version management |
| App version | Game build version | Diagnosing version-specific problems and judging record validity |
| Submission time | Time the server received the record | Record management |
If a user does not enter a display name, none of the information sent to the server is capable of identifying a person. If a user does enter a display name, that name is shown to other users on the ranking screen, so please take care not to enter a real name or other identifying information.
The following is stored in the user's browser storage (localStorage).
(1) Stored on the device only, never sent to the server
(2) Stored on the device and also sent to the server when a score is submitted
The Operator does not access or collect the items in (1). This information is deleted when the user clears the site data in their browser, and cannot be recovered afterwards.
The Game uses Cloudflare (hosting and serverless functions) and Supabase (database). For security and incident response, these services may record access IP addresses, access times, browser information and similar data in their own logs. Such data is handled under each provider's own policy, and the Operator does not use these logs to identify users or for any separate analytics purpose.
The Game offers optional support items for players who wish to help fund development. Supporting is entirely optional; every feature of the Game remains available without it, and supporting confers no in-game advantage.
On any of these routes, the operator does not record support as something linked to a game account or player ID. Supporting changes nothing about your ranking or game records.
The Game carries no advertising and uses no third-party analytics tools (Google Analytics or similar).
Collected information is used only for the following purposes.
Because there are no accounts, rights can be exercised as follows.
| What you want | How |
|---|---|
| Change your display name | In-game pause menu → Name settings (the ranking screen reflects it from your next score submission) |
| Delete past names stored on individual records | Contact us with your Player ID |
| Delete information stored on your device | Clear the site data in your browser |
| Delete your ranking records on the server | Find your Player ID under in-game Pause → Name settings, then contact us with that ID |
A Player ID is required for a server deletion request so that we can confirm the records are yours. The Operator will act on a request and reply with the outcome within 10 days of receiving it.
Once a deletion request has been carried out, the ranking records held under that Player ID, the display names stored on each of those records, and any reports that user filed are all deleted together; no separate copy is kept. Infrastructure logs described in section 2-3 may still be retained for a period under each provider's own policy, and the Operator does not use them to identify users.
| Processor | Work entrusted | Storage location | Privacy contact | Retention period |
|---|---|---|---|---|
| Cloudflare, Inc. | Web hosting and serverless function execution | Global edge network | privacyquestions@cloudflare.com 101 Townsend St., San Francisco, CA 94107, USA | Until the processing agreement ends or destruction under section 5 |
| Supabase, Inc. | Storage and management of the ranking database | Singapore (ap-southeast-1) | privacy@supabase.com | Until the processing agreement ends or destruction under section 5 |
ap-southeast-1) and the Cloudflare global edge network. The transfer takes place at the moment a
user's game ends and the score is submitted, by transmission over HTTPS. The purpose is to provide the ranking
service, and the retention period is as stated in section 5.The Game is rated for all ages and has no age restriction, but it was not designed with children under 14 as its main audience. The Game has no sign-up or age-verification step and does not separately collect information that identifies children.
Where a child under 14 plays, we ask guardians to make sure the child does not enter a real name or other
identifying information as a display name. If no display name is entered, an auto-generated name
(MOMO-XXXX) is used, and in that case no identifying information is collected.
Where this Policy changes, the changes and the effective date will be posted within the Game or on the website from 7 days before that date.
The Operator has appointed a privacy officer with overall responsibility for the handling of personal information, as set out below. Please send privacy enquiries and record-deletion requests to the contact below.
This Privacy Policy takes effect on 31 July 2026.
The revised version takes effect on 26 August 2026 (posted 19 August 2026).
What changed: section 2-4 was added to cover the in-app support items, and the payment wording in section 3 was corrected to describe how payments are actually handled. No new information is collected by the operator.
Amended 7 September 2026.
The iOS app (App Store) was added to the list of payment routes in section 2-4. This adds a description of one more payment route to a clause already in effect; the information collected and your rights are unchanged.