Update default persist last message retention values

The persist last message feature no longer defaults to 365 days for all
paid accounts. Updated all references to reflect the actual defaults:
24 hours (free), 30 days (paid), up to 365 days on request (enterprise).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: kennethkalmer

src/pages/docs/channels/index.mdx

@@ -183,7 +183,7 @@ The rules related to message storage are:
 
 | Rule | Description |
 |------|-------------|
-| Persist last message | If enabled, the very last message published on a channel will be stored for a year. This message is retrievable using [rewind](/docs/channels/options/rewind) by attaching to the channel with `rewind=1`. If you send multiple messages in a single protocol message, for example calling `publish()` with an array of messages, you would receive all of them as one message. Be aware that presence messages are not stored and that messages stored in this manner are not accessible using [history](/docs/storage-history/history). Note that for each message stored using this rule, an additional message is deducted from your monthly allocation. |
+| Persist last message | If enabled, the very last message published on a channel will be stored for the configured [retention period](/docs/storage-history/storage#persist-last-message). This message is retrievable using [rewind](/docs/channels/options/rewind) by attaching to the channel with `rewind=1`. If you send multiple messages in a single protocol message, for example calling `publish()` with an array of messages, you would receive all of them as one message. Be aware that presence messages are not stored and that messages stored in this manner are not accessible using [history](/docs/storage-history/history). Note that for each message stored using this rule, an additional message is deducted from your monthly allocation. |
 | Persist all messages | If enabled, all messages published on a channel will be stored according to the storage rules for your account. This is 24 hours for free accounts and 72 hours for paid accounts. Messages stored in this manner are accessible using [history](/docs/storage-history/history). Note that for each message stored using this rule, an additional message is deducted from your monthly allocation. |
 
 The rules related to security and client identity are:

src/pages/docs/channels/options/rewind.mdx

@@ -30,7 +30,7 @@ If the attachment is successful, and one or more messages exist on the channel p
 Any `rewind` value that cannot be parsed either as a number or a time specifier will cause the attachment request to fail and return an error.
 
 <Aside data-type="note">
-If you have enabled the [persist last message](/docs/storage-history/storage#persist-last-message) rule on a channel, you can attach with `rewind=1` to retrieve the last message. Only the last message published can be stored for up to a year, and persist last message doesn't apply to presence or object messages.
+If you have enabled the [persist last message](/docs/storage-history/storage#persist-last-message) rule on a channel, you can attach with `rewind=1` to retrieve the last message. The last message is stored for the duration of the configured [retention period](/docs/storage-history/storage#persist-last-message). Persist last message doesn't apply to presence or object messages.
 </Aside>
 
 The following example subscribes to a channel and retrieves the most recent message sent on it, if available:

src/pages/docs/platform/account/app/settings.mdx

@@ -26,8 +26,8 @@ The following explains the configuration rules for specific [namespaces](/docs/c
 | Section | Description |
 | ------- | ----------- |
 | Namespace or channel ID | Identify the specific namespace or channel to which this rule will apply. |
-| Persist last message | Stores the last message published on a channel for 365 days, accessible via the rewind mechanism. |
-| Persist all messages | Ably stores all messages for two minutes by default. Depending on your account package, this can be increased to 24 or 72 hours. It is also possible to persist the last message sent to a channel for a year. |
+| Persist last message | Stores the last message published on a channel for the [persist last message](/docs/storage-history/storage#persist-last-message) retention period, accessible via the rewind mechanism. |
+| Persist all messages | Ably stores all messages for two minutes by default. Depending on your account package, this can be increased to 24 or 72 hours. It is also possible to [persist the last message](/docs/storage-history/storage#persist-last-message) sent to a channel. |
 | Identified | Requires clients to authenticate with a client ID to interact with channels in this namespace. |
 | TLS only | Restricts access to channels within this namespace to clients connected using TLS. |
 | Push notifications enabled | Enables publishing messages with a push payload, triggering native push notifications to registered devices. |

src/pages/docs/platform/pricing/limits.mdx

@@ -97,7 +97,7 @@ Therefore, to provide the realtime platform-as-a-service economically to all cus
 | Channel limit | Free | Standard | Pro | Enterprise |
 | ------------- | ---- | -------- | --- | ---------- |
 | **Concurrent channels**<p>*the maximum number of channels that are active simultaneously at any point*</p> | 200 | 10,000 | 50,000 | Unlimited |
-| **Default last message on channel TTL (days)**<p>*the default period that the last message on a channel is stored for, when enabled*</p> | 1 | 30 | 365 | 365 |
+| **Default last message on channel TTL (days)**<p>*the default period that the last message on a channel is stored for, when enabled*</p> | 1 | 30 | 30 | 30<br/>(up to 365 on request) |
 | **Channel creation rate (per second)**<p>*the maximum rate at which channels can be created across an account*</p> | 42 | 250 | 500 | Custom |
 | **Message publish rate per channel (per second)**<p>*the maximum rate at which messages can be published for each channel*</p> | 50 | 50 | 50 | 50 |
 | **Presence members per channel**<p>*the maximum number of clients that can be simultaneously present on a channel*</p> | 200 | 200 | 200 | 200 |

src/pages/docs/pub-sub/guides/dashboards-and-visualizations.mdx

@@ -313,7 +313,7 @@ channel.subscribe('state-update', (message) => {
 
 Enable persistence via [rules](/docs/channels#rules) in your Ably dashboard. For state-based dashboards, publish complete state snapshots as single messages rather than partial updates to ensure clients can reconstruct the full state from a single persisted message.
 
-[Persist last message](/docs/storage-history/storage#persist-last-message) stores only the most recent message on a channel, though for much longer than would otherwise be possible, up to 365 days. This is useful for state-based dashboards where only the current value matters, such as accessing the final match score or the latest sensor reading after an event concludes, and where standard message retention isn't sufficient.
+[Persist last message](/docs/storage-history/storage#persist-last-message) stores only the most recent message on a channel for longer than would otherwise be possible, with a default retention of 30 days on paid accounts. This is useful for state-based dashboards where only the current value matters, such as accessing the final match score or the latest sensor reading after an event concludes, and where standard message retention isn't sufficient.
 
 ## Authentication
 

src/pages/docs/storage-history/history.mdx

@@ -328,7 +328,7 @@ Query parameters for the `options` object when calling `history()`. Note that `u
 | limit | maximum number of messages to retrieve per page, up to 1,000 |
 | untilAttach | when true, ensures message history is up until the point of the channel being attached. See [continuous history](#continuous-history) for more info. Requires the `direction` to be `backwards` (the default). If the channel is not attached, or if `direction` is set to `forwards`, this option will result in an error.|
 
-It is possible to use the history API to retrieve the last message published to a channel that has been [persisted for up to a year with the persist-last feature](/docs/storage-history/storage#persist-last-message), if enabled, even if there is no history available from normal persisted history (if there have been no messages published on the channel for longer than the history retention period). To do this, make a history query with `limit=1` and no `start` or `end` time.
+It is possible to use the history API to retrieve the last message published to a channel that has been persisted using the [persist last message](/docs/storage-history/storage#persist-last-message) feature, if enabled, even if there is no history available from normal persisted history (if there have been no messages published on the channel for longer than the history retention period). To do this, make a history query with `limit=1` and no `start` or `end` time.
 
 ### Continuous history <a id="continuous-history"/>
 

src/pages/docs/storage-history/storage.mdx

@@ -3,7 +3,7 @@ title:  Message Storage
 meta_description: "Explore the different ways Ably can handle Message Storage"
 ---
 
-Ably stores all messages for two minutes by default. This can be increased up to a year, or longer, depending on your account package. It is also possible to persist the last message sent to a channel for a year. Ably [integrations](/docs/platform/integrations) can also be used to send messages outside of Ably for long-term storage.
+Ably stores all messages for two minutes by default. This can be increased up to a year, or longer, depending on your account package. It is also possible to persist the last message sent to a channel for a configurable retention period. Ably [integrations](/docs/platform/integrations) can also be used to send messages outside of Ably for long-term storage.
 
 ## Default message storage - two minutes <a id="default-persistence"/>
 
@@ -44,11 +44,11 @@ Messages can be retrieved using the [history](/docs/storage-history/history) fea
 
 Note that every message that is persisted to, or retrieved from, disk counts as an extra message towards your monthly quota. For example, with persistence enabled a published message counts as two messages for your monthly quota. If the message is then retrieved another message will be deducted.
 
-## Persist last message - 365 days <a id="persist-last-message"/>
+## Persist last message <a id="persist-last-message"/>
 
-You can persist just the last message sent to a channel for one year by setting a [rule](/docs/channels#rules). Note that this does not apply to [presence messages](/docs/presence-occupancy/presence) or [object messages](/docs/liveobjects).
+You can persist the last message sent to a channel by setting a [rule](/docs/channels#rules). The default retention period is 24 hours on free accounts and 30 days on paid accounts. Enterprise accounts can extend this up to 365 days by [contacting Ably](https://ably.com/support). Note that this does not apply to [presence messages](/docs/presence-occupancy/presence) or [object messages](/docs/liveobjects).
 
-Messages persisted for a year can be retrieved using the [rewind channel option](/docs/channels/options/rewind), or from the REST history API using [certain parameters](/docs/storage-history/history#channel-parameters).
+Persisted messages can be retrieved using the [rewind channel option](/docs/channels/options/rewind), or from the REST history API using [certain parameters](/docs/storage-history/history#channel-parameters).
 
 The following diagram illustrates persisting the last message sent on a channel: