From cab2f797c188b3439dfcb4a58f08505e2803c939 Mon Sep 17 00:00:00 2001
From: Austin Lai <76412946+alai97@users.noreply.github.com>
Date: Wed, 11 Jun 2025 16:07:52 -0700
Subject: [PATCH] FMEPRD-186

---
 .../ios-android-browser-sdk-does-the-sdk-cache-expire.md   | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/docs/feature-management-experimentation/20-sdks-and-infrastructure/faqs-client-side-sdks/ios-android-browser-sdk-does-the-sdk-cache-expire.md b/docs/feature-management-experimentation/20-sdks-and-infrastructure/faqs-client-side-sdks/ios-android-browser-sdk-does-the-sdk-cache-expire.md
index 279784ec525..12774d463b4 100644
--- a/docs/feature-management-experimentation/20-sdks-and-infrastructure/faqs-client-side-sdks/ios-android-browser-sdk-does-the-sdk-cache-expire.md
+++ b/docs/feature-management-experimentation/20-sdks-and-infrastructure/faqs-client-side-sdks/ios-android-browser-sdk-does-the-sdk-cache-expire.md
@@ -14,4 +14,9 @@ The Split mobile (iOS and Android) and JavaScript Browser SDKs download a local
 
 ## Answer
 
-The SDK will consider the cache stale if it hasn't been updated for 90 days. In such case it will issue a full download of FME definitions. This is an unlikely scenario since the SDK is continuously synching changes from the Harness FME servers and updating the cache.
\ No newline at end of file
+- For the JavaScript SDK, version 11.2.0 introduces a default cache expiration period of 10 days, which is configurable using the `LOCALSTORAGE` setting. After expiration, the SDK will refresh the cache from scratch. 
+- For the Browser SDK, version 1.2.0 introduces a default cache expiration period of 10 days, which is configurable using the `InLocalStorage` setting. For more information, see [Configuring LocalStorage cache for the SDK](/docs/feature-management-experimentation/sdks-and-infrastructure/client-side-sdks/browser-sdk#configuring-localstorage-cache-for-the-sdk).
+- For the Android SDK, version 5.3.0 introduces a default cache expiration period of 10 days, which is configurable using the `rolloutCacheConfiguration` setting. After expiration, the SDK will refresh the cache from scratch.
+- For the iOS SDK, version 3.3.0 introduces a default cache expiration period of 10 days, which is configurable using the `rolloutCacheConfiguration` setting. After expiration, the SDK will refresh the cache from scratch.
+
+All SDKs continue to store impressions and events for up to 90 days, after which the cache is considered stale and may be purged.