ChurchGather
Acesso antecipado · 18:00 EDT

Content privacy

Share with the audience you actually chose.

ChurchGather content can have different audiences. This page explains the difference between public, church, limited, direct, and administrative content.

Last updated August 25, 2026

01

Public content

Public content may appear on public ChurchGather pages, websites, search results, shared links, or previews, depending on product settings.

  • Examples may include a public church profile, event, bulletin, resource, or giving purpose
  • Do not publish private contact, child, care, membership, or internal information as public
  • A public label should be visible before publishing
02

Follower and church content

Some content may be limited to people who follow a church or whose church membership request has been approved.

  • Following a church is not the same as church membership
  • Church membership is not the same as being an administrator
  • Backend rules must check the person’s current relationship before showing content
03

Ministry and group content

A ministry, team, class, small group, or other church group may have content limited to approved participants or leaders.

  • Use the smallest useful audience
  • Review participation when people leave a role or group
  • Do not copy limited content into a wider public area without permission
04

Direct messages and conversations

Direct and group conversations are not public website content. Access should be limited to conversation participants and approved moderation or safety processes where legally and technically appropriate.

  • Do not expose private messages in public search or previews
  • Protect media and attachments with the same conversation rules
  • Blocking, reporting, and deletion may have separate safety records
05

Administrative and financial content

Membership reviews, role changes, reports, payout details, private notes, security records, and financial settings require restricted administrative access.

  • Use separate roles for sensitive work
  • Membership alone gives no financial access
  • Every sensitive action requires backend authorization
06

Changing the audience

Changing content from private to public can expose information to more people. The interface should clearly warn the leader before a wider audience is selected.

  • Show the current and new audience
  • Require confirmation for important visibility changes
  • Existing copies, notifications, exports, or screenshots may remain outside ChurchGather
07

Church responsibilities

Church leaders are responsible for choosing appropriate audiences, training authorized leaders, respecting consent and safeguarding, and responding to privacy concerns in their church space.

08

ChurchGather responsibilities

ChurchGather is responsible for building clear audience controls, enforcing access through secure systems, limiting staff access, and explaining known privacy limits honestly.

ChurchGather

A content audience looks wrong?

Contact the church leader for content controlled by the church, or contact ChurchGather for a technical privacy or access problem.