Preserve context. Verify independently.
- 01
Evidence
Record the account and relevant messages safely.
What this tells youA useful record identifies the account and the relevant request.
Keep only what is needed for the report in a place you control. Do not circulate private conversations or remove your only copy before reviewing the reporting options.
- 02
Report control
Open the conversation’s official reporting controls.
What this tells youYou are reporting the actual account or conversation, not a lookalike screenshot.
Open the official app independently. A link sent by the suspicious account is not a trusted route to a reporting form.
- 03
Category
Choose the impersonation category and follow the current prompts.
What this tells youYour selected reason matches what happened.
Follow the current prompts and review the information being submitted. Keep any acknowledgement as a record; it does not promise a particular decision.
Verification, reporting and blocking have different jobs.
| Action | Useful outcome | Not a promise of |
|---|---|---|
| Verify identity | Check the claim through a contact route you already trust. | Proof from a familiar name, monogram or photo alone. |
| Record context | Retain the account details and relevant request safely. | Permission to distribute someone’s unrelated private messages. |
| Report | Ask the platform to review the account or conduct. | Immediate removal or a specific enforcement outcome. |
| Block or restrict | Choose an appropriate contact boundary in your account. | A completed report or removal of copies already saved. |
A familiar identity needs an independent check.
A familiar photo asking for emergency money should be verified through an existing trusted contact method.
Unverified request
An account using familiar initials asks for urgent help. The display name is a claim, not verification.
Separate confirmation
Use a contact method you already know. If the identity claim is false, preserve relevant context and report the actual account.
After the report, finish your own checks.
Keep the relevant record
Retain any acknowledgement and useful context without sharing the conversation publicly. Review the boundary you need next.
Compare contact controls →The request is still waiting
Do not accept a suspicious request just to verify its sender. Read the available report or block controls.
Review message requests →You already shared a credential
Treat that as an owner-account security issue. Open official recovery independently and review your own access.
Review account recovery →Do not let urgency choose the route.
A money request can be checked through an existing trusted contact method. Avoid using the new number, link or payment instruction supplied by the questionable account as the only verification.
Keep this boundary.
Reporting is not a guarantee of a particular enforcement outcome.
A report acknowledgement records a submission, not an outcome. Manage further contact as a separate decision.
References and current instructions
Go to the source.
Labels, menu placement and feature availability can change. These are original interface illustrations; use the current official explanation before changing a setting.
Official reporting guidance for an account pretending to be someone else.