D&D Portal Rules Wiki
Identify the content Include the exact page, image, passage, or file.
Explain the reason Describe the rights, privacy, safety, or accuracy concern.
Provide evidence Include relevant ownership, source, or permission information.

Purpose of this page

This page explains how to report material published through the D&D Portal Wiki that you believe should be corrected, restricted, or removed.

A request may concern copyright, attribution, privacy, confidential information, security, unlawful material, or another legitimate concern.

Every request is reviewed according to its specific circumstances. Submitting a request does not guarantee removal, and the absence of an immediate response does not mean that the concern has been ignored.

Last updated: .

Website operator

Website
D&D Portal Wiki
Operator
Toon van Berkel
Country
The Netherlands

When to submit a removal request

A content-removal request may be appropriate when you reasonably believe that material on the Wiki:

Copyright

Uses protected work without permission

For example, text, artwork, photography, maps, software, or other original material that you own or represent.

Attribution

Names the wrong author or source

This includes missing credit, inaccurate authorship, or an incorrect licence statement.

Privacy

Contains personal information

This may include unnecessary names, contact information, photographs, account information, or other personal data.

Confidentiality

Discloses private or restricted material

For example, private campaign information, confidential messages, credentials, or restricted documents.

Safety

Creates a credible security or safety risk

This includes exposed credentials, malicious files, dangerous redirects, or information that creates a serious personal risk.

Legality

Contains material that may be unlawful

Identify the relevant content and explain the legal basis for your concern as precisely as reasonably possible.

Correction instead of removal

Complete removal is not always the most appropriate solution.

Depending on the problem, a request may be resolved by:

  • Correcting the author or source.
  • Adding a missing licence notice.
  • Removing a specific sentence, image, or attachment.
  • Replacing protected wording with an original summary.
  • Removing unnecessary personal information.
  • Changing a full name into a pseudonym or general description.
  • Restricting access while the matter is investigated.
  • Adding context or correcting inaccurate information.
  • Replacing an image with a properly licensed alternative.

You may state your preferred solution in the request. The final action may differ when another solution addresses the concern more appropriately.

Information required

Be specific enough to locate and assess the material

A general statement that the website contains unwanted content may not provide enough information to investigate the request.

A useful request should include:

  1. Your name and contact information. Use a name through which the request can be discussed and an email address at which you can receive a response.
  2. The affected page URL. Include a direct link to every relevant Wiki page.
  3. The exact affected material. Identify the image, paragraph, heading, file, source entry, or other item involved.
  4. The reason for the request. Explain whether the concern relates to copyright, privacy, attribution, confidentiality, safety, or another issue.
  5. Your relationship to the material. State whether you are the author, rights holder, depicted person, authorised representative, contributor, or another affected party.
  6. The requested action. State whether you are requesting correction, attribution, restriction, replacement, anonymisation, or removal.
  7. Supporting information. Provide relevant source links, publication details, licence information, or evidence of authority where reasonably necessary.
  8. A good-faith confirmation. Confirm that the information in the request is accurate to the best of your knowledge.

Submit a request

Send removal requests directly by email. Legal, privacy, or security requests should not be submitted through a public GitHub issue.

Start a content-removal request Open a pre-filled email containing the required information

Requests can also be sent manually to toonvanberkel.public@gmail.com with the subject D&D Portal content removal request.

Do not include unnecessary sensitive information

Provide only the information reasonably necessary to assess the request.

Do not send:

  • Passwords.
  • Authentication tokens.
  • Private keys.
  • Complete identity documents.
  • Payment information.
  • Medical information unrelated to the request.
  • Personal data belonging to unrelated people.
  • Confidential documents when a limited excerpt is sufficient.

Additional verification may be requested only where reasonably necessary to establish identity, authority, ownership, or another relevant fact.

Copyright requests

A copyright request should identify the original protected work and the material on D&D Portal that is claimed to infringe it.

Include where available:

  • The title or description of the original work.
  • The original author or rights holder.
  • The date and location of original publication.
  • A link or reference demonstrating the original work.
  • The exact D&D Portal page or image involved.
  • An explanation of the allegedly unauthorised use.
  • Your authority to act for the rights holder, where applicable.

Public availability does not by itself establish that material is in the public domain or may be freely republished.

A request should also take account of any applicable permission, licence, fan-content policy, public-domain status, or lawful exception.

Privacy and personal-data requests

You may request the correction or deletion of personal data concerning you where applicable.

A privacy request should identify:

  • The personal data involved.
  • The page or file where it appears.
  • Your relationship to the personal data.
  • Why correction or deletion is requested.
  • Any relevant reason that makes the request urgent.

Privacy rights are subject to legal conditions and exceptions. Information may sometimes need to be retained for legal claims, security, documentation, freedom of expression, or another lawful reason.

Urgent security or safety reports

Mark a request as urgent when the published material exposes:

  • A working password or authentication token.
  • A private encryption or signing key.
  • A serious exploitable security vulnerability.
  • A private home address connected to a credible threat.
  • Information creating an immediate personal safety risk.
  • Malware or a dangerous download.

