Skip to main content
The Signatures tab is the evidence. One row per person, written the moment they agreed and never touched again. It appears once the NDA is published.

​
What each row holds

Behind the row Userplay also stores the full content snapshot: the agreement text and every checkbox label, frozen at the moment of signing. That is what makes the record self-contained. Even if you archive the NDA, the snapshot describes what was agreed.

​
Where the evidence comes from

The hash, the snapshot, the IP address, and the user agent are all captured on our side, at the moment the request arrives. Nothing the signer’s browser sends can influence them. That matters: a record the signer could shape is not evidence of anything.

​
Export

Use Export to download the ledger as CSV. It carries the same columns as the table, so it drops straight into a legal or compliance workflow.

​
Signatures are not membership

Signing also puts someone on the NDA’s roster, but the two are separate records.
  • Removing someone from the roster does not remove their signature.
  • Adding someone to a roster by other means does not create a signature.
  • There is no un-signing. A signature is a record of something that happened.

NDA analytics

The same data in aggregate.

The agreement

What the content hash is a fingerprint of.

Player groups

The roster signing also puts people on.

Archiving an NDA

Export before you retire it.