trashDeletion Policies

Create named data retention rules that automatically delete recordings and bug reports after a configurable number of days.

Deletion Policies let you define exactly which recordings and bug reports are automatically deleted, and when.

Each policy is a named retention rule.

You can create multiple policies for different content types, folders, labels, or retention periods.

circle-info

Plan availability: Pro and Enterprise.

triangle-exclamation

How Deletion Policies work

Each policy defines a rule like this:

Delete [subtype] [recordings or bug reports] after [N] days

You can also scope the rule to a specific folder or label.

Enabled policies run once per day at midnight UTC.

Any matching item older than the retention period is permanently deleted on the next run.

Age is based on the item's creation date.

New policies are always created in a disabled state.

That gives you time to review the rule before it starts deleting data.


Create a policy

Deletion Policies are managed from SettingsSecurityDeletion Policies.

1

Go to Deletion Policies

Open SettingsSecurityDeletion Policies.

2

Click New Policy

Click New Policy.

3

Build the rule

The form uses an inline rule builder.

Choose:

  • Resource type — Recordings or Bug reports

  • Subtype — depends on the resource type

  • Retention period — number of days after creation

  • Optional filter — specific folder or specific label

For Recordings, the subtype options are:

  • All

  • Received

  • Sent

  • Live

For Bug reports, the subtype options are:

  • All

  • Video recording

  • Screenshot

  • Instant replay

circle-info

Each policy can use either a folder filter or a label filter.

If you need both, create separate policies.

4

Name the policy

Screendesk generates a name from the rule.

You can edit it to something more descriptive, such as:

  • 30-day received recordings

  • 90-day bug reports

  • GDPR EU customer recordings

Policy names must be unique in your workspace.

5

Create the policy

Click Create Policy.

The policy is saved as disabled by default.


Preview a policy

Before enabling a policy, preview what it will delete.

On the policy list, click the eye icon next to the policy.

The preview shows the items currently scheduled for deletion based on the rule.

Use it to confirm the policy is targeting the right content.

Depending on the policy, the preview can also show scheduled deletions across the upcoming days.


Enable or disable a policy

On the policy list, click the Enabled or Disabled status badge to toggle the policy.

Enabling a policy starts applying the rule on the next daily run.

Disabling a policy stops future deletions immediately.

Items that were already deleted are not restored.


Edit a policy

Click the pencil icon next to a policy to update its rule or name.

Use the status badge on the list page to enable or disable it.

circle-exclamation

Delete a policy

Click the trash icon next to a policy and confirm.

Deleting a policy removes the rule only.

It does not restore anything the policy already deleted.

It also does not trigger extra deletions.


Understand the policy list

The policy list helps you review and manage retention at a glance.

It includes:

  • Rule summary — plain-English summary of the rule

  • Name — your custom policy name

  • Created by — the workspace member who created it

  • Last run — when the job last processed the policy

  • Deleted count — total items deleted by that policy

The deleted count is cumulative.

It only increases over time.


Audit logging

Changes to Deletion Policies are recorded in Audit Logs on the Enterprise plan.

This includes:

  • policy creation

  • edits

  • enabling

  • disabling

  • deletion

See Audit Logs.


What happens when you downgrade

If your workspace moves to a plan without Deletion Policies, all enabled policies are automatically disabled.

No further deletions will run.

The policy definitions remain saved, so you can re-enable them later if you upgrade again.


Best practices

Start with a narrow rule.

Use a folder or label filter first.

This reduces the risk of deleting too much content.

Preview before enabling.

Always confirm the affected items before turning a policy on.

Use clear names.

Good names make audits and team handoffs easier.

Separate short and long retention rules.

Create different policies for different content types instead of one broad rule.

Review compliance needs carefully.

Deletion is irreversible, so align retention periods with your legal and operational requirements.


FAQ

chevron-rightCan I set different retention periods for different recording types?hashtag

Yes.

Create one policy per type or subtype.

For example, keep Received recordings for 90 days and Live recordings for 30 days.

chevron-rightCan I create multiple policies?hashtag

Yes.

You can create as many policies as you need.

chevron-rightCan I filter by folder or label?hashtag

Yes.

A policy can be scoped to one folder or one label.

It cannot use both in the same policy.

chevron-rightWhat exactly gets deleted?hashtag

The full item and its associated data.

This includes the video or image file, thumbnails, comments, labels, and related metadata.

chevron-rightWhen does deletion happen?hashtag

Deletion runs once per day at midnight UTC.

If an item is older than the configured threshold, it is deleted on the next run.

chevron-rightCan I undo a deletion?hashtag

No.

Deletion is permanent and cannot be reversed.

chevron-rightCan multiple policies overlap?hashtag

Yes.

If an item matches more than one enabled policy, the shortest retention rule will delete it first.

chevron-rightWhy does the deleted count only go up?hashtag

The deleted count is cumulative.

It tracks every item that policy has deleted since it was created.


Last updated

Was this helpful?