> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Auto-Cleanup Parameters

> Configure scheduled or one-time cleanup of Endpoint-collected monitoring data — delete from the database, or archive to secure storage first and then delete. Apply per Endpoint or per Endpoint group.

The **Auto-Cleanup** parameters control how Syteca manages the lifecycle of monitored data collected by Endpoints — including when to delete it from the database, and (in on-premises deployments) when to first archive it to secure storage before deletion. Cleanup rules can be applied per Endpoint or per Endpoint group.

<Note>
  **Applies to**: Windows Endpoints, macOS Endpoints, Linux Endpoints. The parameter behaves identically across all three platforms.
</Note>

## Where to find it

These parameters live on the **Editing Endpoint** / **Editing Endpoint Group** page, on the **Properties** tab, in the **Auto-Cleanup Options** section.

## Two types of cleanup

| Type                  | What it does                                                                                                                                                                             | Available in SaaS?          |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- |
| **Cleanup**           | Deletes monitored data collected by the Endpoint(s) from the database. Permanent — no archive copy.                                                                                      | ✅ Yes                       |
| **Archive & Cleanup** | Saves the monitored data to secure storage first, then deletes it from the database. The archived sessions stay accessible in the [Session Viewer](/docs/session-monitoring/player/overview). | ❌ **Not available in SaaS** |

## Three execution frequencies

| Frequency                        | When it runs                                                                                                                                                                                             |
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Never**                        | Cleanup is not performed. Use this to opt a specific Endpoint out while keeping the deployment's default behavior.                                                                                       |
| **Run once**                     | A one-time cleanup runs as soon as you click **Finish** on the Editing Endpoint / Editing Endpoint Group page. See [One-time cleanup](/docs/administration/clients/parameters/auto-cleanup#one-time-cleanup). |
| **Repeat according to schedule** | A scheduled cleanup runs every few days at the specified time. See [Scheduled cleanup](/docs/administration/clients/parameters/auto-cleanup#scheduled-cleanup).                                               |

## One-time cleanup

Use **Run once** for ad-hoc data removal — for example, after migrating data to long-term storage outside Syteca, or when a specific Endpoint's data is no longer needed and you don't want to wait for the next scheduled run.

<Steps>
  <Step title="Open the Client or Client group">
    Log in to the Management Tool as a user with the [administrative Database Management permission](/docs/administration/users/administrative-permissions), click **Clients**, and find the Client or Client group to clean up.

    <Note>
      If you lack the [Client Configuration Management permission](/docs/administration/users/client-permissions) for this Client, the configuration options are disabled.
    </Note>
  </Step>

  <Step title="Select Run once">
    On the **Editing Client** / **Editing Client Group** page, **Properties** tab, scroll to **Auto-Cleanup Options** and select **Run once**.
  </Step>

  <Step title="Choose the action">
    Select **Cleanup** to delete the data, or **Archive & Cleanup** to archive it first (requires [Archive Parameters](/docs/administration/configuration/database-management-settings) configured beforehand; not available in SaaS).
  </Step>

  <Step title="Set the retention period">
    In **Sessions older than (days)**, enter how far back to clean up from.
  </Step>

  <Step title="Save">
    Click **Finish**.
  </Step>
</Steps>

The cleanup executes as soon as you click **Finish** — there's no separate "Run now" button; saving the configuration with **Run once** selected IS the trigger.

## Scheduled cleanup

Use **Repeat according to schedule** for ongoing data lifecycle — for example, to enforce a 90-day retention policy across all Endpoints, or to keep PoC environments from filling up disk during evaluation.

<Steps>
  <Step title="Open the Client or Client group">
    Log in to the Management Tool as a user with the [administrative Database Management permission](/docs/administration/users/administrative-permissions), click **Clients**, and find the Client or Client group to schedule cleanup for.
  </Step>

  <Step title="Select Repeat according to schedule">
    On the **Editing Client** / **Editing Client Group** page, **Properties** tab, scroll to **Auto-Cleanup Options** and select **Repeat according to schedule**.
  </Step>

  <Step title="Set the frequency and time">
    * **Perform every (days)** — how often the cleanup runs.
    * **Start at** — the time of day it executes.
  </Step>

  <Step title="Choose the action">
    Select **Cleanup** to delete the data, or **Archive & Cleanup** to archive it first (requires [Archive Parameters](/docs/administration/configuration/database-management-settings) configured beforehand; not available in SaaS).
  </Step>

  <Step title="Set the retention period">
    In **Sessions older than (days)**, enter how far back each run cleans up from.
  </Step>

  <Step title="Save">
    Click **Finish**.
  </Step>
</Steps>

## Related

<CardGroup cols={2}>
  <Card title="Database management" icon="database" href="/docs/administration/deployment/database-management">
    Higher-level database lifecycle controls beyond per-Endpoint cleanup.
  </Card>

  <Card title="Archived sessions" icon="archive" href="/docs/session-monitoring/archived-sessions">
    Viewing sessions that have been archived via Archive & Cleanup.
  </Card>

  <Card title="User activity recording" icon="video" href="/docs/session-monitoring/recording/user-activity-recording">
    The parameters that determine how much data each Endpoint generates in the first place.
  </Card>

  <Card title="Update Endpoint automatically" icon="refresh-ccw" href="/docs/administration/clients/parameters/update-client-automatically">
    Another cross-platform Endpoint Mode parameter.
  </Card>
</CardGroup>