The impact of transparency on mobile privacy decision making

Smart devices provide unprecedented access to users’ personal information, on which businesses capitalize to offer personalized services. Although users must grant permission before their personal information is shared, they often do so without knowing the consequences of their decision. Based on the EU General Data Protection Regulation, which mandates service providers to comprehensively inform users about the purpose and terms of personal data processing, this article examines how increased transparency regarding personal data processing practices in mobile permission requests impact users in making informed decisions. We conducted an online experiment with 307 participants to test the effect of transparency on users’ decisions about and comprehension of the requested permission. The results indicate increased comprehension of data processing practices when privacy policies are transparently disclosed, whereas acceptance rates do not vary significantly. We condense our findings into principles that service providers can apply to design privacy-transparent mobile apps.


Introduction
Smart devices, which collect personal information such as users' location, calendar, and contacts, allow for new app-based business models that provide location-based (e.g., navigation, targeted advertising), social (e.g., friend finder, social networks), and personalized (e.g., mobile recommendations, mobile banking) services (Dhar and Varshney 2011;Tan et al. 2014).Such networked business models have substantial implications for data privacy because personal information is shared between and processed by a high number of actors (Wohlgemuth et al. 2014).Mobile operating systems feature safeguards against unauthorized access to personal information, and apps must request permission from users for these services prior to installation or at runtime (Aydin et al. 2017;Balebako et al. 2015).App providers can enrich runtime permission requests with custom explanations by adding a textual description to the mobile operating systems' inbuilt formal request dialogues (Tan et al. 2014).Alternatively, apps can present one or more dedicated screens that provide visual and textual explanations before triggering the actual request dialogue.However, so far app providers typically fail to comprehensively inform users about their data collection and sharing practices (Balebako et al. 2013).In turn, users often make decisions without realizing their consequences (Almuhimedi et al. 2015;Lin et al. 2012).In addition, users do not fully understand how data are processed and shared since data transmissions run in the background of apps (Wetherall et al. 2011).The case of Cambridge Analytica, which used a mobile app to collect private information from 50 million Facebook users for voter-profiling, is one of many examples of privacy invasions that happen without users' knowledge (Rosenberg et al. 2018).Apart from illicit service providers that abuse data, even honest providers often fail to comprehensively explain their data practices.Users are given the opportunity to read privacy policies of service providers to make them aware of the personal data collection and sharing practices that are in place.However, studies confirm that privacy policies are ineffective due to their length and convoluted legal language (McDonald and Cranor 2008;Schaub et al. 2015;Tsai et al. 2011).
In response to ongoing transparency issues, policymakers and consumer advocates have increasingly emphasized the need to strengthen consumer rights regarding personal information (Gimpel et al. 2018).Based on the European Union (EU) General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679), which we consider as an exemplary legal framework, we investigate, how an increase in transparency on data processing compared to service providers' current communication practices affects users' privacy decision making in mobile contexts.The EU GDPR replaces the 1995 Data Protection Directive (95/46/EC) and harmonizes the privacy laws across the EU member states.
The regulation mandates, among other things, that service providers must comprehensively inform users about the purpose and terms of personal data processing before users' data are collected (European Union 2016).Users can then decide whether to opt-in giving informed and active consent (Carolan 2016).One could expect that increased transparency would lead users to make such consent decisions with careful consideration (Schaub et al. 2015).However, in light of reports in the media that many popular apps contain privacy threats such as disclosing location information to third parties (Aydin et al. 2017), users might react by not consenting to any data use at all.Without consent, business models that rely on personal data are at risk.Against this background, the central research question is:

RQ:
How does increased transparency regarding personal data processing practices in mobile permission requests impact users in making informed decisions?
The goal of our study is not to verify that users are concerned about privacy, but to determine whether increased transparency actually leads users to make informed decisions.We also investigate whether businesses that do transparently inform users have to fear that the number of users who consent to the collection of businesscritical personal information will decline.We used a parallel-group experimental design with three conditions to test the effect of transparency on users' decisions about and comprehension of the requested permission.The results indicate that the participants' comprehension of data processing practices increases when increased transparency is established while acceptance rates do not significantly vary.We condense the findings of the study and interpretation of the regulation into design principles that aid app service providers in designing privacy-transparent apps that help their users to give informed consent.Following Gimpel et al. (2018) and Tsai et al. (2011), we maintain that increased transparency and protection of privacy can be an asset for service providers, rather than a liability.
The remainder of this paper is structured as follows: Section "Research background" provides more information on transparency regarding mobile privacy decision making and the EU GDPR.Section "Method" presents the research design.Section "Results" provides the results of our study.Section "Discussion" discusses the findings and derives design principles for app service providers, whereas Section "Conclusion" concludes the article.

Research background
Personal data are defined as "any information relating to an identified or identifiable natural person [...]; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person" (Art.4, No. 1, European Union 2016).The terms "personal data" and "personal information" are used as synonyms in the literature and throughout this article.Data processing comprises any operation regarding personal data, including collection, analysis, storage, use, sharing, and deletion (Art.4, No. 2, European Union 2016).Privacy is understood as "an individual's ability to control the terms by which their personal information is acquired and used" (Chellapa and Sin 2005, p.186).

