Skip to main content
The NDA component lets you show an agreement that players must accept before continuing. It runs after Identity and before Screening, ensuring players agree to your terms before they provide additional information or access the game.

Playbooks

Test a confidential build

An NDA, a closed roster, and a short retention window.

Run a closed playtest

Only the people you seed by email can join, NDA included.

Enabling the NDA

The NDA is optional. New playtests start with it disabled. Enable NDA from the Config tab to add the NDA section to your playtest.
1

Enable it on Config

Open the Config tab. In the Playtest Settings card, set NDA to Enabled and click Save. The row reads “Show an NDA players accept before play.”
2

Open the NDA tab

An NDA tab appears in the tab bar, pre-filled with a starter agreement rather than a blank page.

Writing your agreement

Create your agreement using the NDA editor. You can add text and media blocks, up to 20 blocks total. The editor supports the same content types as Onboarding, including:
  • Text blocks.
  • Lists.
  • Images.
  • Videos.
  • Page breaks.
Use Preview to see exactly what players will experience before publishing.

Starting from existing content

You don’t need to write every agreement from scratch. Userplay lets you:
  • Browse Templates to start from a ready-made NDA layout.
  • Use Last Briefing to reuse content from your previous NDA.
Applying either option replaces your current content, so you will be asked to confirm before proceeding.

Player acknowledgement

Every NDA includes a required checkbox:
I have read and agree to the terms above
You can add additional checkboxes for agreements that need separate confirmation. Players must accept every checkbox before they can continue. Use custom checkboxes when you need separate consent, such as:
  • Allowing gameplay recording.
  • Agreeing to specific build restrictions.
  • Confirming rules around streaming or sharing content.

Onboarding

Learn how to introduce your playtest before players begin.

Player Experience

See the full journey players go through when joining a playtest.

Agreement records

The NDA uses a clickwrap agreement flow. Players actively accept your terms by checking the required boxes and clicking I Acknowledge. When a player accepts the NDA, Userplay records:
  • The exact agreement content they accepted.
  • The checkboxes they confirmed.
  • The player’s identity.
  • The time of acceptance.
This creates a record of what each player agreed to at the time they joined the playtest.

Editing the NDA after publishing

Because player agreements must remain consistent, NDA content and checkboxes are locked once the playtest is published. Unpublishing does not unlock the NDA. If you need to change the agreement itself, create a new playtest with the updated terms. Other playtest settings can still be updated based on their own editing rules, but accepted agreements cannot be changed retroactively.

Preview a playtest

Your last chance to read the NDA as a player would, since publishing freezes it.

Test a confidential build

Puts the NDA in order with keys, screening, and a private roster.

Screening players

The step that runs right after a player accepts.

Session flow

Where the NDA lands in the screens a player walks.