Can this agreement be signed electronically?

Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the signature shows intent, consent, attribution, and record retention capability.

When is a BAA required?

A Business Associate Agreement is required if the device will access protected health information. Include HIPAA-specific obligations and retention rules in an addendum to the agreement.

Do I need a notary or witnesses?

Most Mobile Device Agreements do not require notarization or witnesses. If state law or related property obligations apply, obtain notarization; follow state-specific rules when necessary.

How do I revoke or modify consent?

Specify a written amendment or revocation process in the agreement and include timelines for returning devices, removing accounts, and confirming data wipes upon revocation.

What if a device is lost or stolen?

Require immediate reporting (typically within 24 hours), remote-wipe authorization, and cooperation with IT for incident response; document the process to support insurance and regulatory reporting.

How long should signed agreements be retained?

Retain agreements for the active assignment term plus at least three years; add HIPAA six-year retention for healthcare or longer as mandated by state or industry rules.

Electronic Signature
Templates
Miscellaneous
Mobile Device Agreement

Mobile Device Agreement

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

MOBILE DEVICE AGREEMENT

Effective Date:

Provider (Company) Provider Address Recipient (Employee / Assignee) Recipient Address

WHEREAS

WHEREAS, Provider maintains ownership of certain mobile device(s) and permits use by Recipient in furtherance of Provider business operations; and

WHEREAS, Recipient requires access to a mobile device to perform job duties and agrees to comply with the terms and conditions set forth in this Agreement; and

WHEREAS, the parties desire to document the allocation, permitted use, care, return obligations, and financial responsibilities related to the mobile device.

SCOPE OF WORK / DEVICE DETAILS

Device Description (make, model, serial/IMEI)

Make / Model: Serial / IMEI: Assigned Phone Number (if any):

Permitted Use and Responsibilities

Recipient acknowledges responsibility to maintain the device in good working order, to prevent unauthorized access, and to notify Provider immediately in the event of loss, theft, or unauthorized use.

PAYMENT TERMS

Device Cost / Monthly Allowance: $

Payment Schedule: One-time payment Monthly allowance Payroll recovery

If payments are made under a schedule, describe schedule and due dates

Late Fee for Delinquent Payments: (applies to amounts not paid within days of due date).

TERM AND TERMINATION

Term Commencement Date: . Term Expiration Date: .

Either party may terminate this Agreement for convenience upon days written notice to the other party. Provider may terminate immediately for cause including material breach, misuse of device, or failure to remit payments.

Upon termination or separation, Recipient shall return the device in good working condition within days. Provider reserves the right to withhold final compensation or recover device value in accordance with applicable law.

CONFIDENTIALITY AND DATA

Recipient acknowledges that devices may contain confidential or proprietary information. Recipient shall not disclose, copy, or transmit Provider confidential information to third parties and shall take commercially reasonable measures to secure data on the device. Confidential information includes but is not limited to customer data, business records, and access credentials.

Provider may, at its discretion, require secure configuration, the installation of mobile device management software, and may perform remote lock or remote wipe in the event of loss, theft, termination, or security incident. Recipient consents to such remote management actions consistent with applicable law.

GOVERNING LAW; INDEMNIFICATION

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to choice-of-law principles. Recipient shall indemnify and hold Provider harmless from claims arising from Recipient's misuse, negligence, or intentional misconduct relating to the device.

ENTIRE AGREEMENT

This Agreement, including all exhibits and any signed acknowledgments attached hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior negotiations and understandings. Any amendment must be in writing and signed by both parties.

ADDITIONAL PROVISIONS

Assignment: Neither party may assign its rights or obligations under this Agreement without the prior written consent of the other party, except that Provider may assign to an affiliate or successor.

Severability: If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect.

Remedies: The parties acknowledge that monetary damages may be inadequate to remedy certain breaches and that equitable relief shall be available in addition to other remedies at law or in equity.

Acknowledgment: Recipient acknowledges receipt of the listed device and agrees to the terms and conditions of this Agreement as evidenced by the signature below.

Provider:

By:

Date:

Recipient:

By:

Date:

What a Mobile Device Agreement Is and When It Applies

