Skip to main content

Private albums and Letters consent guide

Private media should open only after consent has context.

A private album is not a public gallery. It is a consent path: Letter context, request note, owner review, unlock receipt, revoke expectation, and support handoff. This guide explains the public trust model while album contents and member context remain member-only.

Consent signals

01

A Letter gives the request context.

Album access should not appear as a detached button. The safest path starts with a considered Letter, visible intent, and enough context for the owner to decide.

02

An unlock is a consent event.

Private album access needs request notes, acknowledgement, approval or denial, expiry, revoke expectations, and support history.

03

Private media is never public proof.

Public guides can explain how albums work. Album contents, owner decisions, requester context, and support history stay inside verified member workflows.

Consent sequence

Letter context
Public question

What should happen before a private album request enters the conversation?

Consent receipt

A Letter request should establish member context, intent, and support history before album access is requested or reviewed.

Open Letters ->
Album request
Public question

How should a member ask for private media without making the album feel public?

Consent receipt

The request should carry a note, privacy acknowledgement, partner acknowledgement when applicable, request status, and expiry expectations.

Review album controls ->
Owner review
Public question

What should the album owner see before approving, denying, or ignoring the request?

Consent receipt

The owner needs the requester profile context, Letter history, mutual-interest signal, request note, and clear approve or deny controls.

Open member home ->
Unlock receipt
Public question

How should access be remembered after an album opens?

Consent receipt

Approval, denial, revoke, expiry, and support states should create receipts without exposing album contents on public pages.

Read member trust guide ->
Boundary change
Public question

What happens if a member changes their mind after a Letter, album unlock, event, or trip handoff?

Consent receipt

Block, report, revoke, pause, and support paths should stay close to the context so the member can change the boundary cleanly.

Read safety guide ->
Support handoff
Public question

How can support help without asking a member to repeat private details in public?

Consent receipt

Support should see the relevant account, Letter, album request, and receipt state while album contents and sensitive member history remain member-only.

Contact support ->

Media boundaries

A public trust page can be explicit about what never becomes public.

Album contentsLetter threadsRequest notesOwner decisionsUnlock receiptsRevoked accessExpiry stateSupport historyTrip intentGuest-list context

Private album FAQs

Useful answers for search. Member-only details stay sealed.

How are private album requests connected to Letters?

Letters create the consent-first context before a private album request. A request should carry member intent, acknowledgements, owner review, approval or denial, and a private support record instead of becoming open media browsing.

What should stay member-only during an album request?

Album contents, message threads, requester identity context, owner decisions, expiry state, support history, guest lists, exact trip intent, and information about who else is nearby should stay behind verified access.

Can a member revoke album access?

Private album access should include revoke expectations and receipt history. A member should be able to change the boundary without turning the prior unlock into public proof.

Why does a private album need a receipt trail?

Receipts help support and moderation understand what happened without asking members to expose private media, private messages, or sensitive identity details again.

How should someone compare private media controls across lifestyle platforms?

Look for verified access, consent-first private messaging, request notes, owner approval, expiry or revoke handling, block and report paths, and support handoffs that protect member-only context.

What is the safest next step after reading this guide?

Request verified access, complete profile readiness, and use Letters before any album request, event handoff, or travel context asks members to share sensitive information.