Blocking, reporting & support · Reviewed August 20, 2026
A boundary change should not erase the context.
Blocks, reports, revokes, pauses, RSVP changes, and support requests should keep the right private context close without turning member history into a public record. This guide explains how support history sits beside private messages, albums, trip planning, places to stay, venue listings, and verification review.
Boundary signals
Support should understand the moment without publishing the member.
01
A block should keep context close.
A member should not have to rebuild the full story when they pause contact, block a profile, report a concern, or change an album boundary.
02
A receipt is useful only when it is private.
Support needs enough verified context to act, but Letter threads, album contents, event attendance, guest lists, and trip intent should remain member-only.
03
The support path should explain itself early.
Public trust pages can describe what happens before sensitive action starts, so members know how boundaries will be handled before they need help.
Support sequence
Boundary changes should route to the same trusted surfaces members will use.
| Item | Public question | Support record |
|---|---|---|
| Boundary signal | What should a public guide say when a member wants to pause, block, report, or change the tone of an interaction? | The public answer can explain the path while the actual account, profile, Letter, album, event, or travel context is designed to stay inside reviewed member workflows. Read safety guide |
| Letter context | How should a message boundary be understood without turning a private conversation into public evidence? | Letters are designed to keep request state, replies, reactions, blocks, reports, and support history tied to a consent-first thread. How Letters will work |
| Album access change | What should happen when private album access is denied, expires, or needs to be revoked? | Album receipts should preserve request notes, approval or denial state, expiry, revoke timing, and support handoffs without exposing media contents. Read albums guide |
| Invitation or stay context | How should event or travel boundaries change after a host review, RSVP, room request, or weekend plan shifts? | Invitations, Travel planning, Itinerary, Stays, and Houses should carry enough verified context for support while exact dates, addresses, guest lists, and trip intent remain member-only. How Invitations will work |
| Verification review | When should a boundary issue affect access, profile readiness, or member trust? | Onboarding and verification receipts are designed to give reviewers a private decision trail before sensitive surfaces open or stay open. Read member trust guide |
| Support and compliance | How can a member or reviewer understand the support path without publishing private details? | Contact, privacy policy, and compliance review pages provide the public handoff while the actual support record is designed to stay protected. Contact support |
Private context
Receipts should help support. They are not public proof.
- Member identity
- Letter threads
- Album contents
- Album revokes
- Block state
- Report notes
- Guest lists
- Host decisions
- Trip intent
- Support history
Verified Access
How request access, onboarding review, profile readiness, verification receipts, and support handoffs are designed to prepare the private surfaces.
ReadSafety and Privacy
The broader public trust guide for verified access, Letters, private albums, blocks, reports, and member-only gates.
ReadMember Trust
How onboarding review, verification receipts, Letters, albums, and support handoffs are designed to become one trust path.
ReadPrivate Albums and Letters
How Letter context, request notes, owner review, unlock receipts, and revokes are designed to work around private media.
ReadContact Support
The public support doorway for account, privacy, compliance, and member-safety handoffs.
Contact
Support records FAQs
Public answers for private-support expectations.
What is a support record?
A support record is the private platform context around an important boundary action, such as a block, report, album revoke, Letter issue, event concern, travel handoff, or verification review. It is designed to help support understand what happened without publishing member-only details.
Which boundary changes should create a receipt?
Blocks, reports, private album requests or revokes, Letter concerns, RSVP changes, travel or stay issues, profile readiness reviews, and compliance handoffs should create enough private context for support to respond consistently.
Does the private record of a boundary action expose messages or media publicly?
No. The public guide explains the model. Message threads, album contents, exact event attendance, guest lists, trip intent, member identity, and support history should stay behind verified member controls.
How do blocks and reports fit with Letters?
Letters are designed to keep the request, reply, reaction, block, report, and support context together. That is designed to make a boundary change easier to understand without asking members to repeat sensitive details outside the platform.
How does the private support record help with Invitation and travel changes?
When an Invitation, Stay, venue listing, or trip plan changes, a private support record is designed to give support the reviewed context while exact dates, addresses, guest lists, and private member details remain member-only.
What is the safest next step after reading this guide?
Use the safety guide, member trust guide, and private albums guide to understand the public model. Then join the waitlist before browsing members, writing Letters, asking for albums, RSVPing, or sharing travel context.
Ready when registration opens
JoinTheSwing is opening soon in 2026, subject to our safety and compliance checks.
JoinTheSwing is opening soon in 2026; registration opens once our safety and compliance checks are complete. The prelaunch email list is free and does not create an account. At launch, identity verification is planned as an automated document and biometric face-match and liveness check through Veriff, a third-party identity provider. From the current Veriff check the images never reach JoinTheSwing; we keep the verification result, the provider session reference, a consent receipt and non-biometric review metadata. Veriff's privacy and retention terms apply; the biometric notice sits in the privacy policy.
Related answers
Opening soon in 2026
Get on the list.
We're opening in 2026 — join the list to hear first. Leave one email for approved registration information and occasional useful updates — no account, no card, no spam.
We do not sell your email. Service providers process it as described in our Privacy Policy. 18+ only.