Transparency of personal data processing practices
Personal data, most of which are collected in onlinebased environments, have become a corporate asset with growing monetary value (Wohlgemuth et al. 2014), and service providers extract value from personal data such as customer preferences, social networks, and geographic locations (Schwartz 2004).For example, Alphabet and Facebook have become multi-billion dollar companies, and are the leaders of the digital advertising market because they are profiling service users' data to allow businesses to more effectively target customers suited for their product portfolio (Kosinski et al. 2015).
Although service users can read privacy policies, most users do not comprehend service providers' personal data processing practices (Schaub et al. 2015).Abundant research has shown that service users are unable to fully understand the convoluted legal language of privacy policies (McDonald and Cranor 2008;Schaub et al. 2015), and consequently, many people do not even bother reading them (Tsai et al. 2011).This leads to a lack of transparency that manifests in information asymmetry between user's and service provider's knowledge of processing practices (Acquisti et al. 2015;Jensen and Potts 2004).
In response to the economic significance of personal data and its potential impacts on service users, policymakers and consumer advocates around the world are requesting more transparency regarding service providers' data processing practices (Executive Office of the President 2015).They further concluded that regulations have to intensely focus on enabling individuals to actively make decisions about future usage and disclosures of any collected personal data (Podesta et al. 2014).In Europe, the recent EU GDPR is the central regulation that mandates service providers to more transparently inform users about personal data processing (European Union 2016) than they did so far (Robinson et al. 2009).Transparency aims to enable individuals to make more informed and privacyconscious decisions regarding the disclosure of personal information (Tsai et al. 2011).

EU general data protection regulation
The EU GDPR, which came into effect on 25th May 2018, is meant to reduce information asymmetry by strengthening data protection for EU citizens (European Union 2016).It mandates that any processing of personal data must follow the principles of lawfulness, fairness, and transparency (Art. 5,No. 1a).
Lawfulness (Art.6) requires an active consent, defined as "any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her" (Art. 4,No. 11).
This definition of consent requires that users have a choice, actively opt in ("freely given"), consent to data processing for a "specific" purpose, have received information regarding data processing ("informed"), and be presented the consent form in a clear, understandable way that distinguishes this consent from other contractual terms ("unambiguous") (Art.7, No. 1 and 2).
For a user to be "informed", the service provider must reduce information asymmetry prior to collecting personal data from the data subject (Art.13).Most importantly, users must be informed about the "identity and contact details of the [service provider]" (Art.13, No. 1a), "the purpose of the processing" (Art.13, No. 1c), and "the recipients [...] of the personal data" (Art.13, No. 1e).Further, for processing to be fair and transparent, users must be informed of "the period for which the personal data will be stored" (Art.13, No. 2a), the right to access the information (Art. 15;Art. 13,No. 2b), the rights to rectify and erase data (Art. 16;Art. 17;Art. 13,No. 2b), the right to withdraw consent at any time (Art.13, No. 2c), and "the existence of automated decision making, including profiling" (Art. 13,No. 2f).Finally, all information should be provided "in a concise, transparent, intelligible and easily accessible form, using clear and plain language" (Art.12, No. 1).
Users can make active consent decisions by accepting or declining permission requests, such as giving an app access to location services or contacts.For the decision to be informed, users must have previously received all of the information listed above.The EU GDPR is a legal norm, but does not provide explicit guidelines on how to establish transparency and display the necessary information.Developers can textually provide the mandated information within the permission request (Tan et al. 2014), so that the privacy decision is put into context and the users are given a choice.Additionally, users must be able to access a long-form privacy policy at any time.
We identified five dimensions affecting user's comprehension of the consequences of their actions: users should know what personal information will be used (collected data), when and how often it will be collected (time of collection), how the information will be processed (processing), with whom it will be shared (sharing), and how long it will be retained (erasure).Transparently providing the EU GDPR-mandated information in mobile permission requests should enable users to make informed consent decisions.We assess, whether this form of information provision increases the comprehension of these five dimensions and suggest our first hypothesis:

H1: More transparent provision of information regarding personal data processing practices in mobile permission requests increases users' comprehension of the consequences of the consent decision.
With reduced information asymmetry and increased comprehension of data processing practices, users' perception of the risks associated with disclosing personal information might increase as well.Privacy calculus theory (Dinev et al. 2006) explains that users perform a risk-benefit analysis in which the willingness to provide personal information is positively related to the perceived value of information disclosure and negatively related to the perceived risks thereof (Xu et al. 2011).However, research showed that this rational view of maximizing benefits while at the same time minimizing risks, corresponding to expectancy theory (Dinev et al. 2006), not always holds for real-world user behavior (Keith et al. 2013).The "privacy paradox" (Acquisti and Grossklags 2005;Adjerid et al. 2018) subsumes discrepancies between users' conservative behavioral intentions and their more liberal real-world behavior.In effect, some users ignore long-term privacy costs in favor of shortterm functional and monetary benefits (Gimpel et al. 2018).
Consequently, we assume that with increased comprehension of personal data processing practices, many users will react with skepticism, raise privacy concerns, and deny permission requests (Keith et al. 2016).Although the privacy paradox might mitigate the effect as some users supposedly trade risks for short-term benefits, we expect to see an overall decrease in the number of users consenting.Therefore, the second hypothesis for this study reads as follows: H2: More transparent provision of information regarding personal data processing practices in mobile permission requests decreases the number of users who consent to the use of their data.

