Parties
Identify all participants by legal name, role, and contact details so attribution of actions and consent during the session is unambiguous.
A Video Connection Agreement clarifies consent, evidence trails, and technical responsibilities while enabling remote transactions to meet ESIGN and state electronic transaction laws such as UETA or state ESRA. It reduces ambiguity about recordings, protects privacy expectations, and supports enforceability when signer intent and record retention are documented.
Organizations and individuals use this agreement when identity verification, recording consent, or documented remote interaction is required.
Use depends on the industry, the sensitivity of information shared, and whether the session will be relied on for legal or regulatory purposes.
The party initiating the session who defines technical requirements and consent language. They must ensure the agreement lists recording purposes, storage location, retention period, and signatory authentication methods to avoid later disputes.
The person whose identity is being verified or who consents to recording. They should confirm their legal name, attest to understanding consent language, and provide any required authentication (ID, selfie, knowledge-based answers).
Identify all participants by legal name, role, and contact details so attribution of actions and consent during the session is unambiguous.
Describe the purpose (identity proofing, notarization, telehealth intake), allowed activities, and any exclusions so all parties understand intended uses of the recording.
Provide explicit, informed consent language describing what will be recorded, how recordings will be used, and how long they will be retained.
Specify accepted identity verification steps such as government ID inspection, live selfie matching, KBA, or multi-factor authentication and who performs them.
List minimum audio/video quality, supported browsers or apps, acceptable file formats, and fallback procedures to avoid session failures.
State encryption, access controls, retention periods, and how to request copies or withdrawal of consent consistent with privacy laws and retention policies.
| Step | Configuration |
|---|---|
| Upload Document | Add fields for names, dates, consent, and authentication notes. |
| Authentication | Enable SMS codes, ID upload, or KBA as required by risk level. |
| Recording | Set audio/video capture on and choose storage location. |
| Notifications | Configure email/SMS notifications and signed-copy delivery. |
Ensure the chosen platform supports required integrations, file formats, and authentication before scheduling sessions.
Platforms should log audit trails, secure recordings, and allow export in standard formats for legal preservation and review.
Enter as MM/DD/YYYY; obligations begin on this date.
Specify how long after session consent can be withdrawn.
State retention period and when deletion may occur.
If notarized, note any state-imposed timing for acknowledgements.
List deadlines for any required filings or disclosures.
| 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 trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Premium) | Yes | Yes | Yes | Limited |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes (BAA req) | Varies by contract | Varies by contract | Varies by contract | Varies by contract |
Tim Martin found remote execution streamlined closings and compliance
John Butler relied on integrated eSign and API capabilities for patient forms