Skip to content
Knowledge base

BYOD policy: rules for personal phones and laptops in the company (GDPR, MDM)

The sales director wants to read the CRM on a personal phone, a new designer brings her own laptop, and HR asks whether a departing employee's smartphone can be wiped. A BYOD policy answers these questions before they are asked: it sets the scope of access, the limits of employer control and the rules for compensation.

The sales director wants to read the CRM on a personal iPhone, a new designer brings her own MacBook, and HR asks whether a departing salesperson’s smartphone can be wiped remotely. Each of these requests has a sensible answer, but if the administrator gives it in the corridor, the company soon has many different verbal arrangements and no control over where its data is.

A BYOD policy turns such decisions into rules that apply to everyone in the same way. It is a cybersecurity and data protection document rather than a technical manual: it decides what a personal device can access, what the company can do on it and where the employee’s privacy begins.

What is a BYOD policy and how does it differ from allowing a personal phone?

A BYOD policy is a document that specifies who can connect to which company resources with which personal devices, under what technical conditions and with what rights for the company over those devices. Allowing a personal phone is a single decision; a policy is a rule that repeats that decision in every case and can be enforced. The concept of BYOD and its variants is described in the glossary.

In SP 800-46 Rev. 2 “Guide to Enterprise Telework, Remote Access, and Bring Your Own Device (BYOD) Security”, published in July 2016, NIST recommends developing a telework security policy that defines telework, remote access and BYOD requirements.

Which regulations does a BYOD policy need to take into account?

A BYOD policy has to take into account above all the GDPR, because personal data of customers and employees ends up on personal devices, and for remote work in Poland also the remote work chapter of the Labour Code. The legal position described below is as of 17 November 2026.

Three provisions of the GDPR matter most. Article 5(1)(f) requires data to be processed in a manner that ensures its security, including protection against accidental loss, using appropriate technical or organisational measures. Article 24(2) provides that, where proportionate, the controller’s measures include the implementation of appropriate data protection policies. Article 32 requires measures ensuring a level of security appropriate to the risk, which takes into account, among other things, accidental loss of data and unauthorised access. A BYOD policy is one of those measures: it covers data the company processes, including when it sits on a personal device.

The Polish Labour Code (consolidated text: Journal of Laws 2026, item 1245) defines remote work in Article 67¹⁸ as work performed wholly or partly at a place indicated by the employee and agreed with the employer. For such work, Article 67²⁴ § 2 allows the parties to agree rules for using work materials and tools not provided by the employer. Article 67²⁶ requires the employer to set procedures for protecting personal data for remote work, and Article 67²⁸ governs inspections, including inspection of compliance with information security and protection requirements. Outside Poland, compensation for personal equipment and employee monitoring are governed by the labour law of the country concerned.

These provisions apply to remote work. If a personal phone is also used in the office, it is worth covering both cases with the same security rules and agreeing the settlement of costs with HR and a lawyer.

Which data and systems should personal devices have access to?

Personal devices should get narrower access the less control the company has over their security posture. In SP 800-46 Rev. 2, NIST gives an example of tiered levels of access: organisation-owned computers can access many resources, personally owned computers and third-party-controlled devices a limited set, and personally owned smartphones and tablets only one or two lower-risk resources, such as webmail.

This model reverses the usual order of writing a policy. Instead of starting with a list of technical requirements, the company first classifies its data and systems by risk, and only then assigns device categories to them. Email and calendar are a different class from the HR and payroll system, the code repository or the cloud admin console.

NIST also allows the simplest solution: prohibiting telework involving particular types of information, such as sensitive personal data. In a BYOD policy this means a list of systems that personal devices cannot access at all, regardless of their security — without it, every exception becomes a precedent.

Key takeaways:

  • First classify data and systems by risk, only then set device requirements.
  • In the NIST example, a personal smartphone gets webmail, not access to HR or administrative systems.
  • A list of systems closed to personal devices has to exist, even if it is short.

What technical requirements should a personal device meet?

A personal device should meet a minimum that protects company data if the hardware is lost or stolen and if credentials are compromised. In SP 800-46 Rev. 2, NIST recommends assuming that devices used outside the company will be lost or stolen and acquired by parties who will try to recover data from them or use them to gain access to the network. As ways of mitigating this risk, it lists encrypting the device’s storage, encrypting sensitive data or not storing it on the device, and against device reuse — strong authentication, preferably multi-factor.

This leads to a practical minimum to write into the policy: screen lock, storage encryption, an operating system supported by the vendor and kept up to date, and multi-factor authentication for company resources.

