Community Policy & Likeness Rights
Phoem is a sovereign event photography platform built on decentralized protocols (Nostr and Blossom). Our principles regarding personal privacy, likeness rights, and content removal are detailed below.
1. Decentralized & Sovereign Architecture
Phoem maintains no centralized database or proprietary media cloud. Photo metadata exists as cryptographically signed events on Nostr relays. Media files are hosted on content-addressable (SHA-256) open Blossom servers.
• Metadata: Cryptographically signed Nostr events (Kind 30004 & 1063)
• Media Blobs: Independent Blossom HTTP servers (BUD-01 / BUD-02)
• Client: photo.emre.xyz serves as an open-source viewer & edge aggregator
2. Personal Likeness & Privacy Rights
Every individual has an inalienable right over their own likeness and personal image (GDPR, KVKK, and universal rights of privacy). If you recognize yourself in an event photograph and wish to have it removed, your request is legitimate and honored as a top priority.
3. Photographer & Organizer Responsibilities
All community members who create albums and upload photos to Phoem pledge to respect attendee consent, never publish invasive or sensitive moments, and promptly honor legitimate takedown requests.
- Do not publish photos taken in private, resting, or sensitive event zones.
- Respect verbal or written non-consent requests during the event.
- Acknowledge deletion requests within 48 hours and delete the blob from Blossom.
4. How Technical Deletion Works
Unlike walled gardens, deletion across sovereign decentralized networks operates through coordinated protocol layers:
Blossom Server Deletion (BUD-01 / BUD-02): The uploader signs a Kind 24242 delete authorization via NIP-98 to permanently delete the image blob from their Blossom server.
Nostr Event Deletion (NIP-09): The photographer or album curator publishes a Kind 5 (deletion) event or updates the album event to retract the photo reference from relays.
5. Steps to Request Photo Removal
Step 1: Contact the Photo Uploader (Direct)
Every photograph cryptographically identifies its provider (pubkey / npub). Using our "Photo Removal Request" tool, you can reach the photographer directly via Nostr encrypted DM or open web clients (Primal, njump, Coracle).
Step 2: Reach Out to the Event Organizer
If the photographer does not respond, the event organizer who curates the album can update the event to remove the image from the public gallery.
Step 3: Blossom Host & Platform Moderation
If content remains disputed, you may file an abuse/takedown notice with the Blossom server host, or report it to Phoem maintainers for client-level filtering.
Did you spot yourself in a photo?
Use the SHA-256 hash code and the uploader’s Nostr identity to generate a direct removal request.