A plugin's licence text sets limits its marketing skips

The audio task

A producer finishing a commercial mix wants to know whether the plugins in the session actually permit that use, and whether anything processed through them was, or could be, used to train someone else's model. The marketing page for a plugin rarely answers either question; the end-user licence agreement usually does, in language most sessions never get read before a deadline.

What the documents show

Three vendors publish three different answers. iZotope's software licence agreement, dated 13 August 2026 in its current version, grants a non-exclusive right to run the software on one computer at a time and restricts timesharing and consulting use, but says nothing about who owns audio processed through the plugin or whether that audio trains a model. Waves' end-user licence agreement, last updated in September 2026, is more specific: it grants a licence for the applicable licence term, confirms the user retains ownership of Inputs and Outputs, and states that Waves does not use Inputs or Outputs to train or improve artificial intelligence or machine-learning models unless the user separately agrees. Native Instruments' agreement, effective 1 July 2026, permits commercial or non-commercial use of its sample and instrument content without extra permission, but separately forbids the licensee from using the product itself to train artificial intelligence systems, a clause protecting Native Instruments' own catalogue rather than describing what a user may do with a finished track.

Rights status

None of these three documents claims to settle copyright in a finished mix. iZotope's agreement is silent on output ownership. Waves' agreement affirmatively assigns output ownership to the user and states its own default position on AI training. Native Instruments' agreement addresses training only in the direction of protecting its own content from being mined, not in the direction of a user's rights over a finished recording. Reading three EULAs from three vendors used in one session produces three different, non-interchangeable statements, not one shared standard.

What to check before you use it

This is an editorial checklist, not legal advice. Before a commercial release, confirm whether the EULA states who owns the processed output, whether it mentions AI or machine-learning training of user audio at all and in which direction, whether the licence is tied to an active account that could revoke access, and whether the document on screen today is the version installed with the plugin, since licence text changes between versions without the software prompting a re-read.

• Does this plugin's current EULA say anything about ownership of the audio it processes?
• If the EULA is silent on AI training, does that mean it does not happen, or only that it is not disclosed here?
• Would losing access to this vendor's account affect a track already delivered to a client?

A EULA is a maintained legal document, not a one-time read. The three vendors compared here answer the same question about commercial use and AI training in three incompatible ways, and only the current, dated text of each agreement, checked at the time a track ships, tells a producer which one actually applies.