For particularly risky tasks NIST goes further: high-risk telework may be permitted only from devices issued and secured by the organisation, with multi-factor authentication and storage encryption. A BYOD policy should say so explicitly, so that a request for administrative access from a personal laptop has a clear answer.

MDM or container: how much control over a personal device does a company need?

With personal phones, the company needs control primarily over its own apps and data, not over the whole device. In SP 800-124 Rev. 2 “Guidelines for Managing the Security of Mobile Devices in the Enterprise”, published in May 2023, NIST notes that for enterprises with BYOD policies, using mobile application management (MAM) instead of mobile device management (MDM) may help address users’ privacy concerns. Restricting app functionality without affecting the entire device is, according to NIST, the approach preferred by BYOD users.

In practice this means a container: a separate, encrypted space for company email, messaging and documents that the IT department controls, while photos, personal apps and messages stay out of its reach. What MDM is, what features it has and how it is deployed is covered in the article on MDM systems; the BYOD policy only decides which scope of control the company applies to personal devices.

Laptops need a separate approach. NIST SP 800-124 Rev. 2 explicitly excludes them from its scope, because the security capabilities currently available for laptops are different from those for smartphones and tablets. For personally owned computers, a practical solution may be to limit access to resources that do not store data on the device’s disk, in line with the option of not storing sensitive data described in SP 800-46 Rev. 2.

Where does the employer’s control end and the employee’s privacy begin?

The employer’s control ends where it stops being necessary to protect company data. For remote work, the closest guidance comes from Article 67²⁸ § 2 of the Polish Labour Code: inspection activities may not violate the privacy of the employee and other persons, and under § 1 inspections are carried out in agreement with the employee, at the place of remote work and during their working hours. Monitoring of work email is governed by Article 22³: it may not violate the secrecy of correspondence or the employee’s other personal rights (§ 2), and the same rules apply accordingly to other forms of monitoring (§ 4).

The GDPR adds the principle of data minimisation: Article 5(1)(c) requires data to be limited to what is necessary for the purposes of processing. A tool that collects a list of all apps, location and browsing history from a personal phone collects more than is needed to protect a mailbox. The policy should list what device data the company sees (for example model, system version, security status) and what it does not see.

This boundary also has a security dimension. In SP 800-124 Rev. 2, NIST notes that staff turn to shadow IT when administration practices appear to invade their privacy: they send work documents to personal email accounts or store company data in unapproved cloud services. An overly invasive policy therefore does not increase control; it moves data to places where the company cannot see it at all.

What should happen when a personal device is lost or an employee leaves?

When a personal device is lost or an employee leaves, the company removes only its own data and apps from it, not the entire content. In SP 800-124 Rev. 2, NIST distinguishes a full device wipe, typical for enterprise-owned hardware, from an enterprise wipe, which deletes only the settings, data and apps pushed out for work use and is typically used on an employee’s personal device. When an employee leaves, such a wipe should be a standard item on the offboarding checklist, alongside revoking access.

The policy should specify how quickly the employee reports the loss of a device, to whom, and what happens next. Native remote wipe on iOS and Android requires the device to be powered on and connected to the network, which is why NIST warns against treating it as the sole control: an attacker could access data before the wipe or power the device off to prevent it from receiving the command. The encryption and authentication from the previous sections protect data even when the wipe does not work.

The loss of a device with personal data also needs a GDPR assessment. Under Article 33(1), the controller notifies a personal data breach to the supervisory authority without undue delay and, where feasible, not later than 72 hours after having become aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons. That is why the loss reporting procedure should reach the person who will carry out this assessment, not just the helpdesk.

Who pays for personal equipment used for remote work?

For remote work, an employee who uses agreed personal equipment is entitled to a cash allowance. Article 67²⁴ § 3 of the Polish Labour Code grants it in the amount agreed with the employer where the parties have agreed rules for using tools not provided by the employer, and § 4 allows it to be replaced with a lump sum corresponding to the employee’s expected costs. The exception is occasional remote work, performed at the employee’s request for up to 24 days in a calendar year: Article 67³³ § 2 excludes the application of Article 67²⁴ to it.

The Code also sets criteria for determining the amount. Under Article 67²⁴ § 5, account is taken in particular of the wear norms of work materials and tools, their documented market prices, as well as electricity consumption norms and the cost of telecommunications services. Article 67²⁵ states that payment of the allowance or lump sum does not constitute income under the Polish personal income tax act.

For a BYOD policy, this means that the security rules and the settlement rules should refer to the same list of approved devices. If the policy requires a personal phone to be enrolled, but the remote work agreement does not provide for the use of personal equipment, the documents contradict each other.

