Workspace
Snapshots & data retention
What MadMax keeps: every snapshot, every run, every store row — and the few places display truncates.
The short version: MadMax keeps your history. There is no quiet 30-day purge.
Kept indefinitely
- Snapshots — every activation and publish cuts an immutable snapshot; all of them stay, forever, as the audit trail of what was live when.
- Run history — runs and their per-step inputs/outputs are not pruned.
- Store rows — data stores hold rows until a workflow overwrites them (upserts replace; there's no row history) or you delete the store.
- AI memory — conversation turns persist until you clear them; the window limits what an agent reads, not what's stored.
Where display truncates
Storage and display differ in two places: long loops show the most recent 50 iterations (with an honest "showing the last N of M" note), and the runs list pages in batches of 25. The totals always come from the full data.
Deletion is explicit
Data leaves MadMax when you delete it: a store (typing its slug to confirm), a memory or its sessions, a knowledge base, a workflow, or an archived workspace. Deleting a workflow keeps nothing running: its triggers tear down with it.