Skip to content
Docs
flero.ai

Data & privacy settings

Manage your data: export it, control retention, configure privacy policies.


Data export

Export all my data generates a JSON file containing:

  • Your account profile.
  • Memberships and roles per workspace.
  • Personal credentials (metadata only, secrets are not exported in plaintext).
  • Workflows you own.
  • Executions you triggered (last 90 days).
  • Comments you authored.
  • Audit log entries about your account.

Click the button → Flero prepares the export in the background → you'll get an email with a download link when it's ready (usually within an hour).


Data retention

Workspace-level retention controls (Admin / Owner only):

Setting Default Notes
Execution history retention 30 days Older executions are purged on a nightly job.
Failed executions retention 90 days Often kept longer for debugging.
Sandbox executions retention 7 days Separate, usually shorter.
Workflow file storage retention 30 days Files attached to executions.
Audit log retention 1 year Required minimum on compliance plans.
Notification archive retention 30 days In-app notifications.

Lengthening retention increases storage cost and exposure scope; shortening reduces both at the cost of forensic depth.


  • Functional cookies, required; can't disable.
  • Analytics cookies, first-party only; toggle off if preferred.
  • No third-party trackers. Flero doesn't embed Facebook Pixel, Google Tag Manager, etc.

GDPR / data-subject controls

Available under Data & privacy → Privacy controls:

  • Right of access, same as the export above.
  • Right to rectification, change account fields directly under Account; for changes to data you don't directly control (audit logs, etc.), submit a request.
  • Right to erasure, delete your account (Account → Danger zone). For erasure of data within someone else's workspace, contact the workspace owner.
  • Right to data portability, JSON export is machine-readable.

Workspace-level data isolation

For multi-tenant deployments, workspaces are isolated at the database level, one tenant's queries can't see another's. Your data leaves your workspace only via:

  • Connector calls you've configured (you decide what's sent).
  • Workflows that explicitly export (HTTP nodes posting outbound).
  • Admin-level cross-workspace queries on enterprise plans (audit-logged).

Privacy policy & terms

Links to the current versions, with a changelog. Significant changes trigger an in-app notification.


Tips & gotchas

  • Retention is global per workspace, not per workflow. Need different retention for different workflows? Tag them and use the Log explorer to archive externally before purge.
  • Data exports are big. A busy workspace can produce gigabytes; the file is gzipped JSON.
  • The "Delete account" path anonymises but does not delete history entirely, audit logs retain pseudonymised entries indefinitely as required by SOC 2 / compliance regimes.
  • For compliance-bound industries (healthcare, finance) consult an admin and your legal team before changing retention defaults. There may be regulatory minima.


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