WEBVTT - Workplace Surveillance

0:00:00.240 --> 0:00:04.680
<v Speaker 1>From UFOs to psychic powers and government conspiracies. History is

0:00:04.760 --> 0:00:09.080
<v Speaker 1>riddled with unexplained events. You can turn back now or

0:00:09.200 --> 0:00:12.079
<v Speaker 1>learn the stuff they don't want you to know. A

0:00:12.200 --> 0:00:25.760
<v Speaker 1>production of I Heart Radio. Hello, welcome back to the show.

0:00:25.840 --> 0:00:28.880
<v Speaker 1>My name is Matt. Our colleague Nol is on an adventure,

0:00:28.920 --> 0:00:32.320
<v Speaker 1>but will return shortly. They call me Ben. We're joined

0:00:32.320 --> 0:00:35.800
<v Speaker 1>as always with our super producer Paul Mission controled decades.

0:00:36.000 --> 0:00:39.159
<v Speaker 1>Most importantly, you are you, You are here, and that

0:00:39.240 --> 0:00:42.519
<v Speaker 1>makes this the stuff they don't want you to know.

0:00:43.159 --> 0:00:47.360
<v Speaker 1>It's a new year. Hope everybody was able to get

0:00:47.640 --> 0:00:51.280
<v Speaker 1>some kind of vacations, some kind of holiday slash family time,

0:00:52.000 --> 0:00:56.120
<v Speaker 1>and a lot of us listening now are officially returned

0:00:56.480 --> 0:01:01.880
<v Speaker 1>to work. A holiday season has uh sadly concluded, and

0:01:01.960 --> 0:01:05.760
<v Speaker 1>so as we speak, there are billions of people across

0:01:05.800 --> 0:01:08.360
<v Speaker 1>the planet who are firing up the old laptop, or

0:01:08.400 --> 0:01:11.680
<v Speaker 1>they're you know, putting on the uniform. They're they're starting

0:01:11.720 --> 0:01:17.160
<v Speaker 1>the company van, and they're off on another another episode

0:01:17.360 --> 0:01:23.080
<v Speaker 1>of trying to stay alive in may fortune what they

0:01:23.120 --> 0:01:27.119
<v Speaker 1>say in the Hunger Games and fortunate favorite the Bold,

0:01:27.120 --> 0:01:30.720
<v Speaker 1>Maybe odds be ever in your favor. Matt, you remember

0:01:30.760 --> 0:01:34.560
<v Speaker 1>that song. I always feel like someone's watching me. Somebody

0:01:34.640 --> 0:01:39.440
<v Speaker 1>was watching me. Oh yeah, I've been thinking about that

0:01:39.520 --> 0:01:43.679
<v Speaker 1>a lot as we were researching today's episode. This is

0:01:43.840 --> 0:01:48.360
<v Speaker 1>Orwellian and you know what, fellow conspiracy realist, after thinking

0:01:48.400 --> 0:01:50.760
<v Speaker 1>about it and after digging into this, I can't speak

0:01:50.800 --> 0:01:53.920
<v Speaker 1>for Matt or Mission control, but I do hope you're

0:01:53.960 --> 0:01:56.960
<v Speaker 1>listening to this episode at work, yes, just hopefully not

0:01:57.200 --> 0:02:02.640
<v Speaker 1>on your company issued device. Don't don't do that, right right? Uh?

0:02:02.680 --> 0:02:05.480
<v Speaker 1>If you? The reason this is a cool thing to

0:02:05.520 --> 0:02:09.000
<v Speaker 1>listen to while you're at work is because it gives

0:02:09.040 --> 0:02:12.480
<v Speaker 1>it a little extra punch, a little extra immediacy, right,

0:02:12.680 --> 0:02:15.360
<v Speaker 1>you know, Uh, Matt. People have heard this joke on

0:02:15.360 --> 0:02:18.680
<v Speaker 1>the show before about how stuff they don't want you

0:02:18.720 --> 0:02:21.800
<v Speaker 1>to know has ruined our search histories, and that is

0:02:22.400 --> 0:02:26.359
<v Speaker 1>that is true. But the hazard of an oddball search

0:02:26.440 --> 0:02:29.920
<v Speaker 1>history pales in comparison to what many other people have

0:02:30.000 --> 0:02:33.519
<v Speaker 1>experienced in the workplace. Especially over the past couple of years,

0:02:33.960 --> 0:02:37.920
<v Speaker 1>life turned upside down across the planet. Millions and millions

0:02:37.919 --> 0:02:42.600
<v Speaker 1>of people found themselves let's see, battling disease, financial woes,

0:02:42.800 --> 0:02:47.160
<v Speaker 1>mental health, social unrest, all the while still trying to

0:02:47.240 --> 0:02:50.120
<v Speaker 1>hold down a solid job for a lot of people.

0:02:50.160 --> 0:02:53.720
<v Speaker 1>The world will never be the same. And this this

0:02:53.760 --> 0:02:58.919
<v Speaker 1>goes for employers as well as employee ease. Our episode

0:02:58.919 --> 0:03:03.480
<v Speaker 1>today is about work, it's about watching, It's about ultimately

0:03:03.680 --> 0:03:09.200
<v Speaker 1>who watches the Watchman. So yeah, yeah, and this I

0:03:09.680 --> 0:03:12.000
<v Speaker 1>don't know about you, man, but this, this one spooked

0:03:12.000 --> 0:03:15.400
<v Speaker 1>me out a little too. Oh, definitely, especially because of

0:03:15.440 --> 0:03:18.200
<v Speaker 1>the way work has changed for many of us, especially

0:03:18.200 --> 0:03:22.600
<v Speaker 1>the people right now making this show. Uh, we work

0:03:22.639 --> 0:03:25.839
<v Speaker 1>from home now and for to a large extent, and

0:03:25.880 --> 0:03:29.560
<v Speaker 1>we probably will for oh, I don't know the foreseeable future,

0:03:30.360 --> 0:03:34.519
<v Speaker 1>because because of the safety benefits of being all isolated

0:03:34.600 --> 0:03:37.840
<v Speaker 1>in separate places. And we're we're gonna get into it.

0:03:37.840 --> 0:03:40.280
<v Speaker 1>So let's just talk about statistics while we're sitting here

0:03:40.320 --> 0:03:44.160
<v Speaker 1>and discussing this stuff, right, Yeah, here are the facts.

0:03:44.640 --> 0:03:46.640
<v Speaker 1>If you go to the U. S. Bureau of Labor

0:03:46.640 --> 0:03:52.560
<v Speaker 1>and Statistics, you'll see that across about one in four

0:03:52.880 --> 0:03:57.960
<v Speaker 1>employed people teleworked or worked from home for pay in

0:03:58.120 --> 0:04:00.960
<v Speaker 1>some capacity. That doesn't mean they were all locked up

0:04:01.640 --> 0:04:04.560
<v Speaker 1>hermiting away. That means there were a lot of people

0:04:04.560 --> 0:04:06.560
<v Speaker 1>who were like, I'll go in one day a week,

0:04:06.880 --> 0:04:10.320
<v Speaker 1>or I will be gone for you know, my office

0:04:10.400 --> 0:04:13.200
<v Speaker 1>is closed for a month and we're working remotely. So

0:04:13.360 --> 0:04:16.680
<v Speaker 1>all at all, more than a third of all the

0:04:16.760 --> 0:04:21.640
<v Speaker 1>households in the US reported working from home more frequently

0:04:21.760 --> 0:04:25.560
<v Speaker 1>than they had before COVID hit. But we also found

0:04:26.040 --> 0:04:31.960
<v Speaker 1>some socio economic sociodemographic divides. If you are a younger worker,

0:04:32.320 --> 0:04:36.120
<v Speaker 1>you're less likely to have teleworked due to the pandemic.

0:04:36.240 --> 0:04:39.480
<v Speaker 1>And that's where you know, we learned things like essential workers.

0:04:39.520 --> 0:04:42.440
<v Speaker 1>A lot of younger people who were maybe just getting

0:04:42.480 --> 0:04:46.040
<v Speaker 1>their first job out of high school, during high school

0:04:46.120 --> 0:04:50.839
<v Speaker 1>something like that, they started off in places like retail

0:04:51.080 --> 0:04:56.039
<v Speaker 1>operations or the service industry, and they had to go

0:04:56.080 --> 0:04:59.240
<v Speaker 1>into work in person because of the nature of their profession. Yeah,

0:04:59.240 --> 0:05:02.680
<v Speaker 1>and that's something that also comes into play with these statistics.

0:05:03.120 --> 0:05:07.160
<v Speaker 1>The Census Bureau found that that economic divide that we're

0:05:07.200 --> 0:05:11.719
<v Speaker 1>all seeing accelerate came into play here as well. People

0:05:11.760 --> 0:05:15.600
<v Speaker 1>who made more money tended to more easily telework than

0:05:15.640 --> 0:05:17.880
<v Speaker 1>those who made less money. So if you look at

0:05:17.880 --> 0:05:20.640
<v Speaker 1>the Census Bureau, they found that in the highest earning

0:05:20.680 --> 0:05:24.680
<v Speaker 1>households with incomes of two hundred thousand dollars or more,

0:05:24.760 --> 0:05:30.120
<v Speaker 1>that's combined household seventy three point one. Seventy three point one,

0:05:30.160 --> 0:05:33.000
<v Speaker 1>we're able to switch to telework. Again, like we're able

0:05:33.040 --> 0:05:36.480
<v Speaker 1>to switch to telework. And in contrast to that, only

0:05:36.600 --> 0:05:40.040
<v Speaker 1>twelve point seven percent of households earning under twenty five

0:05:40.080 --> 0:05:44.000
<v Speaker 1>thousand dollars a year where we're able to telework at

0:05:44.040 --> 0:05:46.440
<v Speaker 1>all because they again, like you said, then they had

0:05:46.480 --> 0:05:49.520
<v Speaker 1>to go into work for one reason or another. Yeah, exactly. No.

0:05:50.160 --> 0:05:53.000
<v Speaker 1>Let's do a thought experiment, folks. Imagine that you are

0:05:53.040 --> 0:05:57.400
<v Speaker 1>a manager. Imagine you're a CEO or what have you.

0:05:57.400 --> 0:05:59.680
<v Speaker 1>You have a team of people, and you have a

0:05:59.720 --> 0:06:02.760
<v Speaker 1>group of task If you have your own boss to

0:06:02.800 --> 0:06:05.000
<v Speaker 1>report to, you need to be able to tell that

0:06:05.080 --> 0:06:07.839
<v Speaker 1>person that you've knocked out these tasks or you've made

0:06:07.839 --> 0:06:09.920
<v Speaker 1>progress on them. And of course, if you are a

0:06:09.960 --> 0:06:13.320
<v Speaker 1>good manager, your goal is to make sure your employees

0:06:13.480 --> 0:06:16.600
<v Speaker 1>grow professionally. You want to set them up for success.

0:06:16.640 --> 0:06:20.400
<v Speaker 1>But now your whole team, your whole posse, has turned

0:06:20.480 --> 0:06:26.000
<v Speaker 1>their homes into isolated work cubicles. You can't walk by

0:06:26.160 --> 0:06:28.920
<v Speaker 1>like that office space guy with a cup of coffee anymore.

0:06:29.320 --> 0:06:32.400
<v Speaker 1>You have to find some other way to keep track

