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
Album access is strongest when it behaves like a reviewed handoff.
01
A Letter is designed to give 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
The safest album unlock starts before the request.
| Item | Public question | Consent receipt |
|---|---|---|
| Letter context | What should happen before a private album request enters the conversation? | A Letter request should establish member context, intent, and support history before album access is requested or reviewed. How Letters will work |
| Album request | How should a member ask for private media without making the album feel public? | The request should carry a note, privacy acknowledgement, partner acknowledgement when applicable, request status, and expiry expectations. What a private album is |
| Owner review | What should the album owner see before approving, denying, or ignoring the request? | The owner needs the requester profile context, Letter history, mutual-interest signal, request note, and clear approve or deny controls. How member controls will work |
| Unlock receipt | How should access be remembered after an album opens? | Approval, denial, revoke, expiry, and support states should create receipts without exposing album contents on public pages. Read member trust guide |
| Boundary change | What happens if a member changes their mind after a Letter, album unlock, event, or trip handoff? | 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 | How can support help without asking a member to repeat private details in public? | Support should see the relevant account, Letter, album request, and receipt state while album contents and sensitive member history remain member-only. Contact support |
| Card vs album split | Which photos belong on a profile card and which belong inside a gated private album? | Cropped, never-posted-elsewhere attire photos can introduce your presentation on the profile card while clear face portraits stay inside a revocable private album. Profile card vs private album |
| Album gate definition | How does a per-viewer private album gate differ from an all-members photo gallery? | A private album gate grants viewer-specific access only after mutual context and lets the owner withdraw that permission whenever comfort changes. Read private album gate term |
Media boundaries
A public trust page can be explicit about what never becomes public.
- Album contents
- Letter threads
- Request notes
- Owner decisions
- Unlock receipts
- Revoked access
- Expiry state
- Support history
- Trip intent
- Guest-list context
Verified access
The onboarding path that explains request review, profile readiness, verification receipts, member-only surfaces, and support handoffs.
Verified accessHow Letters will work
Letters are designed for consent-aware introductions, replies, reactions, album handoffs, blocks, reports, and support context.
How Letters will workHow media privacy will work
Planned member controls for profile readiness, media visibility, album settings, and privacy expectations.
How media privacy will workMember trust guide
The broader trust trail across onboarding, verification receipts, private albums, support paths, and member-only boundaries.
Member trust guideSafety guide
Public safety expectations for verification, consent, private albums, blocks, reports, and a private support record.
Safety guideSupport records
How blocks, reports, revokes, pauses, and support handoffs are designed to preserve context without exposing member-only details.
Support records
Private album FAQs
Useful answers for search. Member-only details stay sealed.
How are private album requests connected to Letters?
Letters are designed to 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. Adults who protect workplace, client, or neighborhood discretion often place fresh, cropped attire photos on their profile card — avoiding images reused from professional or social profiles — and keep clear face portraits inside a consent-gated private album unlocked per Letter conversation.
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 are designed to help support and moderation understand what happened without asking members to expose private media, private messages, or sensitive identity details again. Private albums hold member-chosen profile media, whereas identity checks run through Veriff's automated government-ID, biometric face-match, and liveness flow: from the current Veriff check, JoinTheSwing never receives or stores the raw ID, selfie, or biometric images — retaining the verification result, Veriff's session reference, a consent receipt, and non-biometric review metadata — while members from our earlier, retired in-house pass may still have ID, selfie, or couple photos in private verification_documents storage deleted when the account is deleted, as detailed at /legal/privacy.
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?
Join the waitlist; once registration opens, complete profile readiness and use Letters before any album request, event handoff, or travel context asks members to share sensitive information.
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.