🔒 Privacy

1. No Registration Required

You can play the Service without entering an email address, real name, password, or similar information. The Service does not use advertising.

You can also log in with Google (optional) so that you can play with the same match records, collection and Daily Challenge records on another device. All features are available without logging in.

2. Information We Handle

• Stored in your browser: The following are stored inside your browser (in localStorage, and in sessionStorage, which is cleared when the tab is closed). Items with no stated expiry remain until you clear the site data in your browser.
  • Visit source (sessionStorage): The category determined from URL markers and the referring host (English Story, X, search, store, portal, unknown, or a known campaign). Used to measure visits and deleted when you close the tab.
  • Language (localStorage): Your selected language or dismissal of the language suggestion. Used for future suggestions and room invitations.
  • Site you play on (sessionStorage): The name of the browser game site (itch.io or CrazyGames) when you play inside it. Used to decide which screens to hide inside the site and to count how many players came from each site. It also remembers whether a CrazyGames invite or instant play already took you to a room, so you are not moved again when you return to the top page. Deleted when you close the tab.
  • App invitation (localStorage): The time you closed the "Play on the Android app" notice on the top page. Used so the closed notice is not shown again.
  • Store apps (sessionStorage·localStorage): Whether you opened the site from the Google Play or App Store app (deleted when you close the tab), when we asked you to rate it on the store, and whether you turned on the daily reminder in the iOS app. Used to ask only app players, and only once, and to show the reminder button.
  • Identifier, name, and banner (localStorage): A randomly generated identifier for telling players apart, the name you entered, and the banner you chose.
  • Last loaded match stats (localStorage): Your rating, matches played, wins, and rank as last loaded, plus the place, rating change, and time of your recent matches, and a mark showing whose stats they are (a temporary name made from your identifier). This lets the top page show them in the top bar right away, without waiting. Rewritten each time newer stats are loaded.
  • Login (optional) (localStorage·sessionStorage): Only when you log in with Google: a flag that you are logged in, and this device's identifier, name, banner, collection and Daily Challenge records from before switching to the match records of another device (so they can be restored when you log out). Both are deleted when you log out. When the page reloads on login or logout, the notice to show afterward is placed in that tab and deleted once shown.
  • Carry-over from the previous URL (localStorage): When you move over from the previous URL, if this device already has a different identifier, the saved data from the previous URL is held temporarily. It is deleted once the one with more matches has been kept.
  • Rooms you created (localStorage): The room codes of rooms you created yourself (up to the 5 newest). Used to enter the room as its creator.
  • Daily challenge records (localStorage): Daily Challenge results (date, position, time, tiles and emoji map). Results older than one year are removed the next time a result is saved. Action and timing records are also stored to retry a result that could not be sent. Action records whose submission period has closed are deleted the next time a result is saved. While you are logged in with Google, the results (excluding action and timing records) are also stored on the server and synced between the devices you log in on.
  • Collection (localStorage·sessionStorage): Records of the characters that joined your nation in matches (character number, ★, rock-paper-scissors type, name, and when obtained), and the characters newly collected in the current match (to show at the end of the match; cleared when the tab is closed). Not sent to the server while you are not logged in. While you are logged in with Google, the character records (excluding those newly collected in the current match) are also stored on the server and synced between the devices you log in on.
  • Streamer mode (optional) (localStorage·sessionStorage): Only while it is turned on, its settings (deleted when turned off). While it is on, when you move to a room, the room code is placed in that tab so that it does not appear in the address bar (cleared when the tab is closed). Neither is sent to the server.
  • Stamps you pressed, posts you reported and people you blocked on the board (localStorage): The stamps you pressed on the board (which stamp on which post; up to the 300 newest) and the numbers of the posts you reported (up to the 300 newest), and the marks of people you blocked (up to the 300 newest). Used to mark the stamps you have pressed and to fold reported posts and posts and reviews from blocked people on your own screen. Never sent to the server.
  • Display settings (localStorage): Whether sound is muted, the sound effect volume, whether stamps are shown during matches, the difficulty of vocabulary practice, whether "advance automatically on a correct answer" is on for vocabulary questions, the tab you last opened in the rankings, and your keyboard shortcut settings in matches (whether to use them and whether to keep an area selected).
  • Marks of what you have seen (localStorage): The last release version you saw (to show what has changed since your last visit on the top page), whether you saw the tutorial prompt (so it is not shown again), whether you finished the tutorial (to decide whether to highlight the guide for new players), the number of the notice you dismissed or of a regular notice already shown once (so the same notice is not shown again; only the latest one), and when you wrote a review and when you pressed "Later" (to decide whether to show the request for a review on the top page).
