Private
Agreement-specific sessions.
Signing links are designed to be scoped, expiring, single-use, and excluded from indexing, caching, and referrer leakage.
Native TermsForward signing
Native signing
The accepted architecture uses a TermsForward-owned signing ceremony. External signature-management platforms can be optional adapters, not a requirement for the core workflow.
How it works
The signature stays bound to the agreement record.
A signing ceremony should prove the exact document, intended recipient, disclosure, explicit human action, and completion evidence without outsourcing agreement truth.
Exact
Document-bound consent.
The signer views and accepts an exact immutable document version with a recorded disclosure and ceremony evidence.
Portable
Provider-neutral delivery.
Transactional email can carry the invitation, while optional provider adapters may extend management without becoming the source of agreement truth.
A calmer agreement operation