Establishing secure connection…Loading editor…Preparing document…

Video Connection Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

VIDEO CONNECTION AGREEMENT

This Video Connection Agreement ("Agreement") is entered into on by and between:

WHEREAS

WHEREAS, Provider offers video conferencing, connection facilitation, streaming, and related real-time audiovisual communication services ("Video Services"); and

WHEREAS, Client desires to engage Provider to connect Client with specified participants and to provide Video Services under the terms set forth herein; and

WHEREAS, the parties wish to confirm their respective responsibilities for connection quality, data security, recording, and payment.

SCOPE OF WORK

EQUIPMENT, ACCESS, AND TECHNICAL REQUIREMENTS

Provider will supply access credentials and any proprietary connection software required for scheduled connections. Client is responsible for providing compatible endpoint equipment, sufficient internet bandwidth, and a secure location for use of the Video Services. Provider is not responsible for third-party internet outages or end-user device failures.

PAYMENT TERMS

Client shall pay Provider for the Video Services according to the following terms.

Late payments shall accrue interest at on overdue balances until paid. Client shall also reimburse Provider for reasonable collection costs and legal fees incurred to collect any overdue amounts.

TERM AND TERMINATION

This Agreement commences on and will continue until unless earlier terminated in accordance with this Section.

Either party may terminate for convenience by providing days' written notice to the other party. Provider may suspend services immediately for nonpayment or for a material breach that is not cured within 10 days after written notice.

CONFIDENTIALITY

Each party shall treat as confidential all non-public information disclosed in connection with the Video Services that a reasonable person would understand to be confidential ("Confidential Information"). Confidential Information does not include information that (a) is or becomes publicly available through no breach of this Agreement; (b) is rightfully received from a third party without restriction; or (c) is independently developed without use of the other party's Confidential Information. Receiving party shall use at least the same degree of care to protect Confidential Information as it uses to protect its own confidential information, but in no event less than reasonable care.

RECORDING, DATA SECURITY, AND PRIVACY

Provider may record sessions only with prior written consent of the parties. Client provides the following consent to recording: Check to consent

Provider will implement commercially reasonable technical and organizational measures to protect data transmitted or stored in connection with the Video Services. Provider does not warrant absolute security and is not liable for unauthorized access resulting from Client's failure to follow Provider's access or authentication instructions.

LIMITATION OF LIABILITY; INDEMNIFICATION

EXCEPT FOR A PARTY'S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, NEITHER PARTY SHALL BE LIABLE FOR SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT. PROVIDER'S AGGREGATE LIABILITY FOR CLAIMS ARISING UNDER THIS AGREEMENT SHALL NOT EXCEED THE TOTAL AMOUNTS PAID BY CLIENT TO PROVIDER UNDER THIS AGREEMENT DURING THE SIX (6) MONTHS PRECEDING THE CLAIM.

Client shall indemnify, defend and hold Provider harmless from and against any third-party claims arising from Client's breach of this Agreement, misuse of the Video Services, or failure to obtain necessary consents from participants.

FORCE MAJEURE

Neither party shall be liable for delay or failure to perform due to causes beyond its reasonable control, including but not limited to acts of God, telecommunications failures, internet outages, or governmental actions. The affected party shall notify the other promptly and shall use commercially reasonable efforts to resume performance.

GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to its conflicts of law principles.

ENTIRE AGREEMENT

This Agreement, including the Scope of Work and any attachments executed by the parties, constitutes the entire agreement between the parties regarding the subject matter and supersedes all prior or contemporaneous understandings and agreements, whether written or oral. Any amendment must be in writing and signed by both parties.

NOTICES

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses set forth above, or to such other address as a party designates by written notice.

Provider:

By:

Date:

Client:

By:

Date:

Enter text✕

What a Video Connection Agreement Covers

A Video Connection Agreement documents the terms, consent, and technical expectations for a remote video session used to establish identity, transmit information, or record interactions. It typically covers participant consent to recording, authentication methods, permitted uses of recorded content, data protection measures, responsibility for connection quality, and applicable governing law. The agreement can be used for remote onboarding, telehealth intake, virtual notarization sessions, or any process that requires verified identity and an auditable record of a video interaction.

Why this agreement matters and its legal basis

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.

Why this agreement matters and its legal basis

Who typically completes a Video Connection Agreement

Organizations and individuals use this agreement when identity verification, recording consent, or documented remote interaction is required.

  • Real estate agents and title companies arranging remote closings and identity proofing for buyers or sellers.
  • Healthcare providers collecting patient consent for telehealth visits and recorded clinical intake sessions.
  • Employers and HR teams performing remote onboarding or identity checks for new hires.

