Privacy policy
Last updated 2026-10-08
1. What we store
This site (haechigames.com) stores only what is listed below. Anything not in the table is not stored.
| When | What | Why |
|---|---|---|
| Google sign-in | Name · email · profile photo URL · Google account identifier | To recognise you as the same person |
| When you fill in your account page | Nickname · short bio · contact email · favourite game · play style · newsletter opt-in | Because you chose to write it |
| When an admin suspends or reinstates an account | Whether the account is suspended, the suspension period, reason, and note, and which admin handled it and when | To stop abuse |
| When you sign in | A temporary marker for the session you are signed in with, and its time | To stop one account being used on several devices at once (the newer sign-in stays; the earlier one is signed out) |
| When you choose a display language | The language code you picked (ko · en · th) | So the site and the games show the same language |
| When you sign in | Success or failure · reason for failure · time · country · browser type · account identifier · email · IP hash | To notice attempts against accounts |
| When you view a page |
Which page · which game · visitor identifier · referrer · IP hash If you are signed in, your account identifier is recorded too. |
To count which game draws interest |
| When an admin action happens | What was done · the target · the time · one account identifier · IP hash | To trace who changed what |
| When a game figure is edited | The account identifier of whoever edited it | To know which figures a person touched |
| When you send an enquiry | Category · subject · body · reply-to email · account identifier · IP hash | To read it and reply |
| When you send a report from inside a game | Game name, category, subject, message, app version, web/app, the screen you were on, nickname, email, account identifier | To find and fix faults, and to reward confirmed reports |
IP addresses are never stored in the clear. They are mixed with a secret value and kept only as a hash. That tells us whether the same source repeated, but the original address cannot be recovered from it.
2. What we do not store
- · Passwords. We use Google sign-in only, so there is no place for us to receive one.
- · Payment details. This site takes no payments.
- · Raw IP addresses. As above, only a hash is kept.
- · Ad trackers. No third-party advertising or analytics scripts are included. The only things fetched from outside are a font and the sign-in code, both listed in section 4.
3. Relation to game accounts
Membership data on this site and your records inside the games are kept separately. Deleting your site account does not delete game records, and the reverse is also true; to delete game records, do it inside that game. One exception: your display language is stored once on the account and shared by the site and the games.
4. Who we pass it to
We sell or hand it to no one. Running the site does route through the following, though.
- · Google (Firebase Authentication) — sign-in. We verify that the token Google issued is genuine. Google code from
www.gstatic.comis fetched on the sign-in screen only. - · Cloudflare — the front layer. Traffic passes through it.
- · Cafe24 — where the server and database live.
- · jsDelivr — the body font (Pretendard) is fetched from
cdn.jsdelivr.net. This happens on every page, and your IP reaches them at that moment. It is for drawing text, not tracking or analytics; if the fetch fails the page falls back to a system font.
Those two are the only outbound destinations (font, sign-in code).
5. How long we keep it
Membership data is kept until you delete the account. Sign-in and visit records are stripped of the part that identifies a person (the account identifier) and kept only as statistics.
When you delete your account, the membership data goes at once, and the account identifier is erased from what remains — in all four places: sign-in log, visit log, enquiries, and admin log. For enquiries the exchanged text stays, but who sent it and where to reply are erased. The rows themselves stay because statistics like “how many people came and when” hold up without identifying anyone.
6. Seeing or deleting your data
You can see exactly what is stored on your account page, and delete the account from the bottom of the same screen. Deletion cannot be undone.
7. Cookies
Three of them. A session cookie that keeps you signed in (HGSESS), an identifier so one person is not counted many times (hg_v), and one that remembers the display language you picked (hg_lang). None have anything to do with advertising, and none leave for other sites.
8. Contact
Questions about this document, or requests to delete your data, can go through contact. For an error inside a game, that game's “Report a bug” is faster — it carries the screen you were on and what you were doing.