Data and privacy
Retention
How long Loop keeps your raw events. You set the window per project; a scheduled sweep enforces it.
The window
This area has no published API yet.
Segments, analytics, experiments, messages, imports and retention are reached through the console's own API, which exists to serve one first-party client and changes whenever that client does. Rather than print a shape we would have to break, this page describes what is structurally true. The public reference lands when the interface is stable enough to promise.
A per-project number of days, set in Settings. Events older than it are deleted on a schedule. There is a global ceiling above your window that no project can exceed.
What the window governs
It sweeps raw events, and only those.
The window applies to the events table: the one funnels, trends and retention read. Surface interactions, experiment exposures and identity aliases are not inside it and survive past the window. If you are answering a data-retention questionnaire, that distinction is the one that will be asked about.
Shortening it is destructive, and it says so
Before you shorten a window, Loop counts what the new one would delete and shows you that number. A project holding eleven months of history can lose most of it to a single keystroke, so the count is shown against the proposed window rather than the current one; the alternative is telling an operator that zero events will be deleted one moment before destroying a year of them.