A Mobile Device Agreement is a written contract that defines the rights, responsibilities, and acceptable use rules for employer-provided or personally owned mobile devices used for work. It typically covers ownership, permitted applications, security controls, data access, monitoring, reimbursement or stipend terms, return and disposal procedures, and consequences for policy violations. The agreement helps reduce legal ambiguity about data protection, personal privacy, and device custody when devices are used to access corporate systems or handle regulated information.

Why adopt a Mobile Device Agreement

A clear written agreement reduces compliance risk, sets expectations for security and privacy, and documents consent for device management and data access under ESIGN and UETA frameworks.

Who typically completes and signs this agreement

Human resources, IT, and legal teams usually prepare the agreement; employees and contractors sign to acknowledge terms.

IT administrators who configure device management profiles and security settings for corporate access.
Human resources representatives who manage stipends, return procedures, and policy enforcement.
Employees or contractors who accept device provisioning and agree to monitoring, use, and return terms.

Signatories range from full-time staff to temporary contractors; the document is common across industries with sensitive data or remote work policies.

Representative signer profiles

IT Manager

An IT manager signs to certify device configuration and acceptable use enforcement procedures. This profile documents technical controls, remote-wipe authority, and single sign-on or MDM enrollment requirements in one place.

Employee

An employee signs to acknowledge responsibility for physical care, reporting loss promptly, and complying with security measures such as device locking, approved apps, and data handling restrictions; signature documents consent to electronic records under ESIGN.

Essential security and compliance elements

Encryption: AES-256 at rest and TLS 1.2/1.3 in transit

Authentication: Strong passwords and multi-factor authentication

Remote Management: Remote wipe and MDM enrollment required

Audit Logging: Event logs with timestamps and IPs

Privacy Addendum: Notice of monitoring and data access rules

HIPAA Protection: BAA required when PHI is accessed

Core clauses a professional Mobile Device Agreement should include

A complete agreement balances operational needs with employee privacy and legal compliance. Each clause should be clear, measurable, and enforceable.

Device Ownership

Specify whether the device is company-owned, employee-owned with company access (BYOD), or provided under a stipend; include return obligations and conditions for device replacement or repair.

Permitted Use

Define acceptable personal and business use, prohibited activities, and whether personal data will be segregated from corporate data using containers or sandboxing technologies.

Security Requirements

List required controls such as passcodes, encryption, automatic lock, OS update policy, anti-malware, and mandatory MDM enrollment to access corporate resources.

Monitoring and Privacy

Disclose scope of monitoring, data collected, who has access, and how the employer will handle personal data consistent with privacy laws and internal policies.

Loss, Theft, and Reporting

Describe immediate reporting obligations, remote-wipe procedures, employee liability for negligence, and timelines for incident response.

Compliance and Discipline

State consequences for violations, including revocation of access, reimbursement for damage, and disciplinary action up to termination; reference applicable statutory requirements.

Step-by-step: completing and executing the agreement

Follow these steps to prepare, review, sign, and store the agreement securely for compliance and future audits.

01

Prepare: Populate fields and attach device identifiers.
02

Review: Legal and HR verify policy alignment and terms.
03

Sign: Collect electronic signatures and consent disclosures.
04

Store: Save signed PDF with audit trail and retention tag.

Typical digital workflow settings for e-sign and delivery

Configure the workflow to combine authentication, device data, and record retention before sending the agreement for signature.

Field	Configuration
Signature Method	Click-to-sign with audit trail
Authentication	Email link + optional SMS code
Notifications	Automated reminders at 3 and 7 days
Storage	Encrypted PDF with retention tag

Technical considerations for electronic submission

Ensure the platform can produce a tamper-evident signed PDF and maintain an audit trail to meet ESIGN and UETA record retention and evidentiary needs.

Integrations: Salesforce, NetSuite, Microsoft 365
File formats: PDF, DOCX, HTML
Security: AES-256 encryption

How electronic signing typically operates for this agreement

A concise visual workflow: drafting, placing fields, sending, signer authentication, signing, and storing the final record with audit metadata.

Upload: Add the agreement and device inventory attachment
Place Fields: Add signature, date, and initial fields
Send: Email link or invite via platform
Complete: Signer authenticates and signs; platform logs events