Use the email subject: URGENT — D&D Portal security or safety report.

Do not publish sensitive details in a public issue, pull request, commit, or discussion.

Review process

1

Receipt

The request is received and checked for enough information to begin an assessment.

2

Initial assessment

The location, nature, urgency, and apparent basis of the request are reviewed.

3

Temporary action where appropriate

Content may be temporarily hidden, restricted, or replaced while a serious concern is investigated.

4

Further information

The requester, contributor, author, or another relevant party may be asked for clarification.

5

Decision

The content may be retained, corrected, attributed, restricted, replaced, or removed.

6

Notification

Where appropriate and possible, the requester is informed of the outcome.

Temporary restriction

Material may be temporarily hidden or disabled before a final decision when:

  • The request concerns exposed credentials.
  • Continued publication creates a credible immediate risk.
  • The available information indicates a likely serious infringement.
  • Additional time is needed to verify ownership or permission.
  • A service provider requires temporary restriction.

Temporary restriction does not by itself confirm that the content was unlawful or that the requester’s claim was correct.

Possible outcomes

Retained

The content remains available because the request does not establish a sufficient reason for action.

Corrected

Inaccurate wording, attribution, source information, or personal data is corrected.

Restricted

Access is limited temporarily or permanently while preserving necessary records.

Replaced

The affected material is replaced with an original, licensed, or otherwise suitable alternative.

Anonymised

Identifying information is removed or changed while the remaining content is retained.

Removed

The material is removed from the current public version of the Wiki.

Requests affecting contributor material

When a request concerns material submitted by a contributor, the contributor may be informed and given a reasonable opportunity to explain:

  • How the material was created.
  • Which licence or permission applies.
  • Why the attribution is accurate.
  • Whether the material can be replaced or corrected.
  • Why publication should continue.

Information that would unnecessarily expose the requester’s personal data should not be shared.

Contributor rights and responsibilities are described further in the Contribution Terms.

Requesting reconsideration

A requester or affected contributor may ask for reconsideration when they believe that:

  • Relevant evidence was misunderstood.
  • Important information was unavailable during the first review.
  • The wrong content or page was assessed.
  • A licence or permission was incorrectly interpreted.
  • The selected action is unnecessarily broad.

A reconsideration request should identify the previous request and clearly explain what new or corrected information should be reviewed.

Repeated requests containing no meaningful new information may not receive a further detailed assessment.

Repository history, caches, and copies

Removing content from the current website does not guarantee immediate removal from every technical location.

Copies may temporarily remain in:

  • Browser caches.
  • Search-engine caches.
  • Content-delivery networks.
  • Backups.
  • Git commit history.
  • Repository forks.
  • Independent archives.
  • Copies previously downloaded by third parties.

Reasonable steps may be taken to remove or restrict copies controlled by D&D Portal. Independent third-party copies remain under the control of their respective operators or users.

External websites

D&D Portal may link to third-party websites but does not control their content.

A request concerning material hosted entirely on another website should normally be directed to that website’s operator or hosting provider.

Where appropriate, D&D Portal may remove or update its link to external material without being able to remove the external material itself.

False, abusive, or misleading requests

Removal requests must be made honestly and in good faith.

Do not submit requests intended to:

  • Misrepresent ownership.
  • Impersonate a rights holder.
  • Silence lawful criticism or disagreement.
  • Harass a contributor or website operator.
  • Obtain private information about another person.
  • Disrupt the website through repeated unsupported reports.
  • Remove content merely because it is disliked.

Knowingly false or abusive reports may be rejected, documented, or referred to an appropriate service provider or authority where necessary.

Response times

D&D Portal is independently maintained and does not operate a dedicated legal or moderation department.

Requests will be assessed within a reasonable period based on their complexity, urgency, available information, and the need to consult relevant parties.

Urgent security and personal-safety reports receive priority where their urgency can reasonably be established.

No specific response or resolution time is guaranteed unless applicable law requires otherwise.

Preservation of records

Information connected to a request may be retained where reasonably necessary to:

  • Investigate and respond to the request.
  • Document the action taken.
  • Prevent repeated publication of disputed material.
  • Respond to legal claims.
  • Protect the rights of the requester, contributor, or project.
  • Comply with legal obligations.
  • Investigate fraud, abuse, or security incidents.

Request information is handled according to the Privacy Notice.

No admission

Correcting, restricting, or removing material does not automatically mean that:

  • The original publication was unlawful.
  • Liability is accepted.
  • The requester owns every right claimed.
  • The contributor acted intentionally.
  • Every allegation in the request was accepted.

Content may be changed voluntarily to resolve uncertainty, reduce risk, respect a reasonable request, or improve the Wiki.

Changes to this procedure

This content-removal procedure may be updated when the website, contribution process, hosting arrangements, or applicable requirements change.

Material changes may be recorded on the Changelog.

Contact

Content-removal requests toonvanberkel.public@gmail.com
Website operator Toon van Berkel

For general public development suggestions that do not involve private, legal, or security information, you may use the project repository.

Related information

These pages document our table rulings and campaign setting. When in doubt, ask the DM.