Does Castos Work in China? Offshore Podcast Delivery, Listener Data & ICP
Castos stores and serves your podcast media, RSS feed and embedded player through an offshore processor (Cloudflare) and names no mainland-China point of presence — so your episodes reach mainland listeners across the border, your listener analytics are processed in the US, and your own site's in-country delivery is gated by ICP licensing. A compliance-first look at the delivery path and the data behind it.
Does Castos work in China?
Whether Castos works in China is first a delivery question — can your podcast reach mainland listeners reliably — with a lighter data-handling one behind it, not a speed benchmark. Castos is a podcast host: it stores your audio and serves your feed, media files and embedded player, and where it keeps and serves that content is what decides this.
By Castos's own privacy policy, its processor "Cloudflare, which hosts this website and the Castos platform ... and stores podcast media," and "Castos is a United States company" whose information "may be processed, stored, and used in the United States and other countries where we or our processors operate." No mainland-China point of presence is named, so your episodes reach mainland listeners across the border, and reliable in-country delivery is gated by ICP licensing, not a speed dial. The lighter second question is the listener data Castos logs — hashed, by its own account, yet in its words not thereby "outside privacy law" — a cross-border transfer under PIPL. The table below is Castos's own wording and the rules it triggers.
This is a delivery-and-compliance risk map, not a verdict — your obligations turn on how you publish, your data volumes and your role. Our China team can map your Castos exposure with you →
What Castos's own documentation says about China
| Fact | Primary source |
|---|---|
| In Castos's own words: its processor is "Cloudflare, which hosts this website and the Castos platform, provides security features such as Turnstile on some forms, and stores podcast media," and "Castos is a United States company. Information may be processed, stored, and used in the United States and other countries where we or our processors operate." No mainland-China location is named, so your podcast's media, feed and embedded player are stored and served to mainland listeners from offshore infrastructure — which makes the first China question delivery and reachability. | Castos — Privacy Policy (Companies that help us operate; International Transfers of Information), retrieved 2026-10-07 |
| Even a public podcast carries a data question. Castos logs listener analytics — "We log information about each download of a public episode, including data like IP addresses and user-agents" — then hashes them: "IP addresses of podcast listeners are hashed as they are stored." Castos is explicit that this is a reduction, not an exemption: "Hashing reduces identifiability; it does not mean the data is outside privacy law in every jurisdiction." Processed in the US, this is a lighter — not absent — cross-border personal-information question for your China listeners. | Castos — Privacy Policy (Public listener analytics), retrieved 2026-10-07 |
| If you run a private or hybrid podcast, the data is heavier. Castos stores, for each subscriber, "your name, email, and a unique feed access token" and logs their listening — which it calls "more identifiable than the anonymized public analytics described above, because it is tied to a named, emailed individual rather than a hashed identifier." For your China subscribers that named data is processed in the US: a cross-border transfer PIPL governs, needing notice, separate consent and one transfer mechanism. | Castos — Privacy Policy (Private podcast subscribers; International Transfers of Information), retrieved 2026-10-07 |
| Serving a site or service to mainland visitors from infrastructure physically inside China is gated by licensing, not speed: it needs an ICP filing (ICP 备案) under the State Council's Order No. 292 and MIIT's Order No. 33, tied to a mainland hosting resource. Castos, served offshore, gives you no in-country, ICP-filed delivery path of your own — and, separately, your own public-facing site (the WordPress site that embeds the Castos player) needs its own ICP filing, whichever host serves the audio. | PRC Regulations on Telecommunications (State Council Order No. 292); Administrative Measures for the Filing of Non-operational Internet Information Services (MIIT Order No. 33) |
Sources verified by the 21YunBox compliance team on 2026-10-07.
For a mainland-China audience, the first question about Castos is not how polished the player looks — it is whether your episodes actually reach listeners inside the mainland, and how the listener data you gather along the way is handled. Castos is a podcast host: it stores your audio and video, serves your RSS feed and media files, and gives you an embedded player you drop into your site — often a WordPress site. By its own privacy policy, that media is stored and served by an offshore processor, and the company behind it is based in the United States. The episodes are reachable; what needs a second look is the cross-border path they ride, the listener data logged along the way, and the ICP filing your own public site depends on.
Castos in China at a glance
| What decides it | In Castos's own terms |
|---|---|
| What it is | A podcast host: it stores your audio and video and serves your RSS feed, media files and an embedded player (often on a WordPress site). The media is your own content, so the first China question is delivery and reachability, with a lighter listener-data question behind it. |
| Where it's served from | By its privacy policy, “Cloudflare … hosts this website and the Castos platform … and stores podcast media,” and “Castos is a United States company.” No mainland-China point of presence is named for your podcast; it is served offshore. |
| What that means for listeners | Mainland browsers fetch your feed, player and episodes across the border. Large media on a cross-border path can stall or fail in the tail even when Castos itself is healthy — a reliability exposure, not a block. |
| Listener data | Castos logs each public download (IP and user-agent), hashed and generalized to a city or region level; it says hashing “does not mean the data is outside privacy law.” Private or hybrid podcasts additionally store named subscriber data. Both are processed in the US — a cross-border-PI question under PIPL, lighter for public analytics, heavier for named subscribers. |
| Your own site | Separate from Castos: your public-facing site that embeds the player, served to mainland visitors from in-country infrastructure, needs its own ICP filing — whichever host serves the audio. |
Reachable, but served from offshore — delivery comes first
Castos is not blocked in mainland China, and nothing here is about getting around a block. The question is where your podcast is served from. In its own privacy policy Castos names a single hosting and media processor — “Cloudflare, which hosts this website and the Castos platform … and stores podcast media” — and states that “Castos is a United States company” whose information “may be processed, stored, and used in the United States and other countries where we or our processors operate.” Nowhere does it name a point of presence inside mainland China for your podcast.
So every time a listener in the mainland opens your feed, loads the player, or downloads an episode, that request leaves China, fetches from offshore infrastructure, and comes back. Podcast media files are large, and a large file on a cross-border path is exactly where reliability frays: an episode can stall mid-download or fail in the tail for some mainland listeners even when Castos itself is perfectly healthy. We describe this qualitatively on purpose — we publish China delivery numbers only alongside the method, sample and date that produced them, and we hold no first-party Castos measurement to put one here. The honest status of any offshore-served media on a China-facing site is this: reachable, but riding a border you do not control.
The lighter second question — listener data across the border
A podcast host is not an identity platform, so the data question is lighter than for a tool built around personal information — but it is not nothing, and Castos says as much itself. For public episodes it logs analytics: “We log information about each download of a public episode, including data like IP addresses and user-agents.” It then reduces the identifiability — “IP addresses of podcast listeners are hashed as they are stored” — and is refreshingly direct that this is a reduction, not an exemption: “Hashing reduces identifiability; it does not mean the data is outside privacy law in every jurisdiction.”
Run a private or hybrid podcast and the picture is heavier: Castos stores “your name, email, and a unique feed access token” per subscriber and logs their listening, which it describes as “more identifiable … tied to a named, emailed individual rather than a hashed identifier.” Either way, that data is processed in the United States. For your China listeners and subscribers, that is a cross-border transfer of personal information under PIPL — lighter for the hashed public analytics, heavier for named subscribers — carrying the handler’s duties of notice, separate consent, and one transfer mechanism. Whether, and how heavily, this lands on you depends on your volumes and your role; it is a risk to size with counsel, not a blanket verdict.
Why in-country delivery is a licensing question — ICP
The reason you cannot simply “switch on” a mainland point of presence for your podcast is not engineering — it is licensing. Delivering a site or service to mainland visitors from infrastructure physically inside China turns on an ICP filing (ICP 备案) under the State Council’s Order No. 292 and MIIT’s Order No. 33, tied to a mainland hosting resource. Served from offshore, Castos gives you no in-country, ICP-filed delivery path of your own — which is why reliable in-mainland delivery is a licensing question, independent of how fast any network is.
There is a second, separate ICP point that catches podcasters out: your own public-facing site — the WordPress site your Castos player is embedded in — needs its own ICP filing to be served to mainland visitors from in-country infrastructure, whichever host serves the audio behind it. Choosing a better delivery path for your episodes does not remove that obligation on your domain. As with everything here, treat this as a delivery-and-licensing risk map rather than a legal opinion: how it applies turns on what you publish, from where, and to whom — worth settling with counsel before you build.
Where 21YunBox fits — a compliant overlay, not a migration
You keep publishing on Castos exactly as you do today. We add the one piece an offshore-served podcast host cannot: compliant, ICP-filed delivery from inside the mainland, set in front of your existing origin — no rebuild, no second codebase, and no move off Castos. Instead of mainland listeners pulling your feed, player and episodes across the border, they load them from in-country, ICP-filed infrastructure that takes the border out of the critical path. Our China team maps how your podcast actually reaches the mainland, what listener data crosses the border, and whether the site your player lives on needs its own ICP filing — so the delivery and the compliance are handled together.
Related reading:
