Photos and Privacy

Photo flows touch identity, consent, and moderation, so this page is intentionally detailed.

Personal Photo Centre (`/me/photos`)

Your personal photo workspace has two tabs:

Saved: private bookmarks.
Tagged: photos where you are tagged, including approval/rejection.

Tagged Photo Workflows

In Tagged, you can:

Approve pending tags,
Reject pending tags,
Remove tags from already-approved photos,
Use bulk actions when processing high volume.

Profile Photo and Visibility Controls

Profile-facing photo controls now live in /settings/profile.

Those controls include:

Profile visibility scope,
Profile photo visibility scope,
Tagged-photo gallery visibility on your profile,
Avatar behaviour and source preferences.
Advanced per-community tagged-photo contribution choices when you have tagged photos from multiple communities.

The tagged-photo profile setting controls only the gallery shown on your profile page. It does not stop people from tagging you, and it does not hide your name from photo detail surfaces.

Connections and shared-hub relationships affect who can view what.

Hub and Event Photo Surfaces

Hub photo surfaces support album and timeline views.

Visibility is enforced at multiple layers:

Album defaults,
Per-photo moderation/override controls,
Viewer relationship and membership gates.

Some access failures intentionally return Not found to protect private resource existence.

Guest-surface rules also matter:

Public hubs can show PUBLIC albums to both logged-out visitors and logged-in non-members.
Logged-in non-members should still be treated as non-members, not as fully joined viewers: they can browse public albums, but member-only albums stay hidden.
Direct links to non-public albums do not open a richer preview; they show an unavailable/restricted state instead.
Public event pages open shared album cards directly into the chosen album.
Private hub overview pages do not advertise album listings to logged-out visitors, even when a specific public album URL still works.
Private hubs do not expose general photo listings to non-members from the hub photos index or timeline.

Reporting and Moderation

If a photo is unsafe or incorrect:

Use report actions from the photo surface.
Include reason and context.
Hub admins handle local moderation.
Escalate to platform level for severe or repeated abuse.

Practical Privacy Defaults

Start conservative, then widen visibility intentionally.
Review tagged photos before profile promotion.
Keep moderation notes clear for future audits.
Escalate incidents with URL + UTC time + role context.