Why Your Employees Don't Actually Want Privacy (They want something else—and you're probably giving them neither).

Hey there,

I need to tell you about something that completely upended my assumptions about workplace privacy.

It happened during my doctoral research. I was sitting across from a remote worker—let's call her Sarah—interviewing her about her company's new surveillance software. I expected outrage. Maybe some "Big Brother" comparisons.

Instead, she said something I didn't expect: "I don't mind being monitored. I just hate how they're doing it."

Wait, what?

Sarah was furious about keystroke logging. Livid, actually. But when I asked about her manager reviewing her weekly deliverables? No problem. Time tracking software logging her hours? Totally fine. Security cameras in the office she visited monthly? Didn't bother her at all.

I kept hearing versions of this across dozens of interviews. The same information is being collected. Wildly different reactions.

And I realized something: We've been thinking about workplace privacy completely wrong.

Most executives treat privacy like a light switch. It's either on—employees have privacy, no monitoring—or it's off—full surveillance, no privacy.

But that's not how privacy actually works.

Think about your own life for a second. You share your medical history with your doctor, right? But you'd never tell your manager about that rash you're worried about. You tell your spouse your salary. You don't tell your neighbor. You let TSA search your bag at the airport without blinking. But if they tried that at Starbucks, you'd call the cops.

Same information. Different contexts. Completely different expectations.

Your employees are doing the same calculation every single day. And when you violate those invisible contextual boundaries—even if you're technically following the law—you destroy trust faster than any productivity software can rebuild it.

Here's what I learned from hundreds of interviews: employees have incredibly clear expectations about who should know what about them at work. These expectations aren't random. They're based on context.

Your manager knowing about project deadlines and deliverables? That makes sense. It's literally their job. HR knowing about performance reviews? Of course—that's why HR exists. IT monitoring network security logs? Sure, that's protecting everyone.

But here's where companies go off the rails.

Random managers reading Slack DMs between coworkers? Violation. Software capturing every keystroke, including personal passwords typed during lunch? Violation. Taking screenshots of employees' faces every three minutes while they're working from home? Massive violation.

The difference isn't about the type of data. It's about whether that information flow makes sense in the context of the workplace relationship.

Here's what I learned from hundreds of interviews: employees have incredibly clear expectations about who should know what about them at work. These expectations aren't random. They're based on context.

Your manager knowing about project deadlines and deliverables? That makes sense. It's literally their job. HR knowing about performance reviews? Of course—that's why HR exists. IT monitoring network security logs? Sure, that's protecting everyone.

But here's where companies go off the rails.

Random managers reading Slack DMs between coworkers? Violation. Software capturing every keystroke, including personal passwords typed during lunch? Violation. Taking screenshots of employees' faces every three minutes while they're working from home? Massive violation.

The difference isn't about the type of data. It's about whether that information flow makes sense in the context of the workplace relationship.

I spent two years studying remote workers and their responses to different types of workplace monitoring. The patterns were striking.

When companies implemented monitoring that violated contextual integrity—things like keystroke logging that captured personal information, or random screenshot software, or invasive productivity scores—the damage was immediate and measurable. Trust in management dropped by 37 percent. Turnover intentions more than doubled. Job satisfaction tanked. And here's the kicker: productivity actually decreased. The very thing the monitoring was supposed to improve got worse.

But companies that aligned their monitoring with contextual norms saw something completely different. Higher productivity. Better engagement. Stronger retention. Employees actually worked harder and stayed longer when they felt the monitoring respected appropriate boundaries.

Let me be clear about what this means: Privacy and productivity aren't opposites. When you respect context, you get both.

Here's how you can evaluate any monitoring practice—whether you're implementing it or already using it.

Ask yourself three questions. Be honest.

First: Would employees expect this person or system to have access to this information in a traditional office environment? If you're tracking something that wouldn't be visible or accessible in person, you're probably crossing a line.

Second: Is this monitoring directly related to evaluating work output or protecting legitimate business interests? If you can't articulate a clear business justification that employees would recognize as valid, that's a red flag.

Third: Could you achieve the same business goal with less invasive monitoring? If there's a less intrusive alternative that would work just as well, you should be using it.

