Can the agreement be signed electronically?

Yes. Electronic signatures are legally valid under the ESIGN Act (15 U.S.C. §7001) and UETA in most states provided intent, consent, attribution, and retention requirements are met.

When is notarization required?

Notarization is rarely required for a device usage agreement, but state-specific documents (durable POA, deeds) may require notary or witnesses; check state law or use RON where permitted.

Are special rules needed for HIPAA data?

If personal devices will access PHI, include HIPAA-specific safeguards and ensure a Business Associate Agreement (BAA) is in place where required (45 CFR §164.502).

What if an employee refuses MDM enrollment?

Document alternative controls, restrict access to sensitive systems, and follow HR discipline policies; inconsistency can weaken enforceability if not documented.

How should signed agreements be stored?

Retain signed copies in a secure, access-controlled repository with the audit trail; maintain retention consistent with IRS and HIPAA standards where applicable.

How to revoke or update the agreement?

Use an amendment or new agreement signed by both parties; maintain version history and dates to demonstrate the current terms in force.

Electronic Signature
Templates
Personal
Personal Device Usage Agreement

Personal Device Usage Agreement

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

PERSONAL DEVICE USAGE AGREEMENT

Parties and Agreement Date

This Personal Device Usage Agreement (the Agreement) is entered into on this day of , between the Device Owner and the Authorized User identified below.

Device Owner (Provider)

Owner Name Owner Address Owner Contact Phone

Authorized User

User Name Relationship to Owner User Contact

Device Identification

Device Type: Make: Model:

Serial Number / IMEI: Asset Tag:

Device Condition and Description

Scope of Use

The Owner grants the User permission to use the Device for the following authorized purposes only:

Prohibited Uses

The User shall not use the Device for illegal activities, commercial resale, activities that expose the Device to undue risk, or any uses expressly disallowed by the Owner. Prohibited uses include, but are not limited to:

Security, Access and Data

The User agrees to maintain reasonable security measures while using the Device. Required measures (check all that apply):

Password/PIN protection required Biometric lock required Full-disk encryption required

Data Access, Backups and Personal Information

Loss, Damage, Repair and Replacement

The User shall promptly notify the Owner of loss, theft, or damage. User obligations include reasonable care, immediate reporting, and cooperation with repair or recovery. The User is responsible for:

Fees, Reimbursement and Repair Costs

If the Owner charges for repair or replacement, fees will be as agreed in writing. If an amount is pre-agreed, enter amount:

Term, Return and Termination

The term of this Agreement begins on the date above and continues until terminated by either party with reasonable notice or upon return of the Device. Expected return date (if applicable):

Upon termination the User will return the Device in the same condition except for ordinary wear and tear. The Owner reserves the right to inspect the Device upon return.

Liability and Indemnity

The Owner makes no warranty as to fitness for a particular purpose. The User assumes all risk of use and shall indemnify and hold harmless the Owner from claims, losses, or expenses arising from the User's misuse, negligent handling, or breach of this Agreement, except to the extent resulting from the Owner's gross negligence or willful misconduct.

Dispute Resolution and Governing Law

Any dispute arising under this Agreement will be resolved in a reasonable and cooperative manner. This Agreement is governed by the laws of the state or jurisdiction where the Owner resides, except to the extent preempted by applicable law.

Acknowledgment and Certification

By signing below, each party certifies that they have authority to enter this Agreement, they have read and understand the terms, and they agree to comply with all obligations set forth herein.

Owner Printed Name:

By:

Date:

Authorized User Printed Name:

By:

Date:

What a Personal Device Usage Agreement Is

A Personal Device Usage Agreement is a written contract that defines acceptable use, security responsibilities, and ownership expectations when employees or contractors use their own devices (laptops, tablets, smartphones) to access company systems or data. It typically covers permitted applications, data handling rules, password and encryption requirements, reporting obligations for lost or stolen devices, and the employer's right to manage or remove corporate data. The agreement helps balance employee mobility with organizational security and regulatory compliance when personal endpoints join corporate networks.

Why organizations adopt a Personal Device Usage Agreement

A clear agreement reduces data exposure, clarifies responsibilities for device security, and supports compliance with U.S. laws such as ESIGN/UETA for electronic records and HIPAA where protected health information is involved. It also documents consent for monitoring, remote wipe, and data separation to limit liability while enabling mobile work.

Who typically uses this agreement and why it matters

Employers, HR and IT teams, contractors, and managed service providers commonly issue a Personal Device Usage Agreement to set consistent expectations for BYOD (bring your own device) use.

IT administrators: enforce security controls and define remediation for compromised devices.
HR and legal teams: document consent, acceptable use, and disciplinary measures.
Employees and contractors: understand privacy limits, data-handling obligations, and support responsibilities.

Clear assignment of roles reduces disputes and provides a record for audits, incident response, and regulatory reviews.

Core sections to include in a professional agreement

A robust Personal Device Usage Agreement addresses security, privacy, permitted activities, incident reporting, access controls, and remediation. Each section should be practical, enforceable, and aligned with company policies and any applicable regulations.