Typical timelines and deadlines to include

Define response windows so both parties know timing for provisioning, acceptance, and incident reporting.

Signing Response Window:

Require signature within 7 calendar days of delivery

Device Provisioning:

IT must provision company access within 5 business days

Loss/Theft Reporting:

Report missing devices within 24 hours of discovery

Return on Termination:

Return device within 10 business days of separation

Security Patch Timeline:

Apply critical OS patches within 72 hours

Key processing milestones from issuance to return

Track the major stages to ensure compliance and maintain an auditable trail through the device lifecycle.

01

Request Approval

Manager approves device request and stipend, if any

02

IT Provisioning

IT enrolls device in MDM and configures controls

03

Employee Acceptance

Employee reviews terms and electronically signs

04

Return & Audit

Device returned, wiped, and recorded in inventory

Common mistakes when preparing a Mobile Device Agreement

Leaving security requirements vague, which creates enforcement gaps and inconsistent device configurations across users.
Failing to disclose monitoring and data access clearly, risking employee privacy complaints or regulatory issues in protected industries.
Not defining return conditions or deductible amounts, which leads to disputes and unpredictable replacement costs at separation.
Skipping alignment with IT processes and MDM capabilities, resulting in unenforceable technical requirements or failed automations.

Penalties and risks from incorrect or incomplete agreements

Regulatory Fines: HIPAA or state privacy penalties

Data Breach Liability: Company and individual exposure

Employment Claims: Wrongful discipline or privacy disputes

Reputational Harm: Customer trust erosion

Replacement Costs: Unrecovered device value

Contract Voidance: Unenforceable policy terms

Real-world examples of Mobile Device Agreement use

Two compact examples show how organizations apply the agreement to operational workflows and compliance.

Healthcare Clinic

The clinic issued devices to on-call nurses and required MDM enrollment

5 nurses per shift operate remote access
The agreement included a HIPAA addendum, mandatory BAAs for third-party apps, and rapid remote-wipe procedures to protect patient data.

Field Service Contractor

A construction firm provided phones to site supervisors to manage crews

supervisors used devices for timesheets and photos
The agreement specified photo retention rules, safety app requirements, and lien-waiver attachments for project documentation integrity.

Practical tips for accurate and efficient completion

Follow proven practices to reduce errors, speed execution, and maintain compliance across your device program.

Use standard templates

Create a single vetted template for all device types to ensure consistent terms and faster processing; keep a version history for audits.

Automate field population

Pre-fill name, employee ID, device serial, and policy version to reduce manual entry errors and speed signer completion.

Include clear consent language

State monitoring, remote-wipe authority, and data access explicitly to avoid disputes and ensure ESIGN-compliant consent for electronic records.

Archive signed records securely

Store signed PDFs with an immutable audit trail, retention tags, and role-based access controls to meet legal and operational needs.

eSignature vendor pricing and capability snapshot

A concise comparison of common vendors and features relevant to signing Mobile Device Agreements; signNow is listed first for parity and accurate feature mapping.

	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	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 Mobile Device Agreements

Answers to common legal, technical, and operational questions about preparing, signing, and enforcing Mobile Device Agreements.

Need help? Contact support

Can this agreement be signed electronically?
Yes. Electronic signatures are enforceable under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the signature shows intent, consent, attribution, and record retention capability.
When is a BAA required?
A Business Associate Agreement is required if the device will access protected health information. Include HIPAA-specific obligations and retention rules in an addendum to the agreement.
Do I need a notary or witnesses?
Most Mobile Device Agreements do not require notarization or witnesses. If state law or related property obligations apply, obtain notarization; follow state-specific rules when necessary.
How do I revoke or modify consent?
Specify a written amendment or revocation process in the agreement and include timelines for returning devices, removing accounts, and confirming data wipes upon revocation.
What if a device is lost or stolen?
Require immediate reporting (typically within 24 hours), remote-wipe authorization, and cooperation with IT for incident response; document the process to support insurance and regulatory reporting.
How long should signed agreements be retained?
Retain agreements for the active assignment term plus at least three years; add HIPAA six-year retention for healthcare or longer as mandated by state or industry rules.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now