Mobile privacy decision making
Previous research on mobile privacy decision making has highlighted issues regarding the provision of privacy-related information.In general, mobile users value control over their personal information (Pentina et al. 2016), but they are often unaware of the data collection and sharing practices of apps they use (Almuhimedi et al. 2015;Shklovski et al. 2014).When informed about their actual practices, many users are upset and respond by uninstalling the apps (Balebako et al. 2013;Harbach et al. 2014;Shklovski et al. 2014).
Although mobile permission-based access systems should protect users from unwittingly disclosing private information, privacy notices and permission requests provide insufficient explanations of the types of data collected, frequency of collection, entities with which data are shared, and reasons for doing so (Balebako et al. 2013;Lin et al. 2012).Studies have also confirmed that users have difficulty understanding the default mobile permissions (Felt et al. 2012;Kelley et al. 2012) and that their beliefs about apps' behaviors often do not align with their actual behavior (Lin et al. 2012).Some works have proposed highlighting threats to privacy using mobile security extensions like application and network analysis (Aydin et al. 2017), privacy nudges (Acquisti 2009;Balebako et al. 2013), and just-intime disclosures of data sharing (Almuhimedi et al. 2015).
Others have sought to improve the design and timing of privacy notices.Harbach et al. (2014) augmented permission requests with examples of users' personal data to demonstrate the consequences of consent.Kelley et al. (2013) designed a privacy fact sheet.Schaub et al. (2015) presented a framework for designing privacy notices, taking into account the timing, channel, modality, and control of notices.Balebako et al. (2015) compared the impact of timing on users' ability to recall privacy policies as a proxy for an informed consent.Their results indicated that permission requests shown at run time are more salient than is displaying permissions at the time of installation.
Previous research on human-computer interactions further reminds us of the ineffectiveness of warnings, prompts, and permission requests due to users' habits (Böhme and Grossklags 2011;Harbach et al. 2014;Tan et al. 2014).Some users get used to such requests and respond automatically, without making an informed decision.For example, Fisher et al. (2012) showed that 15% of respondents granted all location permission requests on Apple iOS.It is fair to assume that habituation effects will also affect permission requests that transparently explain data processing practices.
Following proven practices from mobile app design (Marrs 2016), privacy information can be presented through onboarding, which is "the process of familiarizing a customer with a firm's service offering" (Voorhees et al. 2017, p. 274).Mobile app designers frequently include short introductory tutorials that explain the app's key benefits.Commonly, this process will comprise a few swipe-through screens that combine images or videos with explanatory text.Studies show that a multi-modal presentation of instructional materials can improve the effects of learning, in line with cognitive load theory (Sombatteera and Kalyuga 2012).The GDPR's transparency principle also proposes using visualization where appropriate (Recital 58).In addition, mobile operating systems' permission request interfaces have word count limits, so developers can only briefly state the mandatory information (Keith et al. 2016), whereas an onboarding process can utilize the full screen of the mobile device.Therefore, we propose an onboarding process as an alternative design, where visual cues accompany a textual representation of the EU GDPR-mandated privacy information.After the user has received the information, he or she is asked to provide consent using the operating system's permission request dialogue.In addition to potentially counteracting habituation, onboarding has higher expressive power than solely text-based permission requests.The onboarding process might reduce the cognitive load required to understand the risks associated with disclosing personal information compared to the text-based request.Thus, the established transparency might negatively affect users' consent decisions in comparison to current nontransparent practices.With regard to an onboarding process, we propose a second set of hypotheses:

H3: More transparent provision of information regarding personal data processing practices in an onboarding process increases users' comprehension of the consequences of a consent decision.
H4: More transparent provision of information regarding personal data processing practices in an onboarding process decreases the number of users who consent to the use of their data.

Method
Design Similar to other studies on mobile privacy notices (Balebako et al. 2015;Harbach et al. 2014;Kelley et al. 2013;Tan et al. 2014), we conducted a web-based experiment and presented participants with app screens framed with a phone border to resemble a virtual smartphone.The experimental design caters to ecological validity as it features both the look and the feel of a real-world mobile app, and a realistic real-world use case.We designed the privacy note and app permission request in accordance with previous research.Following Schaub et al. (2015), the permission request should appear in direct context to the processing practices and block the current application's operations when it wants to access a restricted resource for the first time (Schaub et al. 2015).Our app resembles the flow and user interface (UI) of Apple iOS (version 10, which was current during the experiment) because this operating system uses just-in-time permissions for many years (Tan et al. 2014), while Google Android only recently adopted this behavior (Aydin et al. 2017).

Material and procedure
The use case of our fictitious app-called shop.io-is a mobile shopping platform for high streets (Bartelheimer et al. 2018).Retailers register as partner shops, present their businesses, and engage in targeted location-based marketing, which is facilitated by Bluetooth beacons that retailers install in their shops.These small tokens broadcast a uniquely identifiable signal to which smart devices can react (Betzing 2018).A customer-facing mobile app, which is the subject of our study, allows the user to find local shops and obtain personalized offers.When the customer enters a partner shop, shop.ioreceives the shop beacon's signal and tracks the customer's visit.The system profiles the customer's shopping preferences based on tracked shop visits and uses collaborative filtering to recommend relevant shops and offers that match the user's interests (Bartelheimer et al. 2018).Location-based business models like shop.iodepend on customers' decisions to allow the app to access location services, and to consent to the processing of location information; the use of beacons requires that the app continuously accesses location services in the background to identify beacon signals, even when the user is not actively interacting with the app (Betzing 2018).These concerns, in combination with users' desire for location privacy (Eastin et al. 2016;Keith et al. 2013;Kelley et al. 2013), lead us to test for the "location always" permission instead of other permission requests, such as access to calendars or contacts.
Participants were introduced to the experiment with a detailed description of the setting in which they were hypothetically located.They received a fictive promotional leaflet for shop.io(see Fig. 1) that lists the key benefits of the app and closely resembles realworld app advertisements.Tech-savvy users could infer the app's functionality and behavior from this leaflet.Some statements were directly related to questions regarding comprehension asked in the experiment.Participants then saw the virtual phone's home screen with the app icon and imagined that they were opening shop.iofor the first time.
Our experiment was a hypothetical thought experiment, so participants were asked to select the answer they would choose in real life.After deciding, participants answered ten comprehension questions related to the five dimensions (i.e., collected data, time of collection, data processing, data sharing, and data erasure).The questions are shown in Appendix A.1.Then, participants provided personal and demographic information and were presented with a simple debriefing that explained the purpose of the study.

