DMCA notice and counter-notice procedure

Last updated: August 18, 2026.

Rule34.dev respects copyright and responds to complete, good-faith notices concerning material accessible through the service. We index content from third-party services, and some technical delivery layers may proxy or temporarily cache resources.

Copyright contact

Send notices and counter-notices to [email protected]. Use the subject line DMCA Notice or DMCA Counter-Notice.

Required notice information

  1. A physical or electronic signature of the authorized person.
  2. Identification of each copyrighted work claimed to be infringed.
  3. The exact Rule34.dev URL for each item, plus enough information to identify the material.
  4. Your name, organization, mailing address, phone number, and email.
  5. A statement that you have a good-faith belief that the disputed use is not authorized by the owner, its agent, or the law.
  6. A statement, under penalty of perjury, that the notice is accurate and that you are authorized to act for the copyright owner.

What happens after a valid notice

We record the report, evaluate the identified URLs and identifiers, and disable access when appropriate. Suppression is applied across gallery pages, direct post routes, previews, internal search results, and public API responses. We retain an audit record and may notify the relevant source service or affected party when contact information is available.

Counter-notice

A counter-notice must include:

  1. Your physical or electronic signature.
  2. Identification of the removed material and its former URL.
  3. A statement under penalty of perjury that removal resulted from a mistake or misidentification.
  4. Your name, address, phone number, and email address.
  5. Consent to the jurisdiction of the appropriate United States federal district court and acceptance of service from the original claimant.

If a valid counter-notice is received, it may be forwarded to the claimant. Material may be restored after the statutory waiting period unless the claimant reports that court action has been filed.

Repeat infringement

Rule34.dev maintains a repeat-infringer policy. Repeated valid reports tied to the same source, provider, account, creator identifier, or delivery path may result in broader suppression or termination of access to the relevant service integration.

Knowingly making material misrepresentations may create liability. This page describes our operational process and is not legal advice.