Privacy
BitePods collects almost nothing about you
You don't need an account to use BitePods, and it keeps no record of who made or played a clip. A clip is described entirely by its own link: the publisher's address and two timestamps. This page says what is collected, why, who else sees it, how long it is kept, and how to remove it.
No account needed
Signing in is optional and only keeps your history on every device.
No ads, no tracking
No pixels, no ad cookies. Visits are counted without identifying you.
No copies of audio
Clips play from the publisher's own file. Downloads pass through and aren't kept.
Your history stays with you
Signed out, your bites live in your browser, and we never see them.
When you paste a link or search
Our server fetches the address you pasted and asks public podcast directories about it on your behalf: Apple Podcasts, fyyd, gpodder and YouTube. Those requests carry the address and the show's name, not who you are. Answers are cached on Cloudflare's network for up to a few hours, so the next person pasting the same link gets it faster. When you search by name, your browser asks Apple's directory directly, without cookies; if Apple doesn't answer, our server asks the open directories instead.
When you play or download a clip
The audio and cover art normally come straight from the publisher's own servers, or from YouTube's player when the link is a YouTube video. The publisher sees the request the way it would see any listen, their privacy policy applies to it, and the play counts for the show. A few hosts refuse to serve a page on another site; for those, and when you download a clip as an MP3, the audio or the cover passes through our server on its way to you. It is streamed through and not kept.
What stays in your browser
Signed out, your history — the last few bites you made — is a list kept in your browser's local storage, on your device only. Clearing it removes it. We never see it.
If you sign in
Signing in is optional and only keeps your history on every device. We store your email address, when you signed up and last signed in, the list of bites you made while signed in (each one's link, title, show and cover address), and, if you add one, a passkey's public key and the name of the browser that added it. A passkey's private half never leaves your device. We use your email only to send you sign-in codes: no newsletters, and it is never shared or sold. To check that an address can get mail, we look up its domain (not the address) in public DNS.
Sign-in codes are stored only as a scrambled hash and expire after 10 minutes. A sign-in lasts 30 days, and expired codes and sign-ins are swept away daily. Your account and everything kept with it stay until you delete them, which you can do from the account page at any time; deleting is immediate.
Short links
When you copy a short link, we store the pairing between its short id and the clip's own address, and we count how many times that clip is played. The count is a number per clip, not a record of who played it, and the pairing contains nothing but the clip. Pairings and counts are kept for as long as BitePods runs, so the link keeps working; the episode details remembered with a short link (its name, cover and file address) expire after a year.
AI assistants and the API
BitePods can be used from AI assistants such as ChatGPT and Claude, and from other programs, through its MCP server and its API. A request from one of them carries only what the tool needs: a show's name, a link, or two times. We don't receive your conversation, your account with that assistant, or who you are, and nothing about these requests is kept beyond the same caching and short links described above. The assistant's own privacy policy covers the conversation itself.
If you write to us
The contact form sends your message, your email address and your name, if you give one, to our inbox by email, so that we can reply. Nothing is stored on this site. We keep the email only as long as it takes to deal with it, and you can ask us to delete it.
Hosting and counting visits
BitePods runs on Cloudflare's network, which carries your connection and, like any host, processes your IP address to deliver the site and protect it from abuse, including the rate limits on sign-in and the contact form; Cloudflare's own privacy policy covers that. Sign-in emails and contact messages are sent through Cloudflare's email service. Signing in sets one cookie, which keeps you signed in and does nothing else. There is no advertising, no tracking pixel, and nothing that identifies you. Page views are counted with Cloudflare's cookieless Web Analytics, which doesn't identify you either. We also keep a few totals per day about the editor: how many episodes were opened, and how many times Play bite, Clip it and Copy were pressed. Each is one number for the day, with nothing about who pressed it. Adding ?notrack=1 to any address stops your browser being counted in either.
Questions, or removing something
Use the contact form. If any of the above ever stops being true, this page changes first.
Last updated November 3, 2026.