The Swing is a private community for adults 18 and older. Confirm your age to come in.
By entering you agree to our Terms and Privacy Policy. Cookies are managed separately.
Opening JoinTheSwing…
Vouches and review context
Public ratings can create useful research, but they can also expose attendance, identity, local member activity, and private conflict. JoinTheSwing treats review context as a layered review model: Vouches for member trust, venue listings for fit, reviewed services for business partners, private support channels for boundary changes, and verified access before sensitive context appears.
Review principles
01
A useful signal says who can rely on it, what surface it affects, and where support can review the surrounding context.
02
Public pages can explain the model, city fit, House tone, Patron category, and safety posture without exposing member activity.
03
Blocks, reports, revokes, host concerns, travel issues, and message concerns belong in private support channels rather than public drama.
Review workflow
01 / Public review research
Public pages can explain whether a community has trust signals, review expectations, support paths, and partner context.
JTS explains the review model publicly, then keeps member names, guest-list privacy, event attendance, and exact feedback member-only.
Read safety guide ->02 / Vouches
Public testimonials and popularity marks can flatten trust into social proof without context.
Vouches should stay connected to verified members, moderation state, reports, and support history instead of acting like public ads.
Open Vouches ->03 / Venue context
Club and event reviews can reveal more about attendance, timing, and local member activity than guests expected.
Verified venue listings show fit, city, venue tone, and access model while member attendance and private event context stay behind verified access.
Browse verified venues ->04 / Patron review
Public service reviews can turn sensitive lifestyle services into a search-engine trail.
Patrons should be reviewed by category, benefit readiness, and support path while contact notes and member outcomes remain gated.
Browse Patrons ->05 / Support records
Public complaint threads can create permanent exposure without helping hosts or members resolve the actual issue.
A private support record preserves block, report, revoke, host, travel, and message context privately so support can act without public exposure.
Read the support guide ->06 / Verified access
Anonymous review browsing can invite scraping, drama, and context collapse.
Verified access should come before browsing sensitive Vouches, member context, guest lists, private media, Letters, and exact travel intent.
Request verified access ->Privacy checks
FAQ
A private community can explain how Vouches, venue listings, reviewed services, support history, and verified access work without publishing public scores, guest names, exact attendance, private messages, or sensitive member context.
Invitations, host review, Vouches, support history, and verified member context replace exposed public recap pages. The public guide can explain the trust model, while private guest lists and event chat details remain member-only.
Houses and Patrons separate public fit from private conversion. The public layer can explain category, city, access model, benefit readiness, and review expectations while member interest and contact context stay gated.
No. Vouches are member-to-member trust signals inside the platform. Public pages can explain the model, but the useful context belongs behind verified access with moderation, reporting, and a private support record.
Boundary-changing feedback belongs in private support records, blocks, reports, host review, and moderation workflows. It should not become public gossip, public identity exposure, or a permanent public profile mark.
Use the guide to understand the trust model, then move into verified access before browsing Vouches, reviewing Houses, contacting Patrons, RSVPing, writing Letters, or sharing event and travel context.