• Cookies: Used only when you log in with Google. When you press the login button, a cookie is set for the time between going to Google and coming back (up to 10 minutes) to verify that the person returning is the same person who started the login (it expires after 10 minutes even if you abandon the login). After you log in, cookies are used to keep you logged in (not for advertising or tracking).
• Daily Challenge standings: We send your first result of the day (date, outcome, position, country count, time, tiles and rules version), your device name, and a record of match actions and timing to the server. We replay the record on the same board. Only matching results are saved with your name and a hash of your identifier for 30 days. Action and timing records are kept only for the top 20 for the same period as their results, and removed when a result leaves the top 20. Anyone can watch these replays after submissions close and the standings become final. Anyone can see the names and results of the top 20 players. To prevent the same record from being registered twice and too many submissions from one connection, we also store the record in a form that cannot be reversed (a hash), and count your connecting IP address in a form usable only for that day (a hash). Icons, emoji maps and practice results are not sent.
• Login (optional): Only when you log in with Google, the following are stored on the Service's server.
  • The provider used to log in (Google) and your user ID with that provider (a number unique to each Google account). Only the minimum scope (openid) is requested from Google; your email address, name, and photo are not received.
  • The match records linked to your account (an irreversibly transformed (hashed) form of your identifier).
  • The identifier used to restore the same match records on another device. It is stored in encrypted form, only for people who have logged in (the key never leaves the server).
  • Your collection (character number, ★, rock-paper-scissors type, name, and when obtained) and Daily Challenge records (date, result, position, number of nations, time, tiles and emoji map, excluding action and timing records). They are the same as what is saved in your browser, and are stored per account to sync them between the devices you log in on.
  • The cookie that keeps you logged in. Its content is a random value, and the server stores only an irreversibly transformed (hashed) form of it. In addition, a flag cookie that lets the page know whether you are logged in (its content is just "1") and a verification cookie used during login (between going to Google and coming back; it holds a random value and the page to return to after login, lasts up to 10 minutes, and is deleted once login completes) are used.
