Privacy

What we collect, and why.

Who runs ShareAPod

ShareAPod is run by Off Byte One LLC, a company in the United States. “We” in this policy means Off Byte One LLC. For anything about your data, email us at [email protected].

What we store when you paste a link

The link you pasted, the show or episode details we find for it (title, artwork address, length, date, description), and the links we find for it in each app.

A permalink can be opened by anyone who has its address, so don't paste private links, such as a paid feed with a password or token in it. If a paste fails, we keep the link with the failure report for up to 14 days so we can fix the problem.

What we don't collect

There are no accounts. We don't tie a permalink to whoever made it. We don't sell your data or use it for advertising.

Analytics, only if you accept

PostHog analytics doesn't load until you choose Accept on the cookie banner. If you accept, PostHog records the pages you view, how fast they load, and what you do on them: pasting a link, opening an app, copying a permalink, sorting the list, and the like. Events on a permalink include its code, so we can see which links get used.

PostHog stores a random identifier for your browser in a cookie and local storage, which ties your visits together. We never give it your name or email address. PostHog works out your approximate location (country, region and city) from your IP address, then discards the address. It holds this data in the United States.

Session recording, click autocapture and heatmaps are switched off, and a link pasted into our address bar is replaced with a placeholder before anything is sent.

To change your mind, use Cookies at the bottom of any page. Reject stops analytics and deletes PostHog's identifier from your browser.

Error reports

When something breaks, we send a report to PostHog so we can fix it: the error, the page it happened on, and your browser and device type. From your browser, only if you accept analytics. Errors on our servers are always reported, with the kind of page that failed and nothing that identifies you.

Permalink visit counts

We count views of each permalink in our own database, so we can see which links are actually being opened. A view stores the time, the referring site's domain (not the full page URL), a country code, and a salted one-way digest of your IP address and browser that changes every day.

We never store the IP address itself, and the digest can't be used to follow you from one day to the next. Visit records are deleted after 180 days.

We also keep a daily total of how many times each app's button was opened on each permalink. That total stores nothing about who opened it.

Stored in your browser

Without asking, because they only remember choices you make: your cookie-banner choice, your preferred app and the order you sorted the list in (local storage), the app you last opened on a permalink, for that tab only (session storage), and your theme and language if you change them (cookies).

They stay in your browser. Clearing this site's data in your browser removes them.

Server logs and failure reports

Our hosting providers keep request logs (IP address, browser, the address requested, time) for debugging and abuse prevention, for the periods they set.

Failure reports, including any note you write when you report an issue with a link, are deleted after 14 days, so leave anything personal out of the note.

For pastes from sites we don't support, we keep a daily count per domain (such as example.com, never the full link) for up to a year, so we can see which apps to add next.

Abuse prevention

Rate limits use server-keyed digests of client addresses, never the addresses themselves. Inactive limits are deleted by daily maintenance.

Service providers

Vercel hosts the site, Neon runs our database, Cloudflare sits in front of both, and PostHog runs analytics and error reports. They process data for us and are based in the United States, so your data is handled there.

Podcast catalogs and apps

To find a podcast in each app, our servers query Podcast Index, the podcast's own feed, its hosting service (for example Simplecast), and the catalogs of the apps we link to, such as Apple Podcasts, Spotify, YouTube, Deezer and iHeartRadio. These requests carry only the show and episode details, never anything about you.

Listening and opening apps

Artwork, and audio in the Play here player, load straight from the podcast's own hosts, which receive your IP address and browser details like any web request and may count the play.

When you open an app or another site from a permalink, that service's own privacy policy applies.

Your rights

We use analytics only with your consent. Everything else here (visit counts, logs, failure reports, rate limits) is what we need to run ShareAPod and keep it working.

Depending on where you live, you can ask to see, correct or delete data about you, object to how we use it, or complain to your data protection authority. We hold almost nothing that identifies you, so tell us what to look for, such as a permalink or a date, when you email [email protected].

Removing a permalink

A permalink holds nothing about who made it, and everyone who pastes the same link gets the same permalink, so other people may have shared it too. That's why we don't delete one just because we're asked.

We do remove a permalink that exposes private information, such as a private feed address, or that infringes someone's rights. Email [email protected] with the permalink and what's wrong. If someone saved a copy elsewhere, we can't control that.

Changes

When this policy changes, we update this page and the date below.

Last updated November 18, 2026.