Privacy and data use

Account and workspace information

Accounts, Network membership, roles, publishing records, uploaded files, and support requests are processed to provide the service. A signed-in workspace is different from a public listener website. Publishing content makes the selected audio, artwork, and release information available to an audience.

Published content and draft previews

Public podcast pages and feeds are intended to be read by listeners, podcast directories, and search engines. Review titles, descriptions, artwork, and audio before publishing. A draft preview link can provide access to unpublished material; share it only with intended reviewers.

Browser storage and listening

Browser storage supports functions such as sign-in, preferences, playback state, and pending upload queues. Clearing it can remove playback or upload recovery state. Listener playback measurements are processed for audience reporting; those measurements are separate from public marketing-page measurement.

Optional public-site statistics

Optional statistics are off until you choose Allow statistics in the footer. They count public page views and explicit signup-entry or contact clicks; they do not measure completed accounts or identify individual visitors. Signed-in visitors are excluded from ordinary acquisition counts. Do Not Track and Global Privacy Control signals keep this measurement off.

Events contain an allowed public pathname, an event name, an environment label, and a version marker. They do not include account IDs, emails, form values, page text, query strings, fragments, or referrers. Our retention policy is 180 days for daily aggregate counts and seven days for separate diagnostic counts, with cleanup checked daily. A simple on/off browser preference remembers your choice and is not a visitor identifier. You can change the choice in the footer. Network data may be processed separately for delivery, operational logging, and short-lived abuse prevention.

Service providers and network requests

Hosting, authentication, database storage, media storage, transactional email, and billing rely on service providers. When a browser contacts the service or an external checkout or listening platform, the receiving server can receive network information such as an IP address and user agent. Omitting those fields from an analytics event does not prevent the server from receiving them in the request.

Questions about your data or published content

For account or workspace questions, contact [email protected] or sign in and open Help & Support. For podcast material published by a Network, contact that publisher about its content and publication choices. Third-party listening and payment services have their own privacy information.