1 00:00:05,000 --> 00:00:07,020 Hi, I’m Anthony from Mevanu. 2 00:00:07,660 --> 00:00:08,820 “Privacy by design.” 3 00:00:09,320 --> 00:00:12,725 It sounds reassuring. But what should those words make an engineer do 4 00:00:12,740 --> 00:00:16,065 differently? And how can you tell whether you’re getting meaningful protection 5 00:00:16,080 --> 00:00:18,120 or a well-written marketing line? 6 00:00:18,580 --> 00:00:23,285 At Mevanu, privacy by design means building protection and human control into 7 00:00:23,300 --> 00:00:27,420 every stage of a task—and making those decisions open to scrutiny. 8 00:00:27,860 --> 00:00:29,400 Here’s what that asks us to build. 9 00:00:30,020 --> 00:00:34,040 Imagine asking an AI assistant to turn meeting notes into a client proposal. 10 00:00:34,660 --> 00:00:36,960 Useful work. Possibly sensitive work, too. 11 00:00:37,720 --> 00:00:39,240 First, anticipate the risk. 12 00:00:39,620 --> 00:00:42,180 What could go wrong if those notes reached the wrong person? 13 00:00:42,740 --> 00:00:44,240 Address that before it happens. 14 00:00:44,860 --> 00:00:46,340 Choose protective defaults. 15 00:00:46,740 --> 00:00:48,400 The task needs relevant notes. 16 00:00:48,780 --> 00:00:51,220 Why should your entire inbox come along for the ride? 17 00:00:51,760 --> 00:00:55,865 Build privacy into the architecture: what the assistant can read, what it can 18 00:00:55,880 --> 00:00:57,780 share, and when it must ask. 19 00:00:58,100 --> 00:01:00,780 Those boundaries need to shape how the software works. 20 00:01:01,420 --> 00:01:02,840 Preserve the useful part. 21 00:01:03,220 --> 00:01:06,940 Could the proposal work with fewer personal details or narrower access? 22 00:01:07,380 --> 00:01:10,425 Good design should help you get the job done while protecting your 23 00:01:10,440 --> 00:01:13,080 information. Protect the whole journey. 24 00:01:13,480 --> 00:01:15,780 Where are the notes stored? Who can access them? 25 00:01:15,980 --> 00:01:17,440 How long are copies kept? 26 00:01:17,800 --> 00:01:19,240 Plan for deletion, too. 27 00:01:19,760 --> 00:01:21,340 Make the practices checkable. 28 00:01:21,620 --> 00:01:23,220 Explain what happens to the data. 29 00:01:23,500 --> 00:01:25,320 Give people a way to question it. 30 00:01:25,400 --> 00:01:26,925 Allow independent scrutiny. 31 00:01:26,940 --> 00:01:29,180 And keep people in charge. 32 00:01:29,820 --> 00:01:32,040 Clear choices. Understandable permissions. 33 00:01:32,420 --> 00:01:33,880 A way to say “stop.” 34 00:01:34,480 --> 00:01:37,160 Those are the seven principles guiding Brava’s design. 35 00:01:37,780 --> 00:01:40,865 Brava is in development, so we still have to demonstrate how well we meet 36 00:01:40,880 --> 00:01:44,985 them. That means connecting each principle to an actual safeguard, checking 37 00:01:45,000 --> 00:01:48,340 whether it works, and being clear about what remains unresolved. 38 00:01:48,900 --> 00:01:52,900 When a company promises privacy by design, ask it to show that connection. 39 00:01:53,280 --> 00:01:54,945 What information does this feature need? 40 00:01:54,960 --> 00:01:57,180 What happens when you refuse permission? 41 00:01:57,680 --> 00:01:58,940 Who has checked the answer? 42 00:01:59,480 --> 00:02:04,360 Ask us, too. For the full guide, visit Founder’s Bookshelf at mevanu.ai. 43 00:02:04,860 --> 00:02:09,045 It expands these principles with examples, questions to ask and a review note 44 00:02:09,060 --> 00:02:10,880 you can use. Have an idea? 45 00:02:11,260 --> 00:02:14,280 Drop a prompt, comment, suggestion, or question. 46 00:02:14,860 --> 00:02:15,985 Mevanu. Just. 47 00:02:16,000 --> 00:02:16,680 Smarter.