Privacy Security And Stored Data

Published on

Privacy, Security, and Stored Data

Selfhost Podcasting stores podcast and episode data in WordPress. Optional integrations can send data to external services only when enabled and configured.

WordPress data

The plugin stores:

  • Podcast records as sh_podcasting_pod.
  • Episode records as sh_podcasting_epi or migrated source posts.
  • Podcast and episode metadata in post meta.
  • Background queue data in WordPress options.
  • Error logs in podcast metadata.
  • Temporary RSS import and migration state in transients.

Media data

Episode media URLs, file size, MIME type, extension, source media provider data, and duration may be stored as metadata.

S3-compatible storage

When enabled, the plugin can upload media to your configured storage provider. The provider may process object data, object names, credentials, request logs, and delivery requests according to its own terms.

S3 credentials are encrypted before storage. If WordPress salts change, credentials may need to be re-entered.

Analytics prefixes

When enabled, episode media requests pass through the configured analytics provider before reaching the media file. That provider may receive request metadata such as IP-derived information, user agent, request time, media URL, referrer, and range headers.

Review each provider's privacy policy before enabling analytics.

Podcast Player

When enabled, Selfhost can share feed URLs and show details with the Podcast Player plugin installed on the same WordPress site. Private podcasts are skipped or disconnected from managed public player data.

Pro private podcasting data

The Pro module can store:

  • Subscriber names and email addresses.
  • WordPress user IDs.
  • Grant records and source references.
  • Token selectors, token hashes, encrypted token secret data, token status, expiry, and usage counters.
  • Last-used timestamps.
  • E-commerce source metadata.

Private podcasting may send email notifications containing private feed links, website access information, password setup links, or token status updates through WordPress mail.

REST and preview access

The plugin restricts public REST exposure for private Selfhost episodes and validates access before returning private preview show notes.

Site owner responsibilities

Site owners are responsible for:

  • Explaining enabled analytics and storage providers in their privacy policy.
  • Handling subscriber data retention.
  • Responding to export and erasure requests.
  • Protecting admin access and S3 credentials.
  • Avoiding public submission of private feeds.