Why We Retire Old Chat Conversations After 90 Days (And How to Keep the Ones That Matter)
How conversation retention works on Milly Chat: a 90-day window on Starter and Essentials, the save exemption, and how Core and Enterprise differ.
Every chat conversation a Shopify merchant's AI widget handles is a row in a database — visitor messages, assistant replies, recommended products, captured leads. On a moderately busy store, that's thousands of rows a week. On a busy store, hundreds of thousands. Without retention, old transcripts pile up, the replay tool gets sluggish under the weight, and the storage bill keeps growing.
Conversation retention is the answer, but it has to be the right shape. Aggressive deletion loses the conversations that actually mattered. No deletion at all costs money and degrades every tool that scans transcripts. We landed on a 90-day-rolling default for lower tiers, with explicit exemptions for the conversations a merchant chooses to keep — and no 90-day window on Core and Enterprise.
Why retention exists
Two real costs sit on top of the conversations table:
- Storage cost: each conversation row carries the full message array as JSONB. Multiply by traffic, scale by months, the table grows linearly without bound. Postgres handles it fine for a long time, but eventually queries that scan the table — replay search, gap analysis, certain analytics rollups — start to slow, and the storage line on the bill stops being negligible.
- Signal-to-noise on replay: replay is a merchant tool. They open it to find a specific conversation — "the wholesale buyer who asked about bulk pricing last Tuesday" — or to QA the AI's recent behavior. Both jobs degrade when there are nine months of low-signal conversations cluttering the search space. Recent + interesting is more useful than complete.
These costs are tier-shaped. A Starter merchant on a smaller plan needs storage costs to scale with their pricing. Core and Enterprise plans cover storage at a different unit economic, so they don't use the 90-day window.
The 90-day rolling default
On Starter and Essentials tiers, conversations expire 90 days after creation. A nightly job does two things, in order:
- Stamp
expires_aton conversations approaching 90 days (specifically, those older than 83 days that don't have an expiry yet). The 7-day window before deletion is when the replay UI starts showing a clock icon — the merchant has a heads-up. - Remove conversations whose expiry has passed: they are copied to a private archive and then deleted from the live database, and they no longer appear in replay.
Save / flag exemption
The 90-day timer doesn't apply to conversations the merchant marks as worth keeping. The nightly job doesn't stamp an expiry on a saved conversation, so the 90-day window doesn't apply to it.
The save action is one click on the replay surface. Whatever the conversation contains — a successful B2B inquiry that needs follow-up, an ATC funnel that wants closer inspection, a problematic AI response that's worth keeping for QA — the merchant can keep it without thinking about retention windows. A saved-conversations filter on the replay surface makes the kept set explicit: the merchant can always see what they've flagged to keep.
Unsaving a conversation removes the exemption — the job catches up on the next nightly run and stamps the expiry from the original creation date.
The replay surface, retention-aware
Retention is invisible if it's a silent purge — the merchant tries to find a 4-month-old conversation, doesn't, wonders if the search is broken. Surfacing the retention state explicitly avoids that:
- Clock icon on conversations approaching expiry — visible signal that a conversation has < 7 days left unless saved
- Retention banner on the replay page that explains the active policy and how to save
- Saved filter in the replay list to view only the conversations the merchant has explicitly kept
The visual treatment matters more than it sounds. A merchant who knows the policy can act on it; a merchant surprised by an invisible deletion blames the tool.
Core and Enterprise: no 90-day window
Core and Enterprise stores don't use the 90-day window: the nightly job doesn't stamp an expiry on their conversations. Merchants on these plans often have longer consideration cycles and need multi-month conversation history.
Analytics roll-ups are computed separately from the conversations table — daily aggregates and the weekly recap views are stored separately, so historical metrics stay intact even on Starter/Essentials stores after the underlying transcripts have rolled off. The retention policy applies to transcripts, not to the numbers derived from them.
Frequently Asked Questions
How long does Milly Chat keep chat conversations?
On the Starter and Essentials tiers, conversations expire 90 days after they're created. Core and Enterprise stores don't use the 90-day window. On Starter and Essentials the 90-day timer is a rolling default, not a hard cap: anything you explicitly save is exempt.
Can I keep a specific conversation past the 90-day window?
Yes. Saving a conversation from the replay surface — one click — exempts it from the 90-day timer. A saved filter in the replay list shows exactly which conversations you've kept. Unsaving re-arms the timer, and the next nightly run stamps the expiry from the conversation's original creation date.
Do I lose my analytics when old conversations are deleted?
No. Analytics roll-ups are computed separately from the conversations table and stored in dedicated daily rollup tables, so your historical metrics stay intact even on Starter or Essentials after the underlying transcripts have rolled off. Retention applies to the transcripts, not to the numbers derived from them.