Who can end access before a published date

Two entries publish a way for access to end other than on a date. One states that an existing customer may lose access after fifteen days of inactivity once a legacy period begins. One reserves the right to replace models at any time. For eleven others, an edit to a page is the mechanism. As of 2026-09-12.

Fig. 1 Filled where the vendor has announced something in that column, hollow where it has not.

What each entry has published about losing access other than on a date. Recorded 2026-09-12.
Entry	What is published	Detail
Amazon Bedrock	Access may end after 15 days of inactivity	Inside a window measured in months
LTX Studio	Models may be replaced at any time	No date to be early against
Runway	Not stated, and the credit table can change	A conversion is edited, not announced
Hailuo AI	Not stated for any earlier generation	A promoted line is all that is published
Every other entry	Nothing published	A menu line can be edited without notice

Inclusion rule. Filled from a published sentence about access ending other than on a stated date. A reader's estimate of how fast a menu could change does not fill a cell. Order. Entries publishing a mechanism first, then the rest.

1The disuse clause matches the rhythm of a series

A production alternates between bursts of generation and weeks of writing and edit. A fortnight without calls is an ordinary gap rather than a sign anybody has abandoned anything.

So a team that stopped calling a model to finish scripts can return to find the window it was counting on already spent. Nothing else in this register can remove a published runway that quickly.

Fig. 2 Only the first of the three is published as a sentence a reader can quote.

2Undefined is worse than short

The clause does not say what counts as activity, so no keep-alive can be designed with confidence that it qualifies. A defined minimum would be an inconvenience; an undefined one cannot be engineered around at all.

That is a separate finding from the fifteen days, and the register records the two on different rows for that reason.

3For most entries the mechanism is a page edit

Eleven entries publish no date, no state and no clause, so a model becomes unavailable because a line disappears from a priced page. No date precedes it and no notice follows.

That event is only visible to somebody comparing two dated readings, which is what the data file exists to make possible.

How access can end before the date
Once the Legacy period begins, existing customers may lose access after 15 days of inactivityAmazon Bedrock, model lifecycle / recorded 2026-09-22
Published notice
The pricing page reserves the right to update, modify or replace available models and does not guarantee continued availability of any specific modelthe only one of its kind hereLTX Studio, pricing / recorded 2026-09-12
Notice before the credit table changes
No date announced (as of 2026-09-12)nothing publishedRunway, pricing page / recorded 2026-09-22
Whether earlier Hailuo generations are still reachable
No date announced (as of 2026-09-12)not statedHailuo AI, home page / recorded 2026-09-22

4Sources

Dates come from the vendor that makes the model; menus come from the app, and both are linked on the calendar. Read 2026-09-12. What counts as a date is on sourcing. Nearby: Who moves you, Published states, Older generations.