Join pilot
All guidesCompanions guide

How should companions define allowed touch types?

A consent-first guide to how Humanly Held companions should define what is allowed, what is not allowed, and what stays companion-specific.

Answer first

Humanly Held companions should define allowed touch types in plain language before availability is shown, so the session stays fully clothed, platonic, consent-specific, and easy to review rather than negotiated under pressure.

2026-06-14 · 5 min read

Audience: Companion candidates, cautious adults, operators, and reviewers who want the touch standard to be specific before any session exists.

This guide explains the intended consent structure. It does not claim that live companion menus, approvals, or session offerings are already active on the public site.

Review companion standards

Good fit

  • Companion candidates who want a written standard instead of vague culture language.
  • Clients who feel safer when touch is defined before a request is considered.
  • Operators who need a reviewable consent menu instead of assumptions.
  • Reviewers who want to see that the product protects specificity, not just good intentions.

Not a fit

  • Any system where the meaning of touch is figured out informally once the session starts.
  • Any expectation that clients can purchase access to undefined or expanding touch.
  • Menus that blur platonic contact with bodywork, romance, or sexual intent.
  • Pressure on companions to copy someone else's boundary profile.

What should an allowed-touch definition actually do?

It should make the boundary legible before the room, before the review, and before any emotional pressure appears. The goal is clarity, not complexity.

A strong definition helps everyone understand where the session stays comfortably inside scope.

Why should the menu stay companion-specific?

Because companions are not interchangeable, and boundaries should not be standardized in a way that erases personal agency. Humanly Held should protect a companion's right to define a smaller scope than the platform might technically allow.

That is part of worker protection and part of trust.

What makes a touch menu safer?

The menu should use plain language, stay fully clothed and platonic, pair with pause and stop language, and leave no confusion about what is not offered.

If a menu needs euphemisms to sound appealing, it is probably drifting toward the wrong category.

Why publish this before live sessions?

Because public clarity is part of demand shaping. The right clients should understand early that consent in Humanly Held is specific, reversible, and companion-led within review constraints.

That helps the company attract the people who respect the rules and repel the people who do not.

Related trust pages

Keep reading the operating standard.

Companion Academy

Open

Pause and stop language guide

Open

Companion boundaries guide

Open