Skip to main content

Blocking, reporting & support

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 support history sits beside private messages, albums, hosted events, 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 already use.

Boundary signal
Public question

What should a public guide say when a member wants to pause, block, report, or change the tone of an interaction?

Support record

The public answer can explain the path while the actual account, profile, Letter, album, event, or travel context stays inside reviewed member workflows.

Read safety guide ->
Letter context
Public question

How should a message boundary be understood without turning a private conversation into public evidence?

Support record

Letters keep request state, replies, reactions, blocks, reports, and support history tied to a consent-first thread.

Open Letters ->
Album access change
Public question

What should happen when private album access is denied, expires, or needs to be revoked?

Support record

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
Public question

How should event or travel boundaries change after a host review, RSVP, room request, or weekend plan shifts?

Support record

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.

Browse Invitations ->
Verification review
Public question

When should a boundary issue affect access, profile readiness, or member trust?

Support record

Onboarding and verification receipts give reviewers a private decision trail before sensitive surfaces open or stay open.

Read member trust guide ->
Support and compliance
Public question

How can a member or reviewer understand the support path without publishing private details?

Support record

Contact, privacy policy, and compliance review pages provide the public handoff while the actual support record stays protected.

Contact support ->

Private context

Receipts help support. They are not public proof.

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 helps 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 stay behind verified member controls.

How do blocks and reports fit with Letters?

Letters keep the request, reply, reaction, block, report, and support context together. That makes a boundary change easier to understand without asking members to repeat sensitive details outside the platform.

How does the private support record help hosts and travel changes?

When an Invitation, Stay, venue listing, or trip plan changes, a private support record lets support and hosts understand 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 request verified access before browsing members, writing Letters, asking for albums, RSVPing, or sharing travel context.