Skip to main content

Privacy and Data Handling

Benecaster is built for podcasters who care about doing right by their subscribers. That means being specific about what data the plugin touches, where it goes, and what controls you have over it.

This page documents every category of data Benecaster collects or processes — from subscriber feeds to optional telemetry — and the tools available to you for retention management and right-to-erasure.


Data Benecaster Collects

Free Follower Signups

When the [benecaster_follower_signup] shortcode is placed on a page, it presents a sign-up form to any website visitor — no account or payment required. Submitting the form:

  • Creates a WordPress user account for the submitted email address (if one does not already exist)
  • Generates and stores a feed token for them, recorded with a token type of follower
  • Sends a welcome email to the submitted address containing their private RSS feed URL

Fields collected: Email address (required) and display name (optional — the form can be configured to omit the name field via show_name_field="false").

Personal data erasure: A follower’s data is erasable via the standard WordPress user erasure flow combined with TokenRepository::revoke_user_tokens(). The right-to-erasure tool in Settings → GDPR / Privacy covers follower token records alongside paying subscriber records.

Listener Support Donations

Donations are recorded whichever mode you run — see Listener Support Overview for the difference between link mode and Stripe mode.

What is stored: the show, the amount and currency, the platform, a transaction reference, the donor’s email address and message when they provide them, and the date. In link mode these values are supplied by the donor when they return to your site; in Stripe mode they come from the completed payment.

Card details are never stored. In Stripe mode the payment runs through Stripe’s Payment Element and card data goes directly to Stripe — it does not pass through your WordPress database. In link mode no payment touches your site at all.

Donors are usually not WordPress users. Anyone can donate without an account, so donation records often have no user attached to them. The erasure request form described below works for them the same as for anyone else, by email address.

You have full access to your donor records. Because donations are stored in your own WordPress database, you can see each donor’s name, email, and message — there is no separate visibility control withholding it from you. Use it for sending a personal thank-you, the same way you would with any other record you hold.

Benecaster never sends marketing email itself, and asks nothing on a default install. A consent checkbox appears on the subscribe checkout and the follower signup form only when an add-on asks for one for that show. A donor who ticks the donor mailing-list opt-in also records a yes.

What is stored: one record per person per show — their answer (yes or no), the exact wording of the checkbox they were shown, which form they answered on (subscribe, a free tier on the subscribe form, follow or donation), whether their email address was confirmed, and the time, in UTC. A later answer replaces the earlier one for that show.

Confirmed and unconfirmed answers. The follower form, a guest checkout and the donation form all take an email address anyone could type. An answer given while signed in to that account is confirmed. One given while signed out is stored as unconfirmed until the person proves the address is theirs, by answering again while signed in or by clicking a button that states the answer:

  • The follower confirmation email has two buttons. Confirm and follow only follows, and leaves the answer unconfirmed. Confirm and follow, and yes to: followed by the checkbox’s wording does both. This email only goes out on a show with Ask new followers to confirm their email turned on, under Subscriber Engagement.
  • The Welcome email carries a Yes to: button for someone who signed up for a free tier while signed out and ticked the box.

An unconfirmed answer never replaces a confirmed one, and a signed-out follower submission doesn’t change an answer from a paid checkout or a donation, so nobody can untick the box with someone else’s address, or tick it for them.

On a subscribe checkout the answer is stored only once the membership exists: a declined card stores nothing.

Outbound Webhook Deliveries

If you send events to another service under Settings → Integrations (see Outbound Webhooks), Benecaster keeps a log of each delivery so it can retry a failed one and show you Recent Deliveries. Most events carry the subscriber’s email address in the request body, so these log entries are personal data. Every entry is deleted after 30 days, whatever its status, and sooner on an erasure request (see Right to Erasure below). What the receiving service does with the data is between you and that service.

Third-Party Scripts on Your Site

Two Benecaster features load a script from another company’s servers. Neither is loaded on a default install, and neither runs sitewide — but where they do run, the third party sees your visitor’s IP address, so both belong in your cookie and privacy disclosures.

Stripe.js — payments. Loaded when a page renders the subscribe form or the account and billing-portal pages. Stripe sets two cookies:

Cookie Lifetime Purpose
__stripe_mid About one year Fraud prevention — identifies the browser across sessions
__stripe_sid End of session Fraud prevention within a single checkout

These are payment security cookies, not advertising cookies. Stripe uses them to recognize repeated card attempts from the same browser. They do not track your visitors across other websites and they are not used to profile or target anyone. A cookie audit that mislabels them tends to end in one of two bad outcomes: a privacy policy that describes tracking you do not do, or a podcaster ripping out payments over a misunderstanding.

Benecaster does not store either cookie and never reads them. They are set by Stripe, in your visitor’s browser, and Stripe is the data controller for them.

Where Stripe.js loads is narrower than people assume, which is useful when writing a cookie policy: the script is registered globally but only enqueued at render time, so it loads only on pages carrying [benecaster_subscribe] or the account and billing-portal pages. Never sitewide, never on episode or archive pages that do not carry one of those.

Cloudflare Turnstile — bot protection. Loaded only if you have enabled Bot Protection by saving both Cloudflare keys. On a default install, and on an install where only one key has been saved, nothing is requested from Cloudflare at all.

When it is enabled, Cloudflare receives the visitor’s IP address and their interaction with the challenge. Turnstile is designed to work without tracking cookies, which is much of why it was chosen, but the IP disclosure is real and you should account for it.

Where it loads depends on the donation style you use:

  • With the inline form style, the script loads when a page carrying that form is opened.
  • With the button or icon styles — including the auto-injected prompt, which defaults to a button — the script loads only when a visitor clicks to open the donation modal. A listener who never clicks never contacts Cloudflare.

Benecaster does not receive or store anything from the challenge beyond a pass or fail on the donation attempt itself.

No consent banner, and no lazy-load switch. Benecaster does not ship either, for Stripe.js or for Turnstile, and neither is planned. If your jurisdiction requires consent before these load, that is handled by your own consent tooling — the plugin will not do it for you, and you should not assume otherwise from the narrow load conditions above.

Download Log

Download logging is opt-in, not automatic — it only records requests for a show (or episode) where you have turned on download tracking (Details → Show Flags, with a per-episode override on the Media tab). See Download Tracking for how to enable it. For a show or episode where tracking is off, no download-log entry is written at all. Where it’s on, each entry contains:

  • Episode reference
  • Show reference
  • Token reference
  • User (subscriber) reference
  • Membership tier at time of request
  • Hashed IP address (never plaintext — see below)
  • Byte range from the HTTP Range header, when present

IP hashing: Raw IP addresses are never stored. Before any log entry is written, the requesting IP is hashed using benecaster_ip_hash_salt. The plaintext IP exists in memory only for the duration of that single request.

If GeoIP enrichment is enabled (see below), the GeoIP lookup also runs before the hash, so the lookup and the hash happen in the same request and the plaintext IP is discarded immediately after both operations complete.

GeoIP Enrichment

When GeoIP is enabled in Settings → Tools → GeoIP Database, Benecaster enriches download log records and subscriber token records with geographic data derived from the requesting IP address.

