The Pride Path

Hide, Block, and Report: What Each Control Does

Scope

Hide, block, and report are different controls. This guide focuses on the documented functions and reporting flow, not on whether a report will be acted on or what result it may produce. Recheck the current options in the app before relying on a particular step.

A Quick Decision Guide

Use the control that matches the situation you are trying to manage:

These labels describe different functions. They are not a prediction about what will happen after you use them.

Report Workflow

The following steps reflect the documented reporting flow and may be rechecked in-app.

To begin a report, open the relevant profile, use the block icon in the top-left corner, and choose **Report** from the pop-up menu. [S8-C2] The flow then asks you to choose the category that best fits the situation. [S8-C3]

Take a moment before selecting a category. The purpose here is not to stretch a situation into a label that does not fit, but to use the available categories as they are presented in the flow.

Listed Report Categories

The documented categories are:

Keep the list narrow. These are the categories stated in the packet, not an expanded guide to every type of concern someone might encounter.

Information and Options in the Report Flow

After a category is selected, the flow includes a **Tell Us What Happened** page where you can provide details for the report. [S8-C4] Write only what you are prepared to include and review the information before continuing.

The flow also asks where the offense occurred. Its listed selectable locations are **Profile Photo**, **Profile Information**, **Chat Message**, and **Album content**. [S8-C5] Select the location or locations that apply to the concern you are reporting.

Depending on the selection, the flow may ask whether to include your last 30 chats with the reported person. [S8-C6] That option is conditional, so it should not be described as something that appears in every report.

Before submitting, the listed flow gives you an opportunity to review the report. [S8-C7] Use that point to check the category, the details you entered, and any selected locations or optional information. Submission is a separate action from blocking; a report by itself does not block the profile. [S8-C1]

What Blocking Does

Blocking is a product control with a stated effect on visibility and inbox conversations. When you block another profile, the source says that person will no longer see you in the app, and chats with that person are removed from your inbox. [S8-C8]

This is a function description, not a safety guarantee. It is also distinct from reporting: choosing to report a profile does not automatically perform the block action. [S8-C1]

There is a stated limitation to consider before you look for the block option. The source says blocking is limited to profiles that have sent you a message. [S8-C9] That limitation matters because it determines when the documented blocking route applies.

Hide as an Alternative

If a profile has not messaged you, the source points to hiding the profile instead of blocking it. [S8-C9] In practical terms, the documented decision is not “hide versus block” as interchangeable labels: the stated message-history condition determines which option is described for that situation. [S8-C9]

The documented guidance treats hiding and blocking as separate controls in this situation. [S8-C9]

Unblocking Route

A previously blocked user can be unblocked through **Profile → Settings → Security & Privacy → Unblock Users**, then by selecting the user and confirming the choice. [S8-C10]

Before confirming, pause and make sure you are selecting the intended profile. This is simply a review step for your own account choices; the documented route is about reversing a prior block.

Closing

The practical distinction is straightforward: report uses the reporting flow, block has its stated visibility and inbox effects, and hide is the documented alternative when a profile has not messaged you. [S8-C1][S8-C8][S8-C9] Review the relevant in-app options before making a choice, especially when the documented flow depends on the profile’s message history.

Compare documented app controls

INTERNAL claim-usage list