Skip to main content
An NDA is a standalone agreement with its own link, its own roster, and its own signature ledger. Send the address to anyone. They read it, tick the boxes, and Userplay records exactly what they agreed to.

​
When to use one

Standalone NDAs suit any agreement that is not tied to one playtest:
  • Press and creator embargoes ahead of a reveal
  • Publisher and investor pitches
  • Contractor and collaborator confidentiality
  • A single agreement you reuse across several playtests and demos
If you want an agreement inside one specific playtest, use that playtest’s NDA step instead. It lives on the playtest, freezes with it, and players sign it on their way in.

​
How it works

1

Create an NDA

Open NDAs in the sidebar and click Create NDA. Name it, and you land in the editor.
2

Write the agreement

Start from a template or write your own. Add custom checkboxes if you need specific acknowledgements.
3

Set up onboarding

Choose the identities a signer must connect, and write the screen they land on.
4

Write the acknowledgement

This is what a signer sees the moment the signature is recorded.
5

Publish and share

Click Publish, then copy the link.
6

Read the signatures

Every signature lands in the ledger with its evidence.

​
What you configure

Publishing adds two more views, the signature ledger and the analytics behind it. Announcement is off until you switch it on in Config, and it needs a connected Discord server. Turning it on adds the Announcement tab, where you write the message that posts with a Read and sign button.

​
What a signature records

Every signature is written once and never updated. Alongside who signed and when, Userplay stores: The hash and the snapshot are built from the server’s own view of your published agreement. Nothing the signer’s browser sends can influence what gets recorded.

​
NDAs and groups

Every NDA keeps its signers in a player group of its own. The group is owned by the NDA: you manage it from the NDA, you cannot rename it or add to it by hand, and archiving the NDA archives the group too. Signatures are separate from the roster. Removing someone from the roster never removes their signature, because a signature is evidence rather than membership.

​
Lifecycle

Once published, an NDA moves between published and unpublished for the rest of its life. It never returns to draft.

​
Next steps

The agreement

Writing the terms, and the boxes a signer ticks.

NDA onboarding

The identities to require, and the screen signers land on.

Publishing an NDA

Go live, and get the link signers open.

Signatures

Who signed, when, and against which revision.

NDA analytics

Signature totals, the trend, and revision coverage.

Playtest NDAs

The agreement that lives inside a single playtest.