Operations Console Privacy Policy
Effective 2026-10-16 · Last updated 2026-10-17
hetero8 (“we”) is an independent software studio. This policy explains what personal information we process in the hetero8 operations console, why, and for how long. It applies only to the operators who sign in to the console.
The operations console (console.hetero8.com) is an internal tool we use to run our games — checking service status, handling support requests and reviewing game accounts. It is not open to the public: only people we have registered in advance as operators can sign in.
1. What we receive from Google
Operators sign in with their Google account. We request only the basic sign-in scopes openid, email and profile, and receive:
- your Google account ID, email address, and whether that address is verified
- your name and profile picture
We do not request access to Gmail, Drive, Contacts, Calendar or any other Google data. We do not store your profile picture.
2. What we keep, why, and for how long
| What | Why | How long |
|---|---|---|
| Operator list — email, name, Google account ID, role, status, registration time, last sign-in time | Let registered operators in and refuse everyone else | While you are an operator; deleted when your access ends, except what the two records below must keep |
| Role history — when a role was granted, changed or revoked, and by whom | Show who had which access, as Korea’s personal information security standard requires | 3 years |
| Sessions — sign-in time, last activity, IP address, browser type | Keep you signed in, sign you out after 30 minutes idle or 8 hours, and allow a forced sign-out | Up to 2 years |
| Passkeys (up to 5 per operator) — the ID, public key, signature counter and connection types of each passkey registered on your device, the name you give it (e.g. “office PC”), and when it was added, last used and removed | Confirm it is you before high-risk actions (e.g. deleting a game account) | While you are an operator. A removed passkey’s record is deleted 2 years after removal; when your operator registration is removed, all your passkeys are removed and their names are cleared at once |
| Audit log — sign-ins, sign-outs, failed sign-ins, and every operator action (who, when, what, on which record, result, IP address, browser type) | Keep an audit trail of operator actions and investigate misuse or incidents, as the law requires for access records | 2 years |
If an account that is not registered tries to sign in, it is refused right after Google sign-in. Only a failed-attempt record (email address, time, IP address, browser type) stays in the audit log, for 2 years.
3. How we use Google user data
- Only to authenticate operators and to keep the audit trail above.
- We do not sell it, use it for advertising, or use it to train AI models.
- We share it only with the service providers in section 4, which process it on our behalf, or when the law requires it.
- hetero8’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. Service providers and where data is stored
The console data above is processed on our behalf by these providers and stored outside Korea. It is sent over the network whenever the console is used, and kept for the periods in section 2.
| Provider | Role | Location |
|---|---|---|
| Vercel | Runs the console | Singapore |
| Neon | Console database | Singapore |
| Cloudflare (R2) | Encrypted backups and locked copies of the audit log | Cloudflare data centers |
| Slack | Internal alerts about operator actions (operator email, action, target) | United States |
Google provides the sign-in itself under Google’s privacy policy.
5. Deletion
When a period in section 2 ends, we delete the data so that it cannot be recovered. Encrypted backups expire on their own after 90 days.
6. Security
- Each operator uses their own Google account with 2-Step Verification. Accounts are never shared.
- The session cookie is Secure and HttpOnly, and the session ends after 30 minutes idle or 8 hours.
- High-risk actions need a fresh passkey check (fingerprint, face or device PIN). The check happens on your device: we never receive biometric data or your PIN, only the passkey’s public key and a signed challenge.
- The audit log can only be added to; no one can edit or delete an entry.
- The console sets only the cookies needed to sign you in and keep you signed in.
7. Your rights
Operators can ask at any time to see, correct or delete their data, or to stop its processing, by emailing contact@hetero8.com. The audit log and role history that the law requires us to keep are deleted when their period ends.
8. Changes
We post any change on this page with a new effective date.
9. Contact
hetero8 · contact@hetero8.com
Privacy officer: the representative of hetero8, at the same address.