Attorney review draft

TrustStay Legal Review Pack

A structured set of draft legal/business policy documents for attorney review before TrustStay enables real payments, public bookings, host payouts, and larger-scale launch activity.

Important draft notice

This page is not legal advice and should not be used as final public legal terms. It is a preparation pack so an attorney or legal service can review TrustStay’s business model, policies, risks, and missing decisions faster.

Current assumptions to confirm

TrustStay is a marketplace-style booking platform connecting guests and property owners/hosts.
TrustStay supports demo payment testing and Stripe Connect test-mode payment/payout flows; live production payment launch is still pending final business, legal, tax, and payment-provider setup.
TrustStay uses listing approval, turnover photos, guest arrival photos, safety/habitability review, support tickets, dispute review, account moderation, owner/guest history, admin logs, and email records.
Final operating entity, governing law, tax treatment, insurance, cancellation windows, and payment-provider obligations must be confirmed by counsel.
Drafts below are product/legal planning drafts only and are not final legal advice.

Attorney questions

What operating entity name should appear in the final documents?
Which state/country law and venue should govern the terms?
How should TrustStay describe its role: marketplace, booking platform, payment facilitator, limited agent, or another category?
What liability limits, disclaimers, indemnities, and insurance language are appropriate?
What refund/cancellation wording is safe without creating automatic refund obligations?
What consent language is needed for cleanliness photos, arrival photos, AI/photo review, support records, and admin review?
What privacy disclosures are needed for account details, DOB, address, phone, uploaded photos, support tickets, analytics, emails, and third-party providers?
What Stripe Connect, payout, chargeback, tax, 1099, or marketplace compliance language is required?
For each property location, who is responsible for sales tax, lodging tax, occupancy tax, permits, local rental rules, reporting, and remittance?
What owner verification and guest identity checks should be required before public launch?
What consent and disclosure language is needed for real ID verification, selfie/face-match checks, biometrics, and third-party identity providers?
What account suspension, ban, appeals, and evidence-retention process should be documented?
What review/testimonial rules apply to guest reviews, owner reviews, trust scores, founding-member rewards, and any incentivized feedback?
What SMS, email marketing, unsubscribe, and notification consent language is required before adding text-message support or marketing automation?
What anti-discrimination, accessibility, fair-housing, service-animal, and accommodation rules apply to listings and bookings?

Draft documents

Open each page and send the links, or print/save them for attorney review.

Suggested review workflow

  1. Send this page and the draft document links to an attorney or legal service.
  2. Ask them to confirm TrustStay’s marketplace/payment role, liability limits, privacy obligations, refund rules, and owner/guest obligations.
  3. Update the public `/terms`, `/privacy`, `/cancellation-policy`, and related policy pages only after counsel approves final wording.
  4. Keep demo payments on until production payment/legal setup is complete.