Blur faces in church and nonprofit livestream replays

Why replays create a privacy duty the livestream doesn't

A live stream is ephemeral: someone watching sees the congregation the way an attendee would. A published replay is a permanent, indexed record. Faith communities also carry a special sensitivity — attendance itself can reveal religious affiliation, recovery-group participation, or family circumstances a member never intended to publish. In the EU and UK, religious belief is special-category data under GDPR, which makes identifiable congregation footage genuinely higher-risk than ordinary event video.

Most churches handle this today with a sign at the door and a prayer that nobody complains. The complaints do come — usually from a parent whose child appeared in a wide shot, or a member whose ex-partner found them through a replay. Blurring the congregation while keeping the platform, worship team, and stage untouched resolves the tension: the message stays shareable, the members stay private.

The ten-minute post-stream workflow

BGBlur processes the exported recording, not the live feed, so nothing about your streaming setup changes. Export the replay from OBS, vMix, Restream, or your hardware recorder as an MP4, upload it, and let automatic face detection find every person in frame. Masks track through camera pans and zooms, so the wide shots your volunteers love stay usable.

If your pastor and worship team should stay visible, selective blur lets you exempt specific people while everyone else in frame is anonymized — the same workflow corporate teams use for role-based redaction.

• Works on exports from OBS, vMix, ATEM/hardware recorders, and phone recordings of smaller gatherings.
• Blur all faces, or all faces except your platform team, in one pass.
• Stage lighting, stained glass, and projection screens stay sharp — only people masks are applied.

Kids' ministry and youth events need a stricter default

Children's segments are where photo policies have real teeth. Parents sign (or refuse) media releases at registration, and a volunteer camera operator has no way of knowing which child in the third row opted out. The safe default is to blur every child's face in youth segments before a replay is posted, and to keep the unblurred original in your private archive for families who want it.

The same rule protects baptism, dedication, and confirmation footage — the moments families most want shared are also the moments involving minors on stage. Blur the congregation and the other children; keep the family that asked for the video in focus.

Handling opt-outs without banning cameras

A workable policy has three parts. First, notice: keep the door sign and a line in the bulletin so streaming is never a surprise. Second, a stricter replay standard: publish replays with congregation faces blurred by default, which converts most opt-out requests into non-events. Third, a removal path: when someone asks to be removed from an already-posted replay, re-process the original through BGBlur, blur the affected segment, and re-upload — minutes, not a re-edit.

This is also the realistic answer for older archives. When a former member asks to disappear from three years of replays, batch processing makes honoring the request feasible instead of impossible.

From closing song to posted replay

1. Export the recording. Save the service as MP4 from OBS, vMix, or your recorder — any common resolution up to 4K works.
2. Upload to BGBlur. Drag the file into the editor in your browser. No install; works on the church office PC or a volunteer's laptop.
3. Choose who stays visible. Run automatic face blur for everyone, or exempt your pastor and worship team with selective blur.
4. Spot-check the kids' segments. Scrub the youth and dedication moments to confirm every non-exempt face is masked through camera moves.
5. Export and post. Download the processed MP4 and publish to YouTube, your website, or your app — same quality, no watermark on paid plans.