TL;DR
- COPE phones belong to the company, but employees also use them for personal apps, accounts, and AI tools.
- MDM controls how these phones are set up, but it can’t see what data leaves them or what threats arrive through personal apps.
- Turning on more MDM restrictions closes some gaps, but it also takes away the personal use that made COPE worth choosing.
- The better approach is security on the device that checks where connections go without reading personal content.
- Corrata does this on the phone itself, blocking phishing and uploads to unapproved services while keeping messages, files, and browsing private.
An employee takes a screenshot of a project document in a managed app and sends it to a friend through a personal messaging app on the same phone. That evening, their photo library syncs to a personal cloud account. Your MDM console still shows a compliant, encrypted, fully patched device, because by every measure MDM checks, it is one.
This is the visibility gap on corporate-owned, personally enabled (COPE) phones. MDM tells you whether a phone is configured correctly. It doesn’t tell you what data leaves the phone through personal apps, cloud sync, or AI tools, or which threats arrive through them.
This guide explains where COPE phones can leak data, what MDM can and can’t see, and how to close the gap without taking away the personal use that made COPE attractive in the first place.
What is a corporate owned personally enabled device?
A corporate owned personally enabled (COPE) device is a phone or tablet that the organisation buys, owns, and manages, and that the employee is also allowed to use for personal apps and accounts.
COPE sits between the two other common ownership models:
- BYOD (bring your own device): The employee owns the phone and enrols it for work access, so the organisation’s control is limited to work apps and data.
- COBO (corporate-owned, business only): The organisation owns the phone, and personal use isn’t permitted.

