Tester Privacy

How Testers Access a Playtest#

Testers do not need a Userplay account. They receive a unique, signed playtest URL — typically delivered by the studio through its own channels (email, Discord, an in-game prompt, etc.).

That URL grants access only to the specific playtest’s recording endpoint and consent flow. It cannot be used to access any other part of the studio’s workspace. The URL can be revoked by the studio at any time, instantly invalidating it.

Consent Before Recording#

When a tester opens the playtest URL, Userplay shows them a consent screen before any recording begins. The screen clearly describes:

• What will be captured (screen, microphone if enabled, webcam if enabled).
• Which studio is running the playtest.
• How long recordings will be retained.

The tester must explicitly accept before the recorder starts. If they decline, no data is captured and no upload occurs.

What Testers Can Control#

Testers have meaningful control throughout the session:

• Before recording starts — they choose which screen, window, or browser tab to share using the browser’s built-in picker, and can decline microphone or webcam capture if the playtest requests it.
• During recording — they can stop the session at any time. Data captured up to that point is only uploaded if the tester explicitly confirms.
• After the session — testers can ask the studio (the data controller) to delete their recording. Studios can delete recordings per recording or in bulk. Testers can also contact privacy@userplay.io for requests that require more targeted action.

What Testers See and Don’t See#

Testers see only the consent screen and the playtest itself. They cannot see:

• Other testers’ sessions or recordings.
• The studio’s workspace, other playtests, or any recordings.
• Any data about other participants in the same study.

Microphone and Webcam Defaults#

Both microphone and webcam capture are off by default. A studio must explicitly enable them per playtest. Even when enabled by the studio, the tester’s browser presents its own permission dialog — the tester retains control at the browser level.

Data Minimization#

Userplay is designed to capture what is needed for the playtest and nothing more. The screen recorder is the only live capture path. The optional Chrome extension (for web-based games) operates only after gameplay ends — it never captures data during active play, and it never captures credentials, cookies, or browsing history outside the playtest context.