What should a BYOD policy contain?

A BYOD policy should contain provisions that settle every foreseeable dispute: about access, control, data and costs. The table below lists them in the order in which it is worth settling them, with the typical mistake and the owner of each provision.

Policy provisionWhat it settlesTypical mistakeOwner
Scopewho it applies to (employees, contractors) and which devicescontractors and subcontractors left outIT security
Access tierswhich systems for which device categoryone tier for phones and laptopsIT security and system owners
Excluded systemswhat a personal device cannot access at allno list, exceptions granted ad hocsystem owners
Minimum requirementsscreen lock, encryption, current OS, MFArequirements without automated checksMDM administrator
Scope of controlcontainer or full device managementfull MDM on a personal phone without justificationIT security and data protection officer
Data visible to the companywhat the company sees about the device and what it does notcollecting location and app lists “just in case”data protection officer
Loss and theftwhom to notify and when, who assesses the breachthe report reaches only the helpdeskIT security and data protection officer
Employee departureenterprise wipe as an offboarding checklist itemcompany data stays on a former employee’s deviceHR and IT
Costsallowance or lump sum for remote worksecurity policy and HR agreement inconsistentHR
Acknowledgement and reviewemployee signature, document review datepolicy unchanged for yearspolicy owner

How do you roll out a BYOD policy so that employees actually use it?

A BYOD policy is rolled out so that enrolling a device is easier than getting around it. It starts with announcing the rules and collecting acknowledgements — for remote work, Article 67²⁶ § 2 of the Polish Labour Code requires the employee to confirm in paper or electronic form that they have read the personal data protection procedures and to comply with them.

Then comes device enrolment. Before installation, the employee should know what the IT department will see on their phone and what it will not. Privacy questions that nobody answered come back later as personal email accounts holding work documents.

The policy also needs reviewing, because phone operating systems, company apps and regulations change — the announcement of the consolidated text of the Labour Code dates from 1 September 2026.

Key takeaways:

  • Before enrolment, the employee must know what the company will see on their device and what it will not.
  • For remote work, acknowledging the data protection procedures follows from Article 67²⁶ § 2 of the Polish Labour Code.
  • A policy that is not reviewed after changes to company systems soon stops describing reality.

How can nFlo help you prepare a BYOD policy?

nFlo prepares BYOD policies as part of the security policy development service: rules for personal and mobile devices are part of the set of policies we write for a specific organisation, not from a template. We help set access tiers, minimum requirements and the scope of control so that the provisions can be checked technically.

On the technical side, we implement IBM MaaS360 — from policy configuration and device enrolment to integration with the identity system. The MaaS360 corporate container separates work data from personal data and allows only the container to be wiped, which matches the container model from the section on MDM. Labour law matters, such as the amount of the allowance, remain with the company’s HR department and lawyer.

If you want to put the rules for personal devices in your company in order, let’s talk.

What else is worth knowing about BYOD policy?

Can an employer wipe an employee’s personal phone?

A BYOD policy should provide for wiping only company data and apps, not the whole device. NIST SP 800-124 Rev. 2 describes this mode as an enterprise wipe, typically used to delete work data from an employee’s personal device.

Does BYOD require paying an allowance for personal equipment?

For remote work agreed with the employer in Poland, yes. Under Article 67²⁴ § 3 of the Polish Labour Code, an employee who uses agreed tools not provided by the employer is entitled to a cash allowance in the amount agreed with the employer; § 4 allows it to be replaced with a lump sum. Article 67²⁴ does not apply to occasional remote work (up to 24 days a year) under Article 67³³ § 2.

Does a BYOD policy require MDM?

Not always. NIST SP 800-124 Rev. 2 indicates that for BYOD, managing apps (MAM) instead of managing the whole device may help address employees’ privacy concerns. For high-risk data, NIST recommends devices issued by the organisation rather than full management of a personal phone.

Which GDPR provisions apply to a BYOD policy?

Mainly Article 5(1)(f) (integrity and confidentiality of data), Article 24(2) (data protection policies implemented by the controller where proportionate) and Article 32 (security measures appropriate to the risk). The loss of a device with personal data may also need to be assessed for notification under Article 33.

Can a BYOD policy cover laptops?

Yes, but it requires different measures than phones. NIST SP 800-124 Rev. 2 excludes laptops from its scope, and NIST SP 800-46 Rev. 2 provides for personally owned computers to have limited access to company resources.

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Łukasz Gil

Łukasz Gil

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations