Carbon Hosting DMCA policy

Document date: 2026-10-15

Version date: 2026-10-15

About this policy

This policy explains how copyright takedown requests are handled for content hosted on customer servers on the Carbon Hosting platform: the files, worlds, plugins, and other content that customers store and serve through their rented servers.

This policy is part of the Carbon Hosting legal documents, together with the Terms of Service and the Acceptable Use Policy.

What conduct may be reported

This policy covers direct copyright infringement claims about material hosted on customer servers. Examples: uploading or making available files, addons, or other content that a copyright owner has not authorized, or distributing infringing material through a hosted server.

How to send a notice

A copyright takedown notice should include all of the elements listed below. These elements describe what federal copyright law requires at 17 U.S.C. section 512(c)(3):

The electronic or physical signature of the copyright owner, or of a person authorized to act on the owner's behalf.
Identification of the copyrighted work claimed to have been infringed, or, if several works are covered by one notice, a representative list of those works.
Identification of the material that is claimed to be infringing, with information reasonably sufficient for the operator to locate it: for example the server, the file or path, or any other locating detail that helps.
The complaining party's contact information: name, mailing address, telephone number, and email address if available.
A statement that the complaining party has a good-faith belief that the use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law.
A statement that the information in the notice is accurate and, under penalty of perjury, that the complaining party is authorized to act on behalf of the owner of the exclusive right that is allegedly infringed.

Where to send a notice

What happens after a notice arrives

The operator reviews each notice against the elements listed above.

A complete, valid notice leads to removing or disabling access to the identified material. That can include suspending the affected server where that is needed to stop the claimed infringement. The affected client is informed of the action and the reason by email or through the client area.

An incomplete or invalid notice is not acted on as a takedown, and the sender is told what is missing.

The operator acts promptly on the notices it receives. No response deadline and no number of days is promised anywhere in this policy.

Repeat or clear infringement is handled under the Acceptable Use Policy enforcement ladder and the Terms of Service, up to suspension or termination of the server or the account, as described in the next section.

Repeat infringement

The operator's policy provides for termination, in appropriate circumstances, of the accounts and servers of repeat infringers.

Where valid notices show that a server or an account is repeatedly or clearly infringing, the operator may suspend and then terminate the server or the account under the Acceptable Use Policy enforcement ladder and the Terms of Service.

No numeric threshold is set in this policy: the operator looks at what valid notices actually show, including how often the infringement happens and how clear it is.

Counter-notices

If material was removed by mistake or misidentification, the affected client may send a counter-notice. A counter-notice should include all of the elements listed below. These elements describe what federal copyright law provides at 17 U.S.C. section 512(g):

The client's physical or electronic signature.
Identification of the material that was removed, and the location where it appeared before removal.
A statement under penalty of perjury that the client has a good-faith belief that the material was removed as a result of mistake or misidentification.
The client's name, address, and telephone number.
Consent to the jurisdiction of a federal district court for the judicial district in which the client's address is located, or, if the client's address is outside the United States, for any judicial district in which the operator can be found, and agreement that the client will accept service of process from the person who gave the original notice.

Where a valid counter-notice is received, the law (17 U.S.C. section 512(g)(2)) sets the timing for restoring the material, which is 10 to 14 business days after receiving the counter-notice, unless the complaining party files a court action seeking to restrain that activity first.

Notices made in bad faith

Knowingly making a materially false notice or counter-notice carries legal liability for damages under 17 U.S.C. section 512(f).

The operator handles every notice in good faith, acts on what a notice actually shows, and rejects notices that fail the requirements above.