Suggest a topic, flag an error or ask a general question — plus our full privacy policy, written in the same plain language as the rest of the site.
Amon is a small, independent reference project. There's no customer service department, no live chat and no ticket system — just an inbox read by the people who write the guides. That means replies aren't instant, but it also means the person who reads your message is the person who can actually fix the page you're writing about.
The fastest way to get a useful response is to send the right message to the right address with enough detail for us to act on it. This page explains how, what we can and can't help with, and — further down — exactly what information this website collects when you visit it.
Corrections and broken steps
corrections@yourdomain.com
Topic suggestions and general questions
hello@yourdomain.com
Privacy requests
privacy@yourdomain.com
Reporting harmful content or a safety concern
safety@yourdomain.com — read first, every working day
Corrections are the messages we value most. PC gaming changes constantly — store policies are revised, engines move their save folders, launchers redesign their settings menus — and readers usually notice before we do.
A good correction includes:
Screenshots are welcome, but please crop out anything personal — usernames, friends lists, library contents, other windows. We don't need to see what's in your library to fix a settings menu description, and we'd rather not.
What happens next: we reproduce the issue ourselves where we can, check the source you gave us, and update the page. Substantive changes get a dated note on the page explaining what changed. We don't name the person who sent a correction unless they specifically ask to be credited.
What we can't do: verify claims we have no way to test. If a correction depends on hardware or a region we can't access, we may add a note saying the behaviour has been reported rather than rewriting the guide outright.
Most of our guides started as reader questions. The best suggestions describe a problem rather than a title: "I bought an adult game on an indie store and can't work out how to get updates without redownloading the whole thing" will produce a better guide than "write about indie stores".
Topics we're especially interested in hearing about include confusing storefront settings, engines or file formats we haven't covered, privacy problems on shared or family computers, Linux and handheld compatibility issues, and accessibility in adult games — text size, colour-blind options, controller support and readability.
Topics we won't cover, however often they're requested:
This isn't squeamishness; it's scope. These are either illegal, unsafe, against our editorial rules, or simply better served by other kinds of sites.
If you make, translate or sell adult games and something on Amon describes your engine, platform or patch process inaccurately, we especially want to hear from you. You know your own systems better than we ever will, and a short note pointing to your documentation is often all we need.
Developers sometimes ask whether we'll feature their game. We won't, and that's not personal: we don't review or promote individual titles, paid or unpaid. What we can do is make sure our general guides — how storefront content filters work, how players should verify official patches, where engines keep saves — are accurate, which helps every honest developer whose players read them.
Useful things developers can send:
Advertising and partnerships. Amon carries no advertising of any kind, and we don't sell placements, sponsored articles or "featured" slots, so there's no need to email about those. Messages offering paid links or guest posts are deleted unanswered.
We're happy to answer general questions about how things work — how a type of engine handles saves, what a storefront setting does, how to think about a particular privacy problem. When an answer is likely to help other readers too, we may turn it into a section of a guide, without identifying you.
What we can't offer is one-to-one tech support for a specific game. We don't have access to every title, and developers are far better placed to fix their own bugs. If your question is "game X crashes on startup", the developer's support page, community forum or store discussion board will get you a faster and better answer. Our troubleshooting checklist covers the steps they'll probably ask you to try first.
Things that help us answer quickly:
Things we'll never ask for: your store passwords, payment details, account recovery codes, or for you to install software so we can "look at your computer". If anyone claiming to be from Amon asks for these, it isn't us.
If you believe any page on this site links to, describes or could facilitate access to content involving minors, or content that is otherwise illegal, please email the safety address immediately. Include the page and section. Reports are read first and acted on as a priority; if a report is valid, the content is removed while we investigate.
If you've encountered child sexual abuse material anywhere online, do not download, screenshot or share it, even to report it. Report it directly to your national hotline or law enforcement. In many countries you can use the Internet Watch Foundation, the National Center for Missing & Exploited Children's CyberTipline, or a member hotline of the INHOPE network.
Malware reports. If you followed a description on this site and ended up with a suspicious file, tell us, even though we don't link to downloads. It may mean a once-trustworthy source has been compromised, or that our guidance on identifying official sources needs to be clearer.
Account compromise. If you suspect your store account was hijacked, contact the store's support team first and change your password from a clean device. Our toolkit page covers two-factor authentication and password managers.
Personal wellbeing. If gaming or spending is starting to feel out of your control, it's worth talking to someone you trust or a support service in your area. You don't need to have hit a crisis point to ask for help.
What this website collects, why, who else is involved, and what choices you have. Written in plain language; where it simplifies, it says so.
Amon is a static website. There are no user accounts, no login, no comment system, no newsletter sign-up and no contact form that stores submissions. We do not ask for or store your name, date of birth, payment details or game library.
Like almost every website, the server that delivers our pages keeps standard technical logs: IP address, the date and time of the request, the page requested, the browser's user-agent string and the referring page. These logs are used to keep the site running, diagnose errors and defend against abuse, and are retained only for a limited period before deletion.
If you email us, we receive whatever you choose to send — your email address, your message and any attachments. We use it only to reply and, for corrections, to improve the relevant page. We don't add you to any mailing list, sell or share your address, or publish your message with your name attached. Ask us to delete your correspondence and we will.
Amon does not run advertising, analytics or tracking scripts, and does not load content from third-party ad networks or social media widgets. The site sets no cookies of its own. Pages are plain HTML and a single stylesheet, so what you download when you visit is exactly what you read.
Links to other websites — such as storefront help pages or reporting hotlines — take you to sites with their own privacy practices, which we don't control. Check their policies before sharing information with them.
Amon is intended only for adults aged 18 and over. We do not knowingly collect any information from minors. If you believe a minor has contacted us, tell us and we will delete the correspondence.
Because the site stores no accounts or user content, there is very little personal data to protect on our side. Email is handled by a mainstream provider with standard security protections. No system is perfect, so please don't email us anything sensitive we don't need.
If we change how the site handles data — for example, if we ever added a feature that stored information — this section will be updated with a revised date. Significant changes will be noted at the top of this section.
Last reviewed: October 2026.
The Explore hub lists every topic we cover. A quick look there often answers the question faster than we can.
Crop screenshots, leave out account names and skip details of your library unless they're essential to the question.
We aim to reply to every relevant message within about a week, and to act on safety reports far faster. Corrections may be fixed before we reply.
English is the site's working language, but we're happy to receive messages in other languages and will translate them ourselves. A clear message in your own language is more useful than a confusing one in English.
If you have a correction, a topic idea and a privacy request, three short emails to the right addresses get handled faster than one long email covering everything, because each goes straight to the person responsible for it.
Start with the Explore hub for the full topic map, or read about how the site is written and the rules every page follows.