Reporting a Copied Rushchat Character: Build a Small Evidence Packet

If you believe a Rushchat character copied your original work, collect a small set of relevant links before filing a report. Identify your creation, the disputed listing and the specific material you believe was copied. Do not repost the entire disputed character or publish a collection of personal accusations.

Rushchat’s FAQ says to open a chat with the character, use the report button and choose the corresponding option. It asks for a link to your own creation as proof, and links documenting image ownership where artwork is involved. Those are the published instructions, not a reporting flow we completed.

Identify what is actually disputed

A shared genre, common trait or familiar story premise is not the same observation as matching passages or an identical image. Write down the material at issue before choosing a complaint category.

For example, “both characters are adult archivists” is broad. “The listing repeats my three-paragraph greeting, including the invented museum name and the same unusual spelling error” is a more specific observation. Preserve the original wording privately instead of turning the report into a general similarity argument.

If the image belongs to another artist, do not claim ownership on their behalf unless you have authority to act. A character you assembled from third-party assets can involve several sets of rights, even when your own writing is original.

Make a four-part packet

A useful packet can fit on one page:

1. Your original: its stable URL, title and a date you can support.
2. The disputed version: its current URL and the date you saw it.
3. The matching material: a short, precise description or a limited comparison needed to explain the issue.
4. Your relationship to the work: creator, rights holder or authorised representative, stated accurately.

Keep additional proof available rather than uploading a large archive without being asked. Original project files, dated publication records or earlier version history may help explain the sequence, but private account credentials never belong in the packet.

A timestamp in your own note proves when you made the note, not automatically when the public copy first appeared. Keep that distinction honest.

Preserve evidence without spreading the problem

Capture only the page area necessary to show the listing and disputed content. Remove unrelated usernames, private messages and payment information. If you need the URL visible, include it in a separate text line rather than a screenshot of every open tab.

Do not create another public listing containing the material “for comparison.” That can redistribute the very work you want removed and make the ownership story harder to follow.

Likewise, avoid contacting other users with threats or legal conclusions you cannot support. A clear report gives the service a reviewable issue without turning a content dispute into harassment.

Use the current official reporting route

The FAQ’s in-character report instruction is the starting point. If the current interface differs, look for the service’s own help route instead of handing account access to someone offering to submit a report for you.

A compact explanation could say:

I created the original character at [original URL]. The listing at [disputed URL] appears to reproduce [specific greeting passage or image]. My original publication evidence is [link or date record]. Please review the matching material. I am [accurate relationship to the work].

This is an editorial report template, not a formal legal notice. If a platform requests a legal declaration, read what it asks you to certify rather than pasting a template into fields you do not understand.

Track the report, not just the listing

Save the report date, acknowledgement and any reference number. If you follow up, use that reference and explain what new information you have. Repeated identical reports do not necessarily make a review faster.

A later missing listing does not tell you why it disappeared. A still-visible listing does not prove nobody read the report. Report outcomes should be described using the service’s response and the public state you can actually observe.

For future original characters, keep a clean authoring copy and a minimal publication log. That ordinary record is more useful than trying to reconstruct a character’s history after a dispute has already started.