WEBVTT

1
00:00:00.040 --> 00:00:02.799
<v Speaker 1>Everyone thinks Copilot Memory is just Microsoft's sneaky way of

2
00:00:02.799 --> 00:00:05.559
<v Speaker 1>spying on you. Wrong. If it was secretly snooping, you

3
00:00:05.559 --> 00:00:07.919
<v Speaker 1>wouldn't see that little memory updated badge every time you

4
00:00:07.919 --> 00:00:10.919
<v Speaker 1>give it an instruction. The reality memory stores facts only

5
00:00:10.960 --> 00:00:13.320
<v Speaker 1>when there's clear intent, like when you ask it to

6
00:00:13.359 --> 00:00:16.359
<v Speaker 1>remember your tone preference or a project label. And yes,

7
00:00:16.440 --> 00:00:18.719
<v Speaker 1>you can review or delete those entries at will. The

8
00:00:18.760 --> 00:00:21.359
<v Speaker 1>real privacy risk isn't hidden recording. It's assuming the two

9
00:00:21.440 --> 00:00:25.000
<v Speaker 1>logs everything automatically spoiler it doesn't subscribe. Now this feed

10
00:00:25.000 --> 00:00:28.000
<v Speaker 1>hands you Microsoft clarity on schedule, unlike your inbox, and

11
00:00:28.079 --> 00:00:30.879
<v Speaker 1>here's the payoff. We'll unpack what memory actually keeps, how

12
00:00:30.920 --> 00:00:33.280
<v Speaker 1>you can check it, and how admins can control it,

13
00:00:33.320 --> 00:00:36.200
<v Speaker 1>because before comparing it with recalls screenshots, you need to

14
00:00:36.280 --> 00:00:39.399
<v Speaker 1>understand what this memory even is and what it isn't.

15
00:00:39.840 --> 00:00:43.320
<v Speaker 1>What memory actually is and isn't. People love to assume

16
00:00:43.359 --> 00:00:46.799
<v Speaker 1>Copilot Memory is some all seeing diary, logging every keystroke,

17
00:00:46.920 --> 00:00:50.399
<v Speaker 1>private thought and petty lunch choice. Wrong. That paranoid fantasy

18
00:00:50.600 --> 00:00:53.479
<v Speaker 1>belongs in a pulp spy novel, not Microsoft three sixty five.

19
00:00:53.600 --> 00:00:56.439
<v Speaker 1>Memory doesn't run in the background collecting everything. It only persists.

20
00:00:56.600 --> 00:00:58.880
<v Speaker 1>When you create a clear intent to remember through an

21
00:00:58.880 --> 00:01:02.880
<v Speaker 1>explicit instruction or a clar signaled preference think less surveillance system,

22
00:01:02.880 --> 00:01:05.359
<v Speaker 1>more notepad, you have to hand to your assistant with

23
00:01:05.480 --> 00:01:08.439
<v Speaker 1>the words write this down. If you don't, nothing sticks.

24
00:01:08.480 --> 00:01:11.200
<v Speaker 1>So what does intend to remember actually look like? Two

25
00:01:11.200 --> 00:01:13.560
<v Speaker 1>simple moves. First, you add a memory by spelling it out.

26
00:01:13.760 --> 00:01:16.519
<v Speaker 1>Remember I prefer my summaries under one hundred words. Then

27
00:01:16.760 --> 00:01:19.840
<v Speaker 1>remember that I like gardening examples. And remember I favor

28
00:01:19.840 --> 00:01:22.200
<v Speaker 1>bullet points in my slide decks. When when you do that,

29
00:01:22.239 --> 00:01:24.840
<v Speaker 1>copilot logs it and flashes the little memory updated badge

30
00:01:24.840 --> 00:01:27.920
<v Speaker 1>on screen. No guessing, no mind reading. Second, you manage

31
00:01:27.959 --> 00:01:30.799
<v Speaker 1>those memories anytime. You can ask it directly, but what

32
00:01:30.840 --> 00:01:33.680
<v Speaker 1>do you know about me? And it will summarize current entries.

33
00:01:33.760 --> 00:01:35.959
<v Speaker 1>And if you want to delete one thing, you literally

34
00:01:36.000 --> 00:01:39.239
<v Speaker 1>tell it forget that I like gardening, or if you

35
00:01:39.280 --> 00:01:41.599
<v Speaker 1>tire of the whole concept, you toggle memory off in

36
00:01:41.640 --> 00:01:44.799
<v Speaker 1>your settings. That's all. Add memories, manually check them through

37
00:01:44.799 --> 00:01:47.480
<v Speaker 1>a single question, edit or delete with a single instruction.

38
00:01:47.760 --> 00:01:51.439
<v Speaker 1>Control rests with you. Compare that with actual background data collection,

39
00:01:51.560 --> 00:01:54.359
<v Speaker 1>where you have no idea what's being siphoned and no

40
00:01:54.439 --> 00:01:56.959
<v Speaker 1>clear way to hit the brakes. Now before the tinfoil

41
00:01:57.000 --> 00:02:00.840
<v Speaker 1>had spin. One clarification, Microsoft deliberately disign limits on what

42
00:02:00.920 --> 00:02:04.760
<v Speaker 1>Copilot will remember. It ignores sensitive categories age, ethnicity, health conditions,

43
00:02:04.799 --> 00:02:07.400
<v Speaker 1>political views, sexual orientation. Even if you try to force

44
00:02:07.439 --> 00:02:10.280
<v Speaker 1>feed at such details, it won't personalize around them. So no,

45
00:02:10.360 --> 00:02:13.400
<v Speaker 1>it's not quietly sketching your voter profile or medical chart.

46
00:02:13.520 --> 00:02:16.199
<v Speaker 1>The system is built to filter out those lanes entirely.

