Trust boundary
Meet-first reduces pressure.
It does not remove risk, but it gives both people more context before a private home enters the picture.
Public trust and safety page
How StayHello handles trust and safety.
This is the plain-English safety model: meet first, keep boundaries visible, treat payment pressure as a warning sign, let AI explain concerns, and keep humans in charge of serious decisions.
Meet firstHumans decideVerification is not a guarantee
What StayHello tries to prevent
Pressure before trust exists
The riskiest pattern is usually speed: anonymous overnight asks, secrecy pressure, money pressure, or moving the conversation off-platform before anyone has real context.
Proof boundary
No platform can promise safety
StayHello tries to reduce confusion and pressure. It does not claim perfect safety, perfect moderation, or a badge that replaces your own judgment.
What we do claim
Trust should get clearer
Members should see boundaries, contextual references, and message warnings earlier, before a situation becomes hard to read.
What we do not claim
Verification is identity confidence
Identity checks can help people feel more grounded, but they never equal safety or compatibility.
Who decides
Humans handle serious concerns
AI can explain risky patterns, but people should make user-impacting moderation decisions.
Verification boundary
Identity is not compatibility.
A real identity can still be a bad fit. Boundaries, pacing, and public first contact still matter.
Moderation boundary
AI assists. Humans decide.
Message warnings can help people slow down, but hidden automation should not quietly make serious judgment calls for them.
What this means in practice
Safer first connections should feel obvious inside the product.
Set your first-step preference
Members should be able to say whether coffee, a walk, dinner, or day-hosting feels right before home access is discussed.
Choose readable profiles
Discovery should make boundaries, identity context, and meet-first preferences easy to see before anyone sends a note.
Keep the first plan public
Messages should help people suggest a calm public-first plan on-platform instead of rushing into secrecy, pressure, or overnight asks.
Choose the right category
Some trust problems begin when the real need is booking, work exchange, house sitting, or home swap. Hospitality exchange works better when the category itself is honest.
1. Meet before you stay
The safest first step is usually smaller than an overnight stay.
StayHello is built around coffee, walks, dinners, language exchange, day-hosting, and public meetups before anyone shares a home. That gives both sides more context and reduces pressure to decide too fast.
2. Boundaries are normal
Clear expectations are part of trust, not a sign that someone is difficult.
Hosts and travelers should be able to say what feels safe: quiet hours, accessibility needs, whether meet-first is preferred, what kind of first contact feels comfortable, and what would make them say no.
3. Keep the first conversation on-platform
StayHello should hold the context while trust is still forming.
Moving too quickly to WhatsApp, phone, Telegram, or another private channel can remove useful safety context. StayHello encourages people to slow down before taking a brand-new interaction off-platform.
4. Hospitality is not a payment request
Core stays should not become hidden transactions.
StayHello does not charge per stay, and the product treats money requests, deposits, or payment-app pressure as warning signs because they do not fit the non-transactional hospitality model.
5. AI explains concerns; it does not make the decision
Safety tools should assist, not secretly control people.
StayHello's Safety Brain flags risky language patterns such as off-platform pressure, money requests, secrecy pressure, unsafe urgency, address pressure, and boundary pressure. The goal is to help people slow down and think, not to auto-ban or auto-hide people behind the scenes.
6. Verification confirms identity, not safety
A badge can improve confidence, but it is not a guarantee.
StayHello separates identity confidence from overall safety. Verification may help people feel more comfortable, but it does not remove the need for boundaries, good judgment, public first meetings, and contextual references.
7. Serious concerns go to humans
User-impacting moderation should not be an invisible robot decision.
StayHello can surface flagged messages to a read-only human review queue, but serious safety decisions should still involve people. The product is deliberately designed so AI assists and humans decide.
8. Portable reputation should stay user-controlled
People should be able to bring public trust context with them.
Trust Passport lets members add public profile links from other communities and describe what they actually did there. StayHello does not scrape gated profiles, copy private reviews, or imply endorsement from other platforms.
Frequently asked questions
Does StayHello guarantee safety?
No. No hospitality platform can honestly promise that. StayHello tries to improve safety through meet-first trust, clear boundaries, contextual references, visible messaging warnings, and human review for serious concerns.
What does StayHello's Safety Brain actually do?
It reviews message text for risky patterns such as money requests, secrecy pressure, off-platform pressure, unsafe urgency, address pressure, and boundary pressure. It explains what it saw so people can make better decisions.
Does StayHello automatically ban or hide people?
Not as part of the public safety model described here. StayHello is designed around assistive safety signals and human decision-making, not invisible auto-moderation.
Why does StayHello care so much about meeting first?
Because going from profile to overnight stay is often too large a leap for real trust. Public first contact makes the network more accessible to cautious hosts, cautious travelers, and people who want local connection before home access.
What if I already have reputation on another platform?
StayHello wants you to keep that context. Trust Passport lets you add public links and explain prior hospitality, volunteering, or community history without scraping or copying private reviews.
See the trust model in practice
Safety principles matter most when the product path feels real.
Start with Vancouver, create a free profile, and test the meet-first loop through one readable public-first intro. That is where the trust model becomes easier to judge honestly.
Step 1
Create free profile
Step 2
Start with Vancouver
Step 3
Make one calm first step
The first win is not an overnight yes. It is one readable profile, one calm public-first note or introduction in Vancouver, and enough context for both people to decide what feels right next.
Ready now
Start with Vancouver.
The clearest current StayHello test is one real city circle: create a free profile, understand the first trust loop, and judge the product through an actual public-first connection path instead of just a waitlist promise.
Category clarity matters too
Safety gets easier when people use the right model.
Some awkward first contact comes from using hospitality exchange for a job it should not do. If the real need is booking, labor exchange, house sitting, or home swap, that mismatch can create avoidable trust pressure before any message is sent.
Trust Passport and reputation
Trust should be portable, explainable, and user-controlled.
StayHello wants people to bring public trust context with them instead of rebuilding from zero every time they try a new community. That is why Trust Passport exists, and why StayHello avoids scraping private profiles or pretending other platforms have endorsed anything here.