workplace

Employee monitoring in Switzerland: what SMEs should know

AA
Aurum Avis Labs Author
7 min read

Employee monitoring in Switzerland

Employee monitoring in Switzerland is allowed when it serves a clear purpose and is not mainly there to control behaviour. Art. 26 of the Labour Ordinance (ArGV 3) forbids surveillance systems intended to monitor how staff behave. The FDPIC (EDÖB) expects prior information, proportionality, and a job-related purpose for employee personal data (Art. 328b of the Code of Obligations, guidance on technical monitoring at work). CCTV in the office is a separate topic (CCTV at work in Switzerland). This text is for owners and HR in companies of roughly 20 to 250 people who wonder whether keystroke loggers, screen capture, or «productivity scores» are acceptable.

After a hiring round, retention of application data is covered in how long to keep job applications.

  • ArGV 3Behaviour control

    Surveillance systems meant to monitor conduct are forbidden; security and quality can justify narrow tools if proportionate.

  • FADPOrganisation

    Art. 8 FADP requires appropriate technical and organisational measures. Training is one of them, not a substitute for clear rules on logs.

  • Inform firstTransparency

    Staff should know what is logged before it starts.

  • Not this pageCCTV

    Cameras in workspaces follow overlapping but distinct rules.

Is monitoring mandatory?

No. The FADP does not prescribe a specific monitoring product. It requires appropriate measures for data security. Logs on company devices may be part of that; always-on screen video for performance league tables usually is not. Insurers and customers sometimes ask for «awareness» or «access control». That is not the same as an «employee monitoring» module with hourly screenshots.

What counts as problematic monitoring

Continuous screen recording, keystroke logging on every app, or ranking individuals by mouse activity often look like behaviour control rather than IT security. Tools marketed as «employee productivity» deserve a hard look: which fields are collected, who sees named reports, and whether less intrusive options exist (project time tracking with consent, access logs for security incidents only).

WhatsApp chats used for business are a data protection issue too (WhatsApp for business and data protection), not a monitoring substitute.

Observation of employees: when it is permitted

Observing employees is only narrowly permitted in Switzerland. Art. 26 ArGV 3 forbids surveillance and control systems intended to monitor how staff behave. The FDPIC guidance on technical monitoring at work expects prior information, proportionality and a job-related purpose, together with Art. 328b of the Code of Obligations. Secret continuous observation, keystroke logging on every app, or ranking people by mouse activity typically looks like unlawful behaviour control. Security logs on company devices (malware, unusual logins, DLP) can be acceptable when they are set out in an acceptable-use policy and are not used for performance scoring. Borderline cases such as theft or forensics after an incident need counsel and often a narrow duration. A starting point for management and HR is the security and data-protection overview; after hiring, how long to keep job applications covers applicant files.

What employers still may do

Security monitoring on company devices (malware detection, login anomalies, DLP rules on confidential files) is common if staff are informed in an acceptable-use policy and measures are proportionate. Phishing simulations are a different debate: announce them and do not use click scores in individual performance reviews, as set out in clicked a phishing link at work.

Usually discuss with staff first

  • MDM on company phones
  • Mail and file access logs for security
  • Time recording agreed in contract

Usually avoid without advice

  • Hidden cameras at desks
  • Always-on screen video to managers
  • Secret reading of private messaging on BYOD

BYOD and private phones

When staff use private devices, the job-related purpose test is stricter. Company mail on a private phone may justify security updates and a clear separation, not reading private chats. State what applies on company equipment and what you do not monitor on personal devices. Without a written rule, BYOD becomes a dispute quickly.

Who can defer a formal policy

A five-person office with no remote monitoring and no plans to buy surveillance software can note «no behaviour monitoring» in the staff handbook and revisit when they grow.

A 120-person firm rolling out global «productivity analytics» needs a written assessment, staff involvement where Swiss law requires it, and privacy documentation before rollout. Switzerland does not have a German-style works council in most SMEs; still talk to HR and to the people who will open the dashboards.

What to document before you switch a tool on

Write down the purpose (security incident, loss prevention, or performance), the data fields collected, retention period, and which roles may open named dashboards. If the vendor stores data outside Switzerland, note that in your processing records under Art. 12 FADP. Staff should receive the summary in plain language before logging starts, not only in a 40-page IT policy.

  • Inventory existing tools (MDM, VPN, time tracking, collaboration)
  • Note the purpose per tool: security or performance
  • Information sheet for staff before the first log
  • Align retention and deletion with IT
  • If you only need malware alerts

    Endpoint protection with aggregate alerts to IT is a different conversation from screen video. Buy the smallest feature set that meets the security goal.

  • If a manager asks for «who was on Facebook»

    That is usually behaviour control. Redirect to agreed output targets or project milestones instead of browsing history.

  • If someone is suspected of data theft

    Narrow forensic access for a defined case, with legal advice, beats turning on permanent surveillance for everyone.

A made-up example: a productivity module after the pitch

A made-up example: a services firm with 45 staff and outsourced IT. A line manager wants «productivity insights» after a vendor pitch because home office «feels too loose». HR lists existing logs with IT: VPN, Microsoft 365 sign-ins, contract time tracking already in place. The new module would store screenshots every ten minutes and «activity scores» per person.

Management stops the purchase. Instead: update the acceptable-use policy (what applies on company laptops), tighten project time tracking, and plan a data protection session that explains why browsing history is not the fix. Endpoint protection stays, without screen video.

Employee access requests

Under the FADP, staff may ask what personal data you hold about them, including logs if they exist. If you cannot explain what a monitoring product stores, you are not ready to deploy it. Keep exports from HR and IT tools separate so a subject access request does not accidentally disclose another employee’s records.

Does home office change the rules?

Company laptops on a home network may still run security software you disclosed. Cameras or always-on recording in a private room without a clear rule is higher risk. State what applies on company equipment and what you do not monitor on personal devices.

Is keylogging allowed for IT support?

Support with the person’s consent and a clear end date is different from permanent logging of all staff. Without consent and a narrow purpose, it is risky. Ask counsel if unsure.

How is this different from CCTV at work?

Cameras raise notice duties, fields of view, and often different assessments than software logs. Both need proportionality, but the questions are not identical.

First steps for management

List existing tools: time tracking, VPN logs, MDM, collaboration. Mark whether each tool serves security or performance control. Remove duplicates before you buy a new «productivity» module. Ask IT for a configuration export, not only the marketing brochure.

Data protection training

A live data protection session covers what staff may use for customer contact, what the company may log on devices, and where monitoring crosses the line, in one to two hours. Details are on data protection awareness training.

Surveillance meant to control behaviour is tightly limited at work in Switzerland. Inform people beforehand, stay with a job-related purpose, and do not score individuals for performance reviews. This is orientation under ArGV 3, OR 328b and the FADP, not a legal opinion.

workplace monitoring fadp labour law switzerland
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.