From 3ab492cd6163e8dd0116ecb6c7e43bdaff71c889 Mon Sep 17 00:00:00 2001 From: kartik-mem0 Date: Thu, 23 Jul 2026 20:30:48 +0530 Subject: [PATCH] docs: retitle memory expiration page and convert headings for AEO --- docs/platform/features/memory-expiration.mdx | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/platform/features/memory-expiration.mdx b/docs/platform/features/memory-expiration.mdx index 6f7e7fec3..ed80300e3 100644 --- a/docs/platform/features/memory-expiration.mdx +++ b/docs/platform/features/memory-expiration.mdx @@ -1,9 +1,10 @@ --- -title: Memory Expiration -description: "Give a memory a shelf life: set an expiration date and it stops surfacing in search once that date passes, without deleting the record." +title: "Memory Expiration in Mem0" +sidebarTitle: "Memory Expiration" +description: "Set an expiration date on a Mem0 memory and it stops surfacing in search once that date passes - the record stays stored, nothing is deleted. Works on Platform and Open Source." --- -# Memory Expiration +## Why Use Memory Expiration? Some facts are only true for a while. A trial plan ends, a seasonal preference goes stale, a support ticket ages past its retention window. Set an `expiration_date` on a memory and Mem0 stops surfacing it once that date passes, so you don't need a cleanup job hunting for rows to delete. @@ -18,7 +19,7 @@ Some facts are only true for a while. A trial plan ends, a seasonal preference g - **No expiration date means never expires.** That is the default for every memory. - **Malformed dates fail open**: a stored value Mem0 can't parse is treated as *not* expired. A bad date never makes a memory silently vanish. -## Set an expiration date +## How do you set an expiration date on a memory? Set it when you add the memory: @@ -97,7 +98,7 @@ The same parameter and spelling work on the OSS `Memory` class. See