0:06:32.520 --> 0:06:35.880
<v Speaker 1>of what they're doing. Could you do a weekly zoom meeting. Sure,

0:06:36.240 --> 0:06:40.760
<v Speaker 1>why not? But is that enough? That's when managers and

0:06:40.800 --> 0:06:45.479
<v Speaker 1>employers started asking themselves what else can we do? And

0:06:45.600 --> 0:06:50.680
<v Speaker 1>this leads us to the new age of work surveillance.

0:06:51.160 --> 0:06:53.920
<v Speaker 1>And you know, I just think about this too. Um folks,

0:06:53.920 --> 0:06:57.919
<v Speaker 1>If you remember the last time you got a new job,

0:06:58.320 --> 0:07:01.680
<v Speaker 1>you probably had a bunch of paperwork. I know that.

0:07:01.960 --> 0:07:06.599
<v Speaker 1>You know, when our overlords have changed over the years,

0:07:06.880 --> 0:07:10.240
<v Speaker 1>we have to go through the rigamarole of reading all

0:07:10.240 --> 0:07:14.160
<v Speaker 1>the paperwork again. You know, codes of ethics, financial info,

0:07:14.320 --> 0:07:17.600
<v Speaker 1>insurance stuff, all the all the really juicy reads. But

0:07:17.840 --> 0:07:20.720
<v Speaker 1>in this mountain of paperwork, there's some interesting things. You

0:07:20.760 --> 0:07:24.680
<v Speaker 1>will often find tucked away somewhere in there a statement

0:07:24.800 --> 0:07:28.080
<v Speaker 1>saying something like, any activity you do on company time

0:07:28.120 --> 0:07:31.680
<v Speaker 1>with company equipment needs to be work related. Uh, and

0:07:32.160 --> 0:07:36.840
<v Speaker 1>you don't have maybe intellectual property rights, which sounds abstract,

0:07:36.840 --> 0:07:40.040
<v Speaker 1>but it's really important. This applies to the idea of

0:07:40.160 --> 0:07:45.440
<v Speaker 1>patents and inventions. Like let's say mission control. While we're recording,

0:07:45.520 --> 0:07:49.440
<v Speaker 1>he's secretly using his work machine to invent a new

0:07:49.520 --> 0:07:54.440
<v Speaker 1>kind of case. Ada. That's what. Yeah, then our bosses,

0:07:54.760 --> 0:07:56.600
<v Speaker 1>let's say this case to do blows up. It's like

0:07:56.920 --> 0:08:01.760
<v Speaker 1>transformed the world's understanding of sandwiches. But our bosses, say,

0:08:02.800 --> 0:08:06.600
<v Speaker 1>came up with this while you were at work using

0:08:06.600 --> 0:08:11.280
<v Speaker 1>our equipment, So this case idea belongs to us, pal.

0:08:12.080 --> 0:08:14.360
<v Speaker 1>The problem is how do you improve that it occurred

0:08:14.400 --> 0:08:20.080
<v Speaker 1>on that computer? And when yes, yes, and that's I mean,

0:08:20.080 --> 0:08:24.600
<v Speaker 1>obviously that's an extreme example. It's not unprecedented. Most people,

0:08:24.800 --> 0:08:27.840
<v Speaker 1>most companies aren't going to go to court over case ideas.

0:08:27.880 --> 0:08:30.920
<v Speaker 1>Though for the record, I would watch a show called

0:08:31.000 --> 0:08:33.680
<v Speaker 1>case Adia Court. I think the idea has got legs.

0:08:34.559 --> 0:08:39.040
<v Speaker 1>But you're absolutely right, Matt, Like you're you're if you're

0:08:39.120 --> 0:08:43.040
<v Speaker 1>listening to this, your job, in some way, shape or form,

0:08:43.320 --> 0:08:46.439
<v Speaker 1>is monitoring you. Like, that's as old as the idea

0:08:46.480 --> 0:08:48.880
<v Speaker 1>of clocking in and clocking out on a punch card.

0:08:49.720 --> 0:08:54.480
<v Speaker 1>The issue is, especially nowadays, the process may be much

0:08:54.520 --> 0:08:59.559
<v Speaker 1>more robust, much more conspiratorial, and much less visible, and

0:08:59.640 --> 0:09:02.880
<v Speaker 1>you might think, and it's only going to accelerate in

0:09:02.920 --> 0:09:06.200
<v Speaker 1>the future. Before we move on, I have to ask you, Matt.

0:09:06.240 --> 0:09:07.640
<v Speaker 1>I want to put you on the spot. But do

0:09:07.679 --> 0:09:11.640
<v Speaker 1>you remember please? Oh good, all right, we'll put us

0:09:11.679 --> 0:09:13.320
<v Speaker 1>both on the spot. Do you remember a few months

0:09:13.320 --> 0:09:16.600
<v Speaker 1>ago we were talking about how to get under kind

0:09:16.600 --> 0:09:20.240
<v Speaker 1>of under the hood of your laptop and see what

0:09:20.360 --> 0:09:25.880
<v Speaker 1>other entities were contacting your machine. Well, yes, Ben, one

0:09:25.880 --> 0:09:27.840
<v Speaker 1>of the things you can do if you have a Mac,

0:09:28.000 --> 0:09:30.760
<v Speaker 1>you can check your activity monitor. That's a fun way

0:09:30.800 --> 0:09:33.679
<v Speaker 1>to find out if there's software running in the background

0:09:33.679 --> 0:09:36.600
<v Speaker 1>that you're unaware of that's maybe been installed without your knowledge,

0:09:36.640 --> 0:09:39.120
<v Speaker 1>because you can do that with boss wear. If you're

0:09:39.160 --> 0:09:41.600
<v Speaker 1>running a Windows machine, you check your task Manager and

0:09:41.640 --> 0:09:43.920
<v Speaker 1>do the same thing. We can talk about it and

0:09:43.960 --> 0:09:46.760
<v Speaker 1>get into a little later. But if you somehow block

0:09:47.080 --> 0:09:51.880
<v Speaker 1>the monitoring that your employers have installed on your computer, um,

0:09:51.920 --> 0:09:55.680
<v Speaker 1>that's probably going to cause more problems than just if

0:09:55.720 --> 0:10:00.000
<v Speaker 1>you don't know work around it in some other way. Uh,

0:10:00.040 --> 0:10:02.440
<v Speaker 1>but yeah, we've we found out you could do that.

0:10:02.520 --> 0:10:06.760
<v Speaker 1>There's also certain things like antivirus software that might be

0:10:06.800 --> 0:10:09.800
<v Speaker 1>on your machine that's either installed by you or your employer,

0:10:10.120 --> 0:10:13.400
<v Speaker 1>and that's a good way to monitor when things connect

0:10:13.400 --> 0:10:16.320
<v Speaker 1>to your computer, right if something physically has been plugged

0:10:16.320 --> 0:10:19.240
<v Speaker 1>in of some device, or if something virtually connects to

0:10:19.240 --> 0:10:24.240
<v Speaker 1>your machine. And a lot of these things aren't necessarily nefarious,

0:10:24.360 --> 0:10:28.040
<v Speaker 1>it's it's important to establish that from the get go

0:10:28.440 --> 0:10:31.760
<v Speaker 1>because it turns out a lot of them are very

0:10:31.840 --> 0:10:39.040
<v Speaker 1>much nefarious, insidious, dangerous. Here's where it gets crazy. So

0:10:39.559 --> 0:10:44.840
<v Speaker 1>companies struggled during the pandemic to maintain control and visibility

0:10:45.000 --> 0:10:49.920
<v Speaker 1>with an increasingly remote workforce. You used at our word

0:10:49.960 --> 0:10:53.840
<v Speaker 1>of the day just a second ago, Matt bossware. This

0:10:53.960 --> 0:11:00.280
<v Speaker 1>is just like malware software hardware. Bossware is described vibes

0:11:00.800 --> 0:11:04.839
<v Speaker 1>types of software genre software, as well as an industry

0:11:04.880 --> 0:11:11.920
<v Speaker 1>that is built entirely upon monitoring employees, monitoring productivity, even

0:11:12.000 --> 0:11:16.839
<v Speaker 1>gamifying as Microsoft and Amazon have have done. And if

0:11:16.880 --> 0:11:19.440
<v Speaker 1>you're if you're a data nerd, there's a lot of

0:11:19.440 --> 0:11:22.319
<v Speaker 1>cool stuff you can do. You can compare things, you

0:11:22.360 --> 0:11:26.040
<v Speaker 1>can build tables, you can look at, uh, the metadata

0:11:26.080 --> 0:11:29.240
<v Speaker 1>of people's time and how they spend it. So if

0:11:29.280 --> 0:11:32.400
<v Speaker 1>you you know, if one of your employees is a

0:11:32.520 --> 0:11:37.440
<v Speaker 1>night owl, like someone who is regularly burning the midnight oil,

0:11:37.679 --> 0:11:41.120
<v Speaker 1>then you will know. You will see, oh, these emails

0:11:41.160 --> 0:11:43.920
<v Speaker 1>are being sent out at eight am, but they're being

0:11:44.000 --> 0:11:48.320
<v Speaker 1>scheduled at like midnight. You know that that gives you

0:11:48.360 --> 0:11:53.160
<v Speaker 1>a sense of what your crew is doing. And boss

0:11:53.200 --> 0:11:57.400
<v Speaker 1>wear is usually going to be on a computer, a smartphone,

0:11:57.520 --> 0:12:00.560
<v Speaker 1>maybe a tablet. The important thing about it is it

0:12:00.600 --> 0:12:04.280
<v Speaker 1>has admin privileges. It can access all the info that

0:12:04.360 --> 0:12:07.160
<v Speaker 1>happens on that device. Yeah, it more or less can

0:12:07.200 --> 0:12:13.480
<v Speaker 1>collect anything and everything that happens. Right, And theoretically, these systems,

0:12:13.520 --> 0:12:18.440
<v Speaker 1>the software, and these enterprise clients, they're all about a

0:12:18.600 --> 0:12:25.600
<v Speaker 1>TPS BEEN that's attendance, time, productivity and security. Yes, yeah,

0:12:26.120 --> 0:12:29.480
<v Speaker 1>that's that's what it is, a t p S. This

0:12:29.520 --> 0:12:33.439
<v Speaker 1>stuff already existed in some form or another. As we said,

0:12:33.520 --> 0:12:36.120
<v Speaker 1>you know, regardless of where you work, if you have

0:12:36.360 --> 0:12:40.080
<v Speaker 1>a quote unquote office job, then you probably have some

0:12:40.200 --> 0:12:43.880
<v Speaker 1>kind of I T department or some kind of subcontracted

0:12:43.880 --> 0:12:49.679
<v Speaker 1>I T service, and they will, for instance, probably get

0:12:49.760 --> 0:12:54.320
<v Speaker 1>alerts if someone accesses a not Safer work website on

0:12:54.480 --> 0:12:59.280
<v Speaker 1>company equipment. And I think everybody can agree that's pretty reasonable, right,

0:13:00.800 --> 0:13:04.600
<v Speaker 1>I'm with come on that. That's it's a small battle

0:13:04.640 --> 0:13:07.120
<v Speaker 1>you've had to fight a few times over the years

0:13:07.200 --> 0:13:10.679
<v Speaker 1>just because this show is not safe for work. Again, like,

0:13:10.760 --> 0:13:13.760
<v Speaker 1>I hope you're not listening on your work device, but