What is captured and stored:

  • ISO alpha-2 country code (e.g., US, GB, DE)
  • ISO subdivision/region code (e.g., NY, ENG)

What is read from MaxMind and immediately discarded without storage:

  • City name
  • Postal code
  • Latitude
  • Longitude

The two codes are written to two places:

  • The download log — a country and region code on each recorded download.
  • The subscriber’s token record — a country and region code written once on their first valid feed poll (not updated on subsequent polls).

MaxMind database stays local: The GeoIP database file is downloaded to your server and all lookups run locally. No IP addresses are sent to MaxMind for individual lookups.

To configure GeoIP, see Settings Reference → Tools → GeoIP Database.

Telemetry to the License Server

When you opt in under Settings → Account → Telemetry, Benecaster periodically sends an anonymous usage payload to the Benecaster license server. Opting in is entirely voluntary — both flags default to off.

Sent on every check-in, whether or not you opt in. The daily license validation call carries a minimum payload regardless of your telemetry setting:

Field What it is
Site token, site URL, plugin and WordPress versions Required to validate the license at all
Telemetry opt-in status Whether you have opted in — so the server can tell a declined install apart from one that simply reported nothing
Show count The number of published shows on this site. A bare integer — see the note below
Paying subscriber count A bare integer — how many active paying subscribers you have, across all shows
Total token count A bare integer — paying subscribers plus followers, across all shows

These counts are sent whether or not you opt in to telemetry, and the reason is worth knowing. Your plan limits how many active shows and subscribers you can run, and those limits are checked on the license server against the figures your site last reported. Gated behind telemetry opt-in, they would read zero for everyone who opted out — so the limits would not be relaxed for them, they simply would not be evaluated. Bare counts carry no personal data and nothing about who your subscribers are, so they are sent unconditionally rather than leaving your plan’s limits unenforceable.

✅ Your license key is not sent. It is not in the validation payload and not in the failure-alert payload. The request is authenticated by the per-show site token, which is the only credential the license server reads. Base telemetry (benecaster_telemetry_opted_in), when on, adds:

Field What it is
Episode count Number of published episodes
Average episode duration Across all published episodes, in seconds
Total content hours Sum of all episode durations
Show age Days since your first published episode
Setup wizard completed Boolean flag
Web player play count Aggregate count, no subscriber identity
Add-ons your license includes Which add-ons the license grants, by slug
Add-ons you use Which of those are switched on for at least one show, by slug
Why you switched an add-on off Only if you answered the optional question on Settings → Add-ons after switching an add-on off on its last show: the add-on’s slug, the reason you picked from a fixed list, any comment you typed (up to 500 characters, sent as typed), and when you answered. Each answer is sent once and then deleted from your site. It names no person, email address or show. Omitted when there is nothing to send. Kept against your license on benecaster.com for 24 months, never published or used in benchmarks, included in a copy of your data and deleted on a deletion request
Add-on plugins installed Which Benecaster add-on plugins are installed and active, by slug, read from your Plugins screen whatever the license includes
Add-on plugins deactivated Which Benecaster add-on plugins are installed but deactivated, by slug, read the same way
Active bridge slugs Which membership plugins gate your paid feeds, by plugin slug (memberpress, woo-subscriptions, paid-memberships, restrict-content, benecaster_builtin) — deduplicated across your published shows. Shows with no bridge configured are excluded
Tier breakdown Active subscriber count per tier, keyed by tier slug — counts only, no identities
Benecaster files modified Boolean — whether any of the plugin’s own PHP files differ from the release baseline. Detection only; never disables a feature or shows you a notice
Benecaster modified file count True count of differing files, uncapped
Benecaster modified files Up to 10 of the differing relative paths
Revenue telemetry opt-in flag Whether you also have revenue telemetry on

Revenue telemetry (benecaster_revenue_telemetry_opted_in), when on, additionally includes:

Field What it is
Estimated MRR Each paid plan’s monthly price × the listeners on it, across all your shows, in your currency’s smallest unit. Not sent when your shows charge in more than one currency or a plan’s price can’t be read
Currency The currency code of that figure, such as USD
Estimate flag Marks the MRR value as an estimate rather than a measured figure

This is an estimate — no payment processor data, no transaction history, no subscriber identity is involved. It’s calculated from numbers Benecaster already has: how many active subscribers you have at each tier, and what pricing is configured for those tiers.

The revenue telemetry checkbox is disabled until the base telemetry checkbox is on. Turning off base telemetry automatically clears the revenue flag server-side.

Transcription add-on, when installed and active, adds a further block — base telemetry must also be on:

Field What it is
Transcription provider Which provider is configured, by slug; null when unset
API minutes, last 30 days Minutes transcribed via a provider API, excluding imports
Episodes transcribed, last 30 days Count, excluding imports
Import method distribution Counts per method: api, file, paste, rss_feed
Transcript edit rate distribution Transcripts bucketed by how much of each was edited — corrections never saved, saved with no corrections, light, moderate, heavy
Custom prompt flag Whether the transcription prompt has been changed from the shipped default. The prompt text itself is never sent

Nothing in this block includes transcript content. It reports how much was transcribed and how much editing followed, never what any transcript says.

What is never included in telemetry: subscriber names, emails, IP addresses, episode titles, feed URLs, or any content from your episodes.

Web Player Play Beacon

When the [benecaster_player] shortcode renders on a page, it registers plays via a lightweight unauthenticated beacon: POST /benecaster/v1/analytics/player-play.

This endpoint:

  • Increments a per-episode play counter
  • Increments a site-wide aggregate play counter
  • Does not capture subscriber identity
  • Does not store IP addresses (not even hashed)
  • Does not log episode titles — the episode is referenced by internal ID only

Plays counted this way are the “Web player play count” field included in base telemetry, if you’ve opted in.

Email Editor Opens, Clicks and Notifications

With the Email Editor add-on, episode notifications and broadcasts carry a tracking pixel and route their links through a redirect on your site. For each listener the Email Editor keeps which emails they were sent (with their tier at the time), when they first and last opened each and how many times, each link they clicked with its times and count, and which episodes they were notified about. Their own link to an episode is kept with their clicks. No IP address and no browser details are kept. It all stays on your site and is never sent to Benecaster or anyone else.

Open and click records are deleted after 730 days, notification records 30 days after a notification finishes, and all of it goes when the listener’s account or the show is deleted. Nothing is recorded after a license lapse or with the add-on switched off for a show; emails already delivered keep working. Say in your privacy policy that your emails use a tracking pixel and tracked links to measure opens and clicks.

Transcription Service Add-On Telemetry

When the Transcription Service add-on is active and base telemetry is enabled, six additional fields are included in the telemetry payload:

Field What it is
transcription_provider Provider slug only (e.g., openai, assemblyai) — never your API key
transcription_minutes_api_30d API-transcribed minutes in the last 30 days
transcription_episodes_30d Episodes transcribed in the last 30 days
import_method_distribution Counts of how transcripts arrived: api / file / paste / rss_feed, over 30 days
transcript_edit_rate_distribution Five buckets: never_opened / opened_no_edits / light_0_5pct / moderate_5_20pct / heavy_20pct_plus
has_custom_prompt Boolean — whether Vocabulary hints and context differs from the shipped default