Conditions
To test the hypotheses, we used a parallel group experimental design with three conditions: a baseline Fig. 1 Leaflet that promotes the fictional shop.ioapp condition and two treatment conditions.The baseline condition resembles current app practices; developerspecified explanations for permission requests are vague and do not provide details about the app's data processing practices (Tan et al. 2014).Figure 2a shows a request for the "location always" permission.The headline and buttons are predefined by iOS, and developers can only define the body of the permission request.
To test for hypotheses H1 and H2, the first treatment condition (henceforth, EU notice) uses the same UI but replaces the marketing-driven text with a short-form privacy notice (see Fig. 2b).This treatment features increased transparency and is compliant with the EU GDPR.The text, which we developed in consultation with a legal expert, closely resembles the wording of the regulation and fulfills, to the best of our knowledge, the prerequisites for an informed consent decision (cf.Section 2): the identity of the service provider (shop.ioLtd) and a request for consent; the purpose of collection (to determine shopping preferences and show relevant content); which personal information is collected (visits to partner shops) and when it is collected (every time a shop is visited); a statement that shop.ioprofiles and compares various users' personal data to other users' data; how long the information is stored; and the users' rights regarding access to and deletion of personal information and the option to withdraw consent at any time.
To test for hypotheses H3 and H4, the second treatment condition uses an onboarding process (henceforth, onboarding) which presents the same EU GDPR-mandated information as the EU notice but in a multi-modal fashion.We consulted existing practitioner guidelines regarding mobile privacy notices published by the US National Telecommunications and Information Administration and the OECD.The former suggests a standardized structure for short-form notices (NTIA 2013), but the proposed data categories have been identified as difficult to understand (Balebako et al. 2015).The OECD recommends a process of preparing a long-form privacy policy, developing a simplified notice, testing its usability, and deploying the notice (OECD 2006).However, as Schaub et al. (2015) remarked, the OECD (2006) fails to address what the policy should look like.Therefore, our onboarding process is inspired by real-world examples (Marrs 2016).Figure 3 shows the four onboarding screens and the subsequent permission request.Each screen is consistently structured and focuses on one aspect of data processing.The screens feature a headline, visualization, mandatory information regarding the data processing, and statements that limit the extent of processing.For example, the first screen states that visits to partner shops are tracked but that no other location information is collected.In this treatment, most EU GDPR-mandated information is provided before the permission request is shown.In effect, the explanation only states that it is a consent form, the name of the service provider, and the purpose of data collection.
Participants were randomly assigned to one of the three conditions.The baseline and the EU notice conditions instantly showed the respective location permission requests, whereas participants in the onboarding condition had to go through the onboarding screens before seeing the location permission request.

Measures
The decision variable was binary; participants were asked to either accept or deny the permission request.The comprehension score variable was composed of five comprehension dimensions, each of which had two true/false questions.As suggested by Dolnicar and Grün (2014), participants could choose to respond don't know to prevent contaminating the data with guesses.The comprehension score was continuously coded between −10 points and +10 points (+1 per correct and −1 per incorrect answer).Following the location permission request, participants' privacy preferences were tested and typed according to the Westin privacy index, which categorizes individuals as either a privacy pragmatist, a privacy fundamentalist, or a privacy unconcerned individual (Taylor 2003).We replicated Westin's approach by asking the same three standardized questions (Kumaraguru and Cranor 2005, p.13,15) on a four-point Likert scale and also use the same classification key (p.13).We also controlled for habituation (Böhme and Grossklags 2011;Fisher et al. 2012;Harbach et al. 2014).
To identify users with privacy habits, we both determined the .25 quantile of the decision time as a reference time for quick decision makers and asked two questions using five-point Likert scales (see Appendix A.2).

Participants
The minimum feasible sample size-252 participants, 84 per condition-was estimated using G*power analysis (Faul et al. 2007).This number of participants enables us to make a fairly accurate and reliable statistical judgment (power = 0.95) based on a medium effect size as well as to detect any effect between the three study groups that may result from providing them with different degrees of transparency regarding personal data processing (Cohen 1988).
We recruited 382 EU residents who were at least eighteen years of age via the online recruitment platform prolific.acon the 21st and 22nd of March 2018.This platform is appropriate for random-sample populations (Berinsky et al. 2012), and the behavior of the respondents on online recruiting platforms closely resembles that of participants in traditional laboratory experiments (Mason and Suri 2012).Further, prolific.acallowed us to lock participants to use desktop PCs only to keep this situational variable constant.We pre-tested the study with 45 additional participants from prolific, discussed the experiment in depth with fellow researchers to ensure its clarity and comprehensiveness, and set up a questionnaire to accurately measure the comprehension level.
Unfamiliarity effects were prevented a priori by preselecting participants that primarily use an Apple iOS device.We also surveyed for smartphone experience and found that 87.3% of the respondents had more than four years of experience.To ensure high data quality, respondents who either failed an attention check question (from Oppenheimer et al. 2009) or failed a simple comprehension check question were removed.This process left us with a sample of 307 participants.The mean age of the participants was 33.69 years (median 32 years, SD 11.06 years), and 67.75% were women (see Table 1).Each session lasted an average of 6 min, and respondents were paid £1 for participation.Participants were evenly distributed among conditions.Slight variations are the result of filtering.In total, 105 participants were assigned to the baseline condition, 104 were assigned to the EU notice condition, and 98 were assigned to the onboarding condition.

