Help · Questions

Can an employer require an app on a personal phone?

What employers usually can and cannot ask, why staff object, and how to record attendance without needing to settle the argument.

You do not have to settle this argument to record attendance. Put a screen by the door showing a code that changes every thirty seconds, and people scan it with the camera already on their phone. Nothing is installed, so there is nothing to require, and the question stops being your problem.

Employers generally can set reasonable conditions for work, and in many places that extends to software on a device somebody uses for the job. Whether it is reasonable where you are depends on your contracts and any works council or union agreement — which is exactly the conversation you can skip.

Why it becomes an argument

Three objections come up, and only the first is about privacy.

“It can see where I am.” An attendance app that clocks people in automatically needs background location, which means it can read position when nobody is using it. Staff are right that this is a different thing from opening a page at the door, and telling them otherwise damages your credibility rather than their objection.

“It is my phone, and my data plan.” Somebody on a low-cost plan with a full phone is being asked to give up storage and traffic for their employer’s record keeping. It is a small ask that lands very differently depending on what somebody earns.

“What else is on it?” Most people cannot tell an attendance app from a device management profile, and once one company app is installed, the next request is easier to make. That worry is not paranoid; it is pattern recognition.

Where it usually goes wrong

Not at the objection — at the enforcement. An organization that mandates an install ends up with a group of people who genuinely cannot or will not, and then needs a manual process for them anyway. You now run two systems, and the exception list is the one nobody maintains.

If you are going to need a fallback, it is worth asking whether the fallback should just be the system.

The version of this that avoids the argument

Put a screen at the door showing a code that changes every thirty seconds. People scan it with the camera they already have, a page opens in the browser, they press one button. There is nothing to install, so there is nothing to require, and the objection does not arise.

What we record is the check-in itself: name, time, place, and the result of the checks that location has switched on. Nothing runs in the background, because there is nothing running.

This is not legal advice. If a works council agreement or a national rule applies to you, it applies whichever product you choose — but a product with nothing to install is a much shorter conversation.

Still stuck? Try the demo — most questions here are quicker to answer by pressing the thing than by reading about it.