What is never included: transcript text, episode titles, episode IDs, or any content from your audio or transcripts.


Subscriber Data Retention

Configurable Retention Window

You control how long Benecaster retains subscriber personal data via Settings → GDPR / Privacy → Subscriber Data Retention. The default is 90 days after a subscription ends.

Covered by the retention window:

  • Token records for deactivated subscribers
  • Download log rows linked to those subscribers
  • Email log rows
  • Migration patron records from Patreon/Supercast imports
  • Subscriber history (joined, cancelled and tier-change events) for those subscribers, which is anonymized rather than deleted, so your growth and churn counts don’t change
  • Built-in membership payment records for those subscribers, which are anonymized rather than deleted: the amounts and dates stay as your financial record, and the link to the person is removed
  • Their entries in Benecaster’s sales-tax records (see Right to Erasure below), which are removed outright
  • Their entries in the outbound webhook delivery log, which are removed outright (every entry is also deleted after 30 days regardless)

A nightly cron (benecaster_gdpr_prune, 02:00) automatically purges records older than the window.

Sent Email

Benecaster keeps a record of each email it sends, and a copy of the email itself — which can include a subscriber’s private feed URL or a sign-in link — so it can troubleshoot delivery and resend a message. These are kept for 180 days, then a daily job deletes them. Emails still waiting to be sent are never deleted. This window is separate from the subscriber retention window above; developers can change it with the benecaster_email_log_retention_days filter.

What Is Never Pruned

The unsubscribe log is explicitly excluded from retention purges. It records each opt-out and each opt back in, and how it was made: an email’s unsubscribe link, the one-click button in a mail client, or the listener’s own Email Preferences on the account page. It is retained indefinitely for regulatory compliance — you need to be able to demonstrate that you honored an unsubscribe request, even after the subscriber’s other records are gone.

Episode purchases (the Episode Sales add-on) are excluded too, for a different reason: they’re access someone paid for outright, not aging subscriber activity. The nightly retention sweep never removes a purchase record — only a right-to-erasure request does, below. Don’t assume a quiet buyer’s purchases get tidied away with everything else.

Marketing-consent answers are kept too. The record is your proof that consent was given, and a listener who has gone quiet has not withdrawn it. Only a right-to-erasure request removes it.

Analytics Data Retention

Analytics records — subscriber events, daily snapshots, the download log and feed health history — have a separate Retention window under Settings → Tools → Analytics Data. The default is Forever. This is distinct from subscriber data retention — analytics data may not contain subscriber identity at all (daily snapshots, for example, contain no subscriber references). See Settings Reference → Analytics Data for details on the pruning flow.

Any other window deletes older analytics history every night, and what it deletes can’t be rebuilt. If you use the Analytics Dashboard add-on, its charts, cohort retention, exports and digests lose the pruned dates for good, and pruned feed health days show as Not checked, because Benecaster can’t go back and re-check a past night. Download counts are kept whatever you choose. Unless you have a specific obligation to delete this history, leave the window at Forever.

Donor Data Retention

Donation records have their own window, set under Settings → Listener Support → Donor data retention. The default is to keep donations forever, and that default is deliberate: donations are financial records, and most podcasters need them for their accounts long after the subscriber data around them has aged out.

Set a window in days and a nightly sweep purges donation rows older than it. Consider your bookkeeping and tax obligations before turning this on — the deletion is permanent, and this is the one retention setting where the shortest window is unlikely to be the right one.

Billing Addresses

Benecaster does not store your subscribers’ billing addresses.

When a show collects tax on the built-in membership system, subscribers enter a billing address in a Stripe address form on your signup page — tax has to be calculated from somewhere. The address passes through your site’s server on its way to Stripe, so the tax can be shown before they pay, and is not saved or logged there. It stays with Stripe, and appears on the Stripe invoice your subscriber receives, which carries your business details because you are the merchant. The same goes for an address a subscriber updates later from their account page.

This is deliberate. A home address is more precise than anything else Benecaster keeps — elsewhere the plugin reads a subscriber’s city, postal code and coordinates during a GeoIP lookup and discards all three, retaining only country and region. Keeping addresses would also mean keeping them for years, since tax rules require invoices to be retained long after a subscription ends.

What this means for your privacy policy: you still need to account for the address, because it is collected in the course of your transaction — but you are describing data held by your payment processor, not by your website. Your existing disclosure about Stripe as a payment processor may already cover it. Worth a look rather than an assumption.

See Tax and VAT on Podcast Subscriptions.


Right to Erasure

The Erasure Request Form

Put [benecaster_erasure_request] on your privacy page. Anyone can use it, whether they are a subscriber, a follower or a donor: they type an address, and WordPress emails its own Confirm Action: Erase Personal Data link to it. Once they confirm, the request waits under Tools → Erase Personal Data until you complete it. Nothing is erased before then, so the billing check below and other plugins’ data get a human look.

The page shows the same thing for every well-formed address, so the form can’t be used to test who is on your list. It is limited to 3 requests per address and 5 per visitor an hour, and it uses Turnstile when both Listener Support keys are saved. Signed-in members also get an Erase My Data section on their account page.

Deleting Data Yourself

To delete all data Benecaster holds about a specific subscriber:

  1. Go to Settings → GDPR / Privacy → Delete a Subscriber’s Data.
  2. Enter the subscriber’s email address.
  3. Click Delete Subscriber Data. The button turns red and reads Confirm Delete; nothing has been deleted yet.
  4. Click Confirm Delete. The result lists what was removed, category by category.

The cascade covers: tokens, download log, email log, the person’s stored and queued emails (including any still waiting to be sent, so nothing more goes to them), migration patron records, their entries in Benecaster’s sales-tax records, their entries in the outbound webhook delivery log, and their marketing-consent answers. The subscriber’s history (joined, cancelled and tier-change events) is anonymized rather than deleted: the events stay so your counts don’t change, and the link to the person is removed. The result lists it as Subscriber history rows anonymized: N. Episode preview links you sent to that address keep working, but the name and email they were sent to are removed; the result’s last line is Preview links anonymized: N, shown even when it is 0. Their built-in membership payment records are treated the same way: each payment, its amount and its date stay as your financial record, and the link to the person is removed. Unlike the automatic prune, a manual right-to-erasure request also deletes the subscriber’s entry in the unsubscribe log — the indefinite-retention exception applies only to automated pruning.

Deletion is immediate and irreversible. There is no recovery path.

Nothing is deleted while the person is still being billed. If they hold a built-in membership that Stripe can still charge (active, in a free trial, past due, paused, or set to cancel at the end of the current billing period), if a membership plugin still counts them as an active member of a show, or if a show’s membership plugin is deactivated so there is no way to ask it, the screen deletes nothing. Instead it shows a red box headed Nothing was deleted: this person is still being billed., with one line per show giving the reason and what to do, ending …then delete their data again. Cancel the membership, then delete their data again. These are the same checks Erase Personal Data runs, described below. An email address with no WordPress account on the site has nothing to bill and is deleted as usual. The nightly retention sweep is not affected by this check.

WordPress’s Built-In Export and Erase Tools

Benecaster also registers with WordPress’s own privacy tools, so Tools → Export Personal Data and Tools → Erase Personal Data work for subscribers without you using the dedicated screen above.

