Employees may use their personal phone for work if the employer allows it. But does it make sense? And when a personal phone is used for work, who is actually liable if something goes wrong and sensitive data is, for example, siphoned off?
The basic rule: the company always remains responsible for company data, not the employees. So you need a written policy, a technical separation of private and work content, and a plan for loss and offboarding. Alternatively, you provide the devices yourself, for example through a Device-as-a-Service provider like Everphone. That can also be set up so that private use is allowed on top.
Let's assume for now that the phone belongs to the employee. The obligations are still yours as the person responsible for IT. This imbalance is exactly what makes personal phones at work so tricky: you carry the responsibility for a device you barely have access to.
Who Is Responsible for Company Data on a Personal Phone?
The company. The GDPR defines the "controller" (Art. 4(7)): whoever decides on the purposes and means of data processing is liable for it. The fact that employees use their own phone changes nothing. Customer contacts, personnel files and emails remain company data.
An example: Lena from sales reads customer emails on her iPhone. In the evening her daughter uses the device for a game that requests access to contacts. The data breach is still yours, not Lena's.
Then there is the accountability principle (Art. 5(2)). You must be able to demonstrate that you protected the data appropriately. "We allowed it and regulated nothing" is not proof.
Which GDPR Obligations Apply When Personal Phones Are Used for Work?
The same ones as for any company device. The only difference is how hard they are to implement.
| Obligation | Basis | What it means for a personal phone |
|---|---|---|
| Appropriate technical and organisational measures | Art. 32 | Screen lock, encryption, current updates, separate work area |
| Record of processing activities | Art. 30 | The personal device and the apps used on it are listed in the record |
| Reporting data breaches | Art. 33 | A loss or theft must reach you quickly; the deadline is 72 hours from becoming aware |
| Erasure | Art. 17 | On departure, company data must disappear from the device; private data stays |
| Accountability | Art. 5(2) | Policy and protective measures are documented |
A breach of Art. 32 can be fined up to €10 million or 2 percent of worldwide annual turnover (Art. 83(4)). In practice, amounts for mid-sized companies are far lower. The risk is still real as soon as someone asks after an incident what you had put in place beforehand.
May You Monitor a Personal Phone or Wipe It Remotely?
Only the work part. You have no access to private photos, chats and apps, and wiping the entire device remotely is not an option. That holds even if someone agrees, because consent in an employment relationship is considered problematic: it is rarely truly voluntary (§ 26 BDSG, the German Federal Data Protection Act).
The technical consequence: you need an approach that manages only the work area. On Android that is the work profile; on iPhones it is enrolment as "User Enrollment". Both separate work from private content, and the management side sees only the work apps and data. How this relates to MDM is covered in our article on what the GDPR means for mobile device management.
If you have a works council, it has a say in technical systems that can monitor employees (§ 87(1) no. 6 BetrVG, the German Works Constitution Act). An MDM on personal devices usually falls under this.
What Belongs in the Written BYOD Agreement?
An agreement you can explain on one page. You need these points:
- Which devices and operating system versions are permitted, and when a device no longer qualifies
- Which protective measures are mandatory: screen lock, encryption, updates within a fixed deadline
- Which data and apps may live in the work area and which may not
- What IT may see (only the work area) and what it may not (everything else)
- What to do in case of loss, theft or suspected malware, with a named contact person
- What happens on departure: the work area is removed, the rest of the device is left untouched
- Who pays for what, for example a contribution to the mobile plan and device
On the question of costs: whether and how much the employer has to pay depends on the individual case. So state it explicitly in the agreement instead of leaving it open.
For the reverse situation, a company phone with private use, there is a suitable template in our article on the agreement for private use of work phones.
How Do You Cleanly Separate Work and Private Data Technically?
With a work area that is sealed off from the rest of the device. Work emails, calendars and contacts run there. Private apps cannot reach this data, and the work apps see nothing private.
The edges are where it gets difficult. The address book is one example: if a messenger like WhatsApp syncs private and work contacts, customer data ends up with a service you have no contract with. The work area prevents exactly that, because the messenger cannot access the work contacts. More on this in our article on data separation on company phones.
What remains is people. Anyone who sends company documents as a screenshot into a private chat bypasses every separation. Only training helps against that, and it belongs in your proof under Art. 5(2).
What Happens on Loss, Theft or Departure?
In case of loss, time counts. Your 72-hour window for reporting starts as soon as you learn of the incident. Your advantage with a work area: you can lock or wipe it immediately without touching the personal device. We described the steps for a lost device in Lost company phone: the first 72 hours.
On departure it is simpler, but only if you set it up beforehand. The work area is removed on the last working day. Without a work area, all you have is a request to employees to delete the data themselves. You cannot verify that.
When Personal Phones at Work Aren't Worth It
If the data is sensitive, BYOD does not pay off. That includes health data, personnel files and anything subject to special confidentiality. There, the effort for policy, co-determination and training is higher than the cost of a dedicated device.
The same applies if you cannot give up control. Anyone who must enforce mandatory updates, device lock and wiping needs a device that belongs to them or that they are allowed to manage. You can find the models compared in BYOD vs. COPE vs. CYOD.
A middle way is Choose Your Own Device: employees pick a device, and the company manages it. Freedom of choice remains, responsibility clearly sits with you, and you have every option for meeting your GDPR obligations. The device can be a rental device, with MDM and replacement in case of damage.
Our recommendation: only allow personal phones if the data is uncritical and you have a work-area solution in place. In all other cases, issue devices yourself.
Frequently asked questions
Can an employer require me to use my personal phone for work?
In principle, no. Without an explicit agreement, there is no obligation to use your own device for work. The employer provides the work equipment. Whether there are exceptions depends on the employment contract (under German law).
Does the GDPR apply if employees only read emails on a personal phone?
Yes. As soon as personal data such as the names or contact details of customers appears on the device, you are processing it. The obligations under Art. 32 then apply to that as well.
As an employer, may I locate or read out my employees' personal phones?
No. You only have access to the work area. Locating the device, reading private content or remotely wiping the whole device is not permitted. More on this in What employers may do when monitoring company phones.
What happens if a data leak occurs on a personal phone?
As the controller, you are obliged to report it, as a rule within 72 hours to the data protection authority. If the leak resulted from missing protective measures, a fine may follow. That is why a lost device should reach IT immediately.
