Skip to main content
Settings → Data Lifecycle keeps the size of per-sample time-series data under control. Raw samples such as heart rate at one-minute resolution grow linearly with time and connected devices. This tab lets you aggregate old samples into daily summaries and delete data past a retention window.
This feature is in early access and is not yet ready for production use.
Self-hosting: set DATA_LIFECYCLE_ENABLED=false in the backend .env to turn the feature off. The tab disappears from Settings, the /api/v1/settings/archival endpoints return 503, and the daily archival job stops running. Existing archive data is left untouched.

​
Storage Overview

The top of the page shows the current database footprint:
  • Live Data - size and row count of the raw time-series table, including indexes.
  • Archive Data - size and row count of the archived daily aggregates.
  • Other Tables - everything else.
  • Total Database - the sum.

​
Growth Projection

A chart estimates database size over the next 18 months based on the current ingestion rate and the policies you have configured. The badge above it classifies the outcome: The projection updates as you edit the policies, before you save.

​
Archival Policy

When enabled, per-sample time-series data older than Archive data older than N days is aggregated into daily summaries. This reduces storage substantially while preserving aggregate accuracy. Set the threshold between 1 and 3650 days.

​
Retention Policy

When enabled, data older than Delete data older than N days is permanently deleted. Set the threshold between 1 and 7300 days.
  • Without archival, rows are deleted directly from the live table.
  • With archival, only archived aggregates are deleted. Live rows are always archived first.
Deletion is irreversible. If the retention threshold is lower than or equal to the archival threshold, the page shows a warning: data would be deleted before it can be archived, so archival is effectively disabled. Fix the thresholds before saving.

​
Manual Trigger

The archival and retention job runs on a daily schedule. Run Now executes it immediately with the currently saved policies, which is useful right after changing thresholds or when validating the effect on storage.