Reporting Content

Where to send a report

Email is monitored and is by far the fastest route. Please do not use the contact form on the homepage for urgent takedown requests.

What to include

Every report, whatever the category, should contain:

1. The full URL of the content. For Mastodon that is the permalink to the post; for Matrix, the room ID or alias plus a link to the event; for Nostr, the event ID (note1… or hex).
2. A short description of what is wrong with it and, where relevant, which law or policy it breaks.
3. Your name and an email address that can be replied to.
4. Any deadline you are working to, if one applies.

A screenshot helps, but it is not a substitute for the URL. Content on a federated network moves between servers, and the URL is what identifies which copy is actually hosted here.

Copyright: DMCA notices

ComputingCache responds to notices of claimed copyright infringement under the United States Digital Millennium Copyright Act, 17 U.S.C. § 512. Valid notices result in the material being removed or access to it disabled, and the account holder being notified.

Designated agent

This designation is on file with the United States Copyright Office as registration DMCA-1078102, effective 12 August 2026, and can be verified in the public DMCA Designated Agent Directory.

Required elements of a notice

To be effective under § 512(c)(3), your notice must be in writing and must include substantially all of the following:

1. A physical or electronic signature of the copyright owner, or of a person authorised to act on their behalf.
2. Identification of the copyrighted work claimed to have been infringed, or a representative list if there are several on one site.
3. Identification of the material claimed to be infringing, with enough detail to locate it. A specific URL is required.
4. Your address, telephone number and email address.
5. A statement that you have a good faith belief that the disputed use is not authorised by the copyright owner, its agent, or the law.
6. A statement that the information in the notice is accurate, and under penalty of perjury, that you are the copyright owner or authorised to act on their behalf.

Incomplete notices may be returned with a note about what is missing rather than acted on. Please be aware that under § 512(f) a person who knowingly and materially misrepresents that material is infringing may be liable for damages, including costs and legal fees.

Counter-notification

If your material was removed and you believe that was a mistake or a misidentification, you may send a counter-notice under § 512(g)(3). It must include:

1. Your physical or electronic signature.
2. Identification of the material removed and the location where it appeared before removal.
3. A statement under penalty of perjury that you have a good faith belief the material was removed as a result of mistake or misidentification.
4. Your name, address and telephone number.
5. A statement consenting to the jurisdiction of the Federal District Court for the judicial district in which your address is located (or, if outside the United States, any judicial district in which ComputingCache may be found), and that you will accept service of process from the person who submitted the original notice.

A valid counter-notice is forwarded to the original complainant. If they do not notify us within 10 business days that they have filed a court action seeking to restrain the activity, the material may be restored.

Repeat infringers

Accounts that are the subject of repeated valid infringement notices are terminated. In practice this means a warning on the first notice, a suspension on the second, and termination on the third, applied with judgement rather than as a mechanical count, and faster where the conduct is clearly deliberate.

Illegal content and urgent reports

Child sexual abuse material. Report it immediately to admin@computingcache.com with URGENT CSAM in the subject. It is removed on sight, the account is terminated, and the matter is reported to the NCMEC CyberTipline. You may also report it directly to NCMEC yourself. Do not include the material itself in your email; a URL is enough.

Credible threats of violence or self-harm. Contact emergency services first if someone is in immediate danger, then email us so the content and account can be dealt with and evidence preserved.

Non-consensual intimate imagery, doxxing, targeted harassment. Removed on report. You do not need to be the subject of the content to report it, though it helps if you are able to confirm that you are.

Spam, phishing, malware and network abuse. Send the URL and, for network abuse, log excerpts showing the source and timestamps in UTC.

Content from other servers

Matrix, Mastodon and Nostr are federated. A good deal of what you can see through a ComputingCache service is not hosted here: it originates on someone else's server and is cached or relayed by ours.

What can be done depends on where the content actually lives:

• Content authored on ComputingCache can be removed at source, and the deletion is propagated outward to remote servers.
• Cached remote content can be purged from this server, and the originating server or entire domain can be blocked so it stops arriving. The original copy remains wherever it is hosted, and the operator of that server has to be contacted separately.
• Nostr events can be deleted from this relay. Nostr events are cryptographically signed and copied widely; other relays holding the same event are outside our control.

In every case, tell us anyway. Blocking an abusive remote server is often the most effective thing that can be done from this end.

Law enforcement

Requests for user data must come through valid legal process issued by a competent United States authority: a subpoena, court order or warrant as appropriate to what is being sought. Send it to admin@computingcache.com, and include a point of contact for verification.

Formal, signed preservation requests are honoured for 90 days pending legal process. Retention is short by default, as described in the privacy policy, so there is often less data available than you might expect. Where the law permits it and an investigation would not be prejudiced, affected users are notified before any disclosure.

What happens after you report

1. You get an acknowledgement, normally within 2 business days.
2. The content is reviewed against the terms of service and applicable law.
3. Action is taken: removal, account suspension, remote server block, or no action with a reason given.
4. You are told the outcome. Where an account holder is affected, they are told what was removed and why, and how to dispute it.

Reports made in bad faith, in bulk, or as a way of harassing a user are not acted on, and persistent abuse of this process will be ignored.

Security vulnerabilities

Security issues are not abuse reports. See security.txt for how to disclose one. Good-faith research is welcome and will not be answered with legal threats.