Back to website

Water Valley Voice

Publishing privacy

Updated November 9, 2026

This policy covers the Water Valley Voice publishing workspace, podcast player and connected services.

Website listening

Our podcast player measures plays, listening time and episode progress. These statistics do not identify listeners and use no tracking cookies. Individual playback records are combined into daily totals after 30 days; those totals are retained. We respect Do Not Track and Global Privacy Control settings. Short-lived checks help prevent automated misuse.

Accounts and episode files

We store invited team members’ names, email addresses, roles, sign-in records and account security information. We also store uploaded media, artwork, drafts, publishing choices and publication records so the team can manage its episodes.

Session cookies keep you signed in. Connection and device information, including IP addresses, may be used to operate and protect the service. These pages load fonts from Google.

Connected YouTube data

The workspace uses YouTube API Services. When an Admin connects our channel, Google asks for permission to:

  • Upload videos selected for YouTube publishing.
  • Read channel and video information to confirm ownership and avoid duplicate uploads.
  • Read YouTube Analytics reports to show the team how its videos perform.

We store the connected channel’s details, video identifiers, publishing records and retrieved reports. Google authorization tokens are encrypted before storage and are used by the server to carry out these actions.

Google data is used for these publishing and reporting features. We do not sell it, use it for advertising, or use it to train AI models.

Storage and sharing

Cloudflare hosts the workspace and stores its account records, media and reports. Authorized team members can access the workspace according to their role. Publishing sends the selected content and metadata to the chosen destination; released audio and artwork are available through public podcast feeds and players.

Draft files and local episode records are retained for continued use and recovery. Connected YouTube data follows the access and deletion rules below.

Google connection details and reports are encrypted in separate private storage outside episode backups. Database recovery history contains only unreadable references to that data. Removing a Google connection also removes the keys needed to read its saved data, so restoring an episode backup cannot restore that access.

Disconnecting and requesting deletion

An Admin can use Disconnect in Connections to stop the workspace’s YouTube access, remove its saved YouTube channel and video details and reports, and revoke the Google authorization. If Google is temporarily unavailable, revocation is retried; the encrypted credential used for that retry is kept for at most seven days.

We check connected authorization and video availability regularly. If authorization can no longer be confirmed, the workspace removes the related Google data no later than 30 days after the last successful verification. Recovery requires fresh Google authorization.

Disconnecting does not delete videos from YouTube or your uploaded media here. Local episode identifiers and a record requiring review before another upload remain to help prevent duplicates.

You can revoke the Google grant in Google account permissions. To request deletion of stored account or connected-service data, or to ask about privacy, email erichards@watervalley.com.

Google’s handling of information is described in the Google Privacy Policy.