Last updated: August 14, 2026
Contact AMMB Arcade
Email the site operator at oopowill@gmail.com about a broken game, factual correction, privacy question, accessibility problem or content-rights concern.
Technical and editorial reports
Include the affected page URL, the device or browser involved when relevant, and a concise description of what happened or what should be corrected.
Rights notices
Identify the material and exact URL, explain your relationship to the rights holder, describe the requested action and provide information that supports the request. Do not send passwords, payment details or unnecessary identity documents.
What happens next
Messages are reviewed manually and we aim to reply within 3 business days. We may request limited additional information when it is needed to identify a page, reproduce a technical problem or evaluate a rights request.
The most useful messages name the page before they describe the problem. Every guide on AMMB Arcade has its own address, and a report that includes the full URL takes a minute to write and saves a round of guessing at this end. Pasting the link straight from the address bar is more reliable than typing the game's title, because several titles on the site are close enough in name to be confused for one another.
For a broken or unresponsive game, the browser and the device are the next pieces worth including: which browser you are using, whether you are on a phone, tablet or desktop, and whether the player shows anything at all before it stops. A short description of what you saw is enough. You do not need to send screenshots or technical logs, and you should not send passwords, payment details or identity documents under any circumstances.
Factual corrections are welcome and are the easiest kind of report to act on. Guides here are written from what a game actually shows, so if a control listed on a page does not match what the build does, or an objective is described in a way that would mislead a new player, quoting the sentence and saying what it should say is all that is needed. A specific correction is more useful than a general note that a page feels wrong.
Accessibility reports follow the same format. Name the page, then describe what made it hard to use: text that disappears at larger sizes, a control that cannot be reached without a mouse, a colour combination that is difficult to read, or anything else that got in the way. Reports like this are read as design feedback rather than as complaints, and they are often the most actionable messages that arrive.
Rights concerns have a page of their own. The content-rights section explains how the original guide text is separated from third-party games and artwork, and it lists the details a notice should contain: the exact URL, the material in question, your authority to act for the rights holder, the action you want taken, and any supporting information. Sending a notice there rather than through a general message keeps that correspondence in one thread.
Privacy questions are covered by the privacy page, which explains the consent choices shown on a first visit and links to the advertising controls Google provides. If your question is about information held by this site rather than about advertising, the same mailbox reaches the operator. Messages are read by a person rather than a queue, so a plain description of what you need is more useful than formal wording.