Purpose
Describe why the signature is requested and the transaction’s legal effect so the signer understands the consequences of signing.
A concise disclosure establishes consent, clarifies the signer’s rights, and supports enforceability under ESIGN (15 U.S.C. ch. 96) and state UETA laws; it reduces later disputes about intent and retention.
The disclosure is used by organizations that collect electronic signatures and by individuals asked to sign electronically.
Tailor distribution and authentication to the recipient type and the legal sensitivity of the document.
An executive or officer who has contract authority; must confirm identity and corporate capacity before signing to ensure enforceability and to bind the entity.
A private person providing consent for electronic records; consumer-facing disclosures must explain the right to paper and how to withdraw consent per 15 U.S.C. §7001.
Describe why the signature is requested and the transaction’s legal effect so the signer understands the consequences of signing.
State that the signer agrees to conduct the transaction electronically and acknowledge the right to receive a paper copy.
Confirm the file formats and device/browser requirements needed to access records and demonstrate how to obtain paper copies.
Explain authentication options used (email link, SMS, KBA, or advanced methods) and the data captured for attribution.
Set out how long records will be retained and how they will be produced on request in legible form.
Describe the procedure to withdraw consent and the effect of withdrawal on the transaction or record format.
| Field | Configuration |
|---|---|
| Require Disclosure | Set as required field before signature |
| Auth Strength | Choose email-only, SMS, or KBA |
| Conditional Logic | Show additional fields if signer indicates 'No' or needs paper copy |
| Retention Setting | Mark record retention period and export format |
Confirm platform compatibility, file formats, and signer device requirements before sending the disclosure.
Present disclosure and obtain affirmative consent
Retention begins on effective date or signature date
Paper option must be offered before consent is recorded
Provide required disclosures before tax reporting where applicable
Produce signed records within regulator deadlines
Finalize disclosure text and legal approval
Attach disclosure to signing workflow
Collect signature, consent checkbox, audit data
Store signed record and produce on valid request
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
airSlate SignNow integrated the disclosure into patient consent packages to collect electronic authorization quickly
Used an embedded disclosure for lease signings to confirm tenant electronic consent
A scanned government ID or identity proofing record supports signer attribution and helps meet notary or KBA requirements.
A HIPAA or privacy addendum clarifies health or consumer data handling and complements the disclosure language.
Corporate resolution or power-of-attorney documents demonstrate signers’ authority to bind an entity when required.
Attach the primary contract or form referenced in the disclosure so the signer sees the exact obligations being accepted.