Export Personal Data returns everything Benecaster holds tied to the requested email: tokens, subscriber history, membership and subscription records, badges, donations, sent emails, unsubscribe records, and download history — plus a Benecaster Purchased Episodes section (Episode Sales add-on): the show, what it gave access to, the date granted, and the expiry, including purchases that have since expired. Lifetime access shows Never rather than a date.

If the person has answered a marketing-consent checkbox, the export includes a Benecaster Marketing Consent section, one entry per show: the show, their answer, the wording they were shown, where they answered (Subscribe form, Subscribe form, free tier, Follow form or Donation form), whether their email address was confirmed, and when the answer was recorded.

With the Email Editor add-on, the export includes, under Benecaster Email Editor, Emails opened (Email, Sent, First opened, Last opened, Times opened), Links clicked in emails (Email, Link, First clicked, Last clicked, Times clicked) and Episode notifications (Episode, Status, Updated). Erase Personal Data deletes all of it and keeps nothing, including the person’s own episode links and any clicks on them made by someone they forwarded an email to.

If any outbound webhook deliveries about the person are still in the log, the export includes a Benecaster Webhook Deliveries section: the event, its delivery status and the date for each. The body that was sent is not included; it holds only the person’s own email and identifiers already listed elsewhere in the export.

If the person has bought buy-ups (the extras you sell beside a membership), the export includes a section headed Benecaster Extras, the name subscribers see for buy-ups: the show, the buy-up’s name (under Extra), its status, its period dates, whether it is set to cancel at the end of the period, and when it was cancelled. Stripe’s IDs are not included.

If you have stored or queued emails to the person, the export includes a Benecaster Stored Emails section: the show, the email type, the subject, its status, and when it was queued, scheduled and sent. The body and headers are never included, because an email can hold a private feed URL or a sign-in link.

If you have sent the person an episode preview link, the export includes a Benecaster Episode Previews section: the episode, the name it was sent to, its status, when it was sent and expires, how many times it was viewed and when it was last viewed.

If the person has paid for a built-in membership, the export also includes a Benecaster Membership Payments section, one entry per payment: the show, the tier, the amount paid with its currency, the amount refunded (blank when nothing was refunded), and the date it was paid, in your site’s own timezone. Stripe’s own IDs for the payment are not included.

The Benecaster Emails section lists one entry per email Benecaster logged for that address, with its show, type, subject, Status and Date. Its description reads “Emails we sent you, and emails we did not send and why — usually because you had opted out. Opt-outs are recorded so they can be honored.” The statuses are:

  • queued — waiting its turn to be sent.
  • sent — handed to your site’s mail system. A message that bounces later still reads sent, because Benecaster never hears about it.
  • failed — could not be sent after three attempts. The mail server’s error message is not included: it is about your server, not the person, and can carry server details.
  • suppressed — never sent. These entries have a Why it was not sent row, in words: You had opted out of all emails from this show., You had opted out of announcements and updates from this show., You had opted out of new-episode emails from this show., or The site stopped this email. It was not because of an opt-out of yours. when an add-on or custom code on your site refused it.

The Date is when the email was sent or, for a suppressed one, when it was refused. Emails logged before Benecaster recorded these statuses all read sent, whatever happened to them.

If the person has been notified of a tier or buy-up price change, the export also includes a Benecaster Price Changes section — one entry per change they were notified of, including a change since withdrawn or superseded by a later one. Each entry shows: which tier or buy-up changed, the old and new price, when they were notified, the date they’d first be charged the new price, whether a reminder was sent (a date, or “No”), and the outcome in plain words — moved to the new price; not yet applied; left on the current price (with the reason: their membership had ended, moved tier, was paused, or had a payment problem); not applied because the subscriber switched to a different billing period before the change took effect; not applied because the subscriber cancelled their switch to this billing period; not moved because the update failed; or not applied because the show withdrew or replaced the change — plus the date they were moved and any error details. Dates are shown in the site’s own timezone. Only people matched to a WordPress account are included; a price change sent to someone without an account has nothing to match against.

If the person was imported from another podcast platform through the Migration Wizard, the export also includes a Benecaster Platform Migration section — one entry per show they were imported for: the show, the previous platform, their email and name as imported, the tier they held there, and the date they joined there. That join date is shown exactly as it was imported, never converted or shifted to your site’s timezone — it describes an event on the other platform, not on yours. The entry also shows their migration status and the invitation, completion, and grace-period-end dates, in your site’s own timezone. Someone matched only by email — imported before they ever created a WordPress account — is included the same as a matched account. The payment-setup link they were sent and any private notes you left on the import are never exported.

Before any of the erasure below runs, Benecaster checks whether the person still has a membership that can be billed. If they hold a built-in membership subscription that Stripe can still charge — active, in a free trial, past due, paused, or set to cancel at the end of the current billing period — the whole request is refused and nothing is erased. The same happens if a bridge plugin (MemberPress, WooCommerce Subscriptions, Paid Memberships Pro, or Restrict Content Pro) still counts them as an active member of a show, or if a show’s configured membership plugin is deactivated, since there’d then be no way to ask it. Each plugin’s own idea of “active” decides this: a WooCommerce subscription on hold after a failed payment, a MemberPress renewal being retried, and an RCP membership that’s expired but still being retried do not block erasure, while a fixed-term PMP level does.

When a request is refused this way, WordPress shows Personal data was found for this user but was not erased, with one line per show telling you what to do — cancel the Stripe subscription (settle a past-due balance first, or cancel immediately rather than waiting out a subscription already set to cancel at period end), or cancel or reactivate the relevant membership plugin. Once that’s done, run the same request again. Until then the request stays at Confirmed (or Pending, for a forced erasure), and WordPress’s “your request has been completed” email is never sent — telling the person why is on you, since WordPress doesn’t send a refusal email either. None of this blocks a hand-granted or comped membership with no Stripe subscription behind it, an ended membership, or someone with no WordPress account at all, and it doesn’t stop any other plugin’s own eraser from running.

The reason the whole request is refused, rather than just the parts that would otherwise stay: erasing feed tokens and detaching a subscription from the account while Stripe keeps billing would leave the person paying for something they can no longer access and can no longer cancel themselves from their account page.

Erase Personal Data does not treat every category the same way, because some of it is also the podcaster’s own financial or feed-delivery record:

Data What happens Why
Feed tokens Erased outright The token is the credential — there’s nothing left to anonymize.
Email send log Erased outright No value once detached from who was sent what.
Stored and queued emails Erased outright, including any still waiting to be sent A copy of an email can hold a private feed URL or a sign-in link, and nothing more should go to someone who asked to be erased.
Unsubscribe log Erased outright, on a full erasure request only The indefinite-retention rule above applies to routine operation, not to a request like this one.
Marketing-consent answers Erased outright Kept through routine retention as your proof of consent, but an erasure request removes it. WordPress’s erase screen shows Your answers to Benecaster’s marketing-email consent checkbox were removed.
Outbound webhook delivery log Erased outright A log kept for retries, not a record anyone relies on. WordPress’s erase screen shows Your entries in Benecaster’s outbound webhook delivery log were removed.
Purchased episodes Erased outright It’s an access record with no amount or currency attached — nothing meaningful survives stripping the identity from it. The person’s episodes leave their private feed. The financial side of the purchase (price, receipt) lives in the Episode Sales add-on’s own ledger, not here.
Sales-tax records Erased outright Two lists kept for built-in membership tax: the subscribers whose payments Stripe stopped taxing because it could not place their billing address (the Some subscribers’ payments are not being taxed notice), and the skipped list an Apply Tax to Existing Subscribers run leaves on Settings → Payments, which shows a name or email. Neither is a financial record, so nothing is kept. WordPress’s erase screen shows Your account was removed from Benecaster’s sales-tax records.
Download log Anonymized — identity stripped, row kept Your per-episode download counts are the value of this table and don’t depend on whose download it was.
Subscriber lifecycle events Anonymized Aggregate joined/churned/upgraded/downgraded counts survive; the identifying link doesn’t.
Subscriptions Anonymized Keeps Stripe-side billing reconciliation intact for a subscription that may still be active on Stripe’s side.
Buy-ups Anonymized, and any still running is ended Kept with its Stripe item and dates so your revenue records still match Stripe’s invoices. Ending a running one frees its place under the buy-up’s buyer limit. WordPress’s erase screen shows Your Benecaster Extras purchase records were kept for billing reconciliation, but the link to your account was removed and any still running were ended.
Episode preview links Anonymized — the name and email they were sent to are cleared The link keeps working and its view count stays.
Subscriber badges Anonymized Badge-award analytics (which badges are held, in aggregate) survive.
Built-in membership payments Anonymized — identity cleared, amount, refund and date kept It’s a financial record, handled the same way as donations. WordPress’s erase screen shows a message saying the records were kept.
Listener Support donations Anonymized — identity cleared, amount/currency/date kept It’s a financial record. See Donors Without an Account below.
Price-change records Anonymized — identity and any payment error text cleared, row kept The change itself and what happened to it (old and new price, dates, outcome) are kept so your counts and history for that price change don’t move. WordPress’s erase screen shows a message saying the record was kept. This does remove the one thing that proves this specific person was sent the notice — the same erasure clears the email log too. See Price Change Considerations for whether you need to keep that proof, and how. If the change is still pending when the erasure runs, the person is treated the same as someone whose membership ended: their price is not moved and no reminder is sent to them.
Platform migration records Erased outright Matched by account and by email, so a record from before the person had a WordPress account is caught too. WordPress’s erase screen shows “N record(s) of your import from another podcast platform was/were removed.” Your import’s own totals — how many people it imported, how many completed, how many dropped off — aren’t touched; only the individual’s own record goes. A request refused by the billing check above leaves these records in place, like everything else it touches.

Episode purchases don’t appear on the podcaster-facing Settings → Your Data export in Benecaster itself — that sheet belongs to the Episode Sales add-on, which has the product names and prices this page doesn’t.

Anonymized means the identifying link (the WordPress user, and any denormalized name or email) is stripped from the row, while the row itself, its timestamps, and its non-identifying counters or state stay in place — this is how a donation or a download count survives an erasure request rather than being removed outright.

Deleting a Subscriber’s WordPress Account

Deleting someone’s WordPress account (Users → Delete, or wp user delete) is treated as a request to remove them. Benecaster does three things, in this order:

  1. Cancels their built-in membership billing. Any Stripe subscription that can still charge them is cancelled immediately, with no refund and no cancellation email. If you want to refund them, do it in Stripe.
  2. Switches off their feed. Every Benecaster feed link the person had, on every show, stops working, free follower links included.
  3. Removes their data as Delete a Subscriber’s Data does above, episode purchases included, and also anonymizes five kinds of record that Erase Personal Data anonymizes too: their built-in membership subscriptions, their buy-ups (any still running is ended), their badges, their price-change records (including any payment error text) and their Listener Support donations (name, email and message cleared; amount and date kept). Nothing is left pointing at an account that no longer exists.

Delete a Subscriber’s Data and the nightly retention sweep leave those five linked to the person on purpose: both keep the WordPress account, so the records still have someone to belong to. Delete a Subscriber’s Data does clear the name and email from episode preview links sent to the person, as both erasure routes do.

Unlike Erase Personal Data, an active membership does not block this, because WordPress does not wait: the account is deleted either way, so Benecaster cancels the billing instead of refusing.

If Stripe cannot be reached, the account is still deleted and the subscription is left running. A critical notice in your notification bell names the show and the Stripe subscription: A deleted WordPress account had a paid membership on [show], and Benecaster could not cancel its Stripe subscription ([subscription ID]). Cancel it in your Stripe Dashboard, or Stripe will keep charging the card. Cancel it there.

A membership plugin keeps charge of its own billing. Restrict Content Pro and WooCommerce Subscriptions cancel the person’s subscription themselves when the account is deleted. Paid Memberships Pro cancels only if you tick its cancel option on the Delete Users screen, so tick it, or PMPro keeps charging someone whose feed has stopped. See Paid Memberships Pro Setup.

Donors Without an Account

A donor who gave without ever creating an account asks the same way as anyone else, through the erasure request form. When you complete the request under Tools → Erase Personal Data, every donation record for that address is anonymized: their name, email and any message are cleared, while the amount, currency and date are kept as your financial record. Their donations’ entries in the subscriber history are unlinked from any WordPress account too, keeping the amount, currency and date.

Because the confirmation link goes to the address being erased, nobody can anonymize someone else’s donation history by guessing at their email.

Developers: the benecaster_donor_data_erased action fires whenever donation records are anonymized: when an administrator completes a request under Tools → Erase Personal Data, and when a WordPress account is deleted. It carries the email and the number of rows anonymized, so you can mirror the change into a CRM or mailing list. It fires with a count of 0 too, so check the count before acting on it. See Clean up external records when a donor requests data erasure.


Erasing Your Own Data From Benecaster.com

Everything above is about your subscribers’ data, on your WordPress site. Your own account data on benecaster.com — your license, your invoices, your support history — is a separate request, made by contacting us.

An erasure of your benecaster.com account does not delete everything, and we would rather you know why before you ask.

What happens
Invoices and account credit records Kept. Tax law requires us to retain them for 7 years, or 10 years in the EU
Your name and email on those records Copied onto them, so they remain valid financial documents
Support diagnostic logs you sent us Deleted immediately, rather than waiting out their 90-day window
License, site activations, validation logs, telemetry, support notes Deleted
Your benecaster.com account Deleted, so you can no longer sign in
Your customer record with Stripe, our payment provider — name, billing address, saved cards Deleted, which cancels any subscription still on it straight away. Stripe keeps its own copies of past invoices and payments as its financial records
Referral records where you were the one referred Kept, with your email and first name removed. The record is also the proof of the credit your referrer earned, so it stays without anything that identifies you
Referral records where you referred someone Kept as they are. They name the person you referred, which is their data, not yours. Your referral code and link go with your account
Outreach history, if you were ever a prospect before becoming a customer Deleted — the lead record, its activity log, and every outreach email sent to it. Your address is then removed from our email marketing platform too, and recorded as excluded from future outreach

