Report Abuse

Last Updated: April 26, 2026

ShareText.io is a free text-sharing service. We do not tolerate abuse of the platform. If you have found content on ShareText.io that is malicious, illegal, or violates our policies, please report it using any of the methods below. We review every report and act quickly.

Automated Safeguards

Every share is automatically scanned at creation time and again daily for the first week. Our scanner checks all URLs in the share against:

URLhaus — abuse.ch's live feed of malware command-and-control and payload-distribution URLs.
Jarelllama's Scam-Blocklist — a curated list of ~470,000 known scam, phishing, and malicious domains, refreshed monthly.
Our internal blocklist — manually curated entries from past abuse reports.

Shares matching any of these lists are automatically quarantined and become inaccessible to the public. The owner can still see the share in their dashboard along with the quarantine reason and may appeal to abuse@sharetext.io.

How to Report

You have three ways to report abusive content:

In-page report button. Every shared page has a “Report” action. This is the fastest path — it delivers the report directly to our moderation queue.
Email: abuse@sharetext.io. Please include the full URL of the share (e.g. https://sharetext.io/abc123) and a short description of the issue.
Security researchers: see our security.txt for disclosure contact details.

What We Remove

We remove content that falls into any of the following categories:

Phishing pages, credential-harvesting links, or fake login portals
Malware, malicious scripts, or links distributing malicious payloads
Child sexual abuse material (CSAM) — reported to NCMEC immediately
Doxxing, non-consensual personal information, or stalking content
Non-consensual intimate imagery
Spam, scams, fraud schemes, or “pig-butchering” style content
Content that infringes copyright or trademark (see DMCA below)
Content that violates applicable law in the jurisdiction where we operate
Content promoting violence, terrorism, or organized harm

We do not moderate content proactively at scale, but reported shares are reviewed and, when in violation, removed.

Response Time

We aim to review and action abuse reports within 24 hours of receipt. Reports involving CSAM, imminent harm, or active phishing campaigns are prioritized and typically actioned within a few hours. Shares may be quarantined (made unavailable) before final review.

DMCA / Copyright Takedowns

If you believe content on ShareText.io infringes your copyright, please send a DMCA notice to abuse@sharetext.io. Your notice must include:

Identification of the copyrighted work claimed to have been infringed
The URL of the allegedly infringing content on ShareText.io
Your contact information (name, address, email, phone)
A statement, under penalty of perjury, that you have a good-faith belief the use is not authorized by the copyright owner, its agent, or the law
A statement that the information in your notice is accurate, and that you are the copyright owner or authorized to act on their behalf
Your physical or electronic signature

Law Enforcement Requests

Law enforcement agencies may send subpoenas, court orders, and preservation requests to abuse@sharetext.io. We respond to valid legal process as required by applicable law. Emergency requests involving imminent risk of death or serious physical injury should be clearly marked as such in the subject line.

For Anti-Virus & Reputation Vendors

If your product is flagging sharetext.io due to user-generated content on a specific share URL, please email abuse@sharetext.io with the URL(s) in question. We will remove confirmed malicious content within 24 hours and send confirmation back to your team so the domain-level reputation entry can be revisited. Flagging a specific share URL is fine; flagging the whole domain penalizes legitimate users.

Appeals

If your content was removed and you believe the removal was in error, reply to the removal notice or email abuse@sharetext.io with the context of your share and the reason you believe it was wrongly removed.