How to Report a Hostile Replika Reply Safely

1. Stop chatting and identify the existing reply

Expected result: you have identified the message you mean to report without continuing the exchange.

Read only enough to distinguish the unwanted reply from neighboring messages. Do not ask Replika to repeat the insult, explain its intentions or produce a worse example. You do not need to win an argument with the chatbot before using a reporting channel.

The hostile-message help article directs users to report the particular reply. Its explanation that replies are AI-generated does not require you to keep engaging with content you dislike.

2. Tap the message and look for Report a problem

Tap the unwanted Replika message and select Report a problem if offered. Expected result: a reporting interface for that message.

Check that you selected Replika's reply rather than your own text. The Contact Support instructions describe this message-level path; they do not establish an identical interface across mobile and web.

If tapping does not expose the named action, stop searching through unrelated settings. Do not substitute a rating, delete action or chat message and assume it performs the same function. Continue with step 5.

3. Add a short factual comment

Expected result: your comment identifies the unwanted behavior without retelling your private history.

Suggested wording: The selected reply contained an unwanted personal insult. I am reporting that response. This is an original example, not wording required by Replika. Adjust it to what actually happened; do not label a reply threatening if it was merely irrelevant.

For an irrelevant response, you could write: The selected reply did not address my question. Do not include another person's name, intimate details, passwords or payment information. The cited instructions do not specify what surrounding chat is transmitted automatically; do not assume a particular context window is included or excluded.

4. Select Send and record only what you observe

Select Send if available. Expected result to inspect: the interface's actual next state, not an assumed delivery confirmation.

Replika's support article names Send as the final action. It does not document a particular receipt screen, tracking record or review outcome. If the panel closes, record only that observation; closing alone does not establish who received or reviewed anything.

If an error appears or the outcome is unclear, note that uncertainty without repeatedly generating reports. You can explain the attempted action in a support request. There is no need to restart the conversation to see whether the chatbot has changed.

5. Use official support when the control is unavailable

Open Replika's official support form. Expected result: a request draft explaining the incident and the missing or unsuccessful reporting action.

Use the Submit a request form linked by Contact Support. Follow the current form's required fields; this guide does not classify fields or attachments as optional. Check the destination before entering account information.

Suggested subject: Hostile reply; message reporting unavailable. State the approximate time, your platform, what happened and which action was missing or failed. Distinguish facts from guesses. Supply the account email through the appropriate form field rather than repeating it in a screenshot.

Review the completed form and follow its submission controls. If a field requests information you are unwilling to disclose, pause and reassess rather than inventing an answer. Do not send the full conversation simply because an attachment control is visible.

Privacy, evidence and payment checks

Keep evidence proportionate, and handle billing questions separately from a content report.

The Replika privacy policy, last updated May 27, 2026, describes collection of messages and content and use of service providers, including customer support. Treat information you submit as provider-processed data, not a place to add unrelated sensitive material.

Prefer a concise description over an unnecessary image. If a screenshot is genuinely needed, share the smallest useful excerpt, remove identifying details and inspect the exported image before attaching it. Do not post private chat publicly to attract attention to a request.

Do not upgrade to troubleshoot reporting. If you are also considering leaving, inspect your actual subscription and renewal arrangements independently. A hostile-message report is not evidence that a charge, renewal or refund request has changed. No price or plan entitlement is asserted here.

Limits, stop conditions and practical conclusion

Finish with a minimal report or clearly recorded reporting obstacle, then step away from the conversation.

Stop if the exchange remains unwanted, the controls are unclear or gathering evidence would expose more private information than necessary. Reporting is not a promise that the next reply will improve or that a particular account action will follow.

Keep a short note of the route attempted and any response actually received. If you later need to clarify the issue, use that note instead of recreating the exchange. You can decide whether to return to the app separately; completing a report does not obligate you to keep chatting.

Frequently asked questions