Third-Party Services and Licence Notices

1. What these references establish

A developer-documentation page explains how a service interface works; developer terms govern permitted use; and a privacy policy describes personal-information practices. These are distinct documents. Linking to any of them is not proof of a paid licence, approved API application, copyright clearance, endorsement, or compliance audit.

The references below include providers mentioned in previous Zene material as well as sources visible in the current implementation. A historical reference is not a statement that an integration is active. Zene does not claim that Spotify, Last.fm, SoundCloud, Musixmatch, or Radio.co is a contracted supplier merely because a link appears here.

2. Sources visible in the service

The implementation includes YouTube-related discovery and playback, Radio Browser station discovery, Podcast Index catalogue requests, and LRCLIB lyric searches. Image and entertainment discovery also use automated retrieval from sources such as Pinterest, Bing, Google Trends, Shazam, IMDb, Box Office Mojo, JustWatch, Star Style, Who’s Dated Who, and Kworb. Some requests use a retrieval intermediary such as Firecrawl.

A radio directory is not the broadcaster and does not license every recording in a stream. A lyrics response does not necessarily clear rights in the lyrics. A Pinterest search result does not give permission to reuse the underlying photograph as a public cover. Metadata, audio, video, artwork, and text must each be considered under their applicable rights and provider terms.

Zene can cache and refresh retrieved information for product operation, but a technical cache is not a legal exception. Limits concerning purpose, retention, attribution, refreshing, removal, territories, and commercial use depend on the source and the rights actually granted. A rights holder can identify a disputed use through the copyright contact.

3. Provider documentation, developer terms, and privacy notices

These links are provided for reference and should be read in their proper context. They do not incorporate an unlimited list of developer obligations into a consumer agreement, make a scraped integration an official API, or represent that a provider has authorised Zene’s particular implementation. Provider documents may change independently of this notice.

For YouTube content, the YouTube user terms and Google Privacy Policy are relevant to the user’s interaction. Any separate permission needed by Zene for extraction, caching, playback, commercial use, or other integration behaviour remains Zene’s responsibility. Other providers similarly retain their own access and licensing conditions.

4. Software licences and distribution notices

Zene uses open-source and separately licensed software. The web stack includes Svelte, SvelteKit, Vite, Tailwind CSS, TypeScript, Firebase client libraries, and Sentry integration. The applications use Kotlin, Compose Multiplatform, coroutines and related Kotlin libraries, Ktor, Koin, and relevant platform libraries. The actual set depends on the release and platform.

This is an overview, not a complete software bill of materials or a substitute for required licence text. Each distributed release needs an inventory of direct and transitive components, versions, copyright notices, licence texts, and any required attribution or source offer. SDK service terms and proprietary platform agreements must not be described generically as MIT or Apache-2.0.

Component licences continue to govern their respective components. If a required notice is missing, contact work@zenemusic.co with the application version, platform, and component concerned. A request for missing notices does not waive any right already granted by the component’s licence.