The Uncomfortable Truth About Privacy Consent Banners (deep-dive interview)
Today in Digital MarketingFebruary 09, 2024
1053
00:19:1117.57 MB

The Uncomfortable Truth About Privacy Consent Banners (deep-dive interview)

One of the jobs of a marketer is to instill in the consumer a sense of trust — trust in the brand, trust in the product or service, trust in how the company handles their personal data, and so on.


That latter job is often fulfilled by putting a privacy notice on the site. Sometimes we do it because it's the law in our country; sometimes, in an effort to show people we're a responsible company.


But are we shooting ourselves in the proverbial foot?


That's what Aaron Brough and his colleagues set out to discover. Dr. Brough is an Associate Professor of Marketing at Jon M. Huntsman School of Business at Utah State University. He is the co-author of a new scientific research study called "[The Bulletproof Glass Effect: Unintended Consequences of Privacy Notices](https://journals.sagepub.com/doi/10.1177/00222437211069093)."



.



Privacy & Opt-Out: https://redcircle.com/privacy
[00:00.000 --> 00:05.600] It is Friday, February 9th, and normally, of course, you hear the podcast this time. [00:05.600 --> 00:12.040] Today, our agency is off at a full staff retreat, so instead, we bring you this deep dive interview. [00:12.040 --> 00:16.480] One of the jobs of a marketer is to instill in the consumer a sense of trust, trust in [00:16.480 --> 00:20.760] the brand, trust in the product or service, and trust in how the company handles their [00:20.760 --> 00:22.560] personal data. [00:22.560 --> 00:27.360] The latter job is often fulfilled by putting a privacy notice on the site. [00:27.360 --> 00:30.400] Sometimes we do it because it's the law in our country. [00:30.400 --> 00:34.280] Sometimes in an effort to show people we are a responsible company. [00:34.280 --> 00:38.080] But are we shooting ourselves in the proverbial foot? [00:38.080 --> 00:40.560] That's what Aaron Bruff and his colleagues set out to discover. [00:40.560 --> 00:45.080] Dr. Bruff is an associate professor of marketing at the John M. Huntsman School of Business [00:45.080 --> 00:47.120] at Utah State University. [00:47.120 --> 00:53.120] He is the co-author of a scientific research study called the Bulletproof Glass Effect, [00:53.120 --> 00:57.120] Unintended Consequences of Privacy Notices. [00:57.120 --> 01:00.240] He joins me from his office in Logan, Utah. [01:00.240 --> 01:01.240] Dr. Brock, welcome. [01:01.240 --> 01:02.240] Thanks, Todd. [01:02.240 --> 01:03.240] Good to be here. [01:03.240 --> 01:05.280] All right, let's start with the top line findings. [01:05.280 --> 01:07.440] What were those unintended consequences? [01:07.440 --> 01:14.280] Yeah, so we set out trying to understand how consumers respond to privacy notices. [01:14.280 --> 01:19.640] As part of the research, we surveyed managers across different industries, and a large [01:19.640 --> 01:25.680] majority of these managers expected privacy notices to help customers feel more secure. [01:25.680 --> 01:28.680] But it turns out their intuition was flawed. [01:28.680 --> 01:34.120] We conducted a series of six experiments involving nearly 20,000 people. [01:34.120 --> 01:39.520] We compared consumers' interest in purchasing from a website or an app that either included [01:39.520 --> 01:42.640] or didn't include a privacy notice. [01:42.640 --> 01:47.160] One of the things we found is that telling customers how their personal data is protected [01:47.160 --> 01:51.960] can undermine consumer trust and discourage them from making a purchase. [01:51.960 --> 01:57.160] I like to compare it to going to an elementary school and seeing bulletproof glass and metal [01:57.160 --> 01:58.160] detectors. [01:58.160 --> 02:02.560] Their purpose is there to protect you, but instead of making you feel safe, they could [02:02.560 --> 02:04.560] make you feel more vulnerable. [02:04.560 --> 02:09.280] It's interesting because that's counter to, I think, everything that is both instinctive [02:09.280 --> 02:13.080] as marketers and everything that's taught as well. [02:13.080 --> 02:18.520] You would think that the more we layer on will take care of your data, the more secure [02:18.520 --> 02:19.520] people feel. [02:20.520 --> 02:25.800] Certainly, this does challenge that intuition, telling consumers how their personal data will [02:25.800 --> 02:30.360] be protected is going to be good for business. [02:30.360 --> 02:34.080] For most firms and privacy advocates, that's not great news. [02:34.080 --> 02:40.160] As researchers, my co-authors and I are definitely supportive of respecting consumers' privacy, [02:40.160 --> 02:45.440] and we want to encourage firms to be responsible and transparent in their data practices. [02:45.440 --> 02:51.360] The other thing we looked at after initially discovering this is how could we provide actionable [02:51.360 --> 02:56.520] guidance to managers on how to effectively convey privacy information without hurting [02:56.520 --> 02:58.800] purchase interest. [02:58.800 --> 03:05.280] We tested how changes in the wording of a privacy notice affected consumers' willingness to purchase. [03:05.280 --> 03:10.080] We found that consumers were less turned off by privacy notices that included what we call [03:10.080 --> 03:12.160] benevolence cues. [03:12.160 --> 03:17.760] Those would be statements like, we care about protecting your privacy, or we respect you [03:17.760 --> 03:23.760] and promise to treat you fairly, or we're committed to the protection of your information. [03:23.760 --> 03:28.240] The interesting thing is that although these statements don't offer any legal protection [03:28.240 --> 03:34.120] to consumers, they do seem to help build trust by conveying the consumers that companies [03:34.120 --> 03:36.640] have good intentions. [03:36.640 --> 03:41.120] Having these benevolence cues to a privacy notice can reduce or even reverse its negative [03:41.120 --> 03:43.200] effects on purchase interest. [03:43.200 --> 03:48.360] I think the example that you used in this study was that you changed the phrase, we collect [03:48.360 --> 03:52.600] your information to, we protect your information. [03:52.600 --> 03:57.800] Did you study how people's purchase intent changed when you made substitutions like that? [03:57.800 --> 04:04.120] Yes, so in fact, in one study, people were more likely to buy a product when a privacy notice [04:04.200 --> 04:10.080] had these benevolence cues than when a privacy notice did not include comforting language [04:10.080 --> 04:15.720] or when privacy information wasn't readily available at all during the checkout process. [04:15.720 --> 04:19.840] One of your studies came from a test that you did on a financial services website, like [04:19.840 --> 04:22.280] a real site, one that was in the market. [04:22.280 --> 04:25.320] Can you walk us through what you tested and what you found? [04:25.320 --> 04:31.760] Sure, so there was surprisingly little previous research about how privacy notices affect [04:31.840 --> 04:37.120] consumers' purchase decisions, and as far as I know, we conducted the first published [04:37.120 --> 04:41.520] field experiment looking at this issue with actual customers. [04:41.520 --> 04:46.440] So the company we partnered with was Barwell, which is a Canadian financial technology [04:46.440 --> 04:49.440] firm with over a million users. [04:49.440 --> 04:54.880] And to sign up for Barwell's service, visitors have to complete a nine-step enrollment process [04:54.880 --> 04:58.720] that involves providing some sensitive personal information. [04:58.720 --> 05:03.560] They have to give things like their name, their address, birth date, phone number, income, [05:03.560 --> 05:07.520] financial goals, and access to a credit report. [05:07.520 --> 05:12.120] And so each prospective customer who visited the site was randomly assigned to one of [05:12.120 --> 05:13.720] two conditions. [05:13.720 --> 05:18.920] In the control condition, only a hyperlink to Barwell's privacy policy was provided on [05:18.920 --> 05:21.600] the first screen of the sign-up process. [05:21.600 --> 05:26.360] In the other condition, the link was preceded by an explanation of Barwell's commitment to [05:26.360 --> 05:29.880] the protection of customers' personal information. [05:29.880 --> 05:35.000] And as predicted, enrollment was significantly lower in the condition with the detailed description [05:35.000 --> 05:39.960] of privacy protections than in the control condition that included only a privacy policy [05:39.960 --> 05:41.160] link. [05:41.160 --> 05:46.760] And so these results suggest that prominently displaying detailed privacy protections can [05:46.760 --> 05:51.800] drive consumers away, which could end up costing Barwell hundreds of thousands of dollars per [05:51.800 --> 05:54.360] year and lost revenue. [05:54.360 --> 05:57.000] We conducted this study over a seven-day period. [05:57.000 --> 06:03.080] And so if you extrapolate, that's kind of the estimate for what they could stand to lose. [06:03.080 --> 06:06.040] One of the things I thought was interesting is that you found that while people might be [06:06.040 --> 06:12.600] less willing to buy something after seeing a privacy notice, their perception of the value [06:12.600 --> 06:15.160] of that product didn't actually change. [06:15.160 --> 06:17.160] Did that surprise you? [06:17.160 --> 06:24.040] Yeah, I think the thing that surprised me the most is that consumers [06:24.040 --> 06:29.560] are more likely to purchase from a company that makes no promises regarding the protection [06:29.560 --> 06:36.520] of consumer privacy than from one that is transparent in describing its data practices. [06:36.520 --> 06:41.560] And the reason for that is that a privacy notice places legally enforceable limits on a firm's [06:41.560 --> 06:43.320] data practices. [06:43.320 --> 06:49.560] It communicates safeguards, and it might be expected to promote confidence that one's [06:49.560 --> 06:52.680] personal data will not be misused. [06:52.680 --> 06:57.720] But as I said, instead of making people feel more secure, we found that it does undermine [06:57.720 --> 07:05.880] trust and purchase interest, and yeah, it doesn't change the value, but it does change the willingness [07:05.880 --> 07:09.240] that they have to pay for that product. [07:09.240 --> 07:13.960] And I was also surprised that something as seemingly trivial as including benevolent [07:13.960 --> 07:19.560] skews in the privacy notice, these subtle changes that we make to the language could counter [07:19.560 --> 07:20.800] the negative effects. [07:20.800 --> 07:21.800] Yeah. [07:21.800 --> 07:27.080] Were there any significant differences between generations or genders? [07:27.080 --> 07:35.960] No, so we looked at age and gender as covariates, meaning we tried to see if there were differences [07:35.960 --> 07:39.720] across those variables, and we didn't find any. [07:39.720 --> 07:45.560] I don't often laugh when I'm reading scientific journals or scientific papers, but I did chuck [07:45.560 --> 07:49.760] a little bit because one of the test variations that you did that I thought was clever, we've [07:49.840 --> 07:54.720] talked about sort of the two A, B test that you've done before with this financial services, [07:54.720 --> 07:59.320] but one of your tests included a third option beyond there's a privacy policy link and I [07:59.320 --> 08:02.840] read it, and there was no privacy policy link at all. [08:02.840 --> 08:07.400] And that third option was that you had a link to a privacy policy, but when people clicked [08:07.400 --> 08:11.960] it, the web browser just barfed back a file not found error. [08:11.960 --> 08:18.440] So people were aware that there was a privacy policy, but they didn't get to read it. [08:18.440 --> 08:21.840] How did that change people's purchase intent? [08:21.840 --> 08:28.440] Yeah, so I think that was actually a study that didn't make it into the published paper. [08:28.440 --> 08:31.440] That was one of the earlier studies that we ran. [08:31.440 --> 08:38.200] And one of the reasons it didn't make it into the published paper is because I think one issue [08:38.200 --> 08:44.440] could have been that people are thinking there might be some kind of problem with the [08:44.440 --> 08:49.800] site, right, if they can't get a link to their privacy policy to work properly, then [08:49.800 --> 08:55.440] maybe there's other, you know, incompetence in their ability to, you know, manage my personal [08:55.440 --> 08:56.440] data. [08:56.440 --> 09:00.600] And so that was kind of an alternative explanation for the results of that study. [09:00.600 --> 09:06.120] And so we ran some subsequent studies to be cleaner tests that wouldn't be susceptible [09:06.120 --> 09:07.800] to that alternative explanation. [09:07.800 --> 09:09.040] All right. [09:09.040 --> 09:14.200] You know, a lot of people who are listening to the podcast, people who manage e-commerce [09:14.200 --> 09:18.880] sites and so on, they don't have control, this level of granularity of control over [09:18.880 --> 09:23.920] whether there's a privacy box, what it says, you know, that sort of thing. [09:23.920 --> 09:29.080] So for those people, like I'm thinking people who use kind of like a preset theme in Shopify [09:29.080 --> 09:33.640] or something like that, for those people, is there any way to counter the loss in purchase [09:33.640 --> 09:35.040] intent? [09:35.040 --> 09:39.120] Yeah, that's a good question. [09:39.120 --> 09:45.200] I think, you know, anything that you can do to build consumer trust and to let them know [09:45.200 --> 09:53.280] that you care about them, that you're committed to, you know, not only competently protecting [09:53.280 --> 09:58.680] their privacy, but also that you have their best interest in mind and at heart. [09:58.680 --> 10:05.120] I think any kind of cues that you can give along those lines should be effective. [10:05.120 --> 10:09.800] But you know, you're sometimes limited by the platform in terms of the extent that [10:09.800 --> 10:12.920] you can use to, you know, communicate these cues. [10:12.920 --> 10:13.920] Yeah. [10:13.920 --> 10:14.920] Well, let's go the other way. [10:14.920 --> 10:19.240] Like, if someone has full control over their site and they can choose whether a privacy [10:19.240 --> 10:26.640] notice appears or doesn't appear, is it you're finding that they should just not show one? [10:26.640 --> 10:34.280] No, I would say the finding is if you incorporate benevolence cues into your privacy policy, [10:34.280 --> 10:38.200] we found that in some cases it can actually be beneficial, so it can actually increase [10:38.200 --> 10:44.440] purchase intent beyond what it would be in the absence of any privacy communication. [10:44.440 --> 10:50.240] The downside or the thing you want to avoid is having a privacy notice that does not include [10:50.240 --> 10:51.920] benevolence cues. [10:51.920 --> 10:56.840] And as part of the research, one of the things that we did is we looked at a random sample [10:56.840 --> 11:02.000] of privacy notices of companies listed on the NASDAQ stock exchange and we found that [11:02.000 --> 11:04.780] benevolence cues were in fact quite rare. [11:04.780 --> 11:09.840] So one of the things that I hope that our research will prompt more companies to do is to include [11:09.840 --> 11:16.280] language in their privacy notices that communicates caring and fosters consumer trust so that [11:16.280 --> 11:22.920] consumers are more willing to provide that information and do business with the companies, [11:22.920 --> 11:27.560] but the companies are not discouraged from being transparent in what they're doing with [11:27.560 --> 11:30.400] the companies, with the customer's personal data. [11:31.360 --> 11:35.240] One great thing about our digital marketing world, we have a plethora of tools, one for [11:35.240 --> 11:39.960] whiteboarding, another for collaboration, another for brainstorming, but these often live [11:39.960 --> 11:42.960] in silos, making it hard to manage. [11:42.960 --> 11:44.760] That's where Miro comes in. [11:44.760 --> 11:50.720] With Miro, you can bring everything and everyone together in one place, consolidate different [11:50.720 --> 11:56.360] points of view and increase team collaboration all on one centralized board. [11:56.360 --> 11:59.800] We used Miro to figure out the right flow for our newsletter automations. [12:00.160 --> 12:04.240] And let us get our team all contributing, including our ads, agency people, and saved [12:04.240 --> 12:06.200] us a ton of time. [12:06.200 --> 12:11.200] And it's new AI tool which summarizes and clusters information automatically was a game [12:11.200 --> 12:12.200] changer. [12:12.200 --> 12:16.200] Find simplicity in your most complex projects with Miro. [12:16.200 --> 12:22.320] Your first three Miro boards are free when you sign up today at Miro.com slash podcast. [12:22.320 --> 12:29.560] That's three free boards at M-I-R-O dot com slash podcast, Miro.com. [12:29.560 --> 12:37.200] I only made two New Year's resolutions this time, lose a little weight, and spend less [12:37.200 --> 12:39.760] time on meal planning and shopping. [12:39.760 --> 12:45.320] I do all the cooking for our family, and honestly, after a week of work, all I want to do is chill. [12:45.320 --> 12:48.680] If you're in the same boat, you may want to look into factor. [12:48.680 --> 12:52.680] Factor is ready to eat meal delivery, takes the stress out of meal planning, and sets you [12:52.680 --> 12:54.960] up for success in the New Year. [12:54.960 --> 12:58.800] Skip the grocery stores, prep work, and cooking fatigue. [12:58.800 --> 13:04.160] Dead get chef crafted, dietitian approved meals delivered right to your door, with more [13:04.160 --> 13:09.240] than 35 meals to choose from per week, including options like keto, calorie smart, vegan and [13:09.240 --> 13:10.760] veggie and more. [13:10.760 --> 13:16.800] Plus more than 55 weekly add-ons, you'll have a ton of nutritious and flavorful options to [13:16.800 --> 13:19.280] kickstart your resolutions. [13:19.280 --> 13:25.040] Head to factor meals dot com slash today pod 50 and use code today pod 50 to get 50% [13:25.040 --> 13:26.040] off. [13:26.040 --> 13:40.960] So what would be like the perfect, like if you were VP of policy or VP of privacy or [13:40.960 --> 13:46.680] whatever for an e-commerce company, and the CEO said you've got a day designed for me [13:46.680 --> 13:52.760] the perfect privacy apparatus as it is forward facing to the consumer. [13:52.760 --> 13:53.920] What does it look like? [13:53.920 --> 13:55.120] How is it a box? [13:55.120 --> 13:56.280] Is it a pop up? [13:56.280 --> 13:57.480] How big is it? [13:57.480 --> 13:59.360] Tell me the words to use. [13:59.360 --> 14:02.120] Yeah, that's the million dollar question, right? [14:02.120 --> 14:03.480] If it is. [14:03.480 --> 14:04.480] Or more. [14:04.480 --> 14:13.560] So I think that there's obviously no solution that fits all different situations, and I [14:13.560 --> 14:18.800] think some of that's going to be dictated by the situation in the context. [14:18.800 --> 14:24.600] But I think the key results from our research are do things that build consumer trust. [14:24.600 --> 14:29.320] And so, you know, in addition to conveying that you will protect their information, make [14:29.320 --> 14:33.520] sure that you're communicating how much you care about their privacy and how much you [14:33.520 --> 14:35.600] care about them. [14:35.600 --> 14:39.980] But I think, you know, from other privacy research that I'm familiar with that other [14:39.980 --> 14:44.680] people have conducted, I think there are a lot of best practices out there in terms of [14:44.680 --> 14:52.280] being very concise, you know, trying to avoid jargon that people aren't going to understand. [14:52.280 --> 14:59.720] But to be very open and transparent about what you're doing and explaining to them why you're [14:59.720 --> 15:06.000] collecting this data, how it will be used, and what the benefits are to them of your collecting [15:06.000 --> 15:07.640] this information. [15:07.640 --> 15:13.800] So if you're collecting, you know, a particular piece of information explaining, you know, [15:13.800 --> 15:20.720] this might allow you to customize the product or the experience to their needs, right? [15:20.720 --> 15:25.080] That can be a way to help. [15:25.080 --> 15:27.920] What surprised you the most about your findings? [15:27.920 --> 15:34.280] Well, like I said earlier, I think, you know, one of the biggest surprises was just the [15:34.280 --> 15:39.520] fact that the people would be so willing to give up their personal data without any promise [15:39.520 --> 15:42.160] that it will be protected, right? [15:42.160 --> 15:47.320] When I first started doing this research, I looked at some of the most popular apps on [15:47.320 --> 15:52.240] the app store, and this was before there was regulation that they required them to have [15:52.240 --> 15:58.560] privacy policies, and some of the most popular apps for finance or for fitness where you're [15:58.560 --> 16:04.200] entering, you know, personal health information or medical conditions or things like that, [16:04.200 --> 16:11.080] or you're entering financial data, there were no privacy policies on those apps. [16:11.080 --> 16:15.400] And I thought that was shocking, frankly. [16:15.400 --> 16:19.360] And then the other thing that I think is surprising, like I said earlier, is that I think, you [16:19.360 --> 16:24.600] know, just changing the language slightly can reduce these negative effects that we've observed [16:24.600 --> 16:30.200] of bringing privacy information kind of to the forefront of people's minds. [16:30.200 --> 16:34.200] It's interesting because, you know, I think a lot of people in the industry, I mean, obviously [16:34.200 --> 16:38.800] they're used to multivariate testing, and there's lots of things that we test. [16:38.800 --> 16:43.760] There's image, there's the color of buttons, you know, Google once tested 32 different shades [16:43.760 --> 16:45.120] of blue for their hyperlinks. [16:45.120 --> 16:50.160] I don't know that many people would consider testing the privacy portion of that, and yet [16:50.160 --> 16:54.920] as you discussed, you know, it's pretty critical to the whole thing. [16:54.920 --> 16:57.360] What made you want to study this? [16:57.360 --> 17:02.800] Yeah, so I think part of it was, you know, noticing this about the apps. [17:02.800 --> 17:06.480] I've done some other privacy research. [17:06.480 --> 17:10.680] You know, so I have a couple of recently published papers where we look at the implications [17:10.680 --> 17:14.160] of the pandemic for privacy. [17:14.160 --> 17:18.520] One effect of the pandemic is that there's been this large pool of personal data that's [17:18.520 --> 17:22.040] been generated that was not previously available. [17:22.040 --> 17:26.640] And that's partly due to increased collecting and sharing of consumer information by governments [17:26.640 --> 17:31.360] and businesses, but it's also partly due to an increase in online activities and voluntary [17:31.360 --> 17:35.480] self-disclosure by people who are isolated. [17:35.480 --> 17:40.880] And we identify some opportunities, challenges, and open questions that this poses for both [17:40.880 --> 17:43.320] consumers and marketers. [17:43.320 --> 17:48.640] In another paper, we look at the need to consider both individuals' motivation to protect their [17:48.640 --> 17:52.520] personal information, but also their knowledge of how to do so. [17:52.520 --> 17:58.840] A lot of the research and privacy looks either at motivation or at knowledge, but not at both. [17:58.840 --> 18:02.840] And in fact, many consumers are fairly privacy illiterate. [18:02.840 --> 18:07.640] They're not able to accurately predict how they will respond to privacy threats. [18:07.640 --> 18:12.560] And so in order to do that, we need to consider not only their motivation, but also their familiarity [18:12.560 --> 18:14.440] with privacy-related issues. [18:14.440 --> 18:18.240] So to answer your question, you know, privacy has been something that I've been interested [18:18.240 --> 18:23.200] in for a while now, and working on it from several different angles, and that's kind [18:23.200 --> 18:26.120] of what got me thinking about privacy notices. [18:26.120 --> 18:30.440] As I said, I'm an advocate of transparency in privacy practices. [18:30.440 --> 18:37.520] I think it's ethical for companies to disclose how they are going to be using consumers' [18:37.520 --> 18:38.520] personal information. [18:38.520 --> 18:42.560] And as a consumer, I want my personal information to be protected. [18:42.560 --> 18:47.100] And I think there's a lot of benefits that I can get by providing it, but I want to make [18:47.100 --> 18:52.600] sure that I know how they're going to be using it, how they will be protecting it. [18:52.600 --> 18:56.880] And so, you know, I think privacy notices are important. [18:56.880 --> 19:02.000] And I think that, you know, as our research shows, they can be very influential in influencing [19:02.000 --> 19:03.160] consumer purchases. [19:03.160 --> 19:10.160] I'm curious, given that your research sort of focuses around privacy and the web and e-commerce [19:10.160 --> 19:15.680] and so on, has your research or your experience in this changed the way that you move through [19:15.680 --> 19:18.760] the web as a consumer? [19:18.760 --> 19:24.240] You know, it has a little bit, but I'm like everyone else, I think, where I often don't [19:24.280 --> 19:30.600] read privacy notices all the way through, especially if they're long and full of technical jargon. [19:30.600 --> 19:32.480] But I have become more aware of it, I think. [19:32.480 --> 19:36.840] I've been particularly more aware of their absence, right? [19:36.840 --> 19:40.520] And I think that's the thing that a lot of people, you know, they're just, when they're [19:40.520 --> 19:43.800] shopping, they're not always thinking about privacy. [19:43.800 --> 19:50.120] And so that's the thing that kind of started us off on doing this research is that the absence [19:50.160 --> 19:57.200] of a privacy notice doesn't usually send up red flags to consumers, but it should. [19:57.200 --> 20:01.200] Because what that means is they're making no promises, they could be collecting any data [20:01.200 --> 20:05.800] from you and making no promises about how it'll be protected or used. [20:05.800 --> 20:09.720] And so I think privacy notices are there to protect us. [20:09.720 --> 20:15.840] And so I just want to make sure that companies have a way of communicating that in a way that [20:15.840 --> 20:21.960] won't hurt their business, because otherwise they're essentially given an incentive not [20:21.960 --> 20:26.920] to convey that information, which I think hurts consumers overall. [20:26.920 --> 20:30.440] I hate to say it, I'm one of those people who, when I arrive at a website and it has the [20:30.440 --> 20:36.440] privacy banner, probably GDPR inspired, where there's a big accept everything button and [20:36.440 --> 20:39.920] then a big customize your choices button and then I usually click that. [20:39.920 --> 20:44.840] I like to think I'm privacy aware, I run the Brave browser, I run a VPN on all my devices. [20:44.840 --> 20:53.400] But yet that accept all button is so tantalizingly easy to click, maybe this will eventually [20:53.400 --> 20:54.400] change all of us. [20:54.400 --> 20:57.720] It's certainly interesting research, I'm super delighted that you could share it with us. [20:57.720 --> 21:02.280] Aaron Bruff is an associate professor of marketing at the John M. Huntsman School of Business [21:02.280 --> 21:03.960] at Utah State University. [21:03.960 --> 21:10.000] His study is called the Bulletproof Glass Effect, Unintended Consequences of Privacy Notices. [21:10.000 --> 21:12.360] Dr. Bruff, thank you for joining us. [21:12.360 --> 21:12.800] Thank you, Todd. Transcription results written to '/home/forge/transcribe2.sonicengage.com/releases/20240207164437' directory