Skip to content

Data & privacy settings

Decide how long Flero keeps execution history and other records. Open Settings → Data & Privacy. Organization members see this tab. Only organization admins can change it.

Settings, Data and privacy: how long Flero keeps run data, the training setting, the data agreement, deleting everything, and the Retention and archiving card.Settings, Data and privacy: how long Flero keeps run data, the training setting, the data agreement, deleting everything, and the Retention and archiving card.

Retention Policies

Setting Options Default
Execution Log Retention 30, 60, 90, 180 or 365 days, or Forever 90 days
Audit Log Retention 90, 180, 365 or 730 days, or Forever 365 days
Backup Retention 7, 14, 30, 60 or 90 days 30 days
Temp File Retention 1, 3 or 7 days 7 days

Click Save Retention Policies to apply. The settings apply to the whole organization.

What Execution Log Retention does

Every night at 03:00 (server time), Flero deletes finished executions older than the retention period. Finished means succeeded, failed, stopped, cancelled or timed out. Running and waiting runs are never deleted.

Choosing Forever does not keep runs forever yet. Flero falls back to the instance default, which is 90 days unless your Flero instance is configured otherwise.

The same window bounds trigger deduplication: a polling trigger remembers which items it already emitted only for as long as executions are kept.

The audit, backup and temporary-file values are saved with your organization's settings.

Compliance & Archival

Switch Description
Enable Data Archival Automatically archive old data according to retention policies
Enable Audit Trail Track all user actions for compliance and security

Click Save Compliance Settings to apply.

Where your data goes

  • Workspaces are separated by Flero's application layer. Members of one workspace cannot see another workspace's workflows, executions or credentials.
  • Credentials are encrypted. Their secrets are not included in workflow exports.
  • Outbound data leaves Flero only through the nodes you configure: connector calls, HTTP requests, emails and AI providers.

Tips & gotchas

  • Shorter retention means less history to debug with. Export runs you need to keep from Logs before they age out.
  • Retention is organization-wide, not per workflow or per workspace.
  • Check regulatory minimums before you shorten retention in regulated industries.

Found something out of date? This page lives in the Flero docs content set.