47
00:02:16.319 --> 00:02:19.159
<v Speaker 1>Here's another vital distinction. Memory doesn't behave like a sponge,

48
00:02:19.199 --> 00:02:22.719
<v Speaker 1>soaking up every spilled word. Ordinary conversation prompts write code

49
00:02:22.719 --> 00:02:25.479
<v Speaker 1>for a clustering algorithm do not get remembered. But if

50
00:02:25.520 --> 00:02:28.000
<v Speaker 1>you say always assume I prefer Python for analysis, that's

51
00:02:28.039 --> 00:02:31.319
<v Speaker 1>a declared intent and it sticks. Memory stores the self declared,

52
00:02:31.360 --> 00:02:33.520
<v Speaker 1>not the incidental. But that's why calling it a profile

53
00:02:33.560 --> 00:02:37.039
<v Speaker 1>is misleading. Microsoft isn't building it behind your back. You're

54
00:02:37.039 --> 00:02:39.080
<v Speaker 1>constructing it one brick at a time through what you

55
00:02:39.199 --> 00:02:42.159
<v Speaker 1>choose to share, a cleaner analogy than all the spy novels.

56
00:02:42.159 --> 00:02:44.840
<v Speaker 1>It's a digital sticky note you tape where Copilot can

57
00:02:44.879 --> 00:02:48.000
<v Speaker 1>see it. Those notes stay pinned across outlook word Excel

58
00:02:48.039 --> 00:02:51.319
<v Speaker 1>PowerPoint until you pull them off. Copilot never adds its

59
00:02:51.360 --> 00:02:53.759
<v Speaker 1>own hidden notes behind your monitor. It only reads the

60
00:02:53.759 --> 00:02:55.960
<v Speaker 1>ones you've taped up yourself, and when you add another,

61
00:02:56.240 --> 00:02:59.199
<v Speaker 1>it politely announces it with that memory updated badge. That's

62
00:02:59.240 --> 00:03:02.280
<v Speaker 1>not decoration, it's a required signal that something has changed.

63
00:03:02.639 --> 00:03:05.639
<v Speaker 1>And yes, despite these guardrails, people still insist on confusing

64
00:03:05.639 --> 00:03:08.360
<v Speaker 1>memory with some kind of background archive, probably because in

65
00:03:08.400 --> 00:03:12.199
<v Speaker 1>tech memory triggers the same fear circuits as cookies, something

66
00:03:12.240 --> 00:03:15.680
<v Speaker 1>smuggled in quietly, something you assume is building an invisible portrait.

67
00:03:15.759 --> 00:03:19.599
<v Speaker 1>But here silence equals forgetting, no declaration, no persistence. It's

68
00:03:19.719 --> 00:03:23.479
<v Speaker 1>arguably less invasive than most websites tracking you automatically. The

69
00:03:23.520 --> 00:03:26.479
<v Speaker 1>only real danger is conceptual mixing up memory with the

70
00:03:26.599 --> 00:03:30.039
<v Speaker 1>entirely different feature called recall. Memory is curated and intentional

71
00:03:30.120 --> 00:03:32.960
<v Speaker 1>recall is automated and constant. One is like asking a

72
00:03:33.000 --> 00:03:35.199
<v Speaker 1>colleague to jot down a note you hand them. The

73
00:03:35.240 --> 00:03:37.479
<v Speaker 1>other is like that same colleague snapping pictures of your

74
00:03:37.639 --> 00:03:40.599
<v Speaker 1>entire desk every minute, and understanding that gap is what

75
00:03:40.680 --> 00:03:42.879
<v Speaker 1>actually matters, because if you're worried about the feeling of

76
00:03:42.919 --> 00:03:46.840
<v Speaker 1>being watched, the next feature is the culprit, not this one. Recall,

77
00:03:47.039 --> 00:03:50.199
<v Speaker 1>the automatic screenshot order. Recall, by design, behaves in a

78
00:03:50.240 --> 00:03:53.479
<v Speaker 1>way that unsettles people. It captures your screen activity automatically,

79
00:03:53.800 --> 00:03:56.759
<v Speaker 1>as if your computer suddenly decided it was a compulsive archivist,

80
00:03:57.159 --> 00:03:59.960
<v Speaker 1>not a polite Shall I remember this prompt just silence,

81
00:04:00.039 --> 00:04:03.719
<v Speaker 1>steady collection. This is an optional flare for every Windows machine. Either.

82
00:04:04.159 --> 00:04:07.000
<v Speaker 1>Recall is exclusive to Copilot plus PCs, and it builds

83
00:04:07.000 --> 00:04:09.719
<v Speaker 1>its archive by taking regular encrypted snapshots of what's on

84
00:04:09.759 --> 00:04:12.879
<v Speaker 1>your display. Those snapshots live locally, locked away with encryption,

85
00:04:13.319 --> 00:04:16.839
<v Speaker 1>but the method itself screens captured without you authorizing each one,

86
00:04:17.160 --> 00:04:20.120
<v Speaker 1>feels alien compared to the explicit control you get with memory.

87
00:04:20.439 --> 00:04:23.040
<v Speaker 1>And yes, the engineers will happily remind you encryption local

88
00:04:23.079 --> 00:04:26.560
<v Speaker 1>storage private by design. True, but reassurance doesn't erase the

89
00:04:26.600 --> 00:04:28.800
<v Speaker 1>mental image your PC clicking away like a camera you

90
00:04:28.839 --> 00:04:31.399
<v Speaker 1>never picked up, harvesting slices of your workflow into a

91
00:04:31.439 --> 00:04:37.040
<v Speaker 1>timestamped album. Comfort doesn't automatically come bundled with accuracy, even

92
00:04:37.040 --> 00:04:39.319
<v Speaker 1>if no one else sees it. You can't quite shake

