What to do about impersonator accounts

A situation worth working through

A supporter sends a creator a screenshot of another account using the same profile image and asking for gifts. The creator wants to warn everyone immediately. A useful response preserves evidence, directs people to a verified route, and reports the impersonation without encouraging a crowd to contact or harass the suspected account.

Save the identifiers

Record the profile URL, handle, date, and examples of the impersonation. A screenshot is useful context, but the account address helps distinguish a copy from your real page. Avoid publishing private details of anyone who contacted the account.

Use the platform’s reporting route

Report the account where it appears and explain which identity or work it is copying. Keep your report factual. Do not organize a pile-on or accuse an unrelated person based only on a similar display name.

Tell your audience where your real links live. A concise notice can identify the fake handle and direct people to the official profile without repeating a scammer’s payment instructions.

Make your own identity consistent

Use a recognizable photo, name, and destination across the profiles you control. Link to your Rory page from those established accounts. Consistency helps visitors check context, although a logo or familiar name alone is never proof that a message is genuine.

Record the exact account

Save the profile URL, handle, relevant messages, and dates. Similar display names can make screenshots ambiguous, so capture the address where possible. Do not engage in a prolonged argument with the account or send money to test it. Keep private information out of anything you publish, even when it appears in the suspicious message.

Use the platform’s reporting process

Report the impersonation through the service where it appears and provide the evidence requested through that official workflow. Requirements vary, so check the current instructions. If a payment request is involved, the payment provider may have a separate reporting route. Keep a record of submissions without assuming that a report guarantees immediate removal.

Publish a calm verification notice

Direct readers to the page linked from your established channels. Describe the misleading behavior you observed without repeating unnecessary personal details. Ask people not to send money or share credentials with accounts they cannot verify. A short notice with a stable official route is more useful than reposting every suspicious message and giving it a larger audience.

Words you can adapt

The example below illustrates the approach; it is not a customer message or testimonial. Change the details to match the actual situation. Keep the meaning accurate rather than copying a promise that does not fit your work.

Publicly mobilizing followers can create harm even when the concern is real. A mistaken handle or recycled screenshot can direct attention at the wrong person. Keep the warning factual, avoid personal contact information, and let the relevant platform assess the report. Your audience mainly needs a safe way to find the genuine page.

Try the approach on a real example

Use a past message with its personal details removed, or a fictional practice message. Do not contact a suspicious sender, open an attachment, send a payment, or submit a live report merely to complete an exercise. The purpose of this review is to decide what information you would need before acting and where you would obtain it independently.

On a blank page, write the exact action the message is requesting. Keep this separate from its story about why the action is urgent. A request to share a code, send a payment, or follow a new link should be visible as an action, not hidden inside a sympathetic explanation. If you cannot describe the request clearly, pause rather than guessing.

Next, divide your notes into what you observed and what someone claimed. Record the account address, relevant date, and wording you can actually see. Put assumptions about identity, authority, and intent in the second column. A familiar name or a convincing explanation may be worth checking, but neither should move into the verified column without additional evidence.

Write down the independent route you would use next. It should begin with a service, website, or contact you already trust, not a new destination supplied by the questionable message. Describe the question you would ask through that route. Keep it specific enough that the recipient can answer without needing the whole history of your creator business.

Finally, identify what information should remain private. Remove authentication details, unrelated messages, and unnecessary personal data from any proposed report or public warning. Preserve the original evidence securely if it may be needed. A useful report gives the right recipient enough context while avoiding a second problem caused by exposing information to everyone else.

What to check afterward

Check whether established profiles point to the same current destination and whether supporters can distinguish your actual handle from a display name. Update the warning if the situation changes. Preserve the original evidence privately rather than leaving sensitive screenshots circulating indefinitely.

Write down the outcome in plain language, including anything that remains uncertain. A useful review can end with a smaller change, a decision to wait, or a question that needs a better source. It does not have to end with a new post, a new tool, or a payment. Keep the lesson specific enough that you can use it the next time a similar situation occurs.