Skip to main content
Retention decides how long a completed session’s video, audio, transcript, highlights, and events survive before Userplay removes them permanently. One window covers the whole studio.

Take the guided tour

Set the retention window and see what it covers.

What you need first

  • Whatever your studio has committed to, whether that is a privacy policy, a publisher agreement, or an NDA you have signed.
  • A sense of how your team works. Reviewing weeks later needs a longer window than exporting the same day.
  • Owner or admin access, since members can read the setting but not change it.

The playbook

1

Work out the window you need

The options are 1 week, 1 month, 3 months, 6 months, and 12 months. The default is 1 month.Start from the longest thing you have promised anyone, then check it against how late your stakeholders usually ask for footage.
2

Check what your plan allows

Open Settings > Usage and read the data retention limit under your plan’s details.Pick a period beyond your plan’s cap and Userplay offers the upgrade rather than saving it.

Usage

Where the limit is displayed, alongside every other meter.

Plans and limits

The longest window each plan allows.
3

Set the period

Go to Settings > Studio and set the retention period.It applies studio-wide. No individual playtest can override it.

Data retention

Every window, when the clock starts, and what deletion covers.

Studio settings

The rest of the studio-wide settings on the same page.
4

Export anything near the edge first

If you are shortening the window, export before you save.
Sessions already older than the new window are deleted the next time the cleanup job runs, and deletion is permanent. There is no recovery window.

Exports

Every dataset and artifact format, and when each is available.

Export your playtest data

Playbook: take the data out before the window closes.
5

Pair a short window with an NDA for confidential work

For an unannounced build, turn on the playtest’s NDA and keep the window short.An NDA sets the obligation, a short window limits how long the footage exists to leak.

NDA

The block editor, the checkbox limits, and how acceptances are stamped.

Test a confidential build

Playbook: an NDA, a closed roster, and a short window together.
6

Make the export a habit

Decide who exports what after each playtest wraps, and when.The window is only safe if somebody is taking out what the team will want later.
7

Recheck it when your plan changes

Downgrading clamps your retention setting down to the new plan’s ceiling.Read the new limit in Settings > Usage after any plan change, and export before the shorter window takes hold.

How you know it worked

  • Settings > Studio reads back the period you chose.
  • The retention limit shown in Settings > Usage matches or exceeds it.
  • Sessions older than the window stop appearing, which is the setting working rather than a fault.
  • Your exports are landing somewhere your team can still reach them.

Data retention

Every window, when the clock starts, and what deletion covers.

Export your playtest data

Playbook: take the data out before the window closes.

Plans and limits

The longest window each plan allows.

Test a confidential build

Playbook: an NDA, a closed roster, and a short window together.