93
00:04:39.360 --> 00:04:41.839
<v Speaker 1>the sense that your machine is quietly following you around,

94
00:04:41.959 --> 00:04:45.560
<v Speaker 1>documenting everything from emails half drafted to images opened for

95
00:04:45.600 --> 00:04:48.160
<v Speaker 1>a split second. Picture your desk for a moment. You

96
00:04:48.240 --> 00:04:51.279
<v Speaker 1>lay down a contract, scribblesome notes, sip your coffee. Imagine

97
00:04:51.279 --> 00:04:54.800
<v Speaker 1>someone walking past at intervals, no announcement, no permission requested,

98
00:04:54.879 --> 00:04:57.439
<v Speaker 1>snapping a photo of whatever happens to be there. They

99
00:04:57.480 --> 00:05:02.160
<v Speaker 1>file each picture chronologically in a cabinet, nobody else touched. Secure, yes, harmless,

100
00:05:02.319 --> 00:05:05.959
<v Speaker 1>not exactly. The sheer fact those photos exist induces the

101
00:05:06.040 --> 00:05:09.240
<v Speaker 1>unease that's recall in a nutshell, local storage, encrypted but

102
00:05:09.319 --> 00:05:12.160
<v Speaker 1>recorded constantly without waiting for you to decide. Now, Scale

103
00:05:12.160 --> 00:05:14.120
<v Speaker 1>that desk up to an enterprise floor plan, and you

104
00:05:14.120 --> 00:05:17.879
<v Speaker 1>can see where administrators start sweating. Screens include payroll spreadsheets,

105
00:05:17.959 --> 00:05:22.720
<v Speaker 1>unreleased financial figures, confidential medical documents, sensitive legal drafts. Those fragments,

106
00:05:22.800 --> 00:05:26.600
<v Speaker 1>once locked inside recalls encrypted album still count as captured material.

107
00:05:26.800 --> 00:05:29.120
<v Speaker 1>Governance officers now face a fresh headache. Instead of just

108
00:05:29.160 --> 00:05:31.519
<v Speaker 1>managing documents and chatlocks, they need to consider that an

109
00:05:31.519 --> 00:05:35.319
<v Speaker 1>employees' PC is stockpiling screenshots, and unlike memory, this isn't

110
00:05:35.360 --> 00:05:39.839
<v Speaker 1>carefully curated user instruction, it's automatic data collection. That distinction

111
00:05:39.959 --> 00:05:44.120
<v Speaker 1>forces enterprises to weigh recall separately during compliance and risk assessments.

112
00:05:44.360 --> 00:05:47.319
<v Speaker 1>Pretending recall is just another note taking feature is a

113
00:05:47.360 --> 00:05:51.279
<v Speaker 1>shortcut to compliance failure. Of course, Microsoft emphasizes the design

114
00:05:51.360 --> 00:05:54.839
<v Speaker 1>choices to mitigate this. The data never leaves the device

115
00:05:54.879 --> 00:05:57.839
<v Speaker 1>by default. There is no cloud sync, no hidden server cache.

116
00:05:58.199 --> 00:06:01.120
<v Speaker 1>IT tools exist to set policy these audits and retention

117
00:06:01.199 --> 00:06:04.600
<v Speaker 1>limits on paper, the architecture is solid in practice. Employees

118
00:06:04.600 --> 00:06:07.480
<v Speaker 1>don't like seeing the phrase your PC takes screenshots all day.

119
00:06:07.759 --> 00:06:10.240
<v Speaker 1>The human reaction can't be engineered away with a bullet

120
00:06:10.240 --> 00:06:13.800
<v Speaker 1>point about encryption. And that's the real divide. Technically defensible,

121
00:06:13.959 --> 00:06:17.600
<v Speaker 1>psychologically unnerving. Compare that to memories model. With memory, you

122
00:06:17.720 --> 00:06:21.920
<v Speaker 1>consciously deposit knowledge, Remember my preferred format, or remember I

123
00:06:22.079 --> 00:06:25.720
<v Speaker 1>like concise text in nothing written down, nothing stored with recall.

124
00:06:25.759 --> 00:06:28.079
<v Speaker 1>The archivist doesn't wait. It snaps a record of your

125
00:06:28.120 --> 00:06:30.600
<v Speaker 1>Excel workbook, even if you only glanced at it. The

126
00:06:30.639 --> 00:06:33.879
<v Speaker 1>fundamental difference isn't encryption or storage. It's the consent model.

127
00:06:34.000 --> 00:06:37.600
<v Speaker 1>One empowers you to curate, the other defaults to indiscriminate archiving.

128
00:06:37.720 --> 00:06:41.720
<v Speaker 1>Unless explicitly governed. The psychological weight shouldn't be underestimated. People

129
00:06:41.800 --> 00:06:44.720
<v Speaker 1>tolerate a sticky note they wrote themselves. They bristle when

130
00:06:44.759 --> 00:06:47.360
<v Speaker 1>they learn an assistant has been recording each glance, however,

131
00:06:47.399 --> 00:06:51.160
<v Speaker 1>privately secured. That discrepancy explains why recall spark so much doubt.

132
00:06:51.240 --> 00:06:55.680
<v Speaker 1>Despite the technical safeguards, memory feels intentional. Recall feels ghostly,

133
00:06:55.959 --> 00:06:58.839
<v Speaker 1>like a shadow presence stockpiling your day into a chronological

134
00:06:58.879 --> 00:07:02.120
<v Speaker 1>museum exhibit. This is where the confusion intensifies, because not

135
00:07:02.199 --> 00:07:05.720
<v Speaker 1>every feature in this copilot ecosystem behaves like recall or memory.

136
00:07:05.879 --> 00:07:08.519
<v Speaker 1>Some aren't built to retain at all. There are temporary lenses,

137
00:07:08.560 --> 00:07:11.199
<v Speaker 1>disposable once the session ends, which brings us to the

138
00:07:11.199 --> 00:07:15.639
<v Speaker 1>one that people consistently Mislabelsi vision. The real time mirage.

139
00:07:15.839 --> 00:07:19.040
<v Speaker 1>Vision isn't about hoarding, logging, or filing anything away. It's

140
00:07:19.079 --> 00:07:21.639
<v Speaker 1>the feature built specifically to vanish the moment you stop

141
00:07:21.720 --> 00:07:25.560
<v Speaker 1>using it. Unlike recalls, endless snapshots or memories curated facts,

142
00:07:25.759 --> 00:07:28.959
<v Speaker 1>Vision is engineered as a real time interpreter, available only

143
00:07:28.959 --> 00:07:31.040
<v Speaker 1>when you summon it gone the instant you walk away.

144
00:07:31.120 --> 00:07:33.199
<v Speaker 1>It doesn't keep a secret library of screenshots waiting to

145
00:07:33.199 --> 00:07:37.040
<v Speaker 1>betray you later. Its design is session only, initiated by

146
00:07:37.079 --> 00:07:39.839
<v Speaker 1>you when you click the little glasses icon, and when

147
00:07:39.839 --> 00:07:43.759
<v Speaker 1>that session closes, images and context are erased. One clarification though.

148
00:07:44.040 --> 00:07:48.079
<v Speaker 1>While Vision doesn't retain photos or video, the text transcript

149
00:07:48.079 --> 00:07:50.680
<v Speaker 1>of your interaction can remain in your chat history, something

150
00:07:50.720 --> 00:07:54.000
<v Speaker 1>you control and can delete at any time. So what

151
00:07:54.120 --> 00:07:56.680
<v Speaker 1>actually happens when you engage Vision? You point your screen

152
00:07:56.800 --> 00:07:59.079
<v Speaker 1>or camera at something and open document, a messy slide,

153
00:07:59.120 --> 00:08:01.560
<v Speaker 1>even a live feed from your phone. Vision analyzes the

154
00:08:01.600 --> 00:08:04.360
<v Speaker 1>input in real time and returns context or suggestions right

155
00:08:04.399 --> 00:08:06.600
<v Speaker 1>there in the chat. That's it. No COVID recording, no

156
00:08:06.680 --> 00:08:09.879
<v Speaker 1>uploading to hidden servers. The images and audio vanish after

157
00:08:09.920 --> 00:08:13.160
<v Speaker 1>the session ends, leaving only the text conversation behind. Think

158
00:08:13.160 --> 00:08:16.000
<v Speaker 1>of it less like an endless chain of CCTV cameras

159
00:08:16.000 --> 00:08:18.439
<v Speaker 1>and more like one of those conference interpreters who only

160
00:08:18.519 --> 00:08:21.079
<v Speaker 1>assists while the meeting is happening. They whisper to you

161
00:08:21.120 --> 00:08:25.279
<v Speaker 1>in real time, useful, precise, immediate, but afterwards they don't

162
00:08:25.279 --> 00:08:28.279
<v Speaker 1>produce a diary of the meetings every word. The only

163
00:08:28.319 --> 00:08:30.959
<v Speaker 1>trace might be the official meeting notes you requested, which,

164
00:08:30.959 --> 00:08:33.639
<v Speaker 1>in Vision's case, is the text stored in chat history

165
00:08:33.639 --> 00:08:37.120
<v Speaker 1>and deletable on your command. The ridiculous misunderstanding comes from

166
00:08:37.200 --> 00:08:39.679
<v Speaker 1>people who hear the word camera and immediately imagine they're

167
00:08:39.720 --> 00:08:43.240
<v Speaker 1>cast in a surveillance thriller. No, vision isn't stockpiling images

168
00:08:43.279 --> 00:08:47.000
<v Speaker 1>in some distant Microsoft vault. Microsoft makes the opposite point unmistakable.

169
00:08:47.200 --> 00:08:50.879
<v Speaker 1>Vision processes context locally deletes visuals when the session ends,

170
00:08:50.879 --> 00:08:53.919
<v Speaker 1>and only your text exchanges continue on. If that boundary

171
00:08:53.919 --> 00:08:57.279
<v Speaker 1>sounds obvious to you, congratulations. You're operating one level above

172
00:08:57.320 --> 00:08:59.679
<v Speaker 1>the average user, who still panics at the mention of

173
00:08:59.679 --> 00:09:02.679
<v Speaker 1>system and permissions. It's worth stressing how opt in this

174
00:09:02.759 --> 00:09:05.360
<v Speaker 1>whole construct is. The vision doesn't lurk in the background

175
00:09:05.440 --> 00:09:07.720
<v Speaker 1>waiting for your screen to light up before secretly recording.

176
00:09:07.879 --> 00:09:10.879
<v Speaker 1>It only activates inside a defined session when you click

177
00:09:10.919 --> 00:09:14.120
<v Speaker 1>the glass's icon in the copilot composer or explicitly allowed

178
00:09:14.159 --> 00:09:17.000
<v Speaker 1>in edge or window settings, close the window, toggle it off,

179
00:09:17.080 --> 00:09:20.279
<v Speaker 1>or simply lapse into inactivity, and the session terminates automatically.

180
00:09:20.399 --> 00:09:23.120
<v Speaker 1>To restart vision, you must manually initiate it again. This

181
00:09:23.240 --> 00:09:25.919
<v Speaker 1>is not always on. It's opt in by design. Revisit

182
00:09:25.960 --> 00:09:28.799
<v Speaker 1>the interpreter analogy with this nuance in mind. Imagine asking

183
00:09:28.799 --> 00:09:31.080
<v Speaker 1>a translator to attend a meeting. They step in when

184
00:09:31.120 --> 00:09:33.200
<v Speaker 1>you start, they leave when you end. During the session,

185
00:09:33.240 --> 00:09:36.840
<v Speaker 1>they help you understand what's being discussed live translation, no memorization,

186
00:09:37.360 --> 00:09:39.799
<v Speaker 1>but maybe the moderator also writes a brief summary of

187
00:09:39.840 --> 00:09:42.600
<v Speaker 1>the exchange in the meeting notes. That's what Vision does.

188
00:09:42.679 --> 00:09:45.919
<v Speaker 1>Images and audio vanish, but a text transcript might stay

189
00:09:45.960 --> 00:09:48.200
<v Speaker 1>around until you choose to delete it. If you want

190
00:09:48.200 --> 00:09:50.799
<v Speaker 1>no record whatsoever, you remove the notes, the chat history,

191
00:09:51.240 --> 00:09:53.200
<v Speaker 1>and it's as if the session never happened at all.

192
00:09:53.519 --> 00:09:56.799
<v Speaker 1>Now compare that with memories, persistence and recalls archiving. Vision

193
00:09:56.799 --> 00:10:00.759
<v Speaker 1>doesn't build profiles, doesn't accumulate screenshots, doesn't create comp clients headaches.

194
00:10:01.080 --> 00:10:04.279
<v Speaker 1>It's transient muscle, powerful in the exact moment it's needed,

195
00:10:04.559 --> 00:10:07.639
<v Speaker 1>useless and gone right after. Even the one fragment that remains,

196
00:10:07.720 --> 00:10:11.279
<v Speaker 1>the chat transcript is easy to erase. Unlike recalls, cabinet

197
00:10:11.279 --> 00:10:15.080
<v Speaker 1>of snapshots, or memories preference entries, there are no hidden galleries,

198
00:10:15.080 --> 00:10:19.320
<v Speaker 1>no secret indexes silently following you. Vision is designed for ephemorality,

199
00:10:19.679 --> 00:10:22.120
<v Speaker 1>and that makes it an entirely different class of feature.

200
00:10:22.279 --> 00:10:25.080
<v Speaker 1>This is where nuance matters. Saying Vision is the least

201
00:10:25.159 --> 00:10:28.360
<v Speaker 1>capable of spying is too generous a simplification. More accurately,

202
00:10:28.440 --> 00:10:30.919
<v Speaker 1>Vision is engineered to be ephemeral when it comes to images,

203
00:10:30.960 --> 00:10:34.200
<v Speaker 1>and audio. But the text transcript may persist unless you

204
00:10:34.240 --> 00:10:37.559
<v Speaker 1>delete it yourself. That's not surveillance. It's traceable conversation history

205
00:10:37.639 --> 00:10:40.639
<v Speaker 1>under your control. If you're looking for compliance nightmares, vision

206
00:10:40.679 --> 00:10:43.519
<v Speaker 1>doesn't even make the shortlist, And this practical distinction is

207
00:10:43.519 --> 00:10:48.120
<v Speaker 1>why Vision shouldn't cause enterprises sleepless nights. Sensitivity lives in

208
00:10:48.159 --> 00:10:51.720
<v Speaker 1>persistent data, documents, timelines, records. Vision skips all of those.

209
00:10:51.799 --> 00:10:54.120
<v Speaker 1>What you get instead is a disposable opt in feature

210
00:10:54.159 --> 00:10:57.120
<v Speaker 1>that lets workers analyze demo, brainstorm, and move on without

211
00:10:57.200 --> 00:10:59.480
<v Speaker 1>leaving behind a digital mindfield. Yes, you may need to

212
00:10:59.480 --> 00:11:02.840
<v Speaker 1>remind people that transcripts exist, but that's a simple user habit,

213
00:11:02.919 --> 00:11:05.519
<v Speaker 1>not a governance overhaul. Vision is the ghost that lingers

214
00:11:05.559 --> 00:11:08.759
<v Speaker 1>only long enough to be useful. Understanding those differences is

215
00:11:08.799 --> 00:11:11.840
<v Speaker 1>critical because when you shift back to memory, the picture changes.

216
00:11:11.960 --> 00:11:14.960
<v Speaker 1>Memory doesn't vanish when you close a session. It introduces

217
00:11:15.080 --> 00:11:20.320
<v Speaker 1>visible controls, signals, toggles, mechanisms you and administrators must deliberately manage,

218
00:11:20.399 --> 00:11:23.200
<v Speaker 1>and that management is the point, because privacy here isn't

219
00:11:23.279 --> 00:11:27.240
<v Speaker 1>left to blind trust. The Privacy Power User Toolkit enter

220
00:11:27.240 --> 00:11:30.320
<v Speaker 1>the Privacy Power User Toolkit, the set of levers Microsoft

221
00:11:30.360 --> 00:11:33.000
<v Speaker 1>built so no one mistakes Copilot memory for a background

222
00:11:33.080 --> 00:11:35.279
<v Speaker 1>key logger. These are the actual controls, the ones you

223
00:11:35.279 --> 00:11:37.639
<v Speaker 1>should be using, and yes they are sitting exactly where

224
00:11:37.639 --> 00:11:39.759
<v Speaker 1>you would expect if you bother to look. Step one

225
00:11:39.799 --> 00:11:43.120
<v Speaker 1>the on off switch in Copilot. Go to Settings, then Account,

226
00:11:43.279 --> 00:11:47.399
<v Speaker 1>then Privacy, then personalization and memory. Say it slowly if

227
00:11:47.399 --> 00:11:51.320
<v Speaker 1>you must, Settings, Account, Privacy, Personalization, and memory. That's the

228
00:11:51.360 --> 00:11:54.120
<v Speaker 1>master toggle. Until you flip it on, Copilot is basically

229
00:11:54.200 --> 00:11:57.159
<v Speaker 1>running with short term amnesia. Flip it on, and suddenly

230
00:11:57.200 --> 00:11:59.519
<v Speaker 1>it can remember facts you feed it intentionally. No half

231
00:11:59.519 --> 00:12:02.240
<v Speaker 1>shadows are either disabled or explicitly active. Now suppose you

232
00:12:02.279 --> 00:12:05.480
<v Speaker 1>actually enable it. Microsoft knew that average users tremble at

233
00:12:05.480 --> 00:12:08.320
<v Speaker 1>invisible change, so they added a hyper obvious signal, the

234
00:12:08.399 --> 00:12:11.480
<v Speaker 1>memory updated badge. Every time you teach Copilot something new,

235
00:12:11.519 --> 00:12:14.799
<v Speaker 1>that little tag pops up, like a bureaucrat interrupting your day.

236
00:12:14.960 --> 00:12:17.799
<v Speaker 1>Noted and filed. You can ignore it, but you cannot

237
00:12:17.840 --> 00:12:20.679
<v Speaker 1>claim you weren't told. But here's where practical control enters

238
00:12:20.679 --> 00:12:23.279
<v Speaker 1>the picture. You're not expected to guess what's stored, Just

239
00:12:23.360 --> 00:12:26.360
<v Speaker 1>ask what do you know about me? Copilot will recite

240
00:12:26.360 --> 00:12:29.120
<v Speaker 1>its current memory like a personal assistant, rattling off your

241
00:12:29.120 --> 00:12:31.519
<v Speaker 1>standing orders. Don't like one of them, tell it directly.

242
00:12:31.720 --> 00:12:34.360
<v Speaker 1>Forget that I like bullet points, or forget the gardening examples,

243
00:12:34.360 --> 00:12:36.399
<v Speaker 1>but you want to empty the entire draw order a

244
00:12:36.399 --> 00:12:39.480
<v Speaker 1>full wipe and it forgets everything in one go. Average

245
00:12:39.519 --> 00:12:42.200
<v Speaker 1>software hides this one literally takes dictation from you. And

246
00:12:42.240 --> 00:12:44.720
<v Speaker 1>for the skeptics obsessing about training data, yes, you can

247
00:12:44.759 --> 00:12:47.320
<v Speaker 1>opt out. Flip a switch, and your conversations won't get

248
00:12:47.399 --> 00:12:50.360
<v Speaker 1>used for model training, even while your personal memory still works.

249
00:12:50.440 --> 00:12:54.559
<v Speaker 1>That's the obvious paranoia. Valve answered directly. Your preferences personalize

250
00:12:54.559 --> 00:12:58.039
<v Speaker 1>your copilot. They don't automatically improve the global model unless

251
00:12:58.039 --> 00:13:00.879
<v Speaker 1>you choose to contribute. Crisis averted. The toolkit doesn't stop

252
00:13:00.879 --> 00:13:03.480
<v Speaker 1>with the user. Administrators get a much bigger hammer. They

253
00:13:03.480 --> 00:13:05.960
<v Speaker 1>can disable memory across an entire tenant, or just for

254
00:13:06.000 --> 00:13:10.200
<v Speaker 1>certain groups. More importantly, every memory action, creation, update, deletion

255
00:13:10.399 --> 00:13:14.480
<v Speaker 1>is discoverable through Microsoft Perview Discovery Translation. Governance teams don't

256
00:13:14.519 --> 00:13:16.960
<v Speaker 1>have to squint at half promises. They get audit trails,

257
00:13:17.000 --> 00:13:22.000
<v Speaker 1>receipts and oversight compliance officers rejoice. Average employees grown, and

258
00:13:22.039 --> 00:13:25.559
<v Speaker 1>as always, governance wins the argument. The analogy is easiest

259
00:13:25.559 --> 00:13:27.879
<v Speaker 1>if you compare it to browser cookies, except these are

260
00:13:27.879 --> 00:13:30.360
<v Speaker 1>cookies you name place and can smash whenever you like.

261
00:13:30.519 --> 00:13:33.000
<v Speaker 1>They don't spawn quietly in the background, they don't follow

262
00:13:33.039 --> 00:13:35.279
<v Speaker 1>you to other sites. If you grow tired of them,

263
00:13:35.360 --> 00:13:38.519
<v Speaker 1>you hit forget and the jar empties. Microsoft didn't sneak

264
00:13:38.559 --> 00:13:41.480
<v Speaker 1>in surveillance here. They copied structured compliance playbooks and drop

265
00:13:41.559 --> 00:13:44.919
<v Speaker 1>them into personalization. So what actually comes included a toggle

266
00:13:44.960 --> 00:13:47.559
<v Speaker 1>buried in an obvious menu, a badge announcing every edition,

267
00:13:47.720 --> 00:13:50.879
<v Speaker 1>commands for surgical deletion or full reset, administrative power tools

268
00:13:50.879 --> 00:13:54.440
<v Speaker 1>for tenant wide disablement, integration with audit trails so auditors

269
00:13:54.440 --> 00:13:57.639
<v Speaker 1>know exactly who remembered or forgot what, and that separate

270
00:13:57.679 --> 00:14:01.000
<v Speaker 1>model training opt out for the nervous. That comp isn't ornamental,

271
00:14:01.039 --> 00:14:03.559
<v Speaker 1>it's operational. If you don't engage with it, you're basically

272
00:14:03.639 --> 00:14:06.200
<v Speaker 1>leaving the hammer on the table and then whining about nails.

273
00:14:06.240 --> 00:14:09.279
<v Speaker 1>The real question isn't whether these controls exist. They clearly do.

274
00:14:09.440 --> 00:14:11.600
<v Speaker 1>The question is whether you'll treat memory as a fuss

