How can you tell if a comfort-session request is out of scope?
A practical screen for spotting requests that do not fit Humanly Held's adult-only, fully clothed, platonic, trusted-space model.
Answer first
A request is out of scope when it sounds sexual, romantic, clinical, crisis-driven, private-home based, coercive, intoxicated, or aimed at bypassing review, consent, or trusted-space rules.
2026-06-14 · 5 min read
Audience: Operators, companions, careful clients, and reviewers who need a visible line between acceptable requests and unsafe demand.
This guide explains the screen Humanly Held wants to apply. It does not claim that a live moderation team or live customer queue is already operating at scale.
Operators who need a repeatable first-screen test.
Companions who want the company to block unsafe demand before it reaches them.
Clients who prefer a category with visible stop conditions.
Reviewers who want the boundary written more clearly than a moderation policy alone.
Not a fit
Requests that ask for romance, sexual attention, secrecy, or bodywork.
Requests that need therapy, medical care, crisis response, or a regulated service.
Requests that try to switch locations, switch rules, or rush timing around the review path.
Requests that make ambiguity sound harmless.
What is the fastest first-screen test?
Start with category fit: adult-only, fully clothed, platonic, trusted-space based, and reviewable. If the request falls outside any one of those pillars, it is not a Humanly Held request.
A clear no early is usually safer than a vague maybe that shifts risk onto the companion or room.
What kinds of wording should trigger concern?
Sexual language, romantic framing, bodywork language, crisis urgency, intoxication pressure, location secrecy, or any attempt to bypass the platform should all trigger denial or clarification.
Requests that treat the room rules as flexible usually become harder, not easier, after they are approved.
How should ambiguity be handled?
Ambiguity should not be treated as harmless by default. The operator or companion should have room to ask for clarification, decline, or escalate.
The product gets safer when unclear requests slow down instead of sliding through on benefit of the doubt.
Why is this kind of page public?
Because the service should attract people who respect the boundary before they ever join. The wrong audience should feel the mismatch early.
That protects trust, protects companions, and helps outside systems classify the company correctly.