Employee monitoring law · Germany
The works council holds a veto, and a productivity dashboard is enough to trigger it.
Negotiate a works agreement with the Betriebsrat before deployment. Without one there is no lawful rollout.
- Region
- Europe
- Instruments
- 3 governing
- Employer duties
- 4 listed
- Last reviewed
- August 22, 2026
Germany · what the law requires
Prior approval required
Germany is the jurisdiction most often underestimated. Section 87(1) no. 6 BetrVG gives the works council co-determination over any technical system that is merely capable of monitoring behaviour or performance. Capability, not intent, is the test, so a manager dashboard or a productivity score is squarely inside it. Where a works council exists and has not agreed, deployment is unlawful. Consent is a weak basis in an employment relationship because it is rarely considered freely given; § 26 BDSG is the usual route instead.
- A works agreement before switch-onNegotiate a Betriebsvereinbarung covering what is captured, who sees it, how long it is kept and what it may be used for. Deploying first and negotiating after is the common and expensive mistake.
- Necessity, not convenience§ 26 BDSG asks whether the processing is necessary for the employment relationship. "It would be useful for management" does not meet that bar.
- No permanent surveillance pressureContinuous, gapless monitoring is treated as an infringement of personality rights even where a works agreement exists. Sampling and interval capture survive scrutiny that constant capture does not.
- A DPIA on fileSystematic monitoring of employees is high-risk processing. The assessment has to exist before deployment, not be written up after a complaint.
- Proof Ledger
- Outcomes
- Certificates
- Audit log
- Data access
- Disputes
- Data egress
- Export
- What We See
- Controls
- AKAria K. viewed screenshotsLena M. · 3 capturesScreen capturemacOS · London09:42a91f…4c023d7b…91ee
- JMJon M. exported time reportDesign team · CSVmacOS · Berlin09:313d7b…91ee77c5…0ba4
- SDSara D. opened capture reviewRavi P. · one flagged frameWindows · Manchester09:1877c5…0ba4e208…5f13
- wm_live_7f2… read /v1/deliverablesScoped key · read onlyPublic API · allowlisted IP08:57e208…5f13b64a…2d90
- LMLena M. viewed her own recordWhat We SeemacOS · London08:44b64a…2d901cf9…8e77
- AKAria K. changed capture policyBlur set to alwaysmacOS · London08:261cf9…8e7705d2…ae31
The instruments, and which control answers each duty
- GDPR: Regulation (EU) 2016/679. Sets the floor everywhere in the EEA: a lawful basis, purpose limitation, data minimisation, transparency and a DPIA where monitoring is high risk. National law below adds to this, never subtracts.
- Works Constitution Act: BetrVG § 87(1) no. 6. Co-determination over technical systems capable of monitoring behaviour or performance. This is a veto, not a consultation, no works agreement, no deployment.
- Federal Data Protection Act: BDSG § 26. Processing necessary for the employment relationship needs no individual consent; anything beyond necessity falls to § 26(2), where consent must be voluntary, informed and in writing.
No product does this part
What you must still do yourself
Compliance is a property of your deployment. These are the steps in Germany that no vendor can complete on your behalf, and skipping them is what turns a rollout into a finding.
- 1Negotiate the Betriebsvereinbarung. No vendor can do this for you, and no product setting substitutes for it.
- 2Run and document the DPIA before deployment.
- 3Decide and write down what the data may be used for, particularly whether it may inform performance management.
- 4Appoint or brief your Datenschutzbeauftragter on the specific configuration you intend to run.
- If you get it wrongGDPR fines up to €20m or 4% of global turnover. Separately, works-council breaches can lead to an injunction stopping the system entirely, and evidence gathered through unlawful monitoring is frequently excluded in labour-court proceedings.
Verify the claim
Every control above, on the page that describes it
- Per-app privacy deny-lists applied on the device before transmissionScope what is captured, so a works agreement has something concrete to describe
- Interval screenshot capture with randomised cadence rather than a constant streamShow that capture is not continuous
- Roles scoped to a node in the org treeLimit who can see performance data, as the agreement will specify
- Configurable retention and deletion per policyEvidence the retention the agreement fixes
- Explainability view behind every productivity numberExplain a score to a works council or a labour court
Sources and review date
Last reviewed August 22, 2026This is a summary of how employee-monitoring rules generally work in this jurisdiction, written to help you scope a rollout and brief your own advisers. It is not legal advice, it is not a substitute for it, and law changes. Verify against the primary sources listed and take local counsel before you deploy.
Nearby jurisdictions
Monitoring law elsewhere in Europe
- AustriaA works council veto with no workaround, and no council means individual consent.
- ItalyUnion agreement or a labour inspectorate authorisation, a filing, not a policy.
- NetherlandsWorks council consent, and the regulator treats screenshots as disproportionate by default.
- PortugalThe Labour Code prohibits remote means used to monitor employee performance.
- SwitzerlandSystems for monitoring worker behaviour are prohibited by the labour ordinance.
- FranceConsult the CSE first. Skipping it is the criminal offence of obstruction.
Point it at one team for a week.
Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.
Free for two seats. No card, and no sales call to sit through.