0:13:13.880 --> 0:13:18.040
<v Speaker 1>I hope you are listening at work. Yes, yes, so

0:13:18.679 --> 0:13:21.680
<v Speaker 1>so yeah, this this is something that we have run

0:13:21.679 --> 0:13:24.360
<v Speaker 1>into in the course of stuff. They don't want you

0:13:24.440 --> 0:13:28.440
<v Speaker 1>to know with you know, not not too much sort

0:13:28.480 --> 0:13:31.920
<v Speaker 1>of sound and fury from the suits, but we have

0:13:32.640 --> 0:13:35.040
<v Speaker 1>you know, we we've had to like this has happened

0:13:35.040 --> 0:13:37.520
<v Speaker 1>to Jonathan Strickland on tech stuff too. This happened to

0:13:37.600 --> 0:13:40.040
<v Speaker 1>a lot of our colleagues because you have to dive

0:13:40.120 --> 0:13:43.720
<v Speaker 1>into primary sources, and some of those primary sources are

0:13:43.760 --> 0:13:48.480
<v Speaker 1>in some pretty dicey places online. Uh. And that's just

0:13:48.559 --> 0:13:52.679
<v Speaker 1>the nature of our pursuit, which is somewhat distinct and

0:13:52.720 --> 0:13:56.560
<v Speaker 1>different from a lot of other jobs. But the same

0:13:56.640 --> 0:13:59.160
<v Speaker 1>rules still apply. If you have an I T department

0:13:59.200 --> 0:14:04.560
<v Speaker 1>that gets these alert they're probably not obsessively like going

0:14:04.679 --> 0:14:08.559
<v Speaker 1>employee by employee and reading everyone's browser history. The process

0:14:08.600 --> 0:14:11.840
<v Speaker 1>has probably automated and it gets flagged, sort of the

0:14:11.880 --> 0:14:16.880
<v Speaker 1>way that state level surveillance of citizens works. Uh. And

0:14:17.160 --> 0:14:22.320
<v Speaker 1>that is changing in the remote set up right, it

0:14:22.360 --> 0:14:26.240
<v Speaker 1>was it was much more of a flagging system before

0:14:26.440 --> 0:14:31.040
<v Speaker 1>employees were far far away from the manager's physical position.

0:14:32.000 --> 0:14:36.360
<v Speaker 1>M hm. And this goes more extreme. Here's one that

0:14:36.920 --> 0:14:40.680
<v Speaker 1>you may have on your on your workplace gadgets that

0:14:40.760 --> 0:14:44.960
<v Speaker 1>you don't know about. It's something called a key logger, Matt.

0:14:45.640 --> 0:14:50.120
<v Speaker 1>Key loggers are scary partially because of how effective they are,

0:14:50.160 --> 0:14:54.080
<v Speaker 1>but I said, I think also because of how invisible

0:14:54.320 --> 0:14:58.840
<v Speaker 1>they can be and how just how much information they

0:14:58.840 --> 0:15:04.160
<v Speaker 1>can give out, there's a lot potential for shenanigans. Oh yeah, yeah.

0:15:04.200 --> 0:15:08.240
<v Speaker 1>I imagine that someone can monitor every single key stroke

0:15:08.360 --> 0:15:11.880
<v Speaker 1>that you make. That means every website you've ever visited,

0:15:11.920 --> 0:15:15.200
<v Speaker 1>if you type it in, every password you've ever entered,

0:15:15.680 --> 0:15:19.160
<v Speaker 1>if you type it in, uh, any message that you

0:15:19.200 --> 0:15:23.120
<v Speaker 1>send to anyone with a maybe a messages app or

0:15:23.160 --> 0:15:26.040
<v Speaker 1>with a text messaging service, or even WhatsApp or anything

0:15:26.080 --> 0:15:30.600
<v Speaker 1>like that. Uh, it can get monitored. And it's way scarier.

0:15:30.680 --> 0:15:33.960
<v Speaker 1>I think if this is being monitored by somebody that

0:15:34.040 --> 0:15:37.040
<v Speaker 1>you just don't know, if it's you know, your employer,

0:15:37.520 --> 0:15:41.480
<v Speaker 1>maybe your direct boss or their boss, that's could stink.

0:15:41.960 --> 0:15:43.840
<v Speaker 1>But it's not the same as if it's you know,

0:15:43.920 --> 0:15:46.880
<v Speaker 1>being tracked by some other third party that you're unaware

0:15:46.920 --> 0:15:53.000
<v Speaker 1>of exactly. Your email can also be searched. Calls made

0:15:53.040 --> 0:15:57.240
<v Speaker 1>from company issued devices can be not just recorded, but

0:15:57.400 --> 0:16:00.920
<v Speaker 1>monitoring in real time. So there's definitely the potential for

0:16:01.000 --> 0:16:04.400
<v Speaker 1>someone to be eavesdropping, which again is something that a

0:16:04.440 --> 0:16:07.240
<v Speaker 1>lot of people have just sort of accepted as normal.

0:16:07.640 --> 0:16:09.520
<v Speaker 1>Like I I don't know about you. Well, I do

0:16:09.600 --> 0:16:11.840
<v Speaker 1>know about you. We both, for a very long time

0:16:11.880 --> 0:16:14.200
<v Speaker 1>have taken it for granted that if a camera is

0:16:14.240 --> 0:16:18.200
<v Speaker 1>not physically covered up, you should treat it as though

0:16:18.200 --> 0:16:20.760
<v Speaker 1>it is recording, sort of like a gun should always

0:16:20.760 --> 0:16:23.800
<v Speaker 1>be treated as though it is loaded. Dude, do you

0:16:23.840 --> 0:16:26.280
<v Speaker 1>remember when we were we went around the office and

0:16:26.320 --> 0:16:29.120
<v Speaker 1>in all the studios we started, Well, I I don't know.

0:16:29.200 --> 0:16:31.440
<v Speaker 1>I think you did it too, but I know I

0:16:31.480 --> 0:16:35.960
<v Speaker 1>personally applied tape to many of the studio imax and

0:16:35.960 --> 0:16:39.440
<v Speaker 1>and other machines that just have cameras installed on them,

0:16:39.880 --> 0:16:42.520
<v Speaker 1>just as a like, if you need it, you can

0:16:42.560 --> 0:16:45.760
<v Speaker 1>take the tape off. Yeah, and you were I important

0:16:45.800 --> 0:16:49.760
<v Speaker 1>in your defense. In our defense, we weren't doing like

0:16:49.920 --> 0:16:52.960
<v Speaker 1>sketchy stuff. We weren't even you know, It's not like

0:16:53.280 --> 0:16:58.040
<v Speaker 1>it wasn't like, oh, no, one, we're secretly selling quayludes

0:16:58.160 --> 0:17:00.040
<v Speaker 1>or something like that. We weren't even you know, in

0:17:00.080 --> 0:17:04.920
<v Speaker 1>our noses. Well, I wasn't. No, we weren't doing anything

0:17:04.960 --> 0:17:07.040
<v Speaker 1>to ferries. It's just the fact that it's what you said.

0:17:07.080 --> 0:17:09.640
<v Speaker 1>It's a it's like a loaded gun that's pointed at

0:17:09.640 --> 0:17:12.879
<v Speaker 1>all times, not really obviously and you know, I'm not

0:17:12.920 --> 0:17:15.919
<v Speaker 1>trying to downplay guns or up play cameras. It's just

0:17:16.400 --> 0:17:19.480
<v Speaker 1>something we should be aware of exactly. And there are

0:17:19.880 --> 0:17:24.760
<v Speaker 1>numerous other examples of this monitoring, like some software. We'll

0:17:24.800 --> 0:17:30.080
<v Speaker 1>just take frequent, periodic screenshots of whatever is on your monitor.

0:17:30.440 --> 0:17:34.600
<v Speaker 1>And at this point let's pause for word from our sponsors.

0:17:34.600 --> 0:17:37.320
<v Speaker 1>See who at our job is spying on us, and

0:17:37.359 --> 0:17:42.000
<v Speaker 1>then we'll return to dive into the deeper waters surrounding

0:17:42.119 --> 0:17:53.119
<v Speaker 1>workplace surveillance. Okay, we're back. Like we said, this is

0:17:53.200 --> 0:17:56.639
<v Speaker 1>kind of normalized now. This idea of being monitored at

0:17:56.680 --> 0:18:00.480
<v Speaker 1>work is something that the majority of employees were guardless

0:18:00.520 --> 0:18:05.400
<v Speaker 1>of their specific industries, have come to accept. Some employers, yes,

0:18:05.560 --> 0:18:08.520
<v Speaker 1>are much more extreme than others. Our Offit is pretty

0:18:08.600 --> 0:18:11.200
<v Speaker 1>las fair so far as we know, which is another

0:18:11.240 --> 0:18:13.520
<v Speaker 1>thing we have to bring up in today's episode. But

0:18:14.840 --> 0:18:18.080
<v Speaker 1>there are really really extreme examples, and one that you

0:18:18.119 --> 0:18:21.800
<v Speaker 1>will run into time and time again is Amazon. Oh

0:18:21.840 --> 0:18:27.200
<v Speaker 1>my gosh, Amazon, so many methods to track your employers

0:18:27.920 --> 0:18:32.520
<v Speaker 1>in so many different positions. And let's just use one

0:18:32.560 --> 0:18:35.439
<v Speaker 1>quick example here. Imagine that you drive for a living.

0:18:36.160 --> 0:18:41.159
<v Speaker 1>This is what you do. You're You're an Amazon delivery

0:18:41.240 --> 0:18:44.920
<v Speaker 1>person and inside the vehicle with you at all times.

0:18:45.359 --> 0:18:49.440
<v Speaker 1>At all times is a three sixty degree camera that

0:18:49.560 --> 0:18:52.600
<v Speaker 1>can see anything and everything that you do, every action,

0:18:52.960 --> 0:18:58.200
<v Speaker 1>and it's constantly monitoring and judging you. Did you yawn

0:18:58.480 --> 0:19:02.240
<v Speaker 1>a little bit? Oh bro? Why did you do that?

0:19:02.320 --> 0:19:04.359
<v Speaker 1>Don't do that? Did you take a hand off the

0:19:04.359 --> 0:19:07.080
<v Speaker 1>wheel for a second? You didn't just touch your cell phone?

0:19:07.080 --> 0:19:11.600
<v Speaker 1>Did you like there? It really does monitor everything, and

0:19:11.600 --> 0:19:14.359
<v Speaker 1>it monitors what how much time you spend behind the wheel,

0:19:14.520 --> 0:19:17.080
<v Speaker 1>how much time you're away from that driver's seat to

0:19:17.200 --> 0:19:21.959
<v Speaker 1>deliver packages at a certain location. It's intense stuff, and

0:19:22.000 --> 0:19:24.600
<v Speaker 1>that's why you know it's I would say it's a

0:19:24.680 --> 0:19:28.720
<v Speaker 1>direct reason why you you may have heard these stories.

0:19:28.800 --> 0:19:33.080
<v Speaker 1>We've heard many about drivers having to urinate in the

0:19:33.119 --> 0:19:36.399
<v Speaker 1>car in order to keep their productivity rating up and

0:19:36.440 --> 0:19:39.280
<v Speaker 1>to prevent them from getting in trouble with their little

0:19:39.320 --> 0:19:43.919
<v Speaker 1>three sixty spy that lives with them. And transporting packages