Many organisations choose COPE because it gives IT ownership of the hardware while sparing employees from carrying two phones. How it works depends on the platform. On iPhone, COPE devices are usually enrolled through Apple Business Manager and supervised, with personal Apple Accounts and apps allowed by policy.
On Android, Android 11 brought the work profile to company-owned devices, giving employees the same privacy protections they get on personal phones by restricting IT’s visibility into their personal apps and data.
How can a locked-down COPE phone leak data?
When leadership hears that phones are locked down, they often assume they’re secure. In practice, the lockdown usually applies to the managed side of the device, while the personal side stays open by design. That leaves several routes for company data to leave the phone:
- Screenshots and screen recordings: An employee can capture content from a managed app and share the image through any personal messaging or social app installed on the same phone.
- Personal cloud accounts: A personal Apple Account or Google account can sync photos, notes, and files to storage your organisation doesn’t control, and from there to the employee’s other devices.
- The camera: Photos taken in areas where they shouldn’t be can be backed up automatically before anyone notices.
- Third-party and sideloaded apps: Many COPE policies allow almost any app. On Android, personal-side allowlists and blocklists only govern the Play Store, so if installing from unknown sources is enabled, users can sideload apps that bypass them entirely.
- Encrypted messaging apps: End-to-end encrypted apps keep message content out of reach of network tools, which also makes later investigations harder.
- Shadow AI: Employees paste and upload work content into AI chatbots, and AI features increasingly arrive built into apps and operating systems. Our own detection data shows how fast this is moving: over six weeks, 84% of customer mobile fleets carried AI traffic, and 69% of the AI domains detected had never been seen before, so a blocklist written today is already out of date.
What MDM controls, and what it can’t see
MDM decides what is allowed on a device. On iPhone, Apple’s device management restrictions let you stop users saving screenshots or recording the screen, and iCloud restrictions let you prevent users from using iCloud Photos.
On Android COPE devices, organisations can control which apps are available in the personal Play Store, but they can’t see which apps are actually installed or how they’re used.
Each of these restrictions removes something employees were promised when the organisation chose COPE. A device-wide screenshot block applies to personal photos and chats as well as work documents, and switching off personal cloud sync affects the employee’s own photos. That’s why many organisations leave these settings off, and why the gap usually remains.
Even with every restriction applied, MDM reports configuration and compliance. It doesn’t show where data is going or whether a connection is malicious. Web gateways and VPN tunnels can show that a phone is sending traffic, but on their own they often give security teams little context about what the device is actually doing. Our post on MDM vs MTD covers this division of roles in more detail.
How do you get visibility without breaking the “personally enabled” deal?
Visibility on a COPE phone has to respect the employee’s personal life, or adoption, trust, and often legal sign-off will suffer. The approaches that work tend to share a few principles:
- Inspect connections, not content: Security decisions can be made from where a connection is going, such as the domain, server name, and certificate, without reading messages, photos, or files.
- Decide on the device: Inspecting traffic on the phone itself avoids routing personal browsing through a vendor’s cloud.
- Send only what security needs: Your console needs threat events, device risk, and policy actions, not a record of everything the employee does.
- Tell employees what you can see: A short, plain explanation of what is and isn’t collected does more for adoption than any policy document. Our page on employee buy-in covers how to approach this.
- Involve your DPO early: A clear data inventory makes the DPIA shorter and helps works councils and employee representatives agree.
Our page on privacy by architecture explains how Corrata applies these principles.
Questions to ask a mobile security vendor about COPE
When you evaluate mobile security for a COPE fleet, these questions separate tools built for mixed-use phones from those built for locked-down ones:
- Coverage: Does the tool protect the whole device, or only the work profile on Android?
- MDM fit: Does it work alongside the MDM you already run, or does it require its own?
- Inspection: Is traffic inspected on the phone, or routed through the vendor’s VPN or cloud?
- Data flows: Exactly what data leaves the device, and where is it hosted?
- AI and SaaS visibility: Can it show which AI services and cloud apps employees use, including ones you haven’t heard of?
- Response: Can it cut a compromised device off from corporate apps automatically, and how does the employee fix the problem?
- Integration: Does it share device risk with your identity provider and feed your security tools?
How do you build the business case for COPE security?
Mobile security spending is usually weighed against cost, employee experience, and the level of risk the organisation is prepared to accept. A case that addresses all three is easier to approve than one built on worst-case scenarios.
- Link it to your obligations: If you’re subject to GDPR, NIS2, or customer security audits, show how mobile visibility supports the security measures and evidence those require.
- Map what phones can reach: List the corporate data employees access from their phones, such as email, files, collaboration apps, and single sign-on, and set it against the security controls already in place for the same data on other endpoints. The difference shows the risk that currently goes unmeasured.
- Bring evidence from your own estate: Figures from your own devices carry more weight than industry statistics. Our detection data shows how quickly visibility changes the conversation: when a partner trialled Corrata on three employees’ phones, it recorded 700 hits to AI services in ten days. A short proof of value on a small group of devices can give you equivalent figures on AI use, risky apps, and blocked phishing.
- Show that personal use is protected: Targeted controls, such as blocking uploads to unapproved services, are easier to approve than device-wide restrictions that remove features employees value.
- Settle privacy questions early: Bringing your DPO and employee representatives in at the start, with a clear inventory of what data leaves the device, removes one of the most common reasons approval stalls.
How Corrata secures COPE phones
Corrata adds the visibility and protection that MDM wasn’t built to provide, while keeping personal use private:
On-device threat protection: Reflex, Corrata’s on-device engine, inspects each connection on the phone and blocks phishing sites whether the link arrived by text, WhatsApp, QR code, social media, or a collaboration tool, including sites on newly registered domains with no established reputation.
Shadow AI governance and DLP: Corrata blocks uploads of sensitive files to unsanctioned AI tools, file shares, email, and collaboration services, whether they come from an app or a browser, and discovers and classifies new AI apps as they appear. Find out more about shadow AI and DLP on employee phones.
Risky app detection: Corrata stops apps that over-reach on permissions, carry known vulnerabilities, or come from outside the official stores.
Device quarantine: When Reflex detects signs of compromise, the device is isolated immediately and blocked from enterprise apps, and the employee is guided through fixing the issue. Identity Gate checks that a device is secure at the moment of login.
Works with your MDM: Corrata offers zero-touch deployment and integrates with leading MDM platforms, including Microsoft Intune and Workspace ONE, as well as identity providers such as Microsoft, Google, and Okta, and EDR and XDR tools such as Microsoft Defender for Endpoint. See deployment and integration for details.
Privacy by architecture: Corrata never collects location and never scans files, photos, messages, or browsing history, and personal app data on mixed-use phones stays on the device, with only security verdicts and device risk reaching your console.
To see how Corrata closes the visibility gap on your own COPE devices, request a demo below.




