Where does Benecaster store its data?

Your subscriber data lives entirely in your WordPress database — nothing about your subscribers goes anywhere else. Benecaster adds its own tables for tokens, episodes, analytics, and related data, and keeps settings and configuration in standard WordPress options. The feed cache uses the WordPress object cache, falling back to transients where no persistent cache is available.

Podcaster account data is split across two external systems. Benecaster’s license server (benecaster.com) stores your account details, license, and aggregate telemetry data if you’ve opted in — see What data does Benecaster send to the license server? for specifics. Stripe holds your payment method and billing history. Neither service ever receives subscriber emails, names, feed tokens, or any data about the people who subscribe to your podcast.

No proprietary format locks you in. Benecaster’s hooks and filters are intentionally comprehensive — most developer customizations can be done without touching the database directly, which is the safer approach. Direct table access bypasses the plugin’s internal logic and is prone to breakage as the schema evolves.