Metopedia can be contacted at: [email protected]

Requests are easier to review when they identify the exact page, file, revision, log entry, user account, source, or action at issue. Messages that provide clear evidence, links, and a specific requested action can be handled more accurately.

Contact address

Purpose	Address
General policy questions	[email protected]
Privacy requests	[email protected]
Copyright notices	[email protected]
Correction requests	[email protected]
Abuse and vandalism reports	[email protected]
Account and access issues	[email protected]
Technical reports	[email protected]

What to include

A useful request includes:

the relevant page title;
the exact URL, if available;
the file name, revision ID, diff, log entry, or username involved;
a concise description of the issue;
the requested action;
supporting sources or documentation;
archived links where available;
contact information for follow-up;
any deadline or legal urgency.

Do not include unnecessary private information. Do not send passwords, payment information, private keys, access tokens, government ID numbers, medical records, or unrelated personal documents.

Subject-line categories

Use a clear subject line when possible.

Subject line	Use
Privacy Request	Private information, account privacy, revision hiding, log concerns, or data-access questions.
Copyright Notice	Copyright infringement, licensing dispute, upload concern, or rights-holder complaint.
Correction Request	Alleged factual error, misleading wording, missing context, or source correction.
Abuse Report	Harassment, threats, vandalism, spam, impersonation, malicious uploads, or bot abuse.
Technical Issue	Broken page, rendering problem, upload failure, login issue, server error, or accessibility bug.
Policy Question	General policy, standards, governance, article requirements, or contributor rules.
Account Issue	Login difficulty, access restriction, block review, or account-related question.

Privacy requests

Privacy requests should identify the specific public content, revision, file, log entry, username, or account issue involved.

Useful privacy requests explain:

what information is private;
where it appears;
whether the information concerns the requester or another person;
the safety, legal, or privacy concern;
the requested action, such as removal from the current page, revision hiding, file deletion, log review, or account review.

Metopedia may remove, hide, suppress, or restrict material when it exposes private information, creates a credible safety risk, violates policy, or raises a legitimate legal concern. Some information may remain in backups, logs, archives, or page histories where removal is technically limited or where preservation is required for security, legal, or accountability reasons.

Copyright notices

Copyright notices should identify:

the allegedly infringing page or file;
the original copyrighted work;
the rights holder;
the location of the original work;
the specific material at issue;
the requested action;
contact information;
whether the requester is the rights holder or authorized representative.

Metopedia may remove, restrict, replace, summarize, attribute, or revise material when a copyright concern is credible. Counter-notices and disputes are handled under Metopedia:Copyrights.

Article corrections

Correction requests should identify the exact claim and explain the problem. A strong correction request includes:

the page title;
the disputed sentence or section;
the current citation;
the proposed correction;
a stronger source;
archive links where possible;
a short explanation of why the correction improves accuracy.

Metopedia favors corrections that improve source accuracy, preserve evidence, distinguish claim from interpretation, and make uncertainty clearer.

Abuse and vandalism reports

Reports of spam, vandalism, harassment, threats, impersonation, malicious uploads, bot abuse, doxxing, or disruption should include links and a short description of the conduct.

Useful reports include:

username or IP if visible;
page title;
diff or revision link;
date and time;
description of the behavior;
screenshots only when necessary;
safety concerns if present.

Urgent threats or immediate physical danger should be reported to appropriate emergency or law-enforcement channels. Metopedia contact is not an emergency service.

Account and access issues

Account requests may involve login problems, access restrictions, block review, user-rights questions, or account security concerns.

A useful account request includes:

username;
affected page or action;
error message if any;
date and time;
requested action;
evidence relevant to the review.

Do not send passwords. Metopedia will not ask for a password by email.

Technical issues

Technical reports may involve broken pages, rendering problems, upload failures, missing files, malformed templates, JavaScript errors, server errors, accessibility problems, mobile layout issues, search issues, or broken redirects.

A useful technical report includes:

page URL;
browser and device;
screenshot if relevant;
steps to reproduce;
error message;
whether the issue occurs while logged in, logged out, or both.

Accessibility issues

Accessibility reports should identify the page, device, browser, assistive technology if relevant, and the barrier encountered. Examples include missing alt text, poor heading structure, unreadable tables, color contrast problems, keyboard navigation issues, or mobile display problems.

Metopedia may update page structure, captions, tables, link text, templates, or media handling when an accessibility issue is confirmed.

Legal requests

Legal requests must identify the requester, authority, legal basis, affected page or file, requested action, and deadline. Requests involving court orders, subpoenas, law-enforcement demands, defamation claims, privacy laws, copyright, or other formal legal issues should include sufficient documentation for review.

Metopedia may require clarification, refuse overbroad requests, narrow the requested action, preserve records, or publish a transparency note when lawful and safe.

Response expectations

Metopedia reviews requests according to seriousness, clarity, risk, and available administrator time. Legal, privacy, security, and safety issues receive higher priority than ordinary editorial disagreements.

Requests may not receive a detailed response when they are abusive, duplicative, vague, spam, unrelated to Metopedia, or unsupported after prior review.

Evidence preservation

When reporting an issue, preserve relevant links, screenshots, source copies, page revisions, archive links, and timestamps. Do not alter evidence in a way that makes the issue harder to verify.

If a page contains private information or dangerous content, provide the minimum necessary evidence rather than spreading the material further.

Limits

Metopedia does not provide legal advice, medical advice, financial advice, emergency response, private investigation services, or guaranteed publication. Contacting Metopedia does not create an attorney-client relationship, professional relationship, or obligation to publish submitted material.

Metopedia may decline requests that would erase source integrity, conceal relevant public history, remove properly licensed material, suppress lawful criticism, expose private information, damage security, or exceed the project’s scope.

Metopedia:Contact