Privacy.

Reverb helps invited churches publish and organize sermons. During the pilot, contact your inviting administrator for privacy requests or support.

Information Reverb uses

Reverb stores administrator names, email addresses, password hashes, session information, church memberships, church branding and sermon records. Published sermon details are public. Google authorization is used separately to connect a church-owned YouTube channel.

YouTube and Google authorization

With your permission, Reverb accesses the connected channel, uploads videos, checks video processing, and changes uploaded videos’ visibility when an administrator publishes them. Refresh tokens are encrypted on the server. Reverb does not sell this information or use it for advertising.

Reverb uses YouTube API Services. Google’s handling of information is described in the Google Privacy Policy. You can disconnect your channel in Reverb or revoke access through Google’s permissions settings. Disconnecting removes Reverb’s stored channel credentials; it does not delete your YouTube videos.

Viewing videos

Videos play through an embedded YouTube player. YouTube receives information when its player is loaded and used. Sermon thumbnails are retrieved from YouTube.

Temporary video files

During the browser-upload pilot, videos transfer directly to YouTube. If background mode is enabled later, videos are temporarily stored in private object storage, removed after successful transfer, and expire after three days if unfinished.

Access and deletion

Ask your church administrator to correct sermon information or remove a sermon record. Ask the Reverb operator through your inviting administrator for account or church-data deletion. Deleting a Reverb record does not automatically remove a YouTube video. Backup copies are retained for recovery according to the deployment’s retention schedule.

This pilot notice must be updated with the operator’s public contact details and actual service providers before commercial launch.