Replay access and sharing
Workspace roles control staff access. A replay share link gives its holder access to that replay without an account. You can revoke the link or disable public replay sharing for the workspace.
Read the share link guideDecide who can review a replay, what you share and how long you keep it. These are the controls available in ReplayCore.
Workspace roles control staff access. A replay share link gives its holder access to that replay without an account. You can revoke the link or disable public replay sharing for the workspace.
Read the share link guideAn Evidence Pack starts as an editable draft linked to a replay. Sealing freezes the document and creates the bundle used for export and sharing. Check the content before you seal it.
Read the Evidence Pack guideYour plan defines a retention window. You can delete replays before that window ends. Keep the records you need before deletion or expiry. Removing access cannot recall a copy that someone has already downloaded.
Check retention behaviourRecording settings control captured chat and player information. The data request API supports player data export and erasure. Review these settings against your server rules and the data you need to keep.
Read the data request guideA shared Evidence Pack has a verification page that checks its stored bundle and signature. Open that page from the shared pack to read its current result.
Verification checks the bundle. It does not decide whether a player broke a rule or whether the staff conclusion is correct. Review the exhibits and their context before you make a decision.
Check a shared packEmail the affected page or feature and a description of the issue. Do not include passwords, recording keys or private player data in the first message.