How should users respond to attacks or persistent harassment in companion apps?
Persistent hostility in a companion app should be handled as an observable sequence, not as a debate you must win. The source may be another user, a public community, a shared character, or a generated feature with reporting controls. First identify the channel and stop the easiest path of contact. Then preserve a limited, private record before content disappears, submit a report tied to the specific object, and check whether the incident coincides with unexpected account access. Blocking and reporting can reduce contact and create a review path, but neither is a guarantee. A clear incident board helps you see what has changed and what remains unresolved.
Name the channel and stop live engagement
Record whether the conduct arrives through direct messages, comments, a group space, calls, profile mentions, shared content, email, or a generated reply. Do not continue a hostile exchange merely to collect more examples, and do not forward the messages to an audience. Mute notifications if you need time to organize the next step, then use the narrowest available restrict, leave, block, or visibility control. StopBullying.gov advises not responding or forwarding and recommends blocking and reporting. Product controls vary, so note exactly what a button says: muting may silence alerts, while blocking may affect one account but not every route or newly created account.
Capture a minimal evidence packet before content changes
Save the account name or identifier, profile link, exact content link where available, date and time, channel, and a screenshot that includes enough context to understand the sequence. Keep the files private and unedited; avoid building a public collage that redistributes the material. The Singapore Online Safety Commission lists usernames, profile identifiers, platform, description, screenshots or links, and timestamps as useful report information. If several accounts repeat the same conduct, record the pattern without guessing who controls them. Retain only what is needed for the platform or an appropriate authority, and follow the storage and deletion rules that apply to your situation.
Write a report that a reviewer can act on
Select the closest report category and attach the specific message, post, call, or profile rather than submitting only a general accusation. State what happened in chronological, neutral language: “Account A sent these five messages after being blocked at this time,” for example. Include the control already used and whether contact resumed through another feature. X's help page demonstrates that reports may begin from different content objects such as a post, profile, or direct message. Use the companion app's own current route, save the confirmation or ticket number, and avoid claiming an outcome or rule violation the platform has not yet determined.
Run account integrity checks on a separate track
Harassment does not automatically mean an account was compromised. Check for concrete indicators: unfamiliar sign-ins, changed recovery details, messages you did not send, new linked accounts, unexpected exports, or altered privacy settings. If one appears, change the password through the official app or site, make it unique, review active devices and recovery methods, and enable the service's available multi-step verification. Google's compromised-account guide emphasizes recent security events, devices, and settings. Do not follow links sent by the hostile account to “verify” yourself; navigate to the provider directly. Preserve relevant alerts before ending unfamiliar sessions.
Reduce cross-channel rediscovery
Review who can find you by phone number or email, message you, mention you, add you to groups, see activity status, or view linked social profiles. Remove public details that unnecessarily connect this account to work, home, routines, or other usernames. Tell group administrators which account and content require review instead of asking a crowd to confront the sender. If trusted help would make the process easier, share the report receipt and the specific task you want—such as checking a public profile after you block it—without circulating the hostile material broadly. A new display name may reduce discovery but does not erase prior exposure.
Escalate by evidence and immediacy, then follow up
If the platform decision is unclear, use its appeal or human-support route and reference the original ticket. Set a date to review whether the content, account, or contact route changed. When a message contains a specific, credible indication of immediate physical danger, contact the appropriate local emergency service or law-enforcement channel rather than waiting for an app reply; this article does not determine whether conduct meets a legal threshold. For other external options, consult the official service available in your jurisdiction. Keep outcomes on the incident board: report received, action explained, appeal available, account secured, and any remaining route. That prevents repeated exposure just to check for updates.
Common questions
Should I reply once to tell the person to stop?
If a boundary has already been clear or engagement is escalating, you do not need to continue. Use available controls and preserve the relevant sequence instead.
What evidence should I save?
Keep the minimum useful context: account identifier, content or profile link, time, channel, representative screenshots, and platform report confirmation.
Will blocking stop every form of contact?
No guarantee is possible. Blocking applies according to the product's design, so also review group, mention, discoverability, linked-account, and off-platform routes.