zPodRSS first. Bandwidth off the bill.

Privacy Policy

Effective date: November 8, 2026

zPod is operated by Bristlecone IT Services, LLC, a Tennessee limited liability company (“Bristlecone,” “we,” “us”). This policy says what we keep, why we keep it, and who else sees it. It covers zpod.cc, zPod Studio, the API and the hosted tools, show and network sites hosted on zPod, and the feeds and audio zPod serves.

Account Data

Your studio account stores an email address, a display name, a password (stored only as a hash), optional passkeys, optional authenticator-app settings, the studio or organization you belong to, and which version of the Terms you agreed to and when. We use that to sign you in and to know which shows you can manage. Listeners who sign in for Personal Feeds also have an account, with an email address, a display name and a password stored only as a hash.

Show and Episode Content

Studios upload shows, episodes, artwork, and notes. We host that content so listeners can play it and apps can fetch the feed. You decide what is public. Podcasters own their shows and content; see Your Content in the Terms of Service.

A show can list a feed owner email. When it is set, it is published in the show’s feed for podcast apps and directories. We send the feed-address check only to that address, never to a studio account’s sign-in email in its place; if a show has no feed owner email, we do not send the check. When a show is created in Studio, the feed owner email starts as your account’s sign-in email, including when our staff create it for you during Support Access. An imported show takes the owner email from the feed it was imported from, if that feed has one. You can change or clear it in Studio.

Payments

Stripe processes Audio plan billing. Link, LLC (part of Stripe) is the seller of zPod plans and add-ons and receives your name, billing address and payment details to charge you and calculate tax; Link’s privacy practices apply to what it receives. You pay through Stripe Checkout, which collects a card for the 10-day Audio trial. You manage cards and invoices in Stripe’s Customer Portal. We keep the billing records we need to match your studio to that plan. We do not store full card numbers.

Stripe publishes its own privacy policy at stripe.com/privacy.

Creator Payments: Tips, Subscriptions and Payments

Creator Payments are available only to US studios we have enabled for them. A Tip, Subscription or Payment is sold by the creator through the creator’s own Stripe account, and Stripe processes it. The details you enter at checkout go to Stripe and to the creator’s Stripe account, and the creator’s own privacy practices apply to what the creator receives. zPod does not charge a fee on Tips, Subscriptions or Payments. Refunds and disputes are between the listener and the creator. A creator’s own Tip or Subscription page outside zPod belongs to the creator, and anything bought there falls under that site’s terms.

When you become a Supporter of a show that has a Supporter Feed, we keep the email address and private feed token needed to deliver that feed. Canceling the Subscription ends your Supporter Feed access and stops future Payments. We keep the Subscription record, including your email address, for the creator's records.

When you make a Payment and the creator collects a shipping address, we keep that address so they can send the item. We delete those addresses 90 days after the Payment. Tip records do not store your email.

Email We Send

All zPod mail comes from a zPod no-reply address. Replies to it are not delivered, so write to support@bristleconeit.com instead. We send:

These messages are operational. They are not a marketing list.

Measurement

When someone downloads an episode, we count it so Studio can show downloads, unique listeners, and which podcast apps, device types and countries they come from. We keep the country, not the IP address. Since October 27, 2026, we read the app’s User-Agent once, keep only the app and the type of device (Phone, Tablet, Desktop, Smart Speaker, Watch, Car, Web Browser or Unknown), and do not store the User-Agent itself. Bot traffic and duplicate Apple Watch requests are not counted as downloads.

Analytics records written before October 27, 2026 keep the first part of the User-Agent (up to 100 characters) instead of the app and device type. We keep analytics records for three months, so those older records are gone by about January 27, 2027.

To count a unique listener without keeping who they are, we combine the IP address and User-Agent into a keyed hash (an HMAC). The key is a random value made for each UTC day, and we delete each day’s key after the following day ends. Because the key changes daily, the same listener has a different hash each day, and a hash cannot be turned back into an IP address. For the same reason, the 30-day reach figure in Studio counts listener-days: each listener once for each day they listened. Before October 27, 2026, listener hashes were made without a key; we have cleared those past hashes and kept only the counts.

Analytics data we recorded before October 27, 2026 may include a value derived from a Supporter’s private feed token. That data is deleted automatically within about 3 months of when it was recorded.

The count is for your stats. We do not sell it as a third-party advertising product.

Security and Abuse Prevention

Bot check. Sign-up, password sign-in, email-link sign-in requests, password reset requests and the Cancel a Subscription form use Cloudflare Turnstile to check that a person is using the form. Passkey sign-in does not use it. Turnstile runs in your browser and sends information about the browser and the request, including your IP address, to Cloudflare for that check. Cloudflare’s privacy policy is at cloudflare.com/privacypolicy.

Sign-in limits for connected apps. When an app registers to connect to a zPod account through OAuth sign-in, we limit how many registrations can come from one IP address in an hour. To count them we keep a keyed hash of the IP address, not the address, and delete those counting records after they expire. A registered app that never received access is deleted after 30 days.

Audit records. We keep audit records of security-sensitive actions, such as adding or removing a passkey, turning an authenticator app on or off, creating an API token or webhook, publishing through the API, and actions platform staff take. An audit record names the account and, where it applies, the staff member who acted. Audit records for API and connected-app tokens include a shortened (truncated) IP address, never the full address. We keep audit records for 1 year, to protect accounts and investigate misuse.

Support Access. To help with a support request, platform staff can view a studio as its user. These sessions are time-limited and logged. While viewing, staff cannot change sign-in details, passkeys, authenticator apps, API tokens or webhooks, most studio settings, invitations, Stripe payouts, the feed owner email or feed lock, the Apple Podcasts claim, payment recipients, the Tip link or custom domains, and cannot delete anything. Staff can edit show and episode content. If staff add a new outbound link to a show’s content while viewing a studio, we email the studio’s owners a list of the added links and keep an audit record of it.

Retention and Deletion

Studio owners and organization admins can delete a show after a confirmation step. Deleting a show removes it from the studio. The public feed, episodes, files, and listener feeds go with it. Deleting a show also deletes its Supporter, Subscription, Tip and Payment records, including email addresses. That cannot be undone.

Account records stay while the studio is open. To close an account, email support@bristleconeit.com from the Studio Account email so we can match the request to the studio.

Contact

Questions about this policy or your data: open Support from the signed-in Studio, or email support@bristleconeit.com. For privacy requests and legal notices, email legal@bristleconeit.com or write to Bristlecone IT Services, LLC, PO Box 296, Townsend, TN 37882. Write from the Studio Account email when you can so we can match the request to the studio.

Changes to This Policy

We may update this policy. When we do, we post the new version on this page with a new effective date.

Terms of Service · Trust & Safety