Raw event retention ​

Raw events contain the detailed source history behind Orloi's summaries. They can grow quickly, but deleting them is an operational decision for the owner of the Postgres database—not an automatic Orloi retention policy.

Choose a retention period that meets your audit, recovery, privacy, and legal requirements. The number of days shown in the Retention page is only a cutoff, not a recommendation for every organization. Keep raw events for as long as you need to investigate changes or recompute history from source data.

Use the Retention page ​

The Retention page previews the event scope, count, date range, and estimated storage impact before cleanup.
  1. Open the observed base in Orloi and choose Retention under System.
  2. Choose which events to delete:
    • All raw events includes user, API, automation, and system activity.
    • System events includes formula, rollup, and date recalculations, plus changes from tables synced across bases. User, API, and automation events are not affected.
  3. Enter how many days old an event must be to qualify for deletion, then choose Continue.
  4. Review the preview. It shows the exact number of matching events, their date range, and the estimated storage impact when available. If no events match, there is nothing to delete.
  5. Choose Delete, review the confirmation, and confirm the displayed count. Orloi schedules the cleanup as a background task and deletes the events in batches.

Before you delete ​

  • Resolve any legal hold, investigation, or contractual retention requirement before choosing a cutoff. Orloi does not model legal holds or prevent an authorized database owner from deleting held data.
  • Do not begin a purge until you have a tested provider backup or point-in-time recovery plan.
  • Orloi does not create an archive before cleanup. If you need a custom export or a copy for cold recovery, use the optional custom export and deletion with SQL procedure first.

What cleanup affects ​

The cleanup removes matching raw source event rows for the selected observed base and metric provenance links that point to those raw events.

Compacted events, metric values, reports, process summaries, saved activity history, collaborator profiles, and automation mappings remain available. Deleted raw detail cannot be fully reconstructed, and metric drill-down rows that depended on deleted raw events may no longer be available.

For more custom export and deletion control, see Custom export and deletion with SQL. This optional path is intended for technical operators; the Retention page above is the normal workflow.