← All games

PRIVACY

Privacy policy

1. Scope and purposes

This policy covers the Jetty Arcade introduction pages and rock, paper, scissors game. Data is processed to identify game sessions, run and restore matches, determine results, remember language, theme and input preferences, limit excessive requests, predict hands for the live opponent, diagnose errors and performance, and compile service improvement statistics. Introduction pages are served without scripts.

The operator is Enginitto (professional name). Personal information is processed to the extent necessary to provide the service. Analytics and logs are processed on the basis of legitimate interests in improving the service.

2. Data, collection and retention

Game requests process a random session identifier (the ownership key for server match records); match, round and request identifiers; player and opponent hands; results, scores and stage; hand changes, input sequence and selection timing; and match, activity and round timestamps. Live records also store predictions, probabilities, model name, response time, token usage, call counts and processing state. Language, theme and input preferences are stored in the browser. The connection status indicator on the live match screen shows the round-trip time measured by the server (RTT) and the location code of the Cloudflare data center that received the request (edge code, such as LAX, SJC or ICN). Server request logs and game event statistics are described in section 5. There is no registration form or name/phone input.

On game pages (/ko/play/*, /en/play/*), the automatically injected Cloudflare Web Analytics RUM script collects performance and visit statistics: page URL and referrer, browser, operating system, device type, country, load times and Core Web Vitals. Cloudflare states that URL query strings are not logged. The introduction pages block this script through their Content Security Policy (CSP). Processing and retention are described in section 5.

For rights requests and inquiries, we collect the email address and message content from emails sent by the user. Retention is described in section 7.

Server match records expire after 24 idle hours or a maximum of 7 days from the current match start, whichever comes first. Creating, preparing and submitting are activity; reads alone do not extend retention. Restarting or advancing to the next stage recalculates the new match retention period. Browser retention and removal are described in section 10.

In a 60-second fixed window, limits are 6000 requests per run and 60 new-run start requests per session. Practice and live games share this session limit. Run request counters are held in instance memory and may reset when the server instance is evicted. For live games, model call limits per match in the current stage are 120, 180 and 240 for stages 1, 2 and 3 respectively, and 540 per run across stages, managed with the match record. Practice mode does not call the model.

No separate statutory retention obligation applies, and no backups are kept.

3. Deletion procedures and methods

Records are deleted upon access after expiry or by a scheduled cleanup. The session counter is deleted by a scheduled task after its window expires.

Inquiry and rights-request emails are deleted three months after processing is completed.

4. Third-party sharing

For live opponent predictions, the TypeSafe API (https://api.typesafe.ai) receives model name jev-latest, a fixed question and choices, game, stage, rulesVersion, rules, the most recent 20 rounds of history (player, opponent, outcome, changes, selectedAtMs), score (player, opponent) and observation (player, opponent, elapsedMs; null when absent). The prediction request state does not include session or match identifiers.

TypeSafe is called from the server and receives only gameplay data. No personal information, including user session or match identifiers or user IP addresses, is sent; this is therefore not third-party sharing or outsourced processing of personal information. There is no third-party sharing or outsourced processing of personal information other than that described in this policy.

5. Outsourced processing

Cloudflare handles introduction and game requests and stores server match records in Durable Objects. Workers Logs are server request logs used to diagnose errors and performance. Along with request URLs, methods and processing results, they may contain request information such as IP addresses and headers, retained for up to 7 days. Actual storage and masking of headers, IP addresses, cookies and cf location information have not been confirmed. Other edge log processing follows the Cloudflare policy. Site and game server operations are outsourced to Cloudflare, Inc., located at 101 Townsend St., San Francisco, CA 94107, United States. Contact: dpo@cloudflare.com. See the official privacy policy and DPA for entity details and processing terms.

Processing game-page performance and visit statistics through Cloudflare Web Analytics is also outsourced to Cloudflare, Inc. See the analytics dimensions and official RUM documentation for collected data. Cloudflare states that RUM does not use cookies or localStorage, and that IP addresses received during transmission are discarded at the nearest data center rather than stored in core databases or logs. This statement applies only to RUM processing; it does not guarantee that Workers Logs or other processing do not store IP addresses. The Web Analytics FAQ describes seven days of unsampled beacon data retention, followed by aggregation and sampling for long-term storage. Statistics for the last six months are accessible; this is not treated as a deletion deadline for all data.

Workers Analytics Engine provides server game event statistics processed by Cloudflare to improve the service. Data is retained for three months under Cloudflare’s published retention policy. Schema v4 records event kind (match_created, round_resolved, match_finished, model_call, error, submit_decision), game (rock-paper-scissors), mode (practice, jev-reaction), stage, round number, result/status (none, player, opponent, draw, ok, 503, failed, model-limit), model call kind (none, prepare, observe), call latency and input token count. Live round results additionally record the time from round start to the final hand selection (ms), the number of applied reactions and how many changed the opponent’s hand, and initial and last reaction prediction accuracy (hit, miss, none). Only whether predictions match the player’s actual final hand is recorded, not the predicted values themselves. Submission decisions record fixed outcomes such as accepted, late or duplicate sequence, the difference between server decision time and the deadline (ms, clipped to ±60000), strict deadline policy and clipping status; submitted hands are not included. Game events also record the location code of the Cloudflare data center that received the request (edge code, such as LAX, SJC or ICN), and live rounds record the round-trip time measured by the server (RTT, ms). Because the edge code identifies the data center you connected to, it can be used to roughly estimate your access region (at the level of the city where the data center is located). Depending on network routing, the recorded code may belong to a region far from your actual location. RTT is the time the server measures from sending the round-ready response until the browser’s acknowledgement reaches the server. Both values are aggregated only as statistics without identifiers. A zero input token count for a failed call does not mean that no tokens were used. Error statuses concern failed game reaction slots and model calls, not all HTTP errors.

These Analytics Engine events do not record IP addresses, User-Agent, cookies, session owners, request IDs, round IDs, original match IDs, hashes, analytics match IDs, model names, model inputs or outputs, free-form input or error messages. These exclusions do not guarantee exclusion from Workers Logs or other processing. Events do not track individual users or matches.

Receipt and storage of inquiry and rights-request emails through Gmail are outsourced to Google LLC. Inquiry emails are deleted three months after processing is completed, as described in sections 2 and 7. Address: 1600 Amphitheatre Parkway, Mountain View, California 94043, United States. Privacy contact: googlekrsupport@google.com. The entity name and privacy contact are provided in Google’s official Korean privacy policy, and the address in the Google LLC address in its Terms of Service.

6. International transfers

The overseas recipient is Cloudflare, Inc.; its address and contact details follow the official privacy policy and DPA cited in section 5. Processing necessary to provide the service involves network transfers each time the service is used to the United States and other countries hosting Cloudflare data centers. Transfers cover the request information, logs, match data, analytics events and Web Analytics game-page performance and visit statistics in section 5 for site and game server operations, error and performance diagnosis, and service improvement. Match records follow section 2 retention, request logs are retained for up to 7 days, and Workers Analytics Engine events for three months. Web Analytics statistics are used to analyze game-page performance and visits; retention is described in section 5. You may refuse transfers by discontinuing use; the service cannot be used if transfers are refused. TypeSafe is excluded from personal information international transfers because no personal information is sent to it.

The overseas recipient of inquiry and rights-request emails is Google LLC; its address and privacy contact are listed in section 5. Transfers cover the email address and message content in inquiry emails for receipt and storage of inquiry and rights-request emails through Gmail. When a user sends an inquiry email, it is transmitted over the network to the United States and other countries hosting Google data centers. Inquiry emails are deleted three months after processing is completed. You may refuse this transfer by not sending an email; in that case, email inquiries are unavailable.

7. Your rights and representatives

Send access, correction, deletion, restriction, consent withdrawal requests and questions to enginitto@gmail.com. Legal guardians and authorized representatives can contact the same address. Do not email authentication information such as cookie values.

The operator replies to the request email to confirm that the request comes from the individual or their representative. Requests are handled within 10 days and the outcome is sent by email. Inquiry emails are deleted three months after processing is completed.

8. Privacy officer and contact

Privacy officer: 송창현 (operator)
Contact: enginitto@gmail.com

9. Security measures

The server checks session ownership and validates inputs. Session cookies use HttpOnly and SameSite=Strict, plus Secure over HTTPS. API responses disable caching, and requests and model calls are limited. TypeSafe SDK logging is set to off.

Only the sole operator has access to personal information. Cloudflare, GitHub and Google accounts all use two-factor authentication. Secrets are not stored in the repository.

10. Cookies and browser storage

jev-practice-session · cookie
A random session identifier used to check match ownership. Kept for the browser session, without an explicit expiry. Browser session restore settings may preserve it.
jev-locale · cookie
Remembers Korean or English. Kept for one year (Max-Age=31536000 seconds).
jev-theme · cookie
Remembers the screen theme as system|light|dark. Uses Path=/; Max-Age=31536000; SameSite=Lax and Secure over HTTPS. Kept for one year. Delete or block it in your browser’s site data/cookie settings. Without a saved choice, the display follows system settings; after deletion or blocking, the saved choice will not persist on reload.
jev-practice-match · sessionStorage
Practice match ID, used to restore a match in the same tab. Kept for the tab session.
jev-live-match · sessionStorage
Live match ID, used to restore a match in the same tab. Kept for the tab session.
jev-live-transition · sessionStorage
Recovery information for a stage transition. Removed when the transition completes or recovery information is cleared; otherwise kept for the tab session.
jev-input-mode · localStorage
Remembers click/keyboard or cursor input. No time limit: kept until site data is cleared.

Delete or block cookies in your browser’s site data/cookie settings. Clear the three sessionStorage keys by ending the tab session or clearing this site’s data. Clear the localStorage input preference by clearing this site’s data. Restoring a tab may restore sessionStorage, so clear site data for immediate removal. Blocking or deleting cookies may disconnect a match or reset language preferences; clearing storage resets recovery information and input preferences. Deleting browser data does not immediately delete server match records.

11. Sensitive data, pseudonymized data and automated decisions

Sensitive-data publication: not applicable; game inputs are hands and match controls, with no sensitive-data input or publication screen. Service improvement statistics use the fixed event fields in section 5 without creating per-user or per-match identifiers or hashes. There is no separate pseudonymization feature for scientific research or public-interest archiving. AI predicts a hand for the game opponent; server game rules determine the result.

No sensitive or pseudonymized information is processed. AI hand predictions are opponent actions within the game and do not constitute automated decisions affecting data subject rights.

12. Remedies

13. Effective date and changes

Effective date: September 26, 2026
Changes to this policy are posted on this page and recorded in the revision history below. Full previous versions are available through the links in the revision history.

Revision history