LLMSwaps

Which model each app runs today, and when it last changed

Material that was never in somebody else's product

Where the weights are downloaded, generation happens on hardware the user controls and the output never enters anybody's product. A withdrawal of the listing cannot reach it. What makes the material usable afterwards is the licence printed on the model card, not any retention policy. As of 2026-09-22.

What downloading the weights settles about material and its terms. Recorded 2026-09-22.
What the page is askedWhat Wan-AI publishesWhat that leaves open
Is disposal of material addressedNot applicable, nothing is held for youOutput exists only where you generated it
What a withdrawal reachesThe listing, and not the copy or its outputThe download commands are on the model card
What governs use of the outputThe licence stated on the cardRead the licence text, not a summary of it
What you take on insteadBackups, storage and your own retentionA cost you control rather than a policy

Inclusion rule. Read from the publisher's repository listing and one model card. Retention behaviour of hosted services that serve these weights belongs to those entries. Order. What does not apply first, then what replaces it.

1The column inverts rather than emptying

Every other blank here means nobody has said what happens to material inside a product. This one means there is no inside: the files are already where the customer put them, and no announcement can change that.

Recording it as not applicable keeps the column honest. A reader comparing cells would otherwise treat the most settled arrangement in the register as the least informative.

The retention problem moves rather than disappearingOn hosted entries somebody else keeps the files, badly or well, under a policy that can change. Where the weights are downloaded the output was never in anybody's product, and the keeping becomes the production's own work.The weightsA copy on your own storage,under the stated licenceNothing reaches itUsable after the listingis goneThe outputWritten wherever your pipelinewritesNever enters a productNo disposal policy to readThe choresBackups, retention, hardware, aninference stackYours from day oneA budget line instead ofan announcementGeneration on hardware you controlWhat replaces a retention policy
Fig. 1 Not applicable rather than missing: the most settled arrangement here, and the one with the most chores.

2Permission is the fact worth publishing

What a held copy needs is not retention but terms, and the card states them. That is a different kind of commitment from a date, and it is the reason this entry has a reading in a column about material at all.

It settles what may be done with the output. It does not promise the weights keep running on next year's toolchain, and nothing obliges the publisher to keep publishing anything.

3The retention problem moves rather than disappearing

Somebody still has to keep the files, verify the backups and decide how long to hold them. On every other entry that work is done badly by a vendor; here it is done badly or well by the production itself.

That is the honest trade. The succession reading for this entry describes the same swap from the other side: somebody else's schedule exchanged for your own operations.

4Sources

Read from the repository listing on huggingface.co, 2026-09-22. The whole entry is on Wan-AI, and the column it sits in is on Stored work. Same column, other entries: fal, LTX Studio.