Account, sync, and technical help
For sign-in, Battle.net linking, character sync, broken routes, missing icons, or planner behavior, email player support. Include the page URL, what you expected, what happened, your browser and device, and the approximate time of the problem. A screenshot is useful when it does not expose private account data.
For a character or realm issue, include the region, realm slug, and character name exactly as they appear in World of Warcraft. Do not email access tokens, passwords, authenticator prompts, recovery codes, or raw account cookies.
Guide and database corrections
A strong correction names the exact route and claim, the current game build or season, the activity and difficulty, and a source or in-game reproduction. For a spell or item, include its numeric ID when available. For an encounter, include the boss, difficulty, role, and mechanic name.
WoW-God distinguishes factual corrections from different strategic preferences. When several approaches are valid, the guide should explain their conditions instead of replacing one unexplained recommendation with another.
Privacy and account-data requests
Use the privacy address for access, correction, export, deletion, consent, or advertising-data questions. Identify the WoW-God account email or public profile involved, but do not send identity documents unless the privacy team specifically requests an appropriate verification method.
Account deletion may require identity verification to prevent someone else from deleting your data. Public forum content and derived operational records may be retained where legally permitted, described in the privacy policy, or necessary to protect the service.
Partnerships, advertising, press, and legal
Use the business address for advertising proposals, data partnerships, press questions, vendor matters, and commercial integrations. WoW-God does not sell favorable guide conclusions or undisclosed placement inside editorial recommendations.
Formal legal notices should be sent to the legal address with the affected URL, the basis of the request, the requesting party, and a reliable reply address.