TDM retrieval and opt-out

Releazd is developing a process that technically analyses occurrences in publicly accessible DJ sets and recognises tracks using an acoustic fingerprint.

Retrieval is limited to technical analysis and follows three defined steps:

1. 01
   Temporary retrieval

   A publicly accessible set is retrieved and processed only for the duration of the analysis.

2. 02
   Acoustic fingerprint

   The system derives technical audio features to compare occurrences and stable track identities.

3. 03
   Verifiable deletion

   Once analysis is complete, the temporary audio file is deleted and that deletion is recorded technically.

Technical retrieval relies on Section 44b of the German Copyright Act. It requires lawful access and the absence of an effective reservation of rights. For works made available online, such a reservation must be machine-readable.

This notice does not claim that every legal question concerning text and data mining has been finally settled. Releazd reviews the process continuously and respects effective reservations as well as direct opt-outs.

Machine-readable reservation

Before retrieval, the fetcher evaluates the robots.txt file. A restriction that applies to releazd-tdm or to crawlers generally is respected. One unambiguous example is:

User-agent: releazd-tdm
Disallow: /

Other potential TDM signals such as tdmrep, noai or additional metadata are not currently evaluated automatically. If you use one of them, please also email us.

If the affected material is hosted on a platform whose robots.txt you cannot edit yourself – such as SoundCloud – please use the email route. We can block a profile you manage independently of the platform.

Direct opt-out by email

Rights holders and authorised representatives may permanently block a profile, a domain or individual set URLs. Send the relevant URL and the requested scope of the block to:

We review and register an opt-out as quickly as possible and no later than seven calendar days. Once it has been entered in our block register, the system prevents future retrievals automatically and permanently until the block is withdrawn. A profile-level block also covers the set URLs recorded beneath it.

Product token

releazd-tdm

Version example

releazd-tdm/0.1

Contact

contact@releazd.com

The product token may appear in server logs together with a technical version number. It supports a targeted robots.txt rule and allows enquiries to be matched to the fetcher.

This information page contains no tracking, forms or embedded content. Releazd sets no analytics or advertising cookies. The hosting provider may create technically necessary server logs when the page is loaded.

Cloudflare, the hosting and security service, currently sets the __cf_bm cookie. It helps detect and mitigate automated, abusive traffic and expires after 30 minutes of inactivity, according to Cloudflare. Releazd does not use this cookie for advertising or usage analytics. Cloudflare’s technical explanation.

Email is used only to handle your message and any opt-out request.