0:19:44.359 --> 0:19:48.320
<v Speaker 1>is an incredibly difficult job. Whether it's the postal service,

0:19:48.320 --> 0:19:52.000
<v Speaker 1>whether it's FedEx, whether it's Amazon, people are pretty hard

0:19:52.000 --> 0:19:54.800
<v Speaker 1>on delivery drivers and it's important to remember that a

0:19:54.840 --> 0:20:00.040
<v Speaker 1>lot of times drivers are being forced to go go

0:20:00.240 --> 0:20:04.000
<v Speaker 1>through certain optimized routes they are, you know, they have

0:20:04.320 --> 0:20:07.240
<v Speaker 1>a route dictated to them, and they can in some

0:20:07.280 --> 0:20:10.440
<v Speaker 1>cases be penalized if they say, well, it doesn't make

0:20:10.480 --> 0:20:12.000
<v Speaker 1>sense for me to go this way, so I'm gonna

0:20:12.040 --> 0:20:14.439
<v Speaker 1>go this other way, you know traffic, or I have

0:20:14.480 --> 0:20:17.000
<v Speaker 1>another drop that's just down the street, let me knock

0:20:17.040 --> 0:20:19.640
<v Speaker 1>that out. Well, you know, Ben, it makes a lot

0:20:19.680 --> 0:20:24.000
<v Speaker 1>more sense why there's been a massive uptick in videos

0:20:24.119 --> 0:20:27.800
<v Speaker 1>of delivery drivers like maybe tossing a package a little

0:20:27.800 --> 0:20:29.920
<v Speaker 1>bit to keep down the amount of time they're spending

0:20:29.920 --> 0:20:32.639
<v Speaker 1>in one place. That's it's crazy to think about. And

0:20:32.680 --> 0:20:36.040
<v Speaker 1>you know, it certainly doesn't excuse destroying the contents of

0:20:36.040 --> 0:20:37.840
<v Speaker 1>a package by throwing it or something. But you could

0:20:37.840 --> 0:20:43.000
<v Speaker 1>totally see why what happened. Yeah, absolutely can. And the

0:20:43.040 --> 0:20:46.960
<v Speaker 1>companies that are selling this tracking software, they're making it killing.

0:20:47.520 --> 0:20:50.560
<v Speaker 1>Don't worry about them. They're they're doing fine, we assure you.

0:20:51.000 --> 0:20:53.440
<v Speaker 1>But there's a lot of criticism coming out, and many

0:20:53.440 --> 0:20:57.960
<v Speaker 1>critics are increasingly concerned about what happens when your office

0:20:58.119 --> 0:21:02.960
<v Speaker 1>becomes your home and your company's little version of Big

0:21:02.960 --> 0:21:06.440
<v Speaker 1>Brother becomes in a very real way, like a nosy

0:21:06.560 --> 0:21:10.920
<v Speaker 1>roommate that's hovering over your shoulder. Like, for instance, Matt,

0:21:11.080 --> 0:21:15.440
<v Speaker 1>you are you are recording in your house, in your office.

0:21:15.600 --> 0:21:18.479
<v Speaker 1>I'm recording in a room in my place that I

0:21:18.560 --> 0:21:23.119
<v Speaker 1>just converted into an office. You know, this is just

0:21:23.160 --> 0:21:26.520
<v Speaker 1>a room that I converted into an office as well. Yes, yes, yes,

0:21:26.720 --> 0:21:30.639
<v Speaker 1>we just we're working in conversion rooms, I guess. But

0:21:30.960 --> 0:21:35.600
<v Speaker 1>our personal lives also occur in these rooms, you know.

0:21:35.760 --> 0:21:41.359
<v Speaker 1>And the question then becomes a question about thresholds, boundaries,

0:21:41.760 --> 0:21:46.040
<v Speaker 1>and comfort levels. How much should your employer be able

0:21:46.080 --> 0:21:50.160
<v Speaker 1>to know about your personal life? Uh? Found a great

0:21:50.240 --> 0:21:54.119
<v Speaker 1>quote by an outfit called the Electronic Frontier Foundation the

0:21:54.119 --> 0:21:56.240
<v Speaker 1>e f F. We've talked about them on the show before,

0:21:56.720 --> 0:21:59.159
<v Speaker 1>and I like how they put this. They put it

0:21:59.320 --> 0:22:05.320
<v Speaker 1>pretty succinctly when they talk about when when they introduce

0:22:05.400 --> 0:22:09.479
<v Speaker 1>the concept of bosswear, and when they talk about how

0:22:09.800 --> 0:22:13.119
<v Speaker 1>these tools are sold to employers and how they can

0:22:13.160 --> 0:22:18.400
<v Speaker 1>affect employees. And they say, some vendors build their tools

0:22:18.440 --> 0:22:23.280
<v Speaker 1>as automatic time tracking or workplace analytics software. Others market

0:22:23.320 --> 0:22:27.240
<v Speaker 1>to companies concerned about data breaches or intellectual property theft.

0:22:27.640 --> 0:22:32.480
<v Speaker 1>We'll call these tools collectively bosswear. Hey, here's the term there.

0:22:32.480 --> 0:22:35.399
<v Speaker 1>It is the e f F is using it. So

0:22:35.440 --> 0:22:38.480
<v Speaker 1>I think we were totally fine and using bosswear. Yeah,

0:22:38.600 --> 0:22:41.960
<v Speaker 1>let's continue with the quote. While aimed at helping employers,

0:22:42.040 --> 0:22:45.640
<v Speaker 1>boss ware puts workers privacy and security at risk by

0:22:45.680 --> 0:22:50.480
<v Speaker 1>logging every click and key stroke, covertly gathering information for lawsuits,

0:22:50.680 --> 0:22:53.600
<v Speaker 1>and using other spying features that go far beyond what

0:22:53.760 --> 0:22:58.280
<v Speaker 1>is necessary and proportionate to manage a workforce. Yeah, so

0:22:59.080 --> 0:23:03.200
<v Speaker 1>their their idea is that this is overkilled basically, That's

0:23:03.280 --> 0:23:05.359
<v Speaker 1>that's kind of the crux of their argument. And yeah,

0:23:05.400 --> 0:23:08.240
<v Speaker 1>it's clear that the e f F has a horse

0:23:08.280 --> 0:23:11.040
<v Speaker 1>in this race. They have an opinion, they have a

0:23:11.080 --> 0:23:14.359
<v Speaker 1>badger in the bag because again, they're a nonprofit that

0:23:14.480 --> 0:23:18.240
<v Speaker 1>is intensely focused on worrying about privacy and the digital sphere.

0:23:18.400 --> 0:23:20.840
<v Speaker 1>That is their job, right, So it's not hard to

0:23:20.880 --> 0:23:23.439
<v Speaker 1>see why they have all people would think this is

0:23:23.440 --> 0:23:27.360
<v Speaker 1>a bad thing. Remotely controlling a laptop camera in an office,

0:23:27.640 --> 0:23:31.480
<v Speaker 1>that's one thing. But then imagine you have a camera

0:23:32.160 --> 0:23:35.560
<v Speaker 1>that turns on without your consent in your own bedroom,

0:23:36.200 --> 0:23:40.960
<v Speaker 1>like after work hours. You know, now it's like nine thirty,

0:23:41.160 --> 0:23:45.240
<v Speaker 1>you're kicking it, you know, on the bed, uh, next

0:23:45.280 --> 0:23:47.520
<v Speaker 1>to your desk or something. I don't know, you're watching

0:23:47.640 --> 0:23:51.480
<v Speaker 1>always sunning in Philadelphia, or you're you're knitting because that's

0:23:51.480 --> 0:23:53.879
<v Speaker 1>your new hobby during the pandemic for some reason. In

0:23:53.920 --> 0:23:58.959
<v Speaker 1>this scenario, and all of a sudden, you notice that

0:23:59.040 --> 0:24:03.160
<v Speaker 1>little little red light on your camera whatever your devices

0:24:03.720 --> 0:24:05.680
<v Speaker 1>has popped on and you don't know how long it's

0:24:05.720 --> 0:24:08.360
<v Speaker 1>been on, and you don't know why it's on. You

0:24:08.400 --> 0:24:10.960
<v Speaker 1>can go and shut it off yourself or cover it,

0:24:11.440 --> 0:24:14.359
<v Speaker 1>but now you know someone else can drive your car

0:24:14.560 --> 0:24:17.879
<v Speaker 1>as it were. Add to this the even more black

0:24:17.920 --> 0:24:22.200
<v Speaker 1>mirrorsque part of this. I believe there's functionality in some

0:24:22.280 --> 0:24:25.240
<v Speaker 1>devices to have the camera on without seeming as though

0:24:25.280 --> 0:24:30.080
<v Speaker 1>it is on. But just in in many of these

0:24:30.119 --> 0:24:34.680
<v Speaker 1>software's defense, it is only used on company time, right,

0:24:35.040 --> 0:24:37.919
<v Speaker 1>So if there's a certain number of work hours you're

0:24:37.960 --> 0:24:40.119
<v Speaker 1>supposed to keep in a week, and those work hours

0:24:40.119 --> 0:24:43.639
<v Speaker 1>are between a certain time, then generally it could or

0:24:43.680 --> 0:24:46.720
<v Speaker 1>would be active and then would be inactive, and other

0:24:46.760 --> 0:24:49.800
<v Speaker 1>times that isn't always the case. And you know, there's

0:24:49.800 --> 0:24:52.479
<v Speaker 1>so many variables that go into that. This is a

0:24:52.520 --> 0:24:56.000
<v Speaker 1>real scenario that could happen. Yeah, yeah, And at this

0:24:56.040 --> 0:24:58.560
<v Speaker 1>point there might be some folks in the audience who

0:24:58.640 --> 0:25:00.840
<v Speaker 1>some of us are thinking, well, well, this is kind

0:25:00.840 --> 0:25:04.600
<v Speaker 1>of are we being a sensationalistic or guys, calm down,

0:25:04.720 --> 0:25:08.959
<v Speaker 1>it's the Internet. Privacy doesn't exist anymore. But before we

0:25:09.000 --> 0:25:11.800
<v Speaker 1>ask if this is alarmist, let's look at some of

0:25:11.840 --> 0:25:16.440
<v Speaker 1>those general categories of monitoring. What we have just talked

0:25:16.480 --> 0:25:20.760
<v Speaker 1>about is the most common type of surveillance activity monitoring.

0:25:21.160 --> 0:25:24.760
<v Speaker 1>It's a log of which apps you use, which websites

0:25:24.800 --> 0:25:28.280
<v Speaker 1>you visit. It could include stuff like who you email

0:25:28.880 --> 0:25:33.000
<v Speaker 1>and when, including the subject line metadata. It could also

0:25:33.040 --> 0:25:37.120
<v Speaker 1>include posts you make on social media on your work computer, tablet,

0:25:37.240 --> 0:25:41.679
<v Speaker 1>or phones. Let's say you just got hot news story

0:25:41.880 --> 0:25:44.560
<v Speaker 1>or an announcement and you go to Twitter or you

0:25:44.600 --> 0:25:46.800
<v Speaker 1>go to Facebook and you just pop it up there

0:25:46.840 --> 0:25:49.560
<v Speaker 1>while you're thinking about it. Then your employer will know

0:25:49.640 --> 0:25:54.119
<v Speaker 1>about that as well. And this is one of the

0:25:54.160 --> 0:25:57.160
<v Speaker 1>most widely accepted things. Just assume people know what you're