275
00:14:11.679 --> 00:14:14.120
<v Speaker 1>over settings panel or as a baseline mechanism that can

276
00:14:14.120 --> 00:14:17.120
<v Speaker 1>actually accelerate your work. Because once you strip away the paranoia,

277
00:14:17.240 --> 00:14:19.399
<v Speaker 1>what's left is a tool designed to stop you from

278
00:14:19.440 --> 00:14:22.159
<v Speaker 1>spending your life repeating yourself. And that's where the real

279
00:14:22.200 --> 00:14:25.600
<v Speaker 1>story begins. Eisen why memory matters more than you think.

280
00:14:25.919 --> 00:14:29.799
<v Speaker 1>Memory is not about vigilance or paranoia. It's about refusing

281
00:14:29.799 --> 00:14:32.039
<v Speaker 1>to live in a loop. Feeding the same instructions to

282
00:14:32.039 --> 00:14:35.480
<v Speaker 1>an assistant that politely acknowledges them and then promptly discards

283
00:14:35.519 --> 00:14:39.600
<v Speaker 1>them without it. Every session resets to zero, keep it

284
00:14:39.679 --> 00:14:43.519
<v Speaker 1>under two hundred words, use bullet points, formal closing day

285
00:14:43.559 --> 00:14:47.080
<v Speaker 1>after day. It's professional dejavus performed at keyboard speed. That's

286
00:14:47.120 --> 00:14:50.600
<v Speaker 1>not productivity. That's assisted futility. Now extend that futility across

287
00:14:50.600 --> 00:14:55.399
<v Speaker 1>an organization. Analysts retype formatting directions into Excel. Project managers

288
00:14:55.399 --> 00:14:59.000
<v Speaker 1>specify the same naming conventions in teams. Designers remind copilot

289
00:14:59.000 --> 00:15:02.320
<v Speaker 1>how to lay out slides individually. This is repetitive annoyance

290
00:15:02.720 --> 00:15:06.159
<v Speaker 1>at scale. It is ours hemorrhaged in slow, invisible increments.

291
00:15:06.240 --> 00:15:09.720
<v Speaker 1>People call this minor inconvenience. I call it institutional inefficiency,

292
00:15:09.840 --> 00:15:13.279
<v Speaker 1>convenient shorthand would be death by redundant clicks. The contrast

293
00:15:13.279 --> 00:15:17.120
<v Speaker 1>is almost insulting in its simplicity. Imagine that forgetful colleague

294
00:15:17.120 --> 00:15:19.759
<v Speaker 1>finally learned to write things down. They don't have new intelligence,

295
00:15:19.799 --> 00:15:23.039
<v Speaker 1>but at last they stop discarding information like Confetti tell them.

296
00:15:23.039 --> 00:15:26.200
<v Speaker 1>Once it sticks and efficiency returns. That's the transition Copilot

297
00:15:26.240 --> 00:15:29.919
<v Speaker 1>makes when memories switched on from digital goldfish to dependable

298
00:15:29.960 --> 00:15:33.159
<v Speaker 1>note taker without needing to rewrite its brain, just by

299
00:15:33.240 --> 00:15:35.720
<v Speaker 1>letting it remember. At this point, the skeptics raise their

300
00:15:35.720 --> 00:15:39.360
<v Speaker 1>hand so it remembers your formatting preferences. Who cares? The answer,

301
00:15:39.440 --> 00:15:43.360
<v Speaker 1>scale cares. The individual saves minutes multiply across departments, and

302
00:15:43.399 --> 00:15:47.519
<v Speaker 1>those minutes accumulate into something. Executives actually recognize productivity. A

303
00:15:47.559 --> 00:15:50.600
<v Speaker 1>formatting preference in word, a naming convention in share Point,

304
00:15:50.639 --> 00:15:54.399
<v Speaker 1>and email style in outlook. Small personal tweaks repeated across

305
00:15:54.480 --> 00:15:58.600
<v Speaker 1>hundreds of workflows become measurable gains. Productivity isn't found in heroics.

306
00:15:58.639 --> 00:16:03.159
<v Speaker 1>It's accumulated convenience serving as leverage, and occasionally, memory doesn't

307
00:16:03.200 --> 00:16:06.360
<v Speaker 1>just save time, it changes output quality. One real world

308
00:16:06.399 --> 00:16:09.320
<v Speaker 1>case involved a user who asked Copilot for PowerShell help

309
00:16:09.440 --> 00:16:12.759
<v Speaker 1>because their memory already stored work tied to the Microsoft graph.

310
00:16:13.039 --> 00:16:17.200
<v Speaker 1>Copilot proactively referenced the graph PowerShell SDK in its answer

311
00:16:17.440 --> 00:16:20.480
<v Speaker 1>that's not a pilot trick. It's relevance created by stored context,

312
00:16:21.159 --> 00:16:24.120
<v Speaker 1>A preference remembered equal to better technical response. Connect those

313
00:16:24.159 --> 00:16:26.759
<v Speaker 1>dots and ROI stops being a buzzword and becomes actual,

314
00:16:26.799 --> 00:16:30.919
<v Speaker 1>observable improvement. Microsoft understands this perfectly. That's why their executives

315
00:16:30.960 --> 00:16:34.240
<v Speaker 1>talk about engineering personality. They're not building memory as acute

316
00:16:34.279 --> 00:16:37.759
<v Speaker 1>add on, they're shaping long term adoption. Users engage more

317
00:16:37.759 --> 00:16:40.360
<v Speaker 1>with assistance that feel consistent, that behave as if they

318
00:16:40.399 --> 00:16:44.080
<v Speaker 1>recognize the person behind the keyboard. Trust builds, usage increases.

319
00:16:44.440 --> 00:16:47.799
<v Speaker 1>Enterprises capture their ROI not from the AI's raw IQ,

