Reports are reviewed by topic.
Technical and editorial reports
Email hhuoo0800@gmail.com with the LevelLoop page URL, game title, expected result, actual result, and browser or device. Do not send passwords, payment details, or authentication codes.
Rights reports
A rights holder or authorized representative should identify the affected title or asset, provide the exact URL, explain the requested action, and include evidence of authority. A disputed listing may be disabled while a credible report is assessed.
Privacy requests
Use the same address with the subject line Privacy request. Describe the request and the country or region that applies. We may request enough information to locate a relevant record, but never an account password.
What LevelLoop can change
We can correct our own guide text and remove our links. A problem inside the separately operated game player may also require action by its external provider.
Reports are grouped by topic, and the topic decides what a useful message contains. A technical or editorial report needs the page address, the game title, what was expected, what actually happened, and the browser or device in use. Those five pieces are usually enough to reproduce the issue without a second exchange.
A rights report follows a different shape. The affected title or asset should be identified, the exact address given, the requested action stated, and evidence of authority included. A listing under a credible dispute may be taken down while the report is assessed, which is a review step rather than a conclusion about the claim.
A privacy request goes to the same address with the topic named in the subject line, along with a description of what is being asked and the country or region that applies. Enough detail to locate a relevant record may be requested. An account password is never one of them, and no message here should ever include a password, a payment detail, or an authentication code.
What can actually be changed is worth stating plainly. The guide text and the links on this site are ours to correct or remove. A fault inside the separately operated player, such as a control that misbehaves on one device or a session that will not start, may require action by the external provider that runs it, and a report of that kind is still worth sending because the listing itself can be reviewed.
If the correct category is unclear, send the message anyway with a plain description of what was noticed. A report that needs sorting is more useful than a problem that goes unmentioned, and the subject line can simply say what the message concerns.