All guidesSafety guide

What does Humanly Held ask and not ask before the pilot is live?

A join-path guide to what the public preview should ask, what it should never ask this early, and why the form stays interest-first.

Answer first

Before the pilot is live, Humanly Held should ask only the minimum needed to understand role interest and fit, and it should not ask for raw identity documents, medical or crisis details, sexual history, private-home session addresses, or anything that turns a cautious preview into premature real-data collection.

2026-06-15 · 4 min read

Audience: Cautious adults, companions, trusted-space partners, and reviewers who want the intake path to stay concrete and bounded.

This guide explains the current preview posture. It does not promise when real collection will open or claim that live forms already store or process customer data.

Use the careful join path

Good fit

  • People who want to know what the form is for before they touch it.
  • Companion candidates and space partners checking whether the preview respects data minimization.
  • Operators who need a public explanation for why the join path stays narrow.
  • Reviewers who want the intake posture written in plain language instead of implied.

Not a fit

  • Forms that try to collect every possible detail before the category, privacy, and provider rules are settled.
  • Any flow that requests raw ID uploads, background-check documents, or sensitive personal history through the public preview.
  • Requests that treat the join form like a booking confirmation or a shortcut around manual review.
  • Copy that hides the fact that the current path is still interest-only.

What information is enough for the preview?

The preview only needs enough information to understand broad interest, route the person into the right path, and prepare an approved next step later. In practice, that means the minimum to know whether someone is approaching as a cautious adult, companion candidate, or trusted-space partner.

If the category still needs explanation before the form feels safe, Humanly Held should send the person back to the trust pages instead of trying to collect more.

What should stay out of the public form?

The public form should not ask for raw identity documents, detailed health or crisis information, sexual-history details, private-home session addresses, or anything that would be hard to justify before privacy and provider gates are approved.

The rule is simple: if the company cannot explain the purpose, retention, access, and approval basis clearly, the field is too early.

Why keep the join path interest-first?

An interest-first path gives cautious people a chance to understand the category before they feel exposed. It also keeps Humanly Held from creating a pile of sensitive data before the business has finished legal, privacy, support, and provider readiness work.

That slower posture protects trust better than a more aggressive form that looks operational before the system really is.

What should change before real intake opens?

Before real intake opens, Humanly Held should have approved field purposes, just-in-time notices, retention rules, access controls, and a support path that can explain or correct what was submitted. Real collection should feel explainable before it feels scalable.

That is also when the public copy can stop calling the form demo-safe and start naming the approved live rules precisely.