The right to erasure does not override a legal obligation to keep records, so the financial rows stay — kept whole rather than anonymized, because an invoice that cannot say whose it is is not an invoice. We will tell you exactly what was retained when we action your request. Full detail is in the Privacy Policy.


Email Marketing Integrations

The Email Marketing Integrations add-on is the one part of Benecaster that sends your listeners’ personal data to an email platform you choose: Mailchimp, Kit, ActiveCampaign, MailerLite or Beehiiv. Your platform holds what it receives under its own terms and privacy policy.

What Is Sent to Your Platform

For each person the add-on adds to a show’s list:

  • their email address, and a changed address when they change it on your site;
  • their first name, to your platform’s name field or the field the show chooses, unless the show chooses not to send it;
  • which list they’re on;
  • tags saying whether they follow for free or which tier they pay for, when they move tier or cancel, and whether their podcast app is using their private feed (not set up yet, set up, in use or gone quiet);
  • the name of their tier, if the show sends it to a field;
  • an unsubscribe, when they say no to the show’s emails, or when they opt out of the show’s Benecaster emails on a show set to pass that on.

On MailerLite, which can’t change an address through its API, an address change creates a new subscriber at the new address and deletes the old one with MailerLite’s ordinary delete, not its “forget”. Nothing is sent from a staging site or other copy of your site.

Who Is Added, and on What Basis

Each show chooses who joins its list under Show Settings → Email Marketing → Who Joins the List.

Opt-in, where every show starts, adds only people who tick Email me about new episodes and offers from {show}. on your signup and checkout forms, and Benecaster records their answer as described under Marketing Consent. A follower or free-tier signup who wasn’t logged in joins only once they’ve confirmed their address.

Opt-out and always show no box. They add people who didn’t tick anything: opt-out leaves out only someone who has said no, and always adds every signup. Consent is not your basis for those people. As the controller of your list, you need your own lawful basis for adding them, and for emailing them once they’re there. Whether you have one depends on your audience and the law where they live, so settle it before you choose either option. A show run through a membership plugin can’t use opt-in, because Benecaster can’t add a box to that plugin’s checkout, so it starts on opt-out.

Whatever the option, someone who says no after joining is unsubscribed on your platform. Their contact isn’t deleted, so its tags stay.

What Is Kept on Your Site

The add-on keeps two tables in your WordPress database:

Table What it holds How long
{prefix}benecaster_email_marketing_contacts One row per person per show the add-on added: the email address it sent, the list, the platform’s contact ID, the tag it last applied, and when the row was added and updated While they’re on the list. Deleted when the contact is removed, on erasure, and when the show is permanently deleted
{prefix}benecaster_email_marketing_jobs Each update waiting to be sent, or that failed: the show, the person’s user ID and what to send. A removal also holds the person’s email address, because their account may already be gone Deleted as soon as the update succeeds. A failed update, including a removal and its address, is kept 30 days

Deleting the add-on from Plugins leaves both tables in place. They go when Benecaster’s own data is deleted: uninstalling Benecaster with data removal on, or Reset Plugin Data.

What Removal Means on Each Platform

A person is removed from every show’s list on your platform when their WordPress account is deleted, when you use Delete Subscriber Data, when you complete their request under Tools → Erase Personal Data, and when Benecaster’s data retention deletes them, if you ticked Also remove a contact from your email platform when Benecaster’s data retention deletes the subscriber under Settings → Email Marketing → Removing Data. It reaches every show with a list, whoever added the person, including a list the show later replaced, if the add-on added them to it.

Each removal uses the strongest removal the platform offers, and that differs:

Platform What removal does
Mailchimp Permanent delete: all their personal data is gone, and the address can never be added back through Mailchimp’s API
MailerLite MailerLite’s “forget”: all their data is gone within 30 days
Beehiiv Delete, which Beehiiv says can’t be undone
ActiveCampaign Delete, but ActiveCampaign keeps the contact in its contact archive for 360 days
Kit Kit can’t delete a subscriber through its API, so they’re unsubscribed and the show’s tag and the add-on’s tags come off. The record stays in Kit until you delete it there

So an erasure on Kit isn’t finished until you delete the subscriber in Kit yourself, and on ActiveCampaign a copy stays in its archive for those 360 days.

A show’s Remove someone from the list when they cancel their subscription option is different: it uses the platform’s ordinary delete, which on Mailchimp archives the contact and on MailerLite keeps it in case they come back.

The Exporter and the Eraser

Tools → Export Personal Data includes Benecaster Email Marketing Integrations: an Email marketing contacts entry for each show (Show, Email platform, List, Address sent, Contact ID, Tag applied, Added, Last updated) and any Email marketing updates waiting to be sent (Show, Update, Status, Queued, Updated).

Tools → Erase Personal Data runs an eraser of the same name. It deletes the add-on’s contact records and waiting updates for the person at once, and queues their removal from your platform, reporting Removal from your email platform has been queued and runs within a few minutes. A failure shows in the Benecaster notifications. On a copy of your site it removes nothing from your platform and says This site looks like a copy, so nothing was removed from your email platform. Erase this person on the live site.

With the Add-on Deactivated

While the add-on is deactivated on the Plugins screen, no deletion or erasure reaches your platform. WordPress runs no code from a deactivated plugin, so deleting an account, Delete Subscriber Data and Erase Personal Data all leave the person on your email platform. Remove them there by hand. Switching the add-on off for a show under Settings → Add-ons is different: removals still run.

Suggested Policy Text

Once a platform is chosen, the add-on adds an Email Marketing section to Settings → Privacy → Policy Guide. It names your platform and says that the person’s email address and first name may be added to the show’s list, depending on the show’s setting; that the entry is tagged by follower or tier, and when that changes (moving to another tier, or cancelling), and, if the show chooses, carries their tier’s name in a field on that list; that it is also tagged by whether their feed is in use; that a changed address is passed on and an unsubscribe may be; and that deleting their account or asking for erasure removes them, by unsubscribing and untagging where the platform can’t delete. Its For the site owner note reminds you that while the add-on is deactivated, removal doesn’t reach the platform. Like the rest of the Policy Guide, it’s a starting point you review and edit.


Community Integrations

The Community Integrations add-on sends subscribers’ data to the Discord server or Circle community each show connects, so that their roles and spaces follow their tier. Discord and Circle hold what they receive under their own terms and privacy policies.

What Is Sent

Discord. Nothing is sent about a subscriber until they click Connect Discord on their account page and agree on Discord’s screen. Benecaster then reads their Discord user ID and display name from Discord, adds them to the show’s server, and gives and takes the roles for their tier on that Discord account. Discord’s permission to add them to the server is used once, in the minutes after they connect, and then deleted. Their email address is never sent to Discord.

Circle. For a subscriber on a tier mapped to Circle, their email address and display name are sent, and they’re added to the spaces and member tags for their tier. When they change their email address on your site, the new address is added to those spaces and tags and the old one is taken out of them.

What Is Kept on Your Site

What Why How long
For each show and platform, the tier the platform was last told, and the reason for any sync failure To keep the platform in step with the subscription Until the person is removed from that platform
Circle: the email address used on Circle, and the spaces and member tags added To remove the person after their address changes or their account is deleted Until they’re removed from Circle
Discord: the Discord user ID and display name, whether they’re connected and since when, and the roles given To take away only the roles Benecaster gave Until they disconnect or are erased and the roles are taken back
Discord: the one-time permission to add them to the server, encrypted To add them to the server after they connect Deleted once used, on Disconnect Discord or an erasure, and refused once an hour old