If you answered no to any of these questions, you're probably violating contextual integrity. And your employees can feel it, even if they can't articulate exactly why.

I watched two companies implement monitoring for the same stated goal: ensuring remote worker productivity.

Company A went with keystroke logging. They wanted comprehensive data on employee activity. What they got instead was a retention crisis within six months. Why? Because keystroke logging captures everything. Personal passwords typed during breaks. Private messages to family members. Medical information in personal emails. Financial data from online banking.

Employees perceived this—correctly—as invasive and inappropriate. The message they received was clear: "We don't trust you." The pilot program was abandoned, but not before several high performers left.

Company B took a different approach. They implemented activity-level tracking that showed application usage, active versus idle time, and meeting attendance. This mirrored what a manager would observe in an office environment. It evaluated work patterns without capturing personal content.

Employees saw this as reasonable and transparent. One person told me, "It actually helps me understand my own productivity better." The company adopted the system permanently. Productivity increased by twelve percent.

Same goal. Different approaches to context. Opposite outcomes.

Look, 2025 has become the year that privacy violations got expensive.

Eighteen states have comprehensive privacy laws now. The California Privacy Protection Agency just issued a one-point-three-five million dollar penalty for privacy violations. They're coordinating enforcement across state lines. California alone has received over eight thousand employee privacy complaints.

But here's what keeps me up at night, and what most compliance teams are missing: legal compliance and contextual integrity aren't the same thing.

You can be one hundred percent legally compliant and still violate your employees' contextual expectations. And when you do that, you destroy trust, tank productivity, and accelerate turnover. The law sets a floor. Employee expectations set a ceiling. And right now, most companies are bumping their heads on that ceiling without realizing it.

Over the next several weeks, I'm going to break down the frameworks that actually work for balancing accountability with privacy in remote work environments.

Next week, I'm tackling the transparency trap. You know that advice about "just be transparent about your monitoring and employees will be fine"? Turns out seventy-three percent of companies believe that. The data says they're wrong. Transparency without context makes things worse, not better.

After that, we'll dig into power asymmetries—how monitoring amplifies existing inequalities in ways most executives don't see. Then the compliance maze, because navigating eighteen different state privacy laws is genuinely nightmare fuel. And finally, how to design monitoring that employees actually trust.

Each edition will take you about six to eight minutes to read. And every single one will give you something you can use immediately.

I want to hear from you. What monitoring practices feel appropriate in your workplace? Which ones make you uncomfortable? Hit reply and tell me. I read every response, and your insights shape what I write about next.

Seriously—some of my best newsletter ideas have come from reader questions. If you're wrestling with something specific, there's a good chance hundreds of other people are too.

If this resonated with you, I need three quick favors.

First, if you're reading this because someone forwarded it to you, subscribe so you don't miss the next one. The transparency trap edition next week is going to challenge some deeply held assumptions.

Second, follow me on LinkedIn. I share daily insights on workplace privacy that don't make it into the newsletter—quick takes, breaking enforcement news, practical tips.

Third, forward this to someone who needs it. HR leader dealing with monitoring software? Compliance officer trying to navigate state privacy laws? Executive, wondering why retention is slipping? Send it their way.

And if you've got a burning question about workplace privacy, reply to this email. I might feature it in a future edition. Anonymous, of course.

#FutureOfWork #HRTech #EmploymentLaw #EUAIAct #WorkplaceCompliance #ContextualIntegrity

Remote Work Privacy Insights examines workplace monitoring, employee privacy, and remote work practices through the lens of contextual integrity theory. I translate complex privacy frameworks into practical guidance for executives and HR leaders. This newsletter is educational and does not constitute legal advice.

What makes this newsletter different: most privacy content focuses exclusively on legal compliance. I focus on what actually works—combining academic research, real enforcement actions, and practical implementation frameworks. Because checking the compliance box doesn't mean much if you're hemorrhaging talent in the process.

My credentials: FIP, CIPM, CIPP/US, AIGP, LL.M., D.B.A., with AI Ethics and Governance studies at Oxford University. But honestly, the most valuable part of my research has been the hundreds of conversations with employees and managers working through these challenges in real time. This newsletter is educational and does not constitute legal advice.

© 2025 Edward Halle. All rights reserved.