Scope

Define covered devices, users, and corporate systems to avoid ambiguity about which endpoints and accounts the agreement governs.

Acceptable Use

List permitted and prohibited activities, including restrictions on sensitive downloads, data sharing, and use of unsecured networks.

Security Requirements

Specify minimum protections such as OS updates, passcodes, encryption, anti-malware, and automatic lock settings.

Data Handling

Explain separation of personal and corporate data, data classification, encryption for stored/transmitted corporate data, and backup expectations.

Remote Access and Controls

Describe corporate rights for MDM enrollment, remote wipe, selective wipe, and the process for revoking access when employment ends.

Incident Reporting

Require prompt reporting of lost/stolen devices, suspected compromise, and outline steps for containment and forensic review.

Step-by-step: completing the agreement

Follow these steps to ensure the signed agreement is enforceable and correctly linked to employee access.

01

Read policy: Review the full agreement and linked security policies before proceeding.
02

Provide details: Enter device identifiers, corporate account, and contact information accurately.
03

Accept controls: Acknowledge required security settings and MDM enrollment where applicable.
04

Sign and store: Use a compliant signature method and save a copy for records.

Configuring digital completion and routing

Set up an electronic workflow so submissions trigger provisioning, auditing, and record retention automatically.

Field	Configuration
Signer sequence	Employee signs first, manager or IT approves next.
Authentication	Use email link with optional SMS OTP for higher assurance.
MDM enrollment	Automated link triggers device enrollment after signature.
Archive location	Save executed agreements to secure records manager or encrypted cloud storage.

Typical digital processing flow

A standard e-submission workflow reduces friction while capturing the audit trail needed for legal validity and compliance.

Upload: Administrator uploads the template to the signing platform.
Place fields: Add signature, date, and acknowledgment checkboxes.
Send: System emails the signer a secure link to review and sign.
Complete: Signed document and audit trail are archived automatically.

Technical and platform considerations for e-submission

Ensure the platform supports required integrations, file formats, and authentication methods before automating the agreement.

File formats: Supports PDF, DOCX, and HTML exports.
Integrations: Connects with systems like Microsoft 365, Google Workspace, and HRIS.
Authentication: Allows email, SMS OTP, KBA, and SSO options.

Platform capabilities should align with security, retention, and audit requirements; confirm BAA availability if the agreement covers HIPAA-regulated data.

Required details and declarations to capture

Full legal name: Employee's official name

Device identifier: Make/model/serial

Work account: Corporate email or username

Security acknowledgments: MDM/encryption/passcode

Incident contact: Phone or security desk email

Signature and date: Signed consent and timestamp

Common preparation mistakes to avoid

Using vague terms for 'sensitive data' that create enforcement gaps and inconsistent handling.
Failing to specify acceptable authentication or leaving signature methods undefined for high-risk roles.
Neglecting to state how personal data is separated from corporate data and who controls backups.
Not aligning the agreement with existing policies (IT, HR, privacy), causing conflicting obligations.

Risks and consequences of incomplete or incorrect agreements

Regulatory exposure: Potential HIPAA violations for PHI mishandling (45 CFR §164.530(j))

Tax and recordkeeping: Failure to retain records can affect audits (IRC §6501(a))

I-9 noncompliance: Paperwork fines per 8 CFR §274a.2, $281–$2,789 per violation

Data breach liability: Civil damages and remediation costs for exposed PII

Contract disputes: Ambiguous terms may be unenforceable in litigation

Operational disruption: Unclear device control rights hinder incident response

eSignature vendor comparison for signing Personal Device Usage Agreements

Compare basic pricing and common plan-level capabilities relevant to executing and storing signed agreements; signNow is listed first per vendor ordering conventions.

	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	Varies	Varies	Varies
Bulk Send	Yes (Premium)	Yes	Yes	Yes	Yes
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions about Personal Device Usage Agreements

Answers to common questions about enforceability, signatures, notarization, and recordkeeping when using personal devices.

Need help? Contact support

Can the agreement be signed electronically?
Yes. Electronic signatures are legally valid under the ESIGN Act (15 U.S.C. §7001) and UETA in most states provided intent, consent, attribution, and retention requirements are met.
When is notarization required?
Notarization is rarely required for a device usage agreement, but state-specific documents (durable POA, deeds) may require notary or witnesses; check state law or use RON where permitted.
Are special rules needed for HIPAA data?
If personal devices will access PHI, include HIPAA-specific safeguards and ensure a Business Associate Agreement (BAA) is in place where required (45 CFR §164.502).
What if an employee refuses MDM enrollment?
Document alternative controls, restrict access to sensitive systems, and follow HR discipline policies; inconsistency can weaken enforceability if not documented.
How should signed agreements be stored?
Retain signed copies in a secure, access-controlled repository with the audit trail; maintain retention consistent with IRS and HIPAA standards where applicable.
How to revoke or update the agreement?
Use an amendment or new agreement signed by both parties; maintain version history and dates to demonstrate the current terms in force.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now