I have personal photos on my work phone. Can my employer see them?

Your company gave you a phone, or asked you to add a work account to your own. Over time it filled up with your own life: photos of your kids, a partner, a doctor’s letter. Now you wonder what IT can see from its side. And what happens to those photos when you leave the job? The answer depends on who owns the phone and how your company set it up. Apple and Google both publish what device management can and cannot do. This page sums up those rules. We checked each fact against Apple’s and Google’s own pages on 2026-10-08.

First, who owns the phone?

This decides almost everything.

• Your own phone, with work added. On iPhone, that is usually account-driven User Enrollment. On Android, it is a work profile. Apple says this kind of management covers “only an organization’s accounts, settings, and information provisioned with a device management service, never a user’s personal account.”
• A phone the company owns. On iPhone, that is usually Automated Device Enrollment or Device Enrollment. On Android, it is a company-owned device. Your employer gets much more control.

If you are not sure which one you have, ask IT. On Android, Google says the device policy app you installed at setup “details the data on your device that is captured and recorded.”

What your employer cannot see

Apple publishes a table of what device management can do under each enrollment method. For every method, including company-owned phones, it marks these as Not allowed:

• View personal calendars, contacts, mail, notes and reminders
• View iMessage or SMS messages
• View FaceTime or phone call logs
• View Safari browser history
• Query the device location
• Collect how often you use apps

Apple’s table does not list photos at all. Google is more direct for work profiles: “Your personal apps, data, and usage details aren’t visible or accessible to your organization.”

What your employer can do

Seeing your photos is one question. Removing them is another.

On iPhone, Apple’s table shows that company-owned enrollment methods can:

• Query the list of all apps. Your employer can see the names of the apps you install. User Enrollment cannot.
• Remotely erase all content and settings. That erases your personal photos with everything else. User Enrollment can erase only managed data.
• Configure a global HTTP proxy. On phones set up with Automated Device Enrollment, web traffic can pass through a server the company picks.

On Android, Google says that on a personally owned phone with a work profile, the company can “remotely create, access, and delete data in your Work Profile.” On a company-owned phone, it can also:

• “Disallow (and uninstall) specific apps in your personal profile”
• “Block the use of the private space on the personal profile”
• “Configure factory-reset protection settings and factory-reset the device”
• “Disable device’s camera” and “Block USB file transfers”

Your employer’s own privacy policy and the law where you work may limit this further. Ask IT or HR what they collect.

The real risk: losing the photos

For most people, the risk is not a manager scrolling their camera roll. It is the day the phone goes back. You hand in a company phone when you leave, or IT erases it after a loss or a policy change. Photos that lived only on that phone go with it.

Photos in a work profile are work data. Photos you save into a work app’s storage may count as work data too. Some people use iCloud Photos with a personal Apple Account on a work iPhone. Apple notes that a delete there removes the photo from every device on that account.

So the safe pattern is simple:

1. Keep personal photos on a phone you own, where possible.
2. If they are on the work phone now, copy them to your own phone or your own cloud.
3. Check that the copy is complete, then remove them from the work phone.

When you leave the job, read selling or trading in your phone. It shows how to clear a phone without deleting your cloud copies.

Where York Vault fits

York Vault encrypts each item on the phone with its own key and opens only with its own code. Your employer cannot read your items without that code, and neither can we. The lock options page covers the code types. See what we can and cannot see.

Two limits apply on a company phone. The app itself shows up in the app list that a company-owned iPhone reports. A company-owned Android phone can block or remove it. Disguise icons change what the home screen shows, but they do not hide the app’s name from the system. And if IT erases the phone, York Vault’s local files go too.

That is why the backup matters. York Vault backs up every item, encrypted, under your personal account: your own iCloud on iPhone or your own Google Drive on Android. The encrypted backup page explains how restore works with your code or recovery key.

To move your library to a phone you own, use phone-to-phone transfer. It works between iPhone and Android in both directions, over local Wi-Fi, with no internet. See moving between iPhone and Android. To take everything out in its original format, use export everything. Exported copies are not encrypted. Download York Vault for iPhone or Android.