0:25:57.160 --> 0:26:01.600
<v Speaker 1>doing on the work computer, but the boss where that records,

0:26:01.680 --> 0:26:04.080
<v Speaker 1>you know, physical input on your mouth or your keyboard,

0:26:05.119 --> 0:26:10.280
<v Speaker 1>You might be surprised by by the process that occurs there.

0:26:10.320 --> 0:26:14.040
<v Speaker 1>This takes a look at a minute by minute breakdown,

0:26:14.240 --> 0:26:16.720
<v Speaker 1>you know what I mean, Like, what are Ben and

0:26:16.760 --> 0:26:20.240
<v Speaker 1>Matt typing what are Matt and Ben reading and when

0:26:20.240 --> 0:26:23.000
<v Speaker 1>are they reading it? And then that is used as

0:26:23.080 --> 0:26:26.600
<v Speaker 1>kind of a stand in for productivity, and anybody has

0:26:26.600 --> 0:26:29.560
<v Speaker 1>worked in the field of research before, you know that

0:26:30.520 --> 0:26:32.719
<v Speaker 1>there's a lot of stuff you might be doing that

0:26:32.880 --> 0:26:36.760
<v Speaker 1>looks inactive because you're just you're reading a book, right,

0:26:37.040 --> 0:26:40.800
<v Speaker 1>or you're deep in a weird government PDF. And that's

0:26:40.840 --> 0:26:44.560
<v Speaker 1>the one pager on for like three hours. Yeah, no,

0:26:44.680 --> 0:26:46.760
<v Speaker 1>you're right, And it's a weird thing to bring into

0:26:46.800 --> 0:26:50.600
<v Speaker 1>our world. Been because for me, and let's say the

0:26:50.680 --> 0:26:54.600
<v Speaker 1>last the forty five minutes to the run up of recording,

0:26:55.480 --> 0:26:58.679
<v Speaker 1>I stopped reading and I started jumping in YouTube to

0:26:58.720 --> 0:27:02.560
<v Speaker 1>see how this has been reported on by other outfits, right,

0:27:02.640 --> 0:27:06.040
<v Speaker 1>And so I'm literally sitting here at my computer with

0:27:06.080 --> 0:27:10.080
<v Speaker 1>my cameras covered of course, and my microphone turned off,

0:27:10.440 --> 0:27:13.200
<v Speaker 1>but I'm watching YouTube videos and I'm just trying to

0:27:13.320 --> 0:27:15.800
<v Speaker 1>take in as much information as i can to see

0:27:15.800 --> 0:27:18.720
<v Speaker 1>how other people have covered it. And if this, you know,

0:27:18.760 --> 0:27:21.000
<v Speaker 1>if this system or one of these systems was watching

0:27:21.080 --> 0:27:23.520
<v Speaker 1>me and monitoring me, it would look like I'm literally

0:27:23.560 --> 0:27:27.400
<v Speaker 1>just watching YouTube videos, um, which is what I was doing.

0:27:27.920 --> 0:27:29.840
<v Speaker 1>But it was part of my job. So It's just

0:27:30.040 --> 0:27:34.480
<v Speaker 1>a strange thing. You know, if you're if your job

0:27:34.680 --> 0:27:39.000
<v Speaker 1>is based on you know, a quantitative number of tasks,

0:27:39.040 --> 0:27:43.440
<v Speaker 1>like in you know, the let's say the Amazon drivers circumstance,

0:27:44.440 --> 0:27:47.480
<v Speaker 1>this specific thing monitoring your computer isn't gonna help. But

0:27:47.680 --> 0:27:50.199
<v Speaker 1>a you know, watching how many tasks are done in

0:27:50.240 --> 0:27:53.320
<v Speaker 1>a certain amount of time is like, in a weird,

0:27:53.640 --> 0:27:58.040
<v Speaker 1>messed up, dystopian way, something that an employer should kind

0:27:58.040 --> 0:28:01.719
<v Speaker 1>of be interested in, Um, that kind of metric, I guess,

0:28:02.560 --> 0:28:07.040
<v Speaker 1>but when it comes I mean to an extent, right, yeah,

0:28:07.080 --> 0:28:12.399
<v Speaker 1>But you know, in many office employees situations, it's a

0:28:12.520 --> 0:28:17.040
<v Speaker 1>very different scenario. It's it's almost like you should be

0:28:17.200 --> 0:28:21.399
<v Speaker 1>more focused on the results of whatever those hours are

0:28:21.440 --> 0:28:24.120
<v Speaker 1>spent doing. What are the results of those hours, rather

0:28:24.200 --> 0:28:28.880
<v Speaker 1>than here's all the stuff that's occurring during those hours. Right.

0:28:29.040 --> 0:28:33.240
<v Speaker 1>It changes based on the nature of the task, the

0:28:33.359 --> 0:28:36.400
<v Speaker 1>nature of the work. So for example, if you are

0:28:36.560 --> 0:28:41.200
<v Speaker 1>working in a call center, then the phone becomes a

0:28:41.440 --> 0:28:46.120
<v Speaker 1>very robust way of monitoring how this person made X,

0:28:46.160 --> 0:28:50.040
<v Speaker 1>took X calls or processed why claims in Z space

0:28:50.080 --> 0:28:54.400
<v Speaker 1>of time they spent you know, X amount of time

0:28:55.040 --> 0:28:57.600
<v Speaker 1>on a bathroom break or something like that, you know,

0:28:57.680 --> 0:29:01.120
<v Speaker 1>and even down breaking it down into it by minute increments,

0:29:01.920 --> 0:29:07.000
<v Speaker 1>whereas which is pretty gross. Yeah, yeah, I get that.

0:29:07.080 --> 0:29:11.600
<v Speaker 1>It's like necessary, you know, because maybe somebody just doesn't

0:29:11.640 --> 0:29:13.360
<v Speaker 1>want to be on the phone for a minute and

0:29:13.360 --> 0:29:15.720
<v Speaker 1>they're out of break time, so they just go and

0:29:16.480 --> 0:29:19.480
<v Speaker 1>sit in the bathroom. That happens. People at call centers

0:29:19.520 --> 0:29:24.600
<v Speaker 1>have done that, um, just to get away. But it

0:29:24.800 --> 0:29:29.240
<v Speaker 1>is kind of weird, right because like over time, does

0:29:29.280 --> 0:29:33.920
<v Speaker 1>that mean that your employer has has modeled out your

0:29:34.400 --> 0:29:40.600
<v Speaker 1>bowel movements? Yeah, like three fifteen, we're gonna lose Norman

0:29:40.720 --> 0:29:47.640
<v Speaker 1>or Henrietta for about five minutes. Man Shavid has taken

0:29:47.680 --> 0:29:50.840
<v Speaker 1>a long time to make his sandwich today, All right,

0:29:51.000 --> 0:29:54.800
<v Speaker 1>Well we'll see what happens when he gets back. And

0:29:55.280 --> 0:30:01.400
<v Speaker 1>there are generally two ways boss wear is deployed. Well industry, Yeah,

0:30:01.480 --> 0:30:04.280
<v Speaker 1>this is really important. There could be an app that

0:30:04.440 --> 0:30:08.560
<v Speaker 1>is visible to you or maybe even controllable by the

0:30:08.680 --> 0:30:12.640
<v Speaker 1>worker something where like Okay, I am officially starting my day,

0:30:12.720 --> 0:30:16.600
<v Speaker 1>so I'm going to log into some program and then

0:30:16.640 --> 0:30:19.320
<v Speaker 1>I'm going to log out of that program and the

0:30:19.320 --> 0:30:23.480
<v Speaker 1>stuff I've done is documented, that's transparent. That's just a

0:30:23.480 --> 0:30:26.360
<v Speaker 1>way of keeping people you know, accountable, and it could

0:30:26.360 --> 0:30:28.840
<v Speaker 1>be a win win for everyone because that kind of

0:30:28.880 --> 0:30:35.280
<v Speaker 1>thing also in theory, helps employees establish their boundaries. Right,

0:30:35.320 --> 0:30:39.479
<v Speaker 1>I have logged out. I am no longer Paul Mission

0:30:39.480 --> 0:30:42.600
<v Speaker 1>Control decade. I am Paul the case of thea king,

0:30:43.120 --> 0:30:46.680
<v Speaker 1>uh that that kind of stuff. But the other way

0:30:48.320 --> 0:30:52.640
<v Speaker 1>is not near as as um above board. The other

0:30:52.720 --> 0:30:58.680
<v Speaker 1>way is a secret background process that you cannot see

0:30:58.840 --> 0:31:01.600
<v Speaker 1>unless you know what you're looking for. And a lot

0:31:01.640 --> 0:31:05.400
<v Speaker 1>of people were so overworked these days, frankly, don't consider

0:31:05.400 --> 0:31:08.000
<v Speaker 1>it a good use of time to go digging into that,

0:31:08.200 --> 0:31:10.640
<v Speaker 1>you know, And and the companies that sell this stuff,

0:31:11.080 --> 0:31:16.560
<v Speaker 1>they don't have a strong opinion about which approach organizations

0:31:16.600 --> 0:31:19.600
<v Speaker 1>should take. They will say, hey, well install it either way.

0:31:19.680 --> 0:31:21.840
<v Speaker 1>You want them to know what's up, that's fine. You

0:31:21.880 --> 0:31:24.200
<v Speaker 1>want to you want a secret, you like secrets, will

0:31:24.200 --> 0:31:28.520
<v Speaker 1>do a secret will do a secret one? Yeah, I mean,

0:31:28.840 --> 0:31:31.560
<v Speaker 1>it's just creepy to imagine that it could be happening

0:31:31.640 --> 0:31:34.920
<v Speaker 1>without your knowledge. There are several videos you can find

0:31:34.960 --> 0:31:40.360
<v Speaker 1>on YouTube where there's like a zoom session essentially of

0:31:40.400 --> 0:31:43.920
<v Speaker 1>someone pitching their employee monitoring software and they go into

0:31:44.000 --> 0:31:48.040
<v Speaker 1>a spiel where they they discussed this thing exactly how

0:31:48.080 --> 0:31:51.400
<v Speaker 1>to install it covertly if you wish to, so it

0:31:51.440 --> 0:31:53.920
<v Speaker 1>just goes out to all your employees machines on the

0:31:53.960 --> 0:31:58.800
<v Speaker 1>network at once. Um yikes. And then it gets a

0:31:58.800 --> 0:32:02.680
<v Speaker 1>little complicated depends on if you're like logged into your

0:32:02.680 --> 0:32:05.200
<v Speaker 1>company's VPN or something like that, or how you could

0:32:05.200 --> 0:32:09.080
<v Speaker 1>actually get access in that way. But it is something

0:32:09.120 --> 0:32:11.920
<v Speaker 1>that can happen, and it is designed. Many of these

0:32:11.920 --> 0:32:15.600
<v Speaker 1>softwares are designed to be installed that way. Uh Ben.

0:32:15.680 --> 0:32:18.320
<v Speaker 1>I wanted to take one second, just as we're going

0:32:18.360 --> 0:32:20.400
<v Speaker 1>through all this stuff and just name off a couple

0:32:20.440 --> 0:32:23.280
<v Speaker 1>of these pieces of software so people can be aware.

0:32:24.600 --> 0:32:28.080
<v Speaker 1>I jumped over to PC mag the old PC magazine