Use depends on the industry, the sensitivity of information shared, and whether the session will be relied on for legal or regulatory purposes.

Primary signer roles

Requester — Contracting Officer

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.

Participant — Client/Signatory

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).

Essential sections to include in a professional agreement

A robust Video Connection Agreement organizes expectations, consent, and technical details so the session produces admissible and auditable records.

Parties

Identify all participants by legal name, role, and contact details so attribution of actions and consent during the session is unambiguous.

Scope of Session

Describe the purpose (identity proofing, notarization, telehealth intake), allowed activities, and any exclusions so all parties understand intended uses of the recording.

Consent to Recording

Provide explicit, informed consent language describing what will be recorded, how recordings will be used, and how long they will be retained.

Authentication Methods

Specify accepted identity verification steps such as government ID inspection, live selfie matching, KBA, or multi-factor authentication and who performs them.

Technical Requirements

List minimum audio/video quality, supported browsers or apps, acceptable file formats, and fallback procedures to avoid session failures.

Data Security & Retention

State encryption, access controls, retention periods, and how to request copies or withdrawal of consent consistent with privacy laws and retention policies.

Security and compliance elements to state

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Trail: Timestamp, IP, and action log
Access Controls: Role-based access permissions
HIPAA: BAA required for PHI workflows
Record Integrity: Tamper-evident storage
Accessibility: WCAG 2.0 AA considerations

Step-by-step: complete a Video Connection Agreement

Follow these steps to create, execute, and preserve a valid agreement for a remote video session.

  • 01
    Prepare document: Draft terms, record purpose, and add required fields.
  • 02
    Set authentication: Choose ID checks, MFA, or KBA as needed.
  • 03
    Conduct session: Run the video call, verify identity, and record consent.
  • 04
    Archive record: Store recording and audit trail per retention policy.

How to configure the online workflow

Configure digital steps to reduce signer friction while preserving auditability and consent records.

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.

Where to send or file the completed agreement

Decide final destinations for the signed agreement and recording so distribution and custody are clear from the start.

  • Requester Archive: Primary record stored by the initiating organization.
  • Participant Copy: Provide signatory a copy for their records.
  • Third-Party Custody: Send to escrow, title, or legal counsel as required.
  • Regulatory Filing: File copies where law or regulation mandates submission.

Technical delivery and integration options

Ensure the chosen platform supports required integrations, file formats, and authentication before scheduling sessions.

  • Integrations: Salesforce, NetSuite, Microsoft 365
  • File formats: PDF, DOCX, HTML supported
  • Authentication: SMS code, KBA, SSO

Platforms should log audit trails, secure recordings, and allow export in standard formats for legal preservation and review.

Key timing items and expectations

Track critical dates such as effective date, retention start, and any regulatory submission deadlines to remain compliant.

Effective Date:

Enter as MM/DD/YYYY; obligations begin on this date.

Consent Withdrawal:

Specify how long after session consent can be withdrawn.

Record Retention Notice:

State retention period and when deletion may occur.

Notarization Window:

If notarized, note any state-imposed timing for acknowledgements.

Regulatory Filings:

List deadlines for any required filings or disclosures.

Common mistakes to avoid

  • Unclear consent language that fails to state recording purpose and retention, which can invalidate consent for regulated data.
  • Mismatched names between ID and signature block, causing identity evidence to be questioned or rejected.
  • Omitting authentication details (method, outcome) reduces the probative value of the session in disputes.
  • Failing to preserve the audit trail or recording in tamper-evident storage undermines later evidentiary use.

Potential penalties and legal risks

Invalid Agreement: Enforceability risk
Regulatory Fines: Privacy or HIPAA penalties
Evidence Exclusion: Recording inadmissible
Operational Delays: Rework and verification costs
Contractual Liability: Damages for breaches
Reputational Harm: Loss of client trust

Typical vendor pricing and feature snapshot

Compare starting prices and key capabilities for common eSignature vendors; signNow is listed first per available plan information.

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

Real-world uses and results

Organizations use Video Connection Agreements with eSign to complete remote workflows securely and reliably.

Martin Properties — Founder

Tim Martin found remote execution streamlined closings and compliance

  • He used mobile and offline signing to close deals faster
  • He reports processing and executing documents online with full compliance and improved turnaround without in-person meetings, saving staff time and reducing delays.

Fertility Centers of Illinois — Founder

John Butler relied on integrated eSign and API capabilities for patient forms

  • Integration enabled automated delivery and secure storage
  • He praised responsive vendor support and the platform's ability to provide compliant signing workflows for healthcare operations and patient intake.

Frequently asked questions about Video Connection Agreements

Answers to frequent questions about eSigning, recording consent, notarization, and retention for video-based sessions.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users