• Sent for matches: Your identifier, name, and banner, and your actions during the match. The room server uses them to run the match and to return you to the same nation if your connection drops.
• Random Match records: Your name, banner, rating, number of matches, number of wins, your placing and the time of each match, whether you left partway through, and placing points; your daily and weekly points, matches, and wins (daily and weekly rankings); your matches and wins per season; and your name, banner, rating, matches, and wins at the end of a season (Hall of Fame). Your identifier is not stored as is; it is stored in an irreversibly transformed (hashed) form.
• Random Match game records: To tune the rules, for each Random Match game the following are stored: each nation's placing, final tile count, number of gacha pulls, number of attacks, and wins and losses per character, along with the match length, how it ended, and the rules (ruleset). Names, banners, and identifiers are not included (these records are linked to the rating records of the same match by the match number).
• Usage and entry records: To show daily player counts and busy hours on the top page, understand where first-time visitors leave without playing, and measure return visits, we transform device identifiers into an irreversible form (hashes) and store them with dates for 30 days. We count the first top-page visit, tutorial prompt views and the choice to start or try later, tutorial starts, completions and the step at which it was closed, match starts and completions, and the rank in the first Random Match. The country code inferred from the connecting IP address, distribution channel and source category from the first visit are also linked to the hash for up to 30 days. We determine only a category from URL markers and the referring host; full URLs, full referrers and IP addresses are not stored. URL markers are removed after reading. Hashes for hourly counts are discarded within the same day. Aggregated counts containing no identifiers are stored for 400 days. Detailed entry and retention counts are available only to the operator; only daily and hourly player and match counts are made public.
• Match end logs: To investigate bugs and tune the game, when a match ends, the match length, how it ended, the number of human and CPU nations, and the room settings are logged and stored within Cloudflare's systems for 7 days. In English-learning matches, the number of vocabulary questions asked and the number answered correctly (totals across human nations) are also logged. Names and identifiers are not included.
• Board posts: Your name, banner, post text, tags, and the time of posting (plus, if you add them, the meetup time and room code of a meetup post, or the stream start time and YouTube link of a stream announcement), along with an irreversibly transformed (hashed) form of your identifier. To prevent flooding, the connecting IP address is also counted in a transformed (hashed) form that is usable only for that day. A bot check (Cloudflare Turnstile by Cloudflare, Inc., USA) may be used. When it is used, the check is loaded when the Board's posting form is shown, and your browser sends your IP address, device and browser type, and similar information to Cloudflare. When you post, the Service's server also sends the check result and your connecting IP address to Cloudflare. Cloudflare uses this to judge whether you are a bot and to improve its bot protection. YouTube links are not embedded in the Board; a YouTube page opens only when you click the link (the Service does not send your name or identifier to YouTube). When you report a post, we store the reported post, the reason you chose, the time, an irreversibly transformed (hashed) form of your identifier, and the connecting IP address in a transformed (hashed) form usable only for that post. These are used so that the staff can review the post and so that reports from the same person or the same connection count only once; other users are not shown that you reported a post. When you write a review, we store your name, banner, number of stars, review text, the time and version at which you wrote it, and an irreversibly transformed (hashed) form of your identifier. To check whether you can write a review, we look at your number of Random Match games and 1st-place finishes. Reports on reviews are handled the same way as reports on board posts.
• Access analytics: To improve the Service, we use Cloudflare Web Analytics by Cloudflare, Inc. (USA). When you open a page of the Service, your browser sends Cloudflare the URL of the page you viewed, the page you came from, your device and browser type, and how fast the page loaded. Cloudflare uses this, together with the country derived from your connecting IP address, to compile statistics such as page views for the Service. It does not identify individuals with cookies or similar means, and it does not track your activity on other sites.
• Sharing results: Share images are generated on your device. Only when you press "Post on 𝕏", "Send via LINE", or "📤 Share", the image and the share text are stored on the Service's server for 30 days so that the image can appear on the link card, and deleted automatically when that period ends (the image contains what is shown on screen, such as names, nation names, placings, and ratings). To stop one connection from storing too many images, your connecting IP address is converted into a form usable only for that day (a hash) and counted for 24 hours. "Send via LINE" passes that link to LINE's share page. Saving or copying the image sends nothing to the server. Daily challenges use the same system: an image of the challenge number, result and streak, and the share text including the emoji result, are stored for 30 days. Names and replay actions are not included. When you send a room invite link via "Send via LINE" or "📤 Share", only the link (which includes the room code) is passed, and nothing is stored on the server.
• Links to English Story: The fallen and Unification screens (including the daily challenge) and the character encyclopedia pages contain links to the store pages (App Store and Google Play) of the Company's app "English Story". These links pass through the measurement company AppsFlyer Ltd. (Israel) on the way to the store, so only when you press one, which screen you came from (fallen or Unification, the daily challenge, or the character encyclopedia) and information such as your device and browser type and IP address are sent to AppsFlyer and used to count where English Story installs come from and to prevent fraudulent measurement. Your name and identifier are not sent.
• Connection logs: The Service runs on services provided by Cloudflare, Inc. Connection logs such as the connecting IP address are handled within Cloudflare's systems to prevent abuse and to investigate outages.
• Summary of external transmission: The Service's pages make your browser send information to other companies in the following two cases (external transmission under the Telecommunications Business Act). The information sent and its purposes are as described in each item above. (1) Access analytics: sent to Cloudflare, Inc. (USA), on every page of the Service. (2) Bot check: sent to Cloudflare, Inc. (USA), only when the Board's posting form is shown. In addition, there are links that take you to other sites only when you press them (Google LLC for Google login and YouTube, AppsFlyer Ltd. for the store links to English Story, X Corp. for "Post on 𝕏", and LY Corporation for "Send with LINE"). Handling at those sites is subject to each company's policies.

3. Information Made Public

When you play Random Match, your name, banner, rating, number of matches, and number of wins, along with your points, matches, and wins for the day and the week, appear in the rankings, where anyone can see them (the season and all-time tables list you only after a certain number of matches). When a season ends, the name, banner, rating, matches, and wins of the top players among those who played a certain number of matches that season remain in the Hall of Fame, where anyone can see them. People playing in the same room can see your name and banner. For board posts, anyone can see the name, banner, text, tags, and time (plus the meetup time, room code, stream start time, and YouTube link, if added), along with a short mark that distinguishes the poster. For reviews, anyone can see the name, banner, number of stars, text, and the time and version at which it was written, and the stars are also shown in aggregate, such as an average. Daily Challenge standings show your place out of the total and the number of players per result. Anyone can also see the names and results of the top 20 players for the day. Random Match game records may be presented after being aggregated, for example as averages per ruleset. Individual records are not published. Whether you have logged in and your Google user ID are not made public. Please do not include your real name or contact details in your name.

4. How Information Is Used

We use the information we collect only for the following: running matches; calculating and showing ratings, rankings, the Hall of Fame and Daily Challenge standings; providing the Board, reviews and share links; Google login and carrying your match records, collection and Daily Challenge records over to another device; counting and showing figures such as the number of players on the top page; adjusting the rules; preventing and responding to uses that violate the Terms and other misconduct (including reviewing reports); investigating bugs and improving the Service; and responding to inquiries. Apart from what is described in "3. Information that is made public", we do not provide it to third parties without your consent, except where permitted by law, such as when required by law or when necessary to protect a person's life, body or property and it is difficult to obtain consent.

