Skip to main content
The audit log records security- and data-relevant activity for a project. It is append-only during normal product workflows: a write creates a new row instead of rewriting an earlier event. Retention maintenance can delete old rows after the configured retention window. Each entry records: Secrets are not stored raw in audit payloads. Values whose keys look like credentials, tokens, API keys, or passwords are redacted before insertion.

Retention

Audit rows are kept for AUDIT_RETENTION_DAYS, defaulting to 365 days when the variable is unset. The value must be between 1 and 3650 days. Worker maintenance can run a daily audit-log purge, and the self-hosted purge route calls the same retention helper. The purge deletes rows older than the cutoff; it does not rewrite retained rows.

Action registry

The actions below are the current audit-log action values emitted by the application. API means a project-scoped API-key call; those rows have a null actor and are shown as System in the audit UI.

Account, auth, and access

Projects, settings, and onboarding

Keywords, tags, and saved views

Rank checks and worker maintenance

Providers and notification channels

Alerts and competitors

Signals, reports, and traffic

Team and API keys

Migration and import

These related lifecycle events are not recorded as audit-log rows: