Can a device-captured signature be legally binding?

Yes. Electronic signatures that show intent, consent, attribution, and retention meet the ESIGN Act and UETA standards in the United States when those four elements are satisfied.

When is notarization or RON required?

Notarization is required only when the underlying law or the agreement calls for it; some transactions and documents (e.g., certain deeds or powers of attorney) require notarization or state-approved RON.

What if a device is lost or compromised?

Follow the addendum's incident procedures: report within the required time, remotely wipe if possible, suspend the device's signing privileges, and preserve signed records for forensic review.

How do I update the addendum after execution?

Amend by mutual written agreement specifying effective dates and whether prior signatures remain valid; document approval by the same signatory authority used for the original.

Do consumer-facing forms need extra disclosures?

Yes. ESIGN requires consumer-facing electronic transactions include a clear disclosure of the right to paper and a demonstration the consumer can access the electronic format.

How long should I keep signed device records?

Retain records per applicable law and industry rules: at least three years for tax records, six years for HIPAA-related records, and longer where state or industry rules require it.

Device Usage Addendum

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

DEVICE USAGE ADDENDUM

This Device Usage Addendum (the "Addendum") is entered into as of Effective Date: by and between the parties identified below and supplements any existing agreement between them.

Company Name: Company Address: Recipient Name: Recipient Address:

WHEREAS

WHEREAS, Company from time to time issues electronic devices to employees, contractors or agents for the performance of duties and business purposes; and

WHEREAS, Recipient requires access to certain devices and related accessories as specified herein and the parties desire to set forth the terms governing issuance, use, care, return, and liability for such devices; and

WHEREAS, this Addendum amends and supplements the existing agreement between Company and Recipient and, where inconsistent, the terms of this Addendum shall govern the use of the devices listed below.

SCOPE OF WORK

Company will provide the devices identified below for Recipient's use in connection with Recipient's duties and the performance obligations described in the underlying agreement. Recipient shall use the devices solely for authorized business purposes and in accordance with Company policies and this Addendum.

Detailed Scope / Authorized Use (describe tasks, limitations, and any special configurations):

DEVICE INVENTORY

The following devices and accessories are provided to Recipient at issuance. Recipient shall inspect and acknowledge condition at time of receipt.

Device 1 — Description: Serial Number: Condition at Issuance: Accessories / Included Items: Device 2 — Description: Serial Number: Condition at Issuance: Accessories / Included Items:

Ownership of Devices: Device remains Company property Limited incidental personal use permitted

DEVICE CARE, LOSS, AND RETURN

Recipient shall maintain devices in good working order, apply manufacturer updates and security patches as required, and take reasonable precautions to prevent loss, theft or damage. In the event of loss, theft, or damage, Recipient must report to Company within .

Recipient is liable for repair or replacement costs arising from negligent use, deliberate misconduct, or failure to comply with Company-issued policies. Reasonable wear and tear shall be evaluated by Company in its sole discretion.

Return Procedure: devices must be returned to the Company location specified in Notices within of termination or upon request. Items not returned are subject to replacement charges.

PAYMENT TERMS

Fees associated with device issuance, maintenance, insurance, or replacement shall be as follows.

Issuance / Usage Fee (if applicable): Payment Schedule / Billing Terms: Late Fee / Interest:

TERM AND TERMINATION

The term of this Addendum commences on Start Date: and continues until End Date: unless terminated earlier in accordance with this Addendum.

Either party may terminate this Addendum upon written notice to the other party delivered at least prior to the effective date of termination. Company may terminate immediately for material breach, misuse of devices, or failure to return equipment.

CONFIDENTIALITY

Recipient acknowledges that devices may contain or provide access to Confidential Information. Recipient shall protect such information in accordance with the confidentiality obligations of the underlying agreement and shall not disclose, copy, or remove Confidential Information except as necessary to perform authorized duties. All data stored on Company devices remains property of Company and may be accessed or inspected by Company as permitted by applicable law.

INDEMNIFICATION

Recipient shall indemnify, defend and hold Company harmless from any claims, losses, liabilities or expenses arising from Recipient's negligent or intentional misuse of devices, breach of this Addendum, or failure to timely report loss or damage.

GOVERNING LAW

This Addendum shall be governed by and construed in accordance with the laws of the State of without regard to conflict of law principles.

NOTICES

Company Notice Address: Recipient Notice Address:

ENTIRE AGREEMENT

This Addendum, together with the underlying agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

SEVERABILITY

If any provision of this Addendum is held invalid or unenforceable, the remaining provisions shall continue in full force and effect.

Company Printed Name:

By:

Date:

Recipient Printed Name:

By:

Date:

What a Device Usage Addendum Covers

A Device Usage Addendum is a contract attachment that documents permitted uses, security controls, and responsibilities when a party relies on specific hardware or software for work or signature capture. It can govern company-owned devices, personally owned devices used for business, and how electronic signatures captured on those devices are authenticated, stored, and audited. The addendum typically clarifies device inventory, required security settings, acceptable apps, incident reporting, and whether signatures created on the device meet applicable electronic-signature rules.

Why add this provision to your agreement

A Device Usage Addendum reduces ambiguity about who may use which devices and how signatures created on them will be treated, supports regulatory compliance, and limits operational risk by documenting authentication and retention practices.

Who typically completes a Device Usage Addendum

Final approval often requires sign-off from legal, security, and the designated operational owner before the addendum is executed.

IT and security teams who set device policies and verify configurations
HR or procurement when devices are issued to employees or contractors
Contract managers who need to ensure signatures meet legal and audit requirements

Core elements to include in the addendum

A thorough Device Usage Addendum lists device scope, authentication, permitted applications, security controls, signature rules, and incident handling to make obligations explicit.

Device Scope

Define which devices are covered (make/model/OS or BYOD) and whether the device is company- or personally owned.

Authentication

Specify required signer authentication (email link, SMS code, KBA, multi-factor, biometric or certificate-based) and acceptable strengths.

Permitted Software

List approved apps and versions for signature capture and document handling; disallow unsupported or jailbroken software.

Security Controls

Mandate encryption, device passcodes, remote-wipe capability, and automatic updates to reduce compromise risk.

Signature Rules

State whether electronic signatures meet ESIGN/UETA criteria, and when additional measures (notary, RON, PKI) are required.

Incident Response

Describe notification timelines, escrow of signed records, and remediation steps if a device is lost or compromised.

Key information to record in the addendum

Device ID: Serial/IMEI/MAC

Device Owner: Employee or third party

OS and Version: Platform and release

Approved Apps: Signed app list

Authentication: MFA/OTP/Cert

Encryption: AES-256 at rest

Step-by-step: completing and executing the addendum

Follow this sequence to prepare, approve, and finalize the Device Usage Addendum with clear responsibilities and recordkeeping.

01

Draft terms: Identify devices, uses, controls, and signature requirements.
02

Review with security: Confirm controls meet organizational policy and legal needs.
03

Obtain legal sign-off: Legal confirms enforceability and any statute-specific language.
04

Execute and archive: Sign electronically and store with audit trail.

How to set up an online completion workflow

Configure your e-signing workflow so device attestations and signature fields capture the required evidence and audit data.

Field	Configuration
Device ID field	Mandatory text field with validation
Authentication step	Require MFA or SMS OTP
Signature field	Visible signature plus audit trail
Retention rule	Automatic archive with access controls

Where to file and how to route executed addenda

Define a single routing path for executed addenda to ensure consistent storage, retrieval, and auditability.

Primary repository: Store executed addendum in the contract management system.
Security copy: Mirror encrypted copy in secure cloud storage.
Operational notice: Notify IT/security of device assignments and status.
Audit access: Grant read-only access to compliance reviewers.

Digital signing and platform considerations

Confirm the chosen e-sign platform can export signed PDFs with tamper-evident audit trails and supports the integrations required by your systems.

File formats: PDF, DOCX, and XML supported
Integrations: Salesforce, NetSuite, Google Workspace
Authentication: MFA and audit trail

Typical timelines and processing expectations

Set realistic deadlines for device onboarding, signature collection, and incident reporting so obligations are met consistently.

Onboarding deadline:

Device must be registered within 7 business days of issuance

Signature turnaround:

Signers should complete within 5 business days of request

Security remediation:

Report lost/stolen devices within 24 hours

Audit retrieval:

Archive retrieval request fulfilled within 3 business days

Policy review:

Review the addendum annually or on major platform changes

Common preparation mistakes to avoid

Leaving the device identifier field optional, which makes it difficult to link a signature to a specific piece of hardware
Failing to specify acceptable authentication methods, allowing weak or inconsistent signer verification across use cases
Not documenting who is responsible for remote-wipe or device decommissioning when a device is reassigned or lost
Assuming all electronic signatures are equivalent without specifying when notarization or RON is required

Consequences of incomplete or incorrect addenda

Contract disputes: Enforceability challenges

Regulatory risk: HIPAA/FERPA violations possible

Data loss: Inadequate retention or backups

Operational delay: Longer procurement cycles

Financial exposure: Damages or remediation costs

Reputational harm: Loss of client trust

Real-world examples of similar provisions

The following excerpts show how organizations describe device and signature responsibilities in practice.

Optica Ventures — COO

Brian Fitzgibbons used a concise device clause to standardize mobile signing across broker workflows

Short point: simplified customer signing
The clause ensured consistent signature capture and reduced follow-up, making it easier for customers to sign on mobile while preserving an audit trail and clear device responsibilities.

Xerox — Director

Kodi-Marie Evans documented device approval and integration with NetSuite to ensure signatures matched account records

Short point: integration-based validation
This approach linked device-originated signatures to ERP records, improving traceability and reducing reconciliation effort for operations and compliance teams.

Example eSignature vendor pricing and feature comparison

Basic vendor pricing and common feature availability, shown for high-level comparison. Confirm plan details with each vendor before purchase.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Plan	Yes, 30-day trial	No	No	Yes, limited	Yes, limited
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about the Device Usage Addendum

Answers to common questions about enforceability, notarization, updates, and electronic-signature evidence when signatures originate from devices.

Need help? Contact support

Can a device-captured signature be legally binding?
Yes. Electronic signatures that show intent, consent, attribution, and retention meet the ESIGN Act and UETA standards in the United States when those four elements are satisfied.
When is notarization or RON required?
Notarization is required only when the underlying law or the agreement calls for it; some transactions and documents (e.g., certain deeds or powers of attorney) require notarization or state-approved RON.
What if a device is lost or compromised?
Follow the addendum's incident procedures: report within the required time, remotely wipe if possible, suspend the device's signing privileges, and preserve signed records for forensic review.
How do I update the addendum after execution?
Amend by mutual written agreement specifying effective dates and whether prior signatures remain valid; document approval by the same signatory authority used for the original.
Do consumer-facing forms need extra disclosures?
Yes. ESIGN requires consumer-facing electronic transactions include a clear disclosure of the right to paper and a demonstration the consumer can access the electronic format.
How long should I keep signed device records?
Retain records per applicable law and industry rules: at least three years for tax records, six years for HIPAA-related records, and longer where state or industry rules require it.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now