5. Retention Periods

• Saved room matches are deleted about 6 hours after everyone has left.
• Board posts are deleted after 30 days (any reports on a post are deleted with it). You can delete your own posts at any time from the browser you posted from. The summaries used to count flooding and reports are discarded at 0:00 Japan time. Reviews remain until the writer or the staff deletes them. You can rewrite or delete your own review at any time from the browser you wrote it from (rewriting it also deletes the records of reports on it).
• Hashes in the player count records are deleted after 30 days (hourly ones within the same day), and aggregated counts containing no identifiers after 400 days. Match end logs are deleted after 7 days.
• Random Match game records are deleted after 180 days (the oldest are deleted every day at 0:00 Japan time).
• Results and top 20 replay records for Daily Challenge standings are deleted 30 days after the board date (the oldest are deleted every day at 0:00 Japan time).
• Random Match records are kept for as long as the Service is provided. During the alpha test, they may be deleted by a reset. Daily and weekly ranking aggregates are deleted after 8 days for daily data and 35 days for weekly data. The Hall of Fame (records at the end of each season) is kept for as long as the Service is provided.
• Login accounts (your Google user ID, linked match records, and encrypted identifier) and the collection and Daily Challenge records synced between devices are kept until you delete the account (Daily Challenge records older than one year are removed the next time they are synced). The cookie that keeps you logged in expires after 180 days (extended each time it is used). The verification cookie used during login expires after 10 minutes. Logging out removes the login on that device.
• Data stored in your browser is deleted when you clear the site data in your browser.
• Information deleted on the server, or deleted when its retention period ends, remains in backups kept for failures for up to 30 days and is then deleted.

6. Requests for disclosure, deletion and the like, and inquiries

If you have logged in with Google, you can delete your account (your Google user ID, the link to your match records, your encrypted identifier, your logins, and the collection and Daily Challenge records synced between devices) at any time with "Delete account" in the login section of the top page. The match records themselves remain as the records of when you were not logged in. Records saved in this device's browser remain.

To request deletion of a name or record listed in the rankings, Hall of Fame or Daily Challenge, or of a board post, please contact English Story Support, include "About Eimono Wars" in your message, and provide the name shown in the rankings and the approximate date and time you played.

In addition, requests for disclosure, correction, suspension of use, deletion and the like of your own information handled by the Service, as well as complaints and consultations about how it is handled, are accepted at the same contact. To confirm that you are the person concerned (or an agent such as a parent or guardian), we will ask for details such as the name shown in the rankings and the approximate date and time you played. If we cannot confirm this, we may be unable to respond. No fee is charged. The Company's address and the name of its representative will be provided upon inquiry.

7. Minors

The Service is intended for people aged 13 and over. If you are under 18, please obtain the consent of a parent or guardian before playing. If you are under 16, please read this page together with a parent or guardian.

The Service does not ask for your age or date of birth. If we learn that we hold information about a person under 13, we will delete that information. Parents and guardians who notice this, please let us know through the contact above.

Parents and guardians can request, through the contact above, the deletion of their child's name, records and board posts, or a stop to the use of their child's information.

8. How we protect information

Records such as rankings, board posts and Daily Challenge results do not store identifiers or connecting IP addresses as they are; we store them in an irreversibly transformed (hashed) form (only rooms in a match keep the identifier until the room is removed, so that you can reconnect). Identifiers used for login are stored encrypted. Communication is encrypted (https). The staff screens can be opened only by designated staff, and staff actions such as hiding or deleting posts and replacing names with placeholders are logged. We set retention periods and automatically delete data once they pass. The Company's organizational measures (the person responsible, internal rules, training and so on) are described in the English Story Privacy Policy.

The Service runs on the services of Cloudflare, Inc. (USA), and information stored on the Service's servers is kept on Cloudflare's facilities. The database is kept in facilities in the Asia-Pacific region, but because of how Cloudflare works, it cannot be pinned to a single country. Match rooms run on facilities close to the players, and communication records and end-of-match logs are handled within Cloudflare's systems. You can check the U.S. system for protecting personal information on the Personal Information Protection Commission's page.

9. Changes

When the information we handle or how we use it changes, we will rewrite this page and update its date. The rewritten content takes effect when it is posted on this page. We will not expand the purposes of use to purposes unrelated to the previous ones (if that becomes necessary, we will obtain your consent in advance). When we add information sent externally or new recipients, we will describe them on this page before sending begins. Important changes will also be announced in the notices on the top page.