Deleting the add-on from Plugins deletes the saved Discord and Circle credentials but leaves these records. They go when Benecaster’s own data is deleted: uninstalling Benecaster with data removal on, or Reset Plugin Data.

Removal on Erasure

A person is taken out of every show’s Discord server and Circle community that holds them when their WordPress account is deleted, when you use Delete Subscriber Data, when you complete their request under Tools → Erase Personal Data, and when Benecaster’s data retention deletes them. The removal runs in the background:

  • Discord: their connection ends at once, and the roles Benecaster gave are taken back. No former-subscriber role is given and nobody is removed from the server, whatever the show’s leaving choice.
  • Circle: they’re taken out of the spaces and member tags Benecaster added, and deactivated in the community when the show has Remove from the community entirely on cancel ticked. Benecaster never deletes the Circle account itself. If the request covers it, delete the member in Circle yourself.

Each record is deleted once its platform confirms the removal. A platform that keeps refusing is listed under Member sync on the show’s Community tab.

Removal runs even while the add-on is switched off for every show or its licence has lapsed. It only ever removes: nothing is given to anyone while the add-on is off.

The Exporter and the Eraser

Tools → Export Personal Data runs two exporters:

  • Community Integrations: Circle communities adds a Circle communities entry for each show with a Circle record for the person, found by account or by email address: Show, Circle community, Community URL, Email address used on Circle, Circle spaces, Circle member tags and Tier last sent to Circle.
  • Community Integrations: Discord servers adds a Discord servers entry for each show where they connected Discord: Show, Discord server, Discord user ID, Discord display name, Connected (Yes, or No: disconnected, roles still being taken back), Connected on, Discord roles given and Tier last sent to Discord.

Benecaster keeps no names for Circle spaces, member tags or Discord roles, so the export shows each by number with the tiers it’s for, such as Space 12 (for Gold) or Role 1234 (for every tier).

Tools → Erase Personal Data runs Community Integrations: community platforms. It queues the removal described above and reports, for each show, {Show}: removal from this show’s community platforms is queued. This site deletes its record of the person as each platform confirms the removal; a platform that keeps refusing is listed under Member sync on the show’s Community tab.

With the Add-on Deactivated

While the add-on is deactivated on the Plugins screen, no deletion or erasure reaches Discord or Circle. Remove the person there by hand. Switching the add-on off under Settings → Add-ons is different: removals still run.

Suggested Policy Text

While Discord or Circle is set up for a show the add-on is switched on for, or still holds members, the add-on adds a Community Platforms section to Settings → Privacy → Policy Guide, with a paragraph only for the platforms you use. The Discord paragraph says that a subscriber who connects their Discord account has their Discord user ID and display name stored and used for their tier’s roles, that a list of the roles given is kept, and that the permission to add them to the server is used once and then deleted. The Circle paragraph says that their email address and tier are sent to Circle, that a changed address is passed on, and that the address used on Circle and the spaces and tags are kept. Both end:

“We keep a record of the tier each community was last told you hold, so that it can be kept in step with your subscription. You can ask us for a copy of these records. If you ask us to delete your subscriber data or to erase your personal data, we remove you from these communities and then delete these records.”

Its For the site owner note reminds you that while the add-on is deactivated, a deletion request doesn’t reach Discord or Circle. Like the rest of the Policy Guide, it’s a starting point you review and edit.


Guest Manager

With the Guest Manager add-on, your site keeps a profile for each guest: name, title, organization, bio, photo, website and social links, which are shown on your episode pages, the guest’s own page and in your feed. A profile can also hold the guest’s email. The email is private: it is never shown on your site, in your feed or in the Guests sheet of your data export, and is used only to keep each guest to one profile and, if you use the Guest portal, to email the guest a private link to update it. Nothing a guest sends through the portal is published until you approve it.

The Exporter and the Eraser

Guest Manager registers with WordPress’s privacy tools, and both work even with Guest Manager switched off for every show:

  • Tools → Export Personal Data runs Guest Manager guest profiles. For each guest profile that carries the requested email, including one in WordPress’s trash, it adds a Guest profiles entry with Name, Title, Organization, Bio, Website, Social Links, Publications (Title (Year): URL, the plain address, never a /go/ one) and Email, leaving out any that are empty. When there is something to show, it also adds Changes waiting for approval (what the guest sent through the Guest portal, such as Title: Countess; Photo: a new photo) and Guest portal link (Yes, it works until {date}). The link itself is never exported.
  • Tools → Erase Personal Data runs Guest Manager guest emails. It removes the email from each of those profiles, throws away any Guest portal changes and photo waiting for approval, and stops the guest’s portal link. It keeps the rest: the profile, its bio, its publications and its episode credits. For each one it reports Guest profile kept: {Name}. Delete it on the Guests screen if the request covers it., or for a guest with publications Guest profile kept: {Name}, with their publications. Delete the guest on the Guests screen to remove their profile and publications too. If the request covers the whole profile, delete the guest yourself on Benecaster → Guests.

Suggested Policy Text

Guest Manager adds nothing to Settings → Privacy → Policy Guide. If you collect guests’ emails, a line like this covers it: If you appear as a guest on our podcast, we keep a guest profile with the details shown on our site. We may also keep your email address, privately, to identify your profile and to send you a link to update it; it is never published. Ask us to export or erase it at any time.


With the Sponsor Manager add-on, each sponsor’s record can hold a contact’s name and email. They are seen only by the site’s administrators and never appear on your website or in feeds. Sponsor Manager registers with WordPress’s privacy tools, and both work even with it switched off for every show:

  • Tools → Export Personal Data adds a Sponsor contacts entry for each sponsor, archived ones included, whose contact email matches: Company, Contact name, Contact email and Notes. Campaign dates and rates are left out, as the company’s terms rather than the person’s data.
  • Tools → Erase Personal Data removes the contact name and email and keeps the sponsor, its campaigns and episodes, reporting Sponsor kept: {company}. Its contact name and email were removed. Check its notes on the Sponsors screen if they name this person. Your notes are free text, so check them yourself.

While any sponsor holds a contact email, Settings → Privacy → Policy Guide carries a Podcast Sponsors section with suggested wording for your policy.


The AI Search add-on sends text to the AI provider you choose (OpenAI, Google Gemini, Cohere or Anthropic), with your own API key. Your provider handles what it receives under its own terms and privacy policy. Nothing identifying a listener is sent: no name, email address, IP address or account.

What Your Provider Receives

Your episodes, with OpenAI, Google Gemini or Cohere. To build the search index, each published episode of a show with AI Search on is sent once, and again only when its text changes: its title, description and show notes, as plain text. HTML, images and their alt text, scripts, embeds, shortcode markup and web addresses are left out, as is boilerplate the show repeats across most of its episodes. Long text is sent in pieces. With the Transcription Service add-on active, each episode’s transcript is sent too (the spoken words and speaker labels), unless its visibility is Hidden. Drafts and other unpublished episodes, and shows with AI Search off, are never sent.