320
00:16:48.080 --> 00:16:50.759
<v Speaker 1>but from the fact it remembers you personally. Memory pushes

321
00:16:50.799 --> 00:16:54.519
<v Speaker 1>copilot beyond generic outputs into the realm of organizational alignment.

322
00:16:55.200 --> 00:16:57.879
<v Speaker 1>In excel, metrics tied to a specific roll rise to

323
00:16:57.919 --> 00:17:00.919
<v Speaker 1>the surface. In word, the expected report template is assumed,

324
00:17:01.000 --> 00:17:04.839
<v Speaker 1>not forgotten. In outlook, the drafts resemble the organization's voice,

325
00:17:04.839 --> 00:17:07.559
<v Speaker 1>not a bland computer tone. This is not cosmetic polish.

326
00:17:07.640 --> 00:17:10.680
<v Speaker 1>It's the practical difference between a tool employees despise and

327
00:17:10.720 --> 00:17:12.960
<v Speaker 1>one they quietly depend on. And let's be clear about

328
00:17:12.960 --> 00:17:16.039
<v Speaker 1>the adoption stakes. Enterprises don't roll out AI assystems for

329
00:17:16.160 --> 00:17:19.200
<v Speaker 1>entertainment value. They do it to capture efficiency at scale.

330
00:17:19.319 --> 00:17:22.119
<v Speaker 1>If users find the tool irrelevant or burden, some adoption

331
00:17:22.200 --> 00:17:25.359
<v Speaker 1>flat lines, the investment collapses into shelfware. Memory is the

332
00:17:25.440 --> 00:17:28.319
<v Speaker 1>deciding factor between a system that feels faceless and one

333
00:17:28.359 --> 00:17:32.000
<v Speaker 1>that proves indispensable. Memory doesn't just increase convenience, it ensures

334
00:17:32.000 --> 00:17:35.400
<v Speaker 1>Copilot is adopted rather than abandoned. Now a note for

335
00:17:35.440 --> 00:17:39.240
<v Speaker 1>the privacy conscious viewer. Personalization is enabled in many regions

336
00:17:39.240 --> 00:17:41.920
<v Speaker 1>by default, but, and this is critical, you have the

337
00:17:41.960 --> 00:17:44.279
<v Speaker 1>option to turn it off entirely. Your preference is about

338
00:17:44.279 --> 00:17:46.599
<v Speaker 1>what Copilot should remember, or whether it should remember anything

339
00:17:46.640 --> 00:17:49.640
<v Speaker 1>at all, remain in your control. That Togglin settings ensures.

340
00:17:49.640 --> 00:17:53.599
<v Speaker 1>Personalization is never a hidden imposition. It's a choice you make.

341
00:17:53.880 --> 00:17:57.039
<v Speaker 1>Transparency is built into the architecture, not tagged on after scandal.

342
00:17:57.160 --> 00:17:59.680
<v Speaker 1>So yes, memory matters more than you assumed. It isn't

343
00:17:59.680 --> 00:18:03.160
<v Speaker 1>fluff enhancement or decorative polish. It's the foundation that makes

344
00:18:03.200 --> 00:18:06.960
<v Speaker 1>Copilot scalable, trusted, and actually efficient. Without it, you fight

345
00:18:07.000 --> 00:18:09.640
<v Speaker 1>the same battles every day with it. You transfer those

346
00:18:09.640 --> 00:18:12.279
<v Speaker 1>instructions once and let them persist, both for your sanity

347
00:18:12.400 --> 00:18:15.720
<v Speaker 1>and for the enterprise's appetite for measurable value. And once

348
00:18:15.759 --> 00:18:19.559
<v Speaker 1>you grasp that core function, a final realization follows. Naturally,

349
00:18:19.640 --> 00:18:21.960
<v Speaker 1>memory is not recall, and it's not vision. It is

350
00:18:21.960 --> 00:18:25.839
<v Speaker 1>something altogether different, your deliberate, visible, and controllable layer of

351
00:18:25.880 --> 00:18:30.759
<v Speaker 1>persistence conclusion time. Remember the architecture. Memory is intentionally opt

352
00:18:30.839 --> 00:18:35.319
<v Speaker 1>in and auditable. Recall is automatic device local screenshots, and

353
00:18:35.519 --> 00:18:38.599
<v Speaker 1>vision is session based analysis where text transcripts may persist.

354
00:18:39.079 --> 00:18:42.799
<v Speaker 1>Three tools, three different consent models, confusing them guarantees you'll

355
00:18:42.880 --> 00:18:45.319
<v Speaker 1>argue from the wrong set of assumptions. If this breakdown

356
00:18:45.319 --> 00:18:48.480
<v Speaker 1>spared you from another sloppy LinkedIn rant, reciprocate, subscribe, turn

357
00:18:48.519 --> 00:18:51.640
<v Speaker 1>on notifications, and let the updates arrive like scheduled patches.

358
00:18:51.920 --> 00:18:54.839
<v Speaker 1>Zero effort on your part. Before you leave, run one

359
00:18:54.839 --> 00:18:58.200
<v Speaker 1>final command, ask copilot, what do you know about me? Then,

360
00:18:58.279 --> 00:19:02.559
<v Speaker 1>if the answer unnerves you, talk Personalization offers settings, account privacy,

361
00:19:03.039 --> 00:19:05.519
<v Speaker 1>and since engagement is currency, post in the comments one

362
00:19:05.519 --> 00:19:07.880
<v Speaker 1>example of what you'd actually want co pilot to remember.

363
00:19:08.079 --> 00:19:10.960
<v Speaker 1>It's a more interesting conversation starter than the usual privacy

364
00:19:11.000 --> 00:19:11.319
<v Speaker 1>panic