Player control

Data deletion information.

For visitors to this website

The current static site has no account, gameplay upload, form submissions, analytics, or browser-storage code. Cloudflare Pages is the selected hosting plan. Provider connection and security records are separate from inquiry correspondence; see the website privacy notice for the provider information and privacy contact.

Prepared procedure for inquiry correspondence

This procedure will become available after support@hoonsu.gg delivery is verified.

1. Write to support@hoonsu.gg from the address used for your inquiry. Use the subject “Privacy request” and identify the approximate inquiry date and the action you want: access, correction, deletion, or stopping use.
2. The privacy contact, 홍준기, checks that the request concerns your correspondence. Only information needed to locate the inquiry and verify control of the address should be requested. Do not send passwords, payment details, identity documents, or gameplay files.
3. The operator handles the request in both the Dynadot mailbox and the forwarded Gmail copies, including related replies. The response explains what was done and any applicable legal exception or provider-controlled limitation.

Inquiry correspondence needed for related follow-up is deleted no later than 90 days after resolution, and sooner when it is no longer needed, unless a specific legal obligation requires retention. This is an operating maximum, not a statutory retention period. Deletion covers relevant messages, replies and trash-folder copies in both operator-managed mailboxes. This is a manual operating rule. Provider-controlled backups and security records are separate from mailbox deletion; immediate erasure of those systems is not promised. No unverified automatic deletion or guaranteed completion period is claimed.

For the planned HOONSU app

The app's private coaching data and optional contributions for model development are separate purposes. The public procedure must distinguish deleting local recordings, removing server-side coaching/profile data, withdrawing optional contribution consent, and closing an account.

How a request affects derived measurements, report/profile history, pending contributions, retained backups, audit records, and service-credit records must be stated before launch. Existing local development tools or prototype deletion rules do not establish an operational public deletion service.

Additional controls required before the application launches

1. A published, monitored contact or authenticated request method.
2. A way to verify the requester without asking for passwords, payment details, or API secrets.
3. A clear explanation of which data can be deleted, any justified exceptions, and expected response and completion periods.
4. Confirmation of completion or a clear explanation of remaining limitations.

The inquiry retention rule above does not establish retention periods for future application data. Please do not send recordings, player information, or credentials through this informational site.

See the privacy draft for pending processing details. Draft prepared 5 October 2026.