Descriptive results
In support of hypotheses H1 and H3, which propose that users' comprehension increases when privacy-related information is presented more transparently, participants in the treatment conditions achieved higher comprehension scores than did those in the baseline (Table 2).Thus, it is reasonable to claim that they made more informed consent decisions (Fig. 4a).Appendix A.4 gives the distribution of comprehension performance across conditions.
The comprehension scores of participants in the baseline condition were the lowest of almost all dimensions, followed by participants in the EU notice condition (see Appendix A.4, Table 5).The scores of those in the onboarding condition were much higher than the scores of those in the other two conditions in almost all dimensions.With a maximum of 10 points and a minimum of −10 points, the baseline group achieved an average of −.02 points (EU notice 1.38 points; onboarding 3.76 points) over all dimension areas with homogeneous distribution as the standard deviation is almost identical across conditions (SD baseline 2.68; SD EU notice 3.54; SD onboarding 3.07).Furthermore, we descriptively analyzed how much time participants needed to make their decisions across conditions (see Appendix A.3).

Fig. 4 Dimensional of comprehension results and distribution of privacy types
The distribution of the permission request decision is similar for all conditions.In the baseline condition, 57.1% of the participants allowed access to location services (EU notice 57.7%; onboarding 53.1%), which might indicate that increased transparency does not affect respondents' decisions.
Table 2 also provides descriptive statistics concerning the the shares of habituated users, as well as distribution of the three types of privacy preferences.In total, 7.8% of the participants made privacy-related decisions out of habit, as did 5.7% of those in the baseline condition, 8.7% of those in the EU notice condition, and 9.2% of those in the onboarding condition.Although we expected the onboarding process to counteract habituation, there is no evidence that it does.With regard to the three types of privacy preference, more than half of the participants were privacy pragmatists and around a third were privacy fundamentalists, with fewer reporting to be unconcerned about privacy.The resulting distribution of privacy types (Table 2) can be interpreted as a reliable replication of Westin's 2003 study (presented in Taylor 2003), in which 26% of adults were classified as privacy fundamentalists, about 10% were unconcerned, and 64% were pragmatists.In our study, a large majority (73%) of unconcerned participants allowed access to their data for location services, while the other two groups' decisions were more balanced (Fig. 4b).

Inferential results
Table 3 presents the regression results.We conducted a linear regression to test the effect of increased transparency, in the form of an EU GDPR-compliant notice and the additional onboarding process, on participants' comprehension as well as a logistic regression to test the effect of the treatments on users' decisions.The strong positive relationship indicated by Fig. 4a was confirmed with the following linear regression model: where i indexes the individuals, β 0 is the intercept, β 1 and β 2 are the effects of the respective treatment (i.e., EU notice and onboarding), β 3 , β 4 , and β 5 are the coefficients for the privacy type which are dummy variables, γ is the coefficient for the controls i , which were Habit, Age, and Gender, and ε represents the error term.We used the baseline condition as the reference condition.Model [1] (Table 3) contains only the treatment variable (condition), while Model [2] also includes the covariates indicating the privacy preferences of each individual and the control variables.In Model [1], the comprehension scores of participants in the EU notice condition increased significantly to 1.40 (p < .01).This effect was amplified when the control variables were added (Model [2]: 1.47, p < .01).The effect was even greater for the onboarding condition (Model [1]: 3.77, p < .001;Model [2]: 3.8, p < .001).Therefore, the study provides evidence that the users' comprehension of the consequences of the consent decision increases when there is increased transparency regarding data processing.
To test hypotheses H2 and H4, we used the following logistic regression model that contains the same index, intercepts, and coefficients as the linear model, excluding the linear-specific error term: In line with Model [1] and Model [2], Model [3] features only the treatment variable, while Model [4] also incorporates the covariates for the privacy type and the control variables (Table 3).The results indicate that participants' consent decisions were not significantly negatively affected by a more transparent provision of information regarding data processing (EU notice: Model [3]: 1.02, p = .94,Model [4]: .93,p = .94;onboarding: Model [3]: .85,p = .56,Model [4]: .79,p = .43),so we reject hypotheses H2 and H4.Therefore, increased transparency does not decrease the number of users who consent to data processing.
When we control for privacy preferences, the coefficients of the treatment conditions remain largely unchanged, indicating that the effect is robust, except the EU notice condition significantly caused privacy-unconcerned participants to consent to data processing (EU notice: 10, p = .056).Participants who were unconcerned about privacy were 2.41 times more likely than those with other privacy preferences to accept the permission request (p = .03).The results for the comprehension score largely reflect the findings from the main analysis, except for unconcerned participants in both conditions, who show an insignificant improvement in comprehension (EU notice: .99,p = .45;onboarding: 1.89, p = .20).

