Should I enroll private (BYOD) devices in deeploi?

Enrolling privately owned devices in deeploi is generally not recommended. deeploi's MDM is designed for company-owned devices, and the same controls that make it effective create significant problems when applied to personal hardware.

What is a BYOD device?

A BYOD device is one that the employee bought and owns, is used for both personal and work purposes, and is not part of the company's device lifecycle. deeploi does not procure, configure, or replace BYOD devices.

Why deeploi does not recommend BYOD enrollment

Reason	What it means in practice
Privacy	Enrolled devices expose installed apps and device attributes to the admin console. Even without active inspection, this can damage employee trust.
Risk of data loss	MDM actions like remote wipe and lock apply to the whole device. If a private device is incorrectly flagged as lost or mixed up in the console, personal data can be erased.
Offboarding complexity	MDM and VPN profiles must be cleanly removed when an employee leaves. On BYOD, this is often missed, leaving stale compliance entries and uncontrolled access paths.
Support scope	Once enrolled, employees expect full IT support for the device. deeploi does not cover personal apps, Apple ID issues, or app breakage caused by policy changes on privately owned hardware.
Policy fit	MDM policies are designed for standardized device configurations. BYOD devices vary in OS version and hardware, making policies either too strict or too weak.
Legal complexity	BYOD enrollment requires written employee consent and alignment with data protection regulations covering scope, access, and data deletion.