The Two Buttons Are Not Both There: What You Can Actually Do About a Profile That Unsettles You
You're in Discover and a profile stops you for the wrong reason. Maybe the photos don't quite agree with each other. Maybe the bio reads like it was written at you, not to anyone. Maybe you recognize the face and wish you didn't. You haven't liked them, you certainly haven't matched — and now you want them handled. So you open the full profile and reach for the two tools every safety guide, including ours, teaches by name: block and report. Here is the thing this site has never told you plainly. On a profile you haven't matched with, only one of those buttons exists. This article is about the controls that are actually on that screen, what each one truly does, and the three-part rule that should replace the two-button reflex.
What Is Actually on the Screen
Open any profile from Discover — or from your Likes list, or with no context at all — and the action row at the bottom holds three round buttons: Skip, Super Like, and Like. Below them sits exactly one labelled text button: Report. That's the complete inventory. We didn't skim a screenshot to say that — we executed the app's own profile renderer this morning, four different ways a non-match profile can be opened, against both the code in our repository and the exact script your browser downloads from production. Every render agreed: no Block control appears anywhere on a non-match profile, and Report appears once. The Block button is real — it lives on the profile sheet of someone you've matched with, and in the header of a conversation. We'll come back to what that means. First, the two controls you do have, because they do very different jobs and neither one is decoration.
Report Is for the Record
Tap Report and you'll pick a reason — spam, harassment, fake profile, inappropriate content, underage, or other — add details if you have them, and submit. Here is what happens next, stated exactly: a report record is created for review, and nothing on your screen changes. The profile does not disappear. Your feed does not change. The person is not notified, and nothing about your visibility to each other moves in either direction. Our block-and-report guide said this correctly and it bears repeating, because it's natural to assume reporting does something visible: reporting is you handing the platform evidence, not you pressing an eject button. That's not a weakness. For the profile that unsettles you — especially “fake profile” and “underage,” the two reasons that protect people other than you — the record is the entire point. A report can act on an account. Your other button only ever acts on your own feed.
One mechanical detail worth knowing so the interface doesn't surprise you: you can report the same person once per day. A second report inside twenty-four hours is turned away as a duplicate. If you have new information the day after, you can file again.
Skip Is for Your Feed — and Skip Is Forever
The control that actually removes this person from your world is the one the interface calls Skip — the X. (In the app's internal language, and in our Undo article, the same action is called a pass; one word, one action.) Skip does exactly one thing, and it does it permanently: the person is excluded from your Discover feed, and you from the moment you tap it will not be shown that profile again. The product's own description of the action is one sentence long: they won't appear in discovery feed again. No “for a while.” No cooling-off period after which the algorithm gives them another chance.
We verified the permanence this morning, from both ends. In the application code, the exclusion that filters your feed reads your full history of likes and skips with no time window and no expiry. And on the production server, we enumerated every scheduled job on the machine — the nightly maintenance run, every cron entry, every system timer — and confirmed that nothing anywhere deletes or expires a skip. The maintenance script that runs each night cleans up expired tokens and reconciles subscriptions; it does not touch swipe history. A Skip is the closest thing to “never show me this person again” that exists on this platform, which makes it — not Block — the tool this article's situation actually calls for.
The Honest Scope of a Skip
Skip governs your Discover feed, and that is the claim we can prove. It is a one-way, one-surface control: it decides what you are shown while you browse. Keep the scope in mind rather than rounding it up to “they're gone from the app” — the removal you control is the removal of them from in front of you.
The Five-Minute Exception
Permanence needs its fine print in the same breath: there is exactly one way to take back a Skip, and it is narrow on purpose. Undo reverses only your single most recent swipe, only within five minutes, and only on Premium. All three limits at once — a free account has no undo at all, minute six is too late, and if you skipped someone else afterward, the earlier Skip is already out of reach even inside the window. The Undo article walks through the mechanics. For this article's purposes the practical reading is: treat Skip as permanent when you tap it, because for the profile that unsettled you, permanent is exactly what you wanted.
Block Is a Match-Only Tool
So where is the missing button? Block appears in two places, both of them past the match line: on the profile sheet of someone you've matched with, and in the header of an open conversation. The Blocked Users list in Settings manages people you've already blocked — there is no way to add a name to it directly. In other words, Block is built for someone who got close and needs to be removed from that closeness — what it does there, and when to pair it with a report, is its own guide. For a stranger in Discover, the block workflow simply is not the path the interface offers you — and if you've internalized “block and move on” as the universal answer, that's the reflex to retire. The pre-match answer is the pair you actually hold: Report for the record, Skip for your feed.
The Order Matters: Report First, Then Skip
Do it in that sequence, from the open profile: report while the profile is in front of you, then Skip on your way out. Skip removes them from your Discover feed — which means if you skip first and then wish you'd reported, there is no straightforward way to pull the profile back up to do it. Report is the step you can't easily return to. Spend it first; the Skip isn't going anywhere.
The Three-Part Rule
Report is for the record
It creates evidence for review and changes nothing you can see. Use it whenever the profile is the problem — fake, underage, harassing, scam-shaped — because it's the only control that can ever act on the account rather than on your feed.
Skip is for your feed
It permanently ends this profile appearing in your Discover browsing. Nothing in the code or on the server ever recycles it. The only reversal is Undo: most recent swipe, five minutes, Premium — all three.
Block is a match-only tool
It exists on match profiles and in conversations, for people who got past the first gate. Reach for it there. Pre-match, its job is already covered by the other two.
One last reframe, because the missing button can feel like a missing protection. In the situation this article opened with, you were never in contact with this person — no match, no conversation, no channel. What you needed was for the record to exist and for the profile to stop appearing in front of you, and both of those needs have a button. The unsettling profile got reported and then it got skipped, and skipped is forever. If someone ever does reach the point of contact and behaves badly there, that is a different situation with different tools — our unwanted-messages guide covers it, block included. For the stranger in the feed: the two buttons were never both there. The two that are, do the whole job.
Know Every Tool Before You Need One
The full map of Intently's safety controls — what each does, where each lives, and which situation calls for which — is in the block-and-report guide.
Block, Report, or Both