Metopedia transparency report
This page records transparency-relevant administrative actions on Metopedia. It covers takedowns, legal requests, copyright notices, privacy removals, major redactions, page protections, deletion actions, account restrictions, and safety-related exceptions. Moderation rules appear in Metopedia:Moderation policy.
| Metopedia transparency report | |
|---|---|
| Type | Public accountability log |
| Applies to | Takedown requests, legal demands, copyright notices, content removals, revision suppression, major redactions, account restrictions, page protections, and policy actions |
| Core rule | Significant removals and restrictions must be publicly recorded when disclosure is lawful and safe. |
| Related pages | Metopedia:Moderation policy, Metopedia:Copyrights, Metopedia:Privacy policy, Metopedia:Contact |
Metopedia transparency report records significant administrative actions affecting public access to content or contributor participation. Its purpose is to prevent suppression, preserve accountability, and allow readers to distinguish ordinary maintenance from removals, legal action, privacy protection, copyright enforcement, security response, or moderation.
Transparency does not require exposing private information, security details, minor-user information, abuse-report details, or legally restricted material. It requires publishing the clearest safe explanation.
Reporting principles
| Principle | Meaning |
|---|---|
| Public record | Significant actions affecting public content or users receive a public entry when lawful and safe. |
| Minimum necessary redaction | Private or unsafe details are removed, but the action category and reason remain visible when possible. |
| Evidence preservation | Records, logs, requests, and related evidence are preserved internally or through safe public notes. |
| No takedowns | Content removal requires a reason in logs, page history, or transparency entry unless disclosure creates harm. |
| Source integrity | Removal does not erase the fact that a disputed or removed item existed when metadata can be safely preserved. |
Actions recorded here
This page records:
- legal takedown requests;
- DMCA or copyright notices;
- counter-notices and restoration outcomes;
- privacy requests;
- defamation or right-of-reply requests;
- government or law-enforcement requests;
- major content removals;
- deletion of evidence records;
- revision deletion or suppression;
- account blocks longer than routine anti-spam actions;
- page protections longer than short maintenance protection;
- administrator conflict-of-interest reviews;
- security-related removals when a safe summary is possible;
- major policy enforcement actions affecting public content.
Routine spam cleanup, empty test-page deletion, obvious vandalism rollback, duplicate redirects, and ordinary formatting corrections do not require full transparency entries unless part of a larger pattern.
Entry format
Use this format for each transparency entry:
== YYYY-MM-DD — Short action title ==
{| class="wikitable"
|-
! Field
! Entry
|-
| Action type
|
|-
| Affected page/file/account
|
|-
| Requester or source
|
|-
| Date received
|
|-
| Date actioned
|
|-
| Action taken
|
|-
| Policy basis
|
|-
| Public reason
|
|-
| Redactions
|
|-
| Review status
|
|}
Summary:
Outcome:
Action categories
| Category | Use |
|---|---|
| Copyright | DMCA-style notice, open-license dispute, unauthorized reproduction, file licensing issue. |
| Privacy | Personal information, doxxing, account data, private correspondence, minors, sensitive identifiers. |
| Legal | Court order, subpoena, legal threat, defamation demand, law-enforcement request, government notice. |
| Conduct | Harassment, threats, stalking, impersonation, edit warring, abuse. |
| Security | Malware, exploit, credential exposure, vulnerability, unsafe link, account compromise. |
| Source integrity | Fabricated source, forged document, false citation, altered file, chain-of-custody problem. |
| Editorial | Page outside scope, unsupported allegation, duplicate page, severe article-standard failure. |
| Administrative | Page protection, block, restriction, permission change, policy enforcement. |
Redaction rules
Transparency entries may redact:
- private email addresses;
- phone numbers;
- addresses;
- account tokens;
- passwords;
- private complainant information;
- names of uninvolved private persons;
- details that would assist harassment;
- details that would assist exploitation of a vulnerability;
- minors’ identifying information;
- legally restricted material.
Redaction labels must identify the type of redaction when possible:
[redacted private email address] [redacted security detail] [redacted minor-identifying information]
Copyright and DMCA-style entries
Copyright entries must record:
- claimant or representative when publishable;
- affected page or file;
- copyrighted work identified;
- allegedly infringing material;
- date received;
- action taken;
- whether a counter-notice was received;
- restoration status;
- redactions.
Do not publish private contact details from a copyright notice unless publication is required or already public. Summarize safely.
Privacy entries
Privacy entries must balance accountability and harm reduction.
A public privacy entry may state:
- that private information was removed;
- the affected page or revision range if safe;
- the general category of information;
- the action taken;
- whether revision suppression was used.
Do not reproduce the private information in the transparency entry.
Legal-request entries
Legal-request entries must record:
- requesting party or category;
- jurisdiction when publishable;
- page or content affected;
- legal basis asserted;
- date received;
- action taken;
- whether content was removed, restricted, preserved, or refused;
- redactions.
If publication is restricted by law or creates legal risk, record the safest lawful summary.
Security entries
Security entries must avoid creating additional risk. They may record:
- affected page or file category;
- type of issue;
- action taken;
- date resolved;
- whether credentials, malware, or unsafe links were involved;
- whether users need to take action.
Do not publish exploit steps, active credential material, private tokens, or dangerous payloads.
Moderation entries
Moderation entries are used for significant enforcement actions, not every ordinary warning.
Record:
- username or redacted account identifier if needed;
- policy violated;
- evidence category;
- action taken;
- duration;
- appeal status;
- administrator conflict-of-interest note when relevant.
Current transparency log
Entries are added in reverse chronological order. Routine spam deletion and minor maintenance actions may remain in ordinary MediaWiki logs instead of this report.
2026
| Date | Action type | Affected item | Public reason | Outcome |
|---|---|---|---|---|
| 2026-05-14 | Standards creation | Metopedia:Transparency report | Establishes public log format for removals, requests, and significant policy actions. | Active |
Review schedule
Transparency entries must be reviewed when:
- a removed page is restored;
- a legal request is withdrawn;
- a copyright counter-notice is resolved;
- an appeal changes the outcome;
- a redaction is no longer necessary;
- new evidence changes the public explanation;
- a prior entry contained an error.
Corrections must preserve the correction history rather than silently replacing the record.
Limits
This report does not publish private information, unsafe technical instructions, confidential abuse reports, or legally restricted material. It also does not guarantee publication of every ordinary moderation action.
A transparency entry means an action occurred. It does not automatically mean the underlying claim, complaint, or accusation was true.