Qualitative results
All participants were asked to provide a rationale for their decisions by means of an open-ended question immediately after decision making.The responses were split into two data sets: 172 cases of acceptance and 135 cases of denial of the permission request.We conducted a qualitative content analysis that followed the content structuring approach presented by Mayring (2014).Two researchers independently analyzed the data set to exploratively create a category-based coding scheme that allows responses to be assigned to at least one non-mutually exclusive category.The coding scheme was iteratively revised until a consensus among both researchers was reached and every response could be assigned.
Table 6 in Appendix A.5 provides inter-rater agreements regarding both subsets and individual categories using percent agreement and Cohen's Kappa.The results indicate a very high agreement for both the acceptance (95.60% agreement; overall Cohen's Kappa .840)and rejection (96.48% agreement; overall Cohen's Kappa .853)subsets (Landis and Koch 1977).In instances of disagreement, the researchers discussed the respective codes until a complete consensus was established.
Seven categories were derived from the responses related to acceptance of the permission request.Table 7 in Appendix A.5 provides the categories, their descriptions, and number of mentions.Evidence from the responses was added for clarity.All quotes are taken verbatim without correcting punctuation or spelling.Most respondents reported receiving personal benefits (111, 64.53%) or allowing the app to properly execute its service (89, 51.74%) as rationales for consenting to the request.In total, 56 respondents (32.56%) reported both personal benefits and functional reasons.Ten respondents (5.81%) acknowledged habituation and eight respondents (4.65%) stated that they did not care about the consequences of their decision.Although, shop.io is a fictional app, ten respondents (5.81%) explicitly stated that they trusted the app.Eight of the respondents within this category received the onboarding treatment.Lastly, five participants (2.95%) reported feelings of control as they explicitly or implicitly knew that they could revoke the location permission and their consent later on.
Table 8 in Appendix A.5 lists eight categories of rationales for why participants denied the location permission request.Most frequently, respondents disliked the feeling of intrusiveness evoked by tracking (45, 33.34%), giving the app permanent access to location data (43, 31.85%), or providing personal information in general (42, 31.11%).Across groups, about a third of participants reported that they would grant shop.ioaccess to location data if the information is only collected when the app is opened (i.e., when the user is actively interacting with the app).Twentyone (15.56%) participants had bad experiences in the past, recalling battery drain and high use of mobile data due to background location services.Some users (19, 14.07%) decided out of habit and stated that they completely disabled location features or denied all requests.Seventeen respondents (12.60%) did not understand why shop.iorequired location services and denied the request.Further, ten participants (7.41%) feared a data breach, intrusion by hackers or unauthorized sharing of personal information.Lastly, seven participants (5.19%) denied the request because they were not interested in the app and the functions enabled by location services.

Interpretation of results
Transparency regarding personal data processing practices in mobile permission requests does influence users in making more informed decisions (H1, H3).Both an EU GDPR-compliant notice and an onboarding process are suitable designs that app providers can apply when developing privacy-transparent mobile apps.Since an EU GDPR-compliant notice suffices to give users all of the information required by law, an onboarding process that exclusively informs on data privacy might-at first-appear over-engineered.However, onboarding had the superior comprehension rates to both the baseline and the EU notice designs.From an ethical perspective, service providers should aim at maximizing comprehension.Although legally sufficient, over time the EU notice design (with its brief textual explanation) might come with social penalties if superior practices of disclosure such as onboarding will establish themselves on the market.We maintain that onboarding should be preferred generally to maximize comprehension, and particularly in cases of complicated services that require explanation.Nevertheless, in our case, the onboarding process also had a negative effect on some respondents.Among the seventeen users that did not understand the necessity of granting the permission request (Table 8), nine received the onboarding treatment, which explains in detail that location is sensed through Bluetooth beacons and not via GPS.Although technically correct, this statement caused confusion since users associate the location permission request primarily with GPS.However, Apple iOS uses the same permission and dialogue for both Bluetooth beacons and GPS.This limitation is specific to our case but reminds us that providing more information can sometimes increase the risk of misunderstandings.
We expected that more transparently informing users about data processing practices would reduce acceptance rates (H2, H4).However, users showed no significant differences in their consent decision in either of the two treatment conditions.One the one hand, this might suggest that users are prejudiced, react regardless of the treatment, and are not impacted by increased transparency.On the other hand, a lack of behavioural change at the aggregated level can mask changes at the individual level.Some users who would have previously declined might have become convinced by the given information, while other users might have become alienated.
The qualitative analysis of users' rationales for deciding on the permission request reveals that most participants follow the traditional privacy calculus and weigh permanent tracking against personalized services and monetary benefit (Xu et al. 2011).Regardless of their decision, the established transparency might reduce the users' cognitive load related to their privacy calculus.In contrast to related studies by Shklovski et al. (2014), no participant expressed helplessness or reported lack of transparency as a reason for denying the permission request.
We also find evidence for the privacy paradox (Acquisti and Grossklags 2005;Adjerid et al. 2018).In total, 43 participants were classified as privacy fundamentalists (16 baseline, 16 EU notice, 11 onboarding), but provided their location information to receive personal benefits.Further, with regard to the effect of transparency and perceived control on user behavior, related work names the "Peltzman effect," in which users offset their increased feelings of control and trust by engaging in riskier disclosures (Brandimarte et al. 2013).The EU notice and onboarding treatments do explicitly present the users' rights to access and delete collected data, which can increase users' perceived control relative to the baseline condition.However, given that no statistically significant differences in users' decisions were evident in our study, we cannot confirm the existence of the Peltzman effect.
While this study focuses on the influence of increased transparency on making informed privacy decisions, it also stimulates the need for further research.Trust is a known influence on the willingness to provide personal information (Dinev et al. 2006).Given its expressive nature, an onboarding process could be used by service providers to market their reliability and seriousness regarding the protection of personal information.The qualitative analysis provides preliminary evidence that particularly the onboarding design can evoke feelings of trust (cf.Appendix A.5, Table 7).For example, one participant stated to agree "because the app explains privacy so well that I'd enable location permission."However, further studies are required to explore whether transparent information provision facilitates cognitive and affective trust (Johnson and Grayson 2005), if there is an interplay between trust and the different privacy types (Kumaraguru and Cranor 2005), and how trust mediates the consent decision in such a scenario.
In our case, less than two-thirds of participants consented to data processing (Table 2).In the real world, this would cause businesses models like shop.io, which rely on tracking personal information, to lose potential customers.The most frequently mentioned reasons for declining the permission request were related to privacy concerns and location tracking (cf.Appendix A.5, Table 8).In particular, 33 participants disliked that the app had constant access to location services, preferring to control tracking themselves.One participant stated: "I don't mind if I am using the app, but its a bit creepy to constantly track my location."In response, service providers should consider hybrid approaches to personal data collection, where a secondary means of collection eclipses a primary one.Collecting less personal information might lead to a reduced range of functions, but it would be more likely to retain privacyconscious users.Instead of automatically tracking users, shop.iocould track shop visits through "check-ins" or users could manually select their favorite shops, which would still enable the provider to personalize the service to some extent.Nevertheless, requesting access to a reduced set of personal information after the user denied the primary means of data collection might appear as bold or even "greedy" to some users and might have a negatively impact trust.In total, 7.8% of respondents were classified as habituated based on the quantitative analysis, while the qualitative analysis revealed that 11.4% of respondents acted out of habit.About 6% of respondents stated that they accept all requests or do not care about the consequences of their decisions (cf.Table 7).Another 6% of respondents stated to deny all location permission requests (cf.Table 8).In effect, even when transparently providing information to users, there will be a fraction of potential users who service providers cannot influence either way.

Implications for App service providers
Although the EU GDPR only protects the data of EU citizens, it is the most far-reaching regulation concerning transparency and data privacy to date (Carolan 2016), and thus, should be kept in mind by any privacy-conscious service provider.In its first months of being effective, the regulation most prominently impacted users by omnipresent notifications for updated privacy policies and requests for consent (Hern and Waterson 2018).Researchers also measured a reduction of third-parties that service providers share their service users' personal data with.For example, the number of third-party cookies (e.g., by ad networks) on European news websites declined by 22% (Libert et al. 2018).On the contrary, some service providers lock out EU customers or have shut down their service entirely instead of making their offerings compliant (Hern and Waterson 2018).While making existing business models and services compliant with the EU GDPR is a challenge, it is possible to design new services for transparency.The literature suggests the related concept of privacy by design, which describes practices to embed privacy into information systems design and development (Schaar 2010), such as requiring only a minimum amount of personal information for service delivery and utilizing appropriate technical means to protect data (Gimpel et al. 2018).
To identify the primary requirements for service providers concerning the design of privacy notices in particular and mobile privacy management in general, we consulted the EU GDPR.Against the backdrop of the study results and our interpretation of the regulation, we derived six design principles for privacy-transparent mobile apps (Table 4), which app service providers can apply in conjunction with the privacy by design approach (Schaar 2010).
Service providers must design for privacy by default (DP 1) so that no personal information is collected and processed before informed consent is given (Art.25 Short-form Notice Provide users with short-form EU GDPR-mandated information in the form of a notice or an onboarding process to enable them to give an informed consent.

3
OS Dialogues Make use of mobile operation systems' permission request dialogues to ask informed users for consent to a particular purpose.4 Privacy Self-service Provide the system with a privacy menu that allows users to inspect the personal information that is collected about them (right to access), correct inaccurate data (right to rectification), export collected data (right to data portability), delete their personal data (right to be forgotten), and withdraw given consent (right to object). 5 Long-form Policy Provide users with a long-form privacy policy that follows the principles of lawfulness, fairness, and transparency.6 Plan B Design the app to ask for consent to less privacy-intrusive means of data collection if consent to the primary means is denied.
EU GDPR).As this study showed, transparency can be established by a short-form notice (DP 2) that includes all EU GDPR-mandated information (Art.13).Regardless of whether app designers use a textual description or an onboarding process, the mobile operating system's permission dialogues should be used as a mechanism request consent (DP 3).With a single input, the user gives both legal consent to data processing and technical to the underlying data sources.
Given the goals of transparency and legal compliance, service providers must provide users with extensive control over their personal data.We suggest self-service privacy management (DP 4) within mobile apps that implements the rights users have through the EU GDPR.This system should disclose all information that the service provider has collected on the user (Art.15), such as prior shop visits in the case of shop.io.The system should also allow users to request rectification of inaccurate data (Art.16), decide which data to keep and which to delete (Art.17), and export collected data (Art.20).In addition, the legal expert we consulted stressed that withdrawing a consent must not be more complicated than giving the consent (Art.7, No. 3).Consequently, app service providers must implement means for users to withdraw consent within the app (Art.21).Further, as a part of privacy self-service, users must be able to inform themselves about all data processing practices in detail.Therefore, the short-form notice must be accompanied by a long-form privacy policy (DP 5) that is lawful, fair, and transparent (Art.5).Lastly, as shown before, the study revealed that a binary choice is too restricting; some users might be comfortable with sharing only a subset of personal information or with deciding case by case.Consequently, when a binary choice is denied, service providers should revert to less intrusive methods of data collection (DP 6) with which some users might be more comfortable.

Limitations
Our study features certain limitations.First, our treatments were designed using the EU GDPR as underlying framework.Because the regulation is an abstract norm, it does not give concrete design requirements.While our study and design principles are one potential interpretation, there might be other ways to transparently provide information that will impact users differently.Moreover, users might want to receive further information such as technical details regarding the types of and protective measures applied to involved IT systems, which are categories of information that go beyond those mandated in the EU GDPR.Further, we only tested the impact of the "location always" permission, which is known to raise substantial privacy concerns.
We conducted a hypothetical web-based experiment that resembles real-world conditions by mimicking the look and feel and use case of an Apple iOS app.However, the experimental conditions may have biased the results.
In particular, the level of acceptance might have been negatively affected by the random sample used in the experiment.A random sample is unlikely to be as interested in the app's features as a sample of tech-savvy users; those who download the app are more motivated to use it and are more likely to consent to data processing.Further, the level of comprehension might be positively biased because we asked users to read the text carefully.In the real world, users' primary desire is to use the app and privacy notices and permission requests are often seen as a distraction (Jensen and Potts 2004).

Conclusion
In this work, we demonstrated that increasing the transparency of data processing practices in the context of mobile privacy decision making does increase users' comprehension of their consent decisions but does not influence the decision outcome.We designed two treatments and identified six design principles that app service providers can use to design privacy-transparent mobile apps.Augmentation of standard permission request dialogues with privacy-related information and a dedicated onboarding process support users in making informed decisions.
Data-driven service can be a boon or a bane for users as the perceived benefits of personalization are often more visible than the perceived risks of sharing personal data.Mobile privacy decision making is particularly complicated because mobile devices provide far-reaching access to personal data but their interfaces complicate the communication of privacy-related terms of service.Increased transparency is an essential requirement for making informed consent decisions and might fundamentally influence users' behavior regarding (mobile) privacy decision making in the long run.This stream of research will be fruitful for future interdisciplinary research at the intersection of information systems, computer science, law, psychology, and service marketing.As the EU GDPR will continue to impact both users and service providers, we hope to see studies on the longitudinal impact of increased transparency on users' privacy-related behavior and service providers' business models soon.more time for the entire process, which is plausible as they were confronted with substantially more text.However, it is worth mentioning that these participants took less time to make a decision regarding the actual permission request compared to the other two conditions, despite the fact that the provided text is twice the length of the marketing-driven text in the baseline condition.

A.4 Distribution of comprehension performance across conditions
Table 5 presents the distribution of the total scores achieved by the respective number of participants in each condition.This table ranges from −6 to 10 points as no participant scored below −6 points (i.e., each participant gave at least two correct answers).The baseline condition featured the most participants with very low overall scores.With increasing transparency, a clear shift occurred; more participants achieved considerably higher scores in the other two conditions, with a total of 15 participants who had answered at least questions correctly in the onboarding condition.Participants across all groups who denied the permission request achieved a comprehension score that was about 13% higher than that of participants who gave permission (1.78 vs. 1.57).

A.5 Rationales for deciding on the location permission request
Immediately after making a decision regarding the location permission request and before seeing the comprehension questions, the participants were asked to provide a rationale for their decision by means of an open-ended question.The data was subject to qualitative content analysis (Mayring 2014) and was independently coded by two researchers.Table 6a and b provide the respective inter-rater agreements by content category using percent agreement and Cohen's Kappa.
Tables 7 and 8 provide the participants' reasons for accepting respective denying the location permission requests.The answers are clustered into content categories.For each category, the numbers of mentions by condition, category descriptions, and anchor examples from the survey are provided.111 (39, 38, 34) The respondent gave the permission to receive "I want the best deals" personal benefits such as personalized service and promotions.Functional 89 (26,29,24) The respondent named granting the permission "To allow them to track what shops I go into" a prerequisite for proper service execution.Habituation 10 (5, 3, 2) The decision was made out of habit without reflecting "Knee-jerk reaction.I always allow apps access to its consequences.my location" Trust 10 (1, 1, 8) The respondent explicitly stated to trust the app given "The app gave me a peace of mind after the previously received information.informing me in detail how it will use my personal data -most importantly, my data wouldn't be shared.After that, I felt that I could trust the application."Ignorance 8 (2, 3, 3) The respondent explicitly stated to not care for the "There are so much inevitable data miners in this consequences of the decision.
day and age that even if there was something suspicious about it, it wouldn't mean much."Control 5 ( 1, 2, 2) The respondent explicitly stated a feeling of "I can easily opt out if/when I delete the app [...]" control regarding the option to withdraw consent and revoke the permission later.Unrelated 10 (3, 6, 1) The answer did not contribute any meaningful "as i know its a survey and not real life" explanation of the respondent's behavior.

Fig. 5
Fig. 5 Submit time for each experimental condition

a
Total number of mentions (Baseline, EU Notice, Onboarding) Quotes are taken verbatim J.H. Betzing et al.

Table 2
Descriptive statistics of the results

Table 4
Design principles for privacy-transparent mobile apps

Table 5
Distribution of comprehension performance across conditionsThe impact of transparency on mobile privacy decision making

Table 7
Participants' reasons for the location permission request