Your guests, with OpenAI, Google Gemini or Cohere. While at least one show has both AI Search and the Guest Manager add-on on, each guest’s bio is sent, as plain text and nothing else about the guest: once for the whole roster when AI Search is set up or switches provider or model, and again whenever a guest is saved. With Transcription Service too, each turn a guest takes in a transcript, once the speaker is matched to that guest, is also sent on its own (four words or more, the same words already sent with the transcript, cut by speaker turn). The speaker’s name is not sent, a Hidden transcript’s turns are never sent, and unchanged text is not sent again. Anthropic receives no bios and no turns.

Your episodes, with Anthropic. Nothing is indexed. Each search sends the show’s whole list of published episodes, each as its title and a short summary of at most 400 characters, cleaned the same way. Full show notes and transcripts are never sent.

What listeners type. The words a visitor types into an AI Search box (2 to 200 characters) are sent to your provider with each new search: on their own to OpenAI, Google Gemini or Cohere, and with the episode list above to Anthropic. A search repeated soon after is answered on your site and not sent again.

Your own searches. The words you type into the admin search panel are sent the same way: once per search with OpenAI, Google Gemini or Cohere, and once per show searched with Anthropic.

What Is Kept on Your Site

What Why How long
The search index: numerical representations of your episodes’ text, and with Guest Manager of your guests’ bios and their turns in transcripts Searching and related episodes Until the episode changes or leaves the index, or the add-on is deleted
A search’s result from your provider, filed under a one-way hash of the search words So a repeated search isn’t sent or billed again A day with OpenAI, Google Gemini or Cohere; an hour with Anthropic
A keyed one-way hash of the visitor’s IP address, never the address itself, with a count The limit of 10 searches a minute per visitor Up to 60 seconds
How many paid searches each show has made today The daily limit on paid searches The current UTC day

AI Search keeps no log of what anyone searched for, and stores nothing about who searched.

Deleting the Add-on

Deleting AI Search from Plugins removes the index, the saved search results, its settings and your API key. Deactivating it removes nothing.


Analytics Dashboard and the Feed Request Log

With the Analytics Dashboard add-on, the feed request log’s revoked-link checks are shown per person to your site’s administrators. Its win-back page lists each cancelled subscriber still checking their feed by WordPress name and email, with their last check-in, check-ins a day and app, and its Export CSV writes those names and emails to a file you download. Nothing new is recorded or kept, and nothing leaves your site. The add-on’s Your Data sheets hold only counts.

Backups and Exports

Backups and exports hold personal data. That includes the Email Editor’s Email Opt-Out List sheet, which holds subscribers’ email addresses. By default they sit in wp-content/uploads/benecaster/, inside the web root, with unguessable file names. Where your host gives you a writable folder outside the web root, name it with the BENECASTER_PRIVATE_DIR constant and new files go there; see Backup and Security Best Practices. Uninstalling with data removal on, and Reset Plugin Data, remove the benecaster/ folder there too.

Suggested Privacy Policy Text

Benecaster contributes suggested paragraphs to your site’s privacy policy, one per feature you actually have active — download logging, Listener Support donations (link or Stripe mode), built-in membership, free follower signup, and email logging. A fresh install with everything off contributes nothing.

Find it at Settings → Privacy → Policy Guide (WordPress core’s own privacy policy tool). This text is a starting point, not a finished policy — it is suggested text, and you still own your privacy policy and must review it. Benecaster does not write your privacy policy for you; it drafts the parts that describe what Benecaster itself does, so you don’t start from a blank page for those sections.

Developers: an add-on can append or remove its own {heading, content} entries before the combined text reaches WordPress via the benecaster_privacy_policy_sections filter.

Email Communications

Once your site has sent a subscriber an email, the suggested text includes an Email Communications paragraph:

“When we send you an email — such as a welcome message, a receipt or a renewal reminder — we keep a record of it: the type of email, when it was sent or why it was not, and its delivery status, along with a copy of the email itself. We use these to troubleshoot delivery problems, resend a message you did not receive, and honor unsubscribe requests. We delete them after 180 days, and sooner if you ask us to erase your data.”

The number of days follows your site’s email retention period (see Sent Email above), so the policy never promises a shorter window than your site keeps. If a developer sets the period below one day with the filter, which keeps sent email until it is erased, the last sentence reads “We keep them until you ask us to erase your data.” instead.

If built-in membership is active on your site, the suggested text includes a Paid Subscriptions paragraph:

“We store your subscription status, tier, and billing history. If the price of your subscription changes, we also record that we told you about it, when, whether we sent a reminder, and what happened to your subscription as a result. If you ask us to erase your data, we keep that record but remove anything that identifies you, so our record of the price change stays complete. We can only erase your data once your subscription has ended. While it is active, paused, in a free trial or has a payment outstanding, we need that data to provide the subscription you are paying for, so please cancel it first and then ask again.”

The last two sentences describe the refusal behavior above in plain language for your subscribers, and the middle two describe how a price-change notice survives an erasure request without identifying anyone — see Price Change Considerations for more on that record.

This paragraph is suggested text you can edit like any other paragraph on the Policy Guide screen, and it only appears for a show billed through built-in membership. A show gated by a bridge plugin (MemberPress, WooCommerce Subscriptions, PMP, RCP) doesn’t get it — that plugin already discloses its own billing data and its own erasure limits, and Benecaster doesn’t duplicate them.

Your Responsibilities

Benecaster provides tooling to help you comply with privacy regulations — configurable retention, manual erasure, GeoIP controls, and telemetry opt-ins. But the plugin cannot guarantee compliance on your behalf. You are responsible for:

  • Your site’s privacy policy accurately describing how subscriber data is collected and used.
  • Responding to subscriber data requests (access, correction, erasure) within the timeframes required by applicable law.
  • Configuring retention windows that match your legal obligations in the jurisdictions where your subscribers live.
  • Accounting for the billing address your subscribers give at checkout if you take payment through the built-in membership system. Benecaster does not store it — Stripe does — but it is still collected in the course of your transaction. See Billing Addresses above.
  • Disclosing the third-party scripts your site loads and the cookies they set — Stripe’s __stripe_mid and __stripe_sid on your payment pages, and Cloudflare Turnstile on your donation form if you have enabled Bot Protection. Benecaster neither sets nor reads them, but they run on your domain and your visitors meet them there. See Third-Party Scripts on Your Site above.
  • Obtaining consent for those scripts if your jurisdiction requires it. Benecaster ships no consent banner and no lazy-load option for either.
  • Meeting anti-spam requirements (such as CAN-SPAM) for the emails your site sends — including a valid business or postal address where the law requires one. Set it once per show under Settings → [Show] → Emails → Business address (or on the Details step of the setup wizard when you create the show), and Benecaster adds it as its own line in the footer of every email that show sends. Leave it blank and no address line is shown — the plugin does not add one for you.
  • If you are subject to CCPA: understanding your obligations as a “business” under the California Consumer Privacy Act and whether the data Benecaster processes falls within its scope.

If you’re uncertain about your obligations, consult a legal professional familiar with data protection law.

See Also

Need this built rather than just documented? See our services →

Last updated