Practical guide

Podcast RSS ownership: know what you control

Last materially reviewed 2026-09-19

Quick answerThe audio file, hosting account, feed address and directory listing are separate pieces of control.
What to know

Draw the ownership map

Put the show in the middle of a page and add four surrounding records: original media, hosting account, RSS feed and directory listings. Write the responsible organization beside each. Do not include passwords. This map often reveals that the person uploading episodes is not the person who can recover the account or authorize a move, which is exactly the distinction you need to understand.

What to know

Separate operational access from ownership

A producer may need to edit titles and schedule episodes without controlling billing or the client relationship. Granting enough access to do the job is different from making that person the account owner. Confirm the platform’s actual roles and the organization’s intended arrangement. A shared login may appear convenient at first, but it makes individual responsibility and later access removal harder to explain.

What to know

Keep durable references

Save the exact current feed address, directory URLs and approved recovery contact in an appropriate business record. Also retain original episode files and artwork independently. A website link to a listening application is not a substitute for the underlying feed reference. When something breaks, these records let you describe the affected object without guessing which of several similarly named shows or accounts is involved.

What to know

Use the map before a change

Review the map before hiring a producer, moving hosts or handing a show to a client. Ask who must approve each change and what confirms completion. This is not a legal determination of intellectual-property ownership; it is a practical inventory of control and responsibility. If the parties disagree about ownership, resolve that separately before making technical changes. The best migration checklist cannot repair an unclear agreement about who is entitled to move the show.

Continue when useful

Next: Who should pay for an agency-managed podcast?

Decide who owns the continuing relationship before deciding whose card pays the hosting bill.

Open Who should pay for an agency-managed podcast? →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Transistor multi-show hosting — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19
  2. Transistor for agencies: account responsibility — Merchant documentation · transistor.fm · Merchant-controlled · checked 2026-09-19