Skip to content

Documentation

Data retention

How long audit logs and other records are kept, in the cloud and on a self-hosted install, and how to change it.

Where
Admin → Billing (audit retention add-on) · .env, eventier.env or Helm values (self-hosted)
Permission
Billing admin (cloud add-on) · admin of the host, cluster or server (self-hosted)
Updated
October 2026

Overview

Requests, comments and attachments are never deleted automatically. They go only when someone removes them: a GDPR erasure, or deleting the workspace.

The audit logs and some internal records are kept for a set time, then deleted by a job that runs once a day.

In the cloud, the change log is kept 7 days on Free and 30 days on Standard. The audit retention add-on raises it to 6 or 12 months.

In the cloud, the sign-in and security logs are kept 400 days on every plan.

On a self-hosted install, all three logs are kept forever until you set a number of days.

Step by step

  1. 01

    Keep the change log longer in the cloud

    Buy the audit retention add-on in Admin → Billing, under Audit retention.

    • 6 months or 12 months, at a flat monthly price
    • Turning the add-on off returns the change log to your plan's window
  2. 02

    Set retention on a self-hosted install

    Each log has its own setting: a number of days, or unlimited to keep it forever.

    • AUDIT_RETENTION_DAYS: the change log
    • AUTH_AUDIT_RETENTION_DAYS: sign-ins
    • SECURITY_AUDIT_RETENTION_DAYS: security events
    • unlimited or 0 keeps a log forever, and so does leaving it unset
    • Kubernetes: retention.auditLogDays, retention.signInLogDays and retention.securityLogDays in values.yaml
    • A value that isn't a whole number of days is ignored: nothing is deleted, and a warning is logged at startup
    Example: keep the change log a year, everything else foreverbash
    AUDIT_RETENTION_DAYS=365
    AUTH_AUDIT_RETENTION_DAYS=unlimited
    SECURITY_AUDIT_RETENTION_DAYS=unlimited
  3. 03

    Keep a copy outside EvenTier

    Stream the audit logs to your SIEM, and keep them there for as long as your rules require.

    • See Audit logs for the two ways to stream
  4. 04

    Change other retention windows (self-hosted)

    Other records have their own window, in days. The table below lists the defaults and the setting for each.

    • A setting takes a number of days greater than 0; anything else keeps the default

Retention windows

Defaults on both editions. Self-hosted installs can change the ones with a setting.

RecordKept forSetting (self-hosted)
Change log7 days on Free, 30 on Standard, 6 or 12 months with the add-on; forever when self-hostedAUDIT_RETENTION_DAYS
Sign-in log400 days in the cloud; forever when self-hostedAUTH_AUDIT_RETENTION_DAYS
Security events400 days in the cloud; forever when self-hostedSECURITY_AUDIT_RETENTION_DAYS
API call log90 daysAPI_REQUEST_LOG_RETENTION_DAYS
Webhook deliveries90 daysWEBHOOK_DELIVERY_RETENTION_DAYS
Slack and Teams deliveries90 daysCHAT_INTEGRATION_DELIVERY_RETENTION_DAYS
Read notifications90 daysNOTIFICATION_RETENTION_DAYS
Automation run history90 daysAUTOMATION_RUN_RETENTION_DAYS
Evee conversations180 daysAI_CONVERSATION_RETENTION_DAYS
Knowledge base search history180 daysKB_SEARCH_EVENT_RETENTION_DAYS
Product usage events180 daysUSAGE_EVENT_RETENTION_DAYS

Good to know

  • Shortening a window takes effect at the next daily run, and deleted entries can't be brought back. Export or stream first if you need them.