Data retention
This page summarizes how long different kinds of data are kept.
Retention at a glance
| Data | Retention |
|---|---|
| Workspace clones (closed sessions) | Cleaned up after 7 days |
| Validation objects in the warehouse (temporary databases/tables) | Expire after 24 hours and are swept |
| Application logs | 30 days (default, configurable) |
| Cached warehouse connections / model graph | Short-lived in-memory caches (minutes) |
| Login (one-time) codes | Expire after a few minutes |
| Sessions, messages & cached query results | Retained with the session; removed when the session is deleted |
| dbt catalog (models, columns, lineage) | Kept current with your repository; stale entries removed on sync |
Sessions and cached results
Session history - including generated SQL and cached query results - is retained with the session. When a session is deleted, its messages and cached results are removed with it.
warning
There is currently no automatic time-based purge of sessions or their cached query results independent of session deletion.
Warehouse validation objects
When validating large refactors, Zingle may create disposable validation databases and temporary tables in your warehouse to compare results safely. These are given a 24-hour expiry and swept automatically. See the Production safety model.