0:32:28.080 --> 0:32:31.000
<v Speaker 1>that I used to get in the mail. Really miss

0:32:31.000 --> 0:32:35.280
<v Speaker 1>it and miss it? That's okay, um there, This is

0:32:35.320 --> 0:32:39.400
<v Speaker 1>their best employee monitoring software for two. You can find

0:32:39.440 --> 0:32:44.880
<v Speaker 1>this online right now. One is called Tara Mind. Tara Mind.

0:32:45.360 --> 0:32:47.360
<v Speaker 1>I heard a lot about this one, and in the

0:32:47.360 --> 0:32:51.520
<v Speaker 1>research for this there's also active track heard about that

0:32:51.560 --> 0:32:56.680
<v Speaker 1>one one called I've been I'm gonna say very atto cerebral.

0:32:58.000 --> 0:33:02.440
<v Speaker 1>So it looks like it looks like riato cerebral um

0:33:02.680 --> 0:33:08.800
<v Speaker 1>Controlo's hub staff that sounds more like like an actual

0:33:08.840 --> 0:33:13.360
<v Speaker 1>staffing saying, um like it sounds like a service that

0:33:13.760 --> 0:33:18.040
<v Speaker 1>rents out husbands for people. That's the old hub staff.

0:33:19.440 --> 0:33:23.520
<v Speaker 1>Oh man. Uh, there's also inter Guard. You can learn

0:33:23.560 --> 0:33:26.920
<v Speaker 1>a lot about Interguard. That one has been featured I

0:33:26.960 --> 0:33:29.680
<v Speaker 1>think by the BBC and CBS and a couple other

0:33:29.840 --> 0:33:39.040
<v Speaker 1>couple other outlets staff cop. I don't like that one. Nope, nope. Uh.

0:33:39.160 --> 0:33:43.080
<v Speaker 1>There's also vera clock sounds like a timekeeping one, desk,

0:33:43.200 --> 0:33:50.080
<v Speaker 1>time Pro and work Pulse without the new LS. Yeah,

0:33:50.560 --> 0:33:53.120
<v Speaker 1>that's just that. That's just a few because there are

0:33:53.160 --> 0:33:56.080
<v Speaker 1>there are so many. There are too many really for

0:33:56.200 --> 0:34:00.920
<v Speaker 1>us to name in today's show. But the f did

0:34:00.960 --> 0:34:04.040
<v Speaker 1>some great work digging into these. Again, yes they are

0:34:04.160 --> 0:34:08.480
<v Speaker 1>biased source, but we want to acknowledge that they found

0:34:08.560 --> 0:34:14.160
<v Speaker 1>some commonalities across these many, many companies and services. First

0:34:14.200 --> 0:34:18.440
<v Speaker 1>thing first, every piece of software, every product they looked at,

0:34:18.840 --> 0:34:22.719
<v Speaker 1>had the ability to take those regular, frequent screenshots of

0:34:22.719 --> 0:34:27.320
<v Speaker 1>a company device. Ben is up at three am reading

0:34:27.560 --> 0:34:32.560
<v Speaker 1>you know about the history of her Hermetic Magic. Okay, okay,

0:34:32.800 --> 0:34:37.360
<v Speaker 1>says you know, whatever whatever I have saw on department

0:34:37.560 --> 0:34:40.200
<v Speaker 1>is watching my computer at the time. He better do

0:34:40.239 --> 0:34:43.719
<v Speaker 1>an episode about this, because otherwise this guy is just

0:34:44.320 --> 0:34:49.239
<v Speaker 1>being a midnight wizard. It's PM Eastern and Matt has

0:34:49.280 --> 0:34:52.319
<v Speaker 1>recorded another piano riff and he's attempting to edit it

0:34:52.360 --> 0:34:57.239
<v Speaker 1>on his work machine. Crap, I love this. Yeah, yeah,

0:34:57.360 --> 0:35:01.520
<v Speaker 1>it's uh. Let's see it's uh. At the same time,

0:35:01.920 --> 0:35:06.840
<v Speaker 1>this is saar On sees At for some reason, then

0:35:06.880 --> 0:35:11.200
<v Speaker 1>has twenty three tabs open on the history of the

0:35:11.200 --> 0:35:14.240
<v Speaker 1>refugee crisis in Bhutan, and now he's going to wiki

0:35:14.280 --> 0:35:23.719
<v Speaker 1>travel and now he's looking up a recipe for casseroles.

0:35:23.719 --> 0:35:25.960
<v Speaker 1>So the screen scots are one thing, they can see

0:35:25.960 --> 0:35:30.239
<v Speaker 1>what's actively happening on your machine, but it's still contained

0:35:30.280 --> 0:35:34.560
<v Speaker 1>within your machine, right. The other thing many of them

0:35:34.640 --> 0:35:38.000
<v Speaker 1>can do, not all of them. Many of them can

0:35:38.080 --> 0:35:43.040
<v Speaker 1>provide real time video links to your the device, So

0:35:43.160 --> 0:35:46.480
<v Speaker 1>can you can actually monitor the employee themselves rather than

0:35:46.520 --> 0:35:49.600
<v Speaker 1>just what the employee is in putting into the computer.

0:35:50.680 --> 0:35:53.240
<v Speaker 1>You can see that you can see that person's face

0:35:53.760 --> 0:35:58.760
<v Speaker 1>as they read an email, right or as they listen

0:35:58.840 --> 0:36:01.080
<v Speaker 1>to a zoom call with the belief that they have

0:36:01.160 --> 0:36:05.439
<v Speaker 1>turned their camera off. This also I'm getting a little

0:36:05.440 --> 0:36:07.600
<v Speaker 1>sci fi here, but this is also really interesting to

0:36:07.680 --> 0:36:09.880
<v Speaker 1>me because if it was coupled with the right kind

0:36:09.920 --> 0:36:14.239
<v Speaker 1>of algorithm, with the right kind of AI, you could

0:36:14.320 --> 0:36:19.880
<v Speaker 1>conceivably measure people's micro expressions, the little little emotional ticks

0:36:19.880 --> 0:36:23.560
<v Speaker 1>that folks can't often control, and then you would get

0:36:23.600 --> 0:36:28.920
<v Speaker 1>great insight into what those employees were actually thinking. Legally,

0:36:29.000 --> 0:36:31.480
<v Speaker 1>that is something you can do, but it feels really

0:36:31.680 --> 0:36:35.880
<v Speaker 1>ethically fraught, doesn't it. I mean, let's let's see. Okay,

0:36:35.880 --> 0:36:38.920
<v Speaker 1>so let's say this, you're, for some reason, checking on

0:36:39.200 --> 0:36:43.520
<v Speaker 1>checking on Matt as he learns about vitamin D and

0:36:43.560 --> 0:36:47.680
<v Speaker 1>its effects with a macron for his newest song that

0:36:47.760 --> 0:36:51.759
<v Speaker 1>he's writing. And sure, yeah, sure, and uh and so

0:36:52.560 --> 0:36:56.560
<v Speaker 1>uh the soone, the I T or whatever monitoring apartment says, Oh,

0:36:56.560 --> 0:36:58.560
<v Speaker 1>this is interesting. I like that. I like that riff.

0:36:58.560 --> 0:37:02.960
<v Speaker 1>He's really he's really spreading his wings musically. I wonder

0:37:03.040 --> 0:37:05.879
<v Speaker 1>what it looks like right now when he's playing this,

0:37:06.000 --> 0:37:09.160
<v Speaker 1>and they could turn on the feed and maybe they see,

0:37:09.360 --> 0:37:12.920
<v Speaker 1>you know, they see you diligently editing the song you

0:37:12.960 --> 0:37:20.920
<v Speaker 1>have created, but then they say sorry, But then they say,

0:37:20.960 --> 0:37:25.839
<v Speaker 1>I'm suspicious of this new kind of like app or

0:37:25.880 --> 0:37:30.640
<v Speaker 1>this program that he downloaded for this music editing mission.

0:37:31.160 --> 0:37:35.319
<v Speaker 1>So I'm gonna jump in. I'm gonna take control of

0:37:35.360 --> 0:37:39.480
<v Speaker 1>his desktop, remotely access it, and I'm gonna learn more

0:37:39.480 --> 0:37:41.560
<v Speaker 1>about this program, and I might delete it if I

0:37:41.640 --> 0:37:44.200
<v Speaker 1>want to, and I don't have to. I don't have

0:37:44.239 --> 0:37:46.160
<v Speaker 1>to say that I did it. I'm just gonna do it.

0:37:47.080 --> 0:37:51.719
<v Speaker 1>So the problem here is that these these pieces of

0:37:51.760 --> 0:37:55.200
<v Speaker 1>software don't really distinguish between your work related stuff and

0:37:55.239 --> 0:37:59.080
<v Speaker 1>your personal stuff. So if you have an office job

0:37:59.120 --> 0:38:01.680
<v Speaker 1>and you have a compute, or you've probably used it

0:38:01.760 --> 0:38:05.719
<v Speaker 1>for some personal thing, a small digital errand that's very,

0:38:05.800 --> 0:38:09.320
<v Speaker 1>very common almost everywhere, except for the kind of offices

0:38:09.360 --> 0:38:12.960
<v Speaker 1>you need a security clearance to work in. So imagine this.

0:38:12.960 --> 0:38:14.480
<v Speaker 1>This is what I was thinking of. I think a

0:38:14.560 --> 0:38:18.160
<v Speaker 1>lot of people have experienced this. You're working on something

0:38:18.719 --> 0:38:20.360
<v Speaker 1>and then it hits you. You You go, oh, it's the

0:38:20.360 --> 0:38:22.560
<v Speaker 1>twenty nine I need to pay that utility bill. I

0:38:22.600 --> 0:38:24.480
<v Speaker 1>don't want to be late on it. Or oh I

0:38:24.520 --> 0:38:26.640
<v Speaker 1>should check my bank account just to make sure you

0:38:26.680 --> 0:38:29.720
<v Speaker 1>know a charge went through or something. The vast majority

0:38:29.719 --> 0:38:31.839
<v Speaker 1>of people are not going to think twice about just

0:38:32.600 --> 0:38:35.800
<v Speaker 1>knocking out that little task. They're gonna open another tab

0:38:35.840 --> 0:38:38.200
<v Speaker 1>and whatever their browser is, they're gonna go to the

0:38:38.200 --> 0:38:41.160
<v Speaker 1>website they need, they're going to enter their password, their

0:38:41.280 --> 0:38:43.640
<v Speaker 1>use their name, and they're gonna pay up. And the

0:38:43.719 --> 0:38:47.760
<v Speaker 1>monitary service sucks that up as well. So your employer

0:38:47.920 --> 0:38:51.600
<v Speaker 1>might not you know, I know that you're making pasta

0:38:51.719 --> 0:38:54.439
<v Speaker 1>for dinner or something, but they can definitely know your

0:38:54.800 --> 0:38:58.920
<v Speaker 1>bank information, your personal log It's for everything, for social

0:38:58.960 --> 0:39:02.200
<v Speaker 1>media as well. That can spell trouble if a hack occurs,

0:39:02.520 --> 0:39:06.520
<v Speaker 1>if corruption occurs, and it can also is the scary part.

0:39:07.040 --> 0:39:12.960
<v Speaker 1>It could conceivably be used to pressure employees. Man, I

0:39:13.200 --> 0:39:17.840
<v Speaker 1>I check my bank account today on my work machine.

0:39:19.239 --> 0:39:26.040
<v Speaker 1>Uh well, let's pause for a second so we can

0:39:26.040 --> 0:39:29.400
<v Speaker 1>all go change our passwords and then we'll return to

0:39:29.520 --> 0:39:41.239
<v Speaker 1>explore the future of the workplace surveillance conspiracy. Okay, so

0:39:41.280 --> 0:39:43.239
<v Speaker 1>this is this is the thing I wanted to bring

0:39:43.320 --> 0:39:45.439
<v Speaker 1>up with you, Matt, and I'm really interested to see

0:39:45.440 --> 0:39:50.479
<v Speaker 1>what our fellow listeners think about this. So what if

0:39:51.080 --> 0:39:55.279
<v Speaker 1>an employer finds something and finds evidence of something that

0:39:55.400 --> 0:40:01.200
<v Speaker 1>is against company policy, not like not necessarily um a crime,

0:40:02.000 --> 0:40:05.239
<v Speaker 1>maybe just some like they were they were sloppy with

0:40:05.280 --> 0:40:10.520
<v Speaker 1>confidential information, or they did some kind of violation of policy,

0:40:10.560 --> 0:40:16.320
<v Speaker 1>like they're not allowed to be on personal uh personal

0:40:16.360 --> 0:40:19.000
<v Speaker 1>sites or something like that during work hours, but they were.

0:40:19.400 --> 0:40:22.160
<v Speaker 1>What if the employer doesn't, you know, immediately flag that

0:40:22.280 --> 0:40:25.000
<v Speaker 1>and ask them to discontinue that behavior. What if they

0:40:25.080 --> 0:40:31.120
<v Speaker 1>save that as AMMO as leverage for the future, you

0:40:31.160 --> 0:40:33.879
<v Speaker 1>know what I mean? Like that that is possible? Yeah,

0:40:33.960 --> 0:40:36.839
<v Speaker 1>I guess so, I'm trying to imagine this. I think

0:40:36.840 --> 0:40:39.240
<v Speaker 1>there are only a few scenarios where that could occur.

0:40:40.120 --> 0:40:42.239
<v Speaker 1>It reminds me of a discussion we had with a

0:40:42.239 --> 0:40:45.399
<v Speaker 1>certain person that came on our show that I won't

0:40:45.520 --> 0:40:52.360
<v Speaker 1>name of like saving Ammo for like contract disputes, you know, um,

0:40:52.360 --> 0:40:55.920
<v Speaker 1>for the future. But I don't know. I can't imagine.

0:40:56.520 --> 0:40:59.880
<v Speaker 1>I can't imagine they're not being some pr nightmare for

0:40:59.880 --> 0:41:05.279
<v Speaker 1>a company that like saves compromise on their employees, right right, Well,

0:41:05.320 --> 0:41:08.880
<v Speaker 1>think about it. Maybe, I agree would be a rarefied field,

0:41:08.960 --> 0:41:11.960
<v Speaker 1>But think about it. Maybe in the world of politics

0:41:13.320 --> 0:41:17.400
<v Speaker 1>that that's where that information could be useful and actionable.

0:41:18.280 --> 0:41:21.120
<v Speaker 1>When we're looking at the future workplace surveillance. That is

0:41:21.160 --> 0:41:24.080
<v Speaker 1>an extreme example. I think it's safe to say that

0:41:24.160 --> 0:41:28.160
<v Speaker 1>the majority of companies are not scheming to like blackmail

0:41:28.200 --> 0:41:33.760
<v Speaker 1>and extort their employees, not necessarily because it's an ethical quantry,

0:41:34.120 --> 0:41:37.080
<v Speaker 1>more so because it's like why it's not worth the effort.

0:41:37.320 --> 0:41:40.719
<v Speaker 1>It's kind of like a Rube Goldberg esque approach to

0:41:41.000 --> 0:41:43.759
<v Speaker 1>getting people to do stuff you want. You could just

0:41:43.920 --> 0:41:48.399
<v Speaker 1>ask them, you do pay them to work? Yeah, you know, Yeah,

0:41:48.440 --> 0:41:52.319
<v Speaker 1>that's the thing. A lot of this feels like, so,

0:41:52.560 --> 0:41:56.560
<v Speaker 1>I don't know, covert coercion to get your employees to

0:41:56.600 --> 0:41:58.400
<v Speaker 1>do what you want them to do, rather than just

0:41:58.480 --> 0:42:03.680
<v Speaker 1>being an active you know, an active boss without monitoring,

0:42:03.680 --> 0:42:08.040
<v Speaker 1>an active manager, without micromanaging. There's a you know, you

0:42:08.080 --> 0:42:10.920
<v Speaker 1>can do it. I I don't know if I don't

0:42:10.920 --> 0:42:12.680
<v Speaker 1>want to see it. I don't know. We run teams

0:42:12.719 --> 0:42:15.400
<v Speaker 1>here and and I don't know if we're good at

0:42:15.400 --> 0:42:17.600
<v Speaker 1>it or not. I I guess we have to get

0:42:17.600 --> 0:42:20.879
<v Speaker 1>feedback from our people. But it feels like you can

0:42:20.920 --> 0:42:24.280
<v Speaker 1>be hands on without being a micro manager and without

0:42:24.320 --> 0:42:30.680
<v Speaker 1>employing the most massive, intrusive micromanagement available, which is this

0:42:30.800 --> 0:42:35.319
<v Speaker 1>boss ware. Yeah, and the concerns are pretty self evident here.

0:42:36.000 --> 0:42:40.000
<v Speaker 1>Your job is conspiring, but they're not necessarily conspiring against you.

0:42:40.040 --> 0:42:43.280
<v Speaker 1>They're conspiring to make sure that you're focused. And most people,

0:42:43.600 --> 0:42:45.799
<v Speaker 1>if we're being honest are not about to risk their

0:42:45.840 --> 0:42:50.279
<v Speaker 1>livelihoods rocking the boat for privacy. You know what I mean. Like,

0:42:50.320 --> 0:42:54.920
<v Speaker 1>if you are not somehow being monitored yet, your odds

0:42:54.920 --> 0:42:58.279
<v Speaker 1>to be monitored in the future are incredibly high. And

0:42:58.360 --> 0:43:03.360
<v Speaker 1>that is because of is explosion of people working remotely

0:43:03.440 --> 0:43:06.960
<v Speaker 1>or working from home. Back in in fact, found this

0:43:07.120 --> 0:43:10.680
<v Speaker 1>survey by an off it called Gardner, and their survey

0:43:10.800 --> 0:43:17.520
<v Speaker 1>showed that of organizations across the planet are already using

0:43:18.160 --> 0:43:23.880
<v Speaker 1>some form of employee movement data, seventeen percent again across

0:43:23.920 --> 0:43:29.440
<v Speaker 1>the planet, we're already monitoring computer usage information and sixteen

0:43:29.560 --> 0:43:35.280
<v Speaker 1>percent we're monitoring activity on Microsoft Outlook or generic calendar usage.

0:43:35.560 --> 0:43:40.520
<v Speaker 1>That was pre pandemic. The numbers have skyrocketed since and

0:43:40.600 --> 0:43:45.799
<v Speaker 1>it's pretty difficult to find accurate numbers right now, just

0:43:45.840 --> 0:43:50.800
<v Speaker 1>because it all happened so quickly. Your employer can legally

0:43:50.880 --> 0:43:55.560
<v Speaker 1>monitor almost anything you do at work. They're like the

0:43:55.680 --> 0:43:59.000
<v Speaker 1>laws are written such that they they can't follow you

0:43:59.080 --> 0:44:01.919
<v Speaker 1>in the bathroom basically, but they know when you're going,

0:44:02.520 --> 0:44:05.120
<v Speaker 1>they know Norman, they know what you're doing, and really

0:44:05.960 --> 0:44:09.319
<v Speaker 1>it makes sense they can do this as long as

0:44:09.360 --> 0:44:13.320
<v Speaker 1>the reason for their monitoring. The rationale is important enough

0:44:13.680 --> 0:44:17.799
<v Speaker 1>to them. This is this goes into like reading mail.

0:44:17.920 --> 0:44:21.280
<v Speaker 1>You get snail mail that goes to a business. Uh,

0:44:21.400 --> 0:44:25.640
<v Speaker 1>for instance, our job. Our job has never like gone

0:44:25.640 --> 0:44:30.040
<v Speaker 1>through packages sent to us. But that's that's not because

0:44:30.080 --> 0:44:32.839
<v Speaker 1>they can't. It's because most of the people who work

0:44:32.880 --> 0:44:37.280
<v Speaker 1>with really cool and then also there frankly, they're probably

0:44:37.280 --> 0:44:40.360
<v Speaker 1>too busy. Yeah, we definitely Uh, I don't think anyone's

0:44:40.400 --> 0:44:43.239
<v Speaker 1>gone through that. I did notice one time we had

0:44:43.480 --> 0:44:47.960
<v Speaker 1>a letter, and actual snail mail letter that looked as

0:44:47.960 --> 0:44:50.799
<v Speaker 1>though it had been opened and then reclosed, you know,

0:44:50.960 --> 0:44:57.359
<v Speaker 1>using Steam. What that's flattering. It's a long time ago.

0:44:58.400 --> 0:45:01.280
<v Speaker 1>I cared enough. Wow, and they were just checking for anthrax.

0:45:01.320 --> 0:45:05.640
<v Speaker 1>I think, so, yeah, this this thing is real. It's

0:45:05.719 --> 0:45:09.680
<v Speaker 1>very real. I'd like to just quickly mentioned Ben. Right

0:45:09.719 --> 0:45:16.320
<v Speaker 1>before we started rolling, I texted our boss and asked

0:45:16.400 --> 0:45:21.160
<v Speaker 1>that person if there's any employee monitoring software installed in

0:45:21.200 --> 0:45:24.680
<v Speaker 1>our computers or if they use any kind of productivity analytics,

0:45:25.440 --> 0:45:29.920
<v Speaker 1>and this person said they were unaware of such software.

0:45:30.360 --> 0:45:34.040
<v Speaker 1>I was unable to locate anything physically running on my machine,

0:45:34.760 --> 0:45:39.399
<v Speaker 1>and that makes me feel pretty good about our situation. Yeah,

0:45:39.440 --> 0:45:43.920
<v Speaker 1>we're fortunate, especially when you consider how closely other people

0:45:44.160 --> 0:45:48.040
<v Speaker 1>are monitored to a degree it becomes tyrannical. You know,

0:45:48.520 --> 0:45:53.040
<v Speaker 1>uh this, of course, it's not necessarily sinister. Of course,

0:45:53.120 --> 0:45:56.280
<v Speaker 1>not all companies are the same. There are almost certainly

0:45:56.360 --> 0:46:00.640
<v Speaker 1>bad faith actors out there, right. It is completely possible,

0:46:00.719 --> 0:46:03.879
<v Speaker 1>I would even say plausible, that there's you know, a

0:46:03.880 --> 0:46:08.040
<v Speaker 1>creepy individual who might be using this to spy on

0:46:08.200 --> 0:46:12.720
<v Speaker 1>someone inappropriately. But that doesn't mean that the entire company

0:46:12.840 --> 0:46:16.080
<v Speaker 1>is doing right. But the problem there is that there

0:46:16.160 --> 0:46:20.680
<v Speaker 1>is no uniform process to address like data breaches, for instance,

0:46:21.000 --> 0:46:23.160
<v Speaker 1>and there's not really a lot of leeway on the

0:46:23.160 --> 0:46:29.160
<v Speaker 1>employees side to draw clear work home boundaries. The legislation

0:46:29.239 --> 0:46:32.319
<v Speaker 1>just isn't there yet. And until that stuff catches up,

0:46:32.719 --> 0:46:36.719
<v Speaker 1>it is seriously, I know it sounds a little stereotypical

0:46:36.760 --> 0:46:39.279
<v Speaker 1>to say this, It is seriously best to assume that

0:46:39.320 --> 0:46:43.400
<v Speaker 1>you are being observed whenever you are around work equipment.

0:46:45.000 --> 0:46:50.680
<v Speaker 1>Just just just know it, embrace it. And it's a

0:46:50.760 --> 0:46:56.520
<v Speaker 1>weird scenario mm hmm, yeah, but also it's it's strange.

0:46:56.560 --> 0:46:58.799
<v Speaker 1>One thing that really stuck out to me about a

0:46:58.800 --> 0:47:03.600
<v Speaker 1>lot of this criticism is that state level actors can

0:47:03.680 --> 0:47:05.759
<v Speaker 1>do a lot of the same stuff you know what

0:47:05.800 --> 0:47:08.560
<v Speaker 1>I mean. This is what we're seeing is a strategy

0:47:08.719 --> 0:47:13.720
<v Speaker 1>and a technique across the public private sphere. Don't do anything.

0:47:13.800 --> 0:47:17.280
<v Speaker 1>You're a camera if you don't want your boss, possibly

0:47:17.360 --> 0:47:20.719
<v Speaker 1>our n ESA in turn steve to see it. And

0:47:20.880 --> 0:47:23.880
<v Speaker 1>be careful with your personal devices to Like Matt, you

0:47:23.880 --> 0:47:26.319
<v Speaker 1>made the excellent point earlier. He said, Hey, maybe you

0:47:26.320 --> 0:47:28.040
<v Speaker 1>can listen at work, but don't listen on your on

0:47:28.080 --> 0:47:31.839
<v Speaker 1>your work device. Here's the thing, though, There's a question

0:47:31.920 --> 0:47:34.759
<v Speaker 1>I have for you. If say, for instance, you have

0:47:35.000 --> 0:47:40.960
<v Speaker 1>your own personal smartphone and you have installed work apps

0:47:41.320 --> 0:47:44.960
<v Speaker 1>on there of some sort, like a productivity thing or

0:47:45.000 --> 0:47:49.160
<v Speaker 1>an email app of some kind, how much access does

0:47:49.239 --> 0:47:51.799
<v Speaker 1>that give your employer to the other stuff on your

0:47:51.840 --> 0:47:59.040
<v Speaker 1>personal device. That's interesting Theoretically with something like Microsoft, they've

0:47:59.040 --> 0:48:04.759
<v Speaker 1>got Viva insights and monitoring that occurs with us, that

0:48:04.840 --> 0:48:09.560
<v Speaker 1>that happens to us, ben our Microsoft Outlook and our

0:48:09.640 --> 0:48:14.239
<v Speaker 1>calendar and all the other massive Microsoft three sweet can

0:48:14.280 --> 0:48:18.080
<v Speaker 1>be monitored if it's on your device. But that doesn't

0:48:18.239 --> 0:48:21.160
<v Speaker 1>mean that they can look at everything else that you

0:48:21.200 --> 0:48:23.399
<v Speaker 1>do on your phone. At least to my knowledge from

0:48:23.560 --> 0:48:27.080
<v Speaker 1>my understanding of reading several articles here, all kind of

0:48:27.120 --> 0:48:33.520
<v Speaker 1>associated with stuff life life hackers, security gladiators, Gizmoto. I

0:48:33.600 --> 0:48:35.320
<v Speaker 1>looked at a bunch of that stuff just to see

0:48:35.960 --> 0:48:39.880
<v Speaker 1>what can happen. But that does mean that certain activity

0:48:40.000 --> 0:48:44.799
<v Speaker 1>on your personal device is monitored, um in some way,

0:48:45.080 --> 0:48:49.000
<v Speaker 1>whether it's just by Microsoft and with Viva, it's just

0:48:49.040 --> 0:48:51.880
<v Speaker 1>giving you insights on your activity, and it's not sharing

0:48:51.920 --> 0:48:57.799
<v Speaker 1>that necessarily with your boss. But I don't know if

0:48:57.840 --> 0:49:00.759
<v Speaker 1>it can access your microphone or camera, and in that

0:49:01.080 --> 0:49:04.520
<v Speaker 1>in that case, you would have to give that system

0:49:04.560 --> 0:49:07.359
<v Speaker 1>like you'd have to give Microsoft teams access to your

0:49:07.480 --> 0:49:14.120
<v Speaker 1>camera and microphone. Oh shoot, which we all do right, yeah,

0:49:14.239 --> 0:49:16.600
<v Speaker 1>well said. And this is where we stand on the

0:49:16.640 --> 0:49:22.080
<v Speaker 1>precipice right of all the surveillance to come, it's important

0:49:22.080 --> 0:49:25.480
<v Speaker 1>to know that it's not just your employer doing it.

0:49:25.480 --> 0:49:30.040
<v Speaker 1>It's kind of like, obviously every country that can afford

0:49:30.080 --> 0:49:34.319
<v Speaker 1>spies is gonna hire spies because they work your job.

0:49:34.520 --> 0:49:38.239
<v Speaker 1>Isn't out to get you, quote unquote, but they do

0:49:38.440 --> 0:49:42.080
<v Speaker 1>want to have as much visibility as possible, and they've

0:49:42.160 --> 0:49:45.520
<v Speaker 1>kind of I think the pendulum swung. And what's happened

0:49:45.560 --> 0:49:48.160
<v Speaker 1>is that because so many people are working from home,

0:49:48.280 --> 0:49:51.560
<v Speaker 1>and because so many leaders in a given company or

0:49:51.680 --> 0:49:55.239
<v Speaker 1>organization want to be able to show that they produce results.

0:49:55.719 --> 0:49:59.120
<v Speaker 1>They're clamping down and they're they're trying to learn as

0:49:59.239 --> 0:50:03.319
<v Speaker 1>much about what their employees are doing as possible. That

0:50:03.440 --> 0:50:08.040
<v Speaker 1>itself is not necessarily a bad thing. The problem is

0:50:08.440 --> 0:50:14.080
<v Speaker 1>that the line between your expectations, your completely reasonable expectations

0:50:14.080 --> 0:50:18.640
<v Speaker 1>of privacy, and the desires of an employer, that line

0:50:18.719 --> 0:50:22.440
<v Speaker 1>is really fuzzy, and it's align that's easy to step on.

0:50:22.600 --> 0:50:25.239
<v Speaker 1>It's a line that's easy to cross, and it's very

0:50:25.239 --> 0:50:29.480
<v Speaker 1>difficult to pull things back once you've gone over that threshold.

0:50:29.960 --> 0:50:32.719
<v Speaker 1>So be safe out there, folks. Can't wait to hear

0:50:33.040 --> 0:50:38.279
<v Speaker 1>your war stories about odd surveillance monitoring. I can't. You know,

0:50:38.360 --> 0:50:41.920
<v Speaker 1>these are kind of episodes that UH sometimes lead like

0:50:42.040 --> 0:50:45.240
<v Speaker 1>I t experts to write to us with tips and tricks,

0:50:45.280 --> 0:50:47.759
<v Speaker 1>and I love that. So shout out to our pal

0:50:47.880 --> 0:50:52.279
<v Speaker 1>James if you're listening that. Uh. I always enjoyed those conversations.

0:50:52.840 --> 0:50:55.000
<v Speaker 1>But yeah, give us tips and tricks that we can

0:50:55.040 --> 0:50:58.520
<v Speaker 1>share with your fellow listeners about how to how to

0:50:58.640 --> 0:51:01.800
<v Speaker 1>maintain that boundary as best as you can to be safe,

0:51:02.000 --> 0:51:05.200
<v Speaker 1>you know, Yeah, no matter what you're doing or what's

0:51:05.280 --> 0:51:09.080
<v Speaker 1>what you think might be monitoring. Just remember that Cortana

0:51:09.160 --> 0:51:13.719
<v Speaker 1>and Alexa and your Google Home and your phone can

0:51:13.760 --> 0:51:16.239
<v Speaker 1>always hear you because it's always listening for you to

0:51:16.280 --> 0:51:24.120
<v Speaker 1>wake it up, so it doesn't really matter. That's very inspiring, yep,

0:51:24.800 --> 0:51:28.480
<v Speaker 1>very inspiring. Mr Frederick uh We we want to hear

0:51:28.520 --> 0:51:30.719
<v Speaker 1>from you. What do you think the future of workplace

0:51:30.760 --> 0:51:33.920
<v Speaker 1>surveillance is? Let us know. We try to be easy

0:51:33.960 --> 0:51:36.560
<v Speaker 1>to find online. You can find us on Facebook and

0:51:36.600 --> 0:51:40.920
<v Speaker 1>Twitter and YouTube at Conspiracy Stuff on Instagram. We are

0:51:40.960 --> 0:51:43.719
<v Speaker 1>a Conspiracy Stuff show. If you don't want to use

0:51:43.760 --> 0:51:47.160
<v Speaker 1>social media, you can instead use your phone and your

0:51:47.239 --> 0:51:51.200
<v Speaker 1>mouth to contact us via voice. Our number is one

0:51:51.280 --> 0:51:54.759
<v Speaker 1>eight three three st d w y t K. Yes,

0:51:54.800 --> 0:51:58.920
<v Speaker 1>you'll have three minutes. Those three minutes are yours. Go nuts,

0:51:59.760 --> 0:52:03.480
<v Speaker 1>give weird with it, give yourself a cool nickname. Let

0:52:03.560 --> 0:52:05.600
<v Speaker 1>us know if we can use your name and door

0:52:05.760 --> 0:52:08.960
<v Speaker 1>voice on the air, and most importantly, when you call

0:52:09.040 --> 0:52:11.879
<v Speaker 1>one three three st d w y t K, I'd

0:52:11.920 --> 0:52:14.359
<v Speaker 1>just like to say it um when you call. Don't

0:52:14.400 --> 0:52:16.719
<v Speaker 1>feel like you have to censor yourself. If you have

0:52:16.840 --> 0:52:20.839
<v Speaker 1>a tail that needs more than three minutes, just write

0:52:20.880 --> 0:52:24.120
<v Speaker 1>us an email. Attached the links give us some leads

0:52:24.360 --> 0:52:26.600
<v Speaker 1>on websites to start digging into, and you will have

0:52:26.680 --> 0:52:29.560
<v Speaker 1>made our day. We read every single email week get

0:52:29.760 --> 0:52:31.360
<v Speaker 1>All you have to do is drop us a line

0:52:31.440 --> 0:52:53.719
<v Speaker 1>where we are conspiracy at i heart radio dot com.

0:52:53.880 --> 0:52:55.960
<v Speaker 1>Stuff they don't want you to know is a production

0:52:56.000 --> 0:52:59.080
<v Speaker 1>of I heart Radio. For more podcasts from my heart Radio,

0:52:59.239 --> 0:53:02.120
<v Speaker 1>visit the i heart radio app, Apple Podcasts, or wherever

0:53:02.160 --> 0:53:03.480
<v Speaker 1>you listen to your favorite shows.