Developer Policy

Last Modified: 2025-02-04

At Taddy, we offer developers access to content through our API or through our own SSS feeds (collectively the "APIs"). All content available through our API must abide by our API Distribution Policy.

What our APIs cannot be used for:

Wrongfully claiming ownership. Don’t claim ownership of content that you do not create. Don't do things that may cause confusion between the ownership of content you get from our APIs and your own business.

Manipulation of content. You must not modify or adapt any content you get from our API in any way that changes the meaning or context of the original media. This includes manipulation of content by the insertion of ads.

Circumvent payment to creators. Part of the information you get back from our APIs may be a link to hosted content that requires payment to consume that content. You must not circumvent payment for access to this content.

Copying of hosted content. Part of the information you get back from our APIs may be a link to hosted content (mp3 link, image link, or video link). You must not copy or re-upload that content or pieces of that content. (Often a creators’ pay depends on knowing how many people are consuming their content and this is done by tracking the number of downloads of this hosted content)

Restrict access to content to generate revenue for your service. Your service must not restrict access to any content from from our APIs for the purpose of generating revenue. This includes a paywall, unlocking content with ads, or using in-app purchases. The exception to this term is for SSS feeds when the restriction to a piece of content is defined in the SSS feed itself.

Train AI to generate derivative work. Your service must not use any content provided by our APIs to train an algorithm that results in derivative work.

💡

A good rule of thumb is: Do you think a podcast creator would ask you to remove their content from your service if they find out their content is being used inside your service? In general, podcast creators want their podcasts to be on services that increase the number of listeners and ad revenue for their podcasts and dislike services that take away listeners and ad revenue.

The rules in our developer policy are designed to be creator-friendly. Podcast creators are providing their episodes publicly via an RSS feed but they still own all the IP and copyright to their content. One of the reasons Taddy API has millions of podcasts available through our API is because of our creator-friendly policies. Reach out to [email protected] if you have a question about this.

Unlawful Uses. Don't use our APIs to conduct illegal behaviour. Don't use Taddy for fraud or phishing or for any kind of exchange of regulated drugs, substances, devices, goods, or weapons.

Respect the creator’s copyright

Both the RSS (and SSS) specifications have a copyright attribute, which lists details on the copyright holder. For SSS feeds, the default copyright notice can be found here.

What happens to rule breakers?

If we conclude that you are violating these guidelines, you may receive a notice via email. If you don't explain or correct your behavior, we may remove access to our APIs and / or take action against your account (including permanent account suspension). We do our best to ensure fair outcomes, but in all cases we reserve the right to suspend accounts, or remove access to our APIs, without notice, for any reason, but particularly to protect our services, infrastructure, creators, users, and community. We reserve the right to enforce, or not enforce, these guidelines in our sole discretion, and these guidelines don't create a duty or contractual obligation for us to act in any particular manner.

Removing the content of a creator from your application

If a content creator lets Taddy know they want to remove their content from Taddy, we validate that they are the rightful owner of the content, remove the content from Taddy, and then send a webhook notification about their removal request to you. You must also remove the content from your service, as this is the copyrights holder of the content requesting the content be taken off.

💡

Suggestion: Include a way for podcast creators to “opt out” their podcast from your service.

Have questions or feedback

Don't hesitate to reach out at [email protected]