<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Evaluating ambiguity of privacy indicators in a secure email app</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Borce Stojkovski</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Gabriele Lenzini</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Interdisciplinary Centre for Security, Reliability and Trust (SnT) University of Luxembourg</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>Informing laymen of security situations is a notoriously hard problem. Users are usually not cognoscenti of all the various secure and insecure situations that may arise, and this can be further worsened by certain visual indicators that instead of helping users, fail to convey clear and unambiguous messages. Even in well established and studied applications, like email clients providing end-to-end encryption, the problem seems far from being solved. Motivated to verify this claim, we studied the communication qualities of four privacy icons (in the form of coloured shapes) in conveying speci c security messages, relevant for a particular secure emailing system called p p. We questioned 42 users in three di erent sessions, where we showed them 10 privacy ratings, along with their explanations, and asked them to match the rating and explanation with the four privacy icons. We compared the participants' associations to those made by the p p developers. The results, still preliminary, are not encouraging. Except for the two most extreme cases, Secure and trusted and Under attack, users almost entirely missed to get the indicators' intended messages. In particular, they did not grasp certain concepts such as Unsecure email and Secure email, which in turn were fundamental for the engineers. Our work has certain limitations and further investigation is required, but already at this stage our research calls for a closer collaboration between app engineers and icon designers. In the context of p p, our work has triggered a deeper discussion on the icon design choices and a potential revamp is on the way.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>This work reports on preliminary research where we questioned how users understand security
indicators|either used independently, or alongside text labels, or with explanations|that are
shown in an email application that o ers end-to-end encryption1.</p>
      <p>Security indicators are graphical clues or icons that, in secure email apps, are reserved to
tell users about two speci c concepts: con dentiality of a message, meaning that an email is or
has been encrypted, and authenticity and integrity, meaning that the message is coming from a
trusted party, that is, from a party whose public key we hold and trust. Di erent choices exist
to express those concepts either in their positive and in their negative variants (e.g. violation of
con dentiality, untruthfulness of a party, and lack of any knowledge on the matter), but there
is no uniformity in how di erent apps should graphically convey those messages.</p>
      <p>
        We investigate the question in the context of \Pretty Easy Privacy"2(p p), a relatively
new secure email app that attempts to deploy a tra c-light semantic as a clear and easily
understandable presentation of the di erent privacy states that messages and communication
peers can have[
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. The design choices regarding the indicators within p p diverge from those
of other applications, and how this re ects on users has not been studied before. Furthermore,
other secure email apps also di er from one another. Overlooking that Lausch et al. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] discuss
that an \envelope" in various conditions (e.g. broken, closed, open) is a better metaphor than a
\padlock" in its various forms (e.g. open or closed, and red or green-coloured), applications opt
for their own security icons and metaphors|for instance, the popular open-source Enigmail3
for Thunderbird uses padlocks for con dentiality and sealed envelopes for authentication and
integrity (see Figure 1). The reasoning underpinning choices is often not explicitly stated.
1.1
      </p>
      <sec id="sec-1-1">
        <title>The hard quest for good security indicators</title>
        <p>The lack of standards is surely not helping secure email designers to converge in choosing the
same security indicators. Part of the problem is the considerable amount of di erent situations
that arise when talking about email con dentiality, authenticity, and integrity: distinguishing
and representing all of them with icons, or with a combination of icons, does not have any
obvious solutions.</p>
        <p>
          Even the choice of what is the right metaphor is unclear and, at least in the end-to-end
encryption case, it seems that metaphors do not help users understand the real functionality
of an application [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ]. Thus, designers nd themselves in the di cult position to either simplify
the message, at risk of paternalizing users (= not letting them be in control), or deliver a fully
edged description, at risk of confusing them.
        </p>
        <p>
          Recently the situation may have gotten worse. The General Data Protection Regulation
(GDPR) suggests the use of icons in order to give a meaningful overview of the intended
processing in an \easily visible, intelligible and clearly legible manner" (Art. 12.7) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. The
GDPR has renewed a general interest in security indicators. While most of them are variants of
padlocks and shields, many others are new, and more are expected to be proposed in response
to the GDPR call.
        </p>
        <p>
          Without a common agreement on what security icons to use and in which circumstances,
having a large pool of icons to choose from may actually confuse app designers and users
alike. For example, research on security indicators in the context of web browsers, which has
been an active research area for almost two decades [
          <xref ref-type="bibr" rid="ref12 ref4">4, 12</xref>
          ], cautions that people don't always
understand security indicators. In contrast to the pictograms of bio or chemical hazards, which
are standardized internationally by the Globally Harmonized System [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ], at the moment there
is no equivalent agreement that can characterize what security `hazards' are and how they can
be represented.
        </p>
        <p>And, unlike written texts for which tests of understandability exist, icons do not have an
accepted intelligibility test. Thus, secure email engineers have to nd their ways without clear
guidelines and instruments for the design of security indicators.</p>
        <p>Even in the case of security applications that have been available for decades, like secure
email apps, there is still room for improvement. Our investigation brings up some data that
can revive a discussion about the pros and cons of certain design choices in this application
domain. By shedding light on the use of the tra c-light semantic within a new system that
aspires to bring crypto to the masses, our work contributes to the discourse on the usability and
e ectiveness of security and privacy indicators, which in the secure email context has received
relatively little attention.
2</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Background and Research Questions</title>
      <p>p p is an opportunistic peer-to-peer end-to-end encryption software which tries to unburden
users from managing their encryption keys. p p automatically generates user keys, appends
the public key to each outgoing message, and extracts and stores keys from incoming messages.
Messages are automatically encrypted and decrypted. Peers can be veri ed to be authentic by a
second-channel out-of-bound communication, e.g. a phone call where the peers verify a
humanfriendly version of their ngerprint; this version is a sequence of easily readable words, called
trustwords, taken from a dictionary according to an index that depends on the combination of
the two peers' ngerprints.</p>
      <p>Depending on several factors, each communication channel to di erent peers may have a
di erent privacy status. For example, the system can independently and automatically
categorise a particular message as reliable whenever it can be encrypted or decrypted with su cient
cryptographic parameters. However, the system cannot independently categorise the message
as trusted unless the user carries out a p p handshake and con rms to trust the sender in the
p p interface.</p>
      <p>Internally, p p distinguishes among 13 situations which are surjectively mapped into colour
codes</p>
      <p>
        (chosen according to a tra c light semantics), privacy rating labels, as well as corresponding
privacy rating explanations [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. Table 1 provides an overview of the di erent internal ratings,
codes and labels. Table 2 provides an overview of how these ratings are currently displayed in
the user interface of p p for Thunderbird.
      </p>
      <p>For instance, the p p rating \mistrust" is assigned the colour code \red", the user
interface label \Mistrusted", and explanation \This message has a communication partner that has
previously been marked as mistrusted".</p>
      <p>In addition, p p uses privacy indicators which are icons from an icon set made up of four
coloured shapes (e.g. see Figure 2 and Figure 3) corresponding to the colour code assigned to
each situation. \Under Attack", \Broken", and \Mistrusted" are the situations represented by a
red square, for instance. The rating codes from 0 to 5 are not assigned any colour label, however,
in the user interface, these codes are represented by a gray circle. Reliable communication (i.e.
Rating Code
-3
-2
-1
0
1
2
3
4
5
6
7
8
9</p>
      <p>Rating Label
under attack
broken
mistrust
unde ned
cannot decrypt
have no key
unencrypted
unencrypted for some
unreliable
reliable
trusted
trusted and anonymized
fully anonymous
rating code 6 ) is represented using a yellow shape, and trusted communication (i.e. colour code
7 ) is represented with a green shape.</p>
      <p>The design choice of p p's privacy icons is justi ed by arguments, but not by evidence.
While discussing with the p p developers, we were told that the shapes are meant to be easily
understood by colour-blind persons, and were suggested after consultation with experts. The
colour choices are meant to re ect the universally-deployed tra c light semantic.</p>
      <p>There are many interesting questions that could be investigated, such as, how to draw user
attention to these indicators; where to display those icons in the user interface; what situations
do such shapes suggest to users; are shapes better than conventional icons (e.g. envelopes), etc.</p>
      <p>Nevertheless, here we conduct an enquiry into the most basic question of \how would
prospective or rst-time p p users understand the p p privacy indicators". Formally stated,
we intend to shed light on the following research questions:
1. Which of the 4 visual icons do users associate with the di erent p p privacy ratings?
2. Which of the 4 visual icons do users associate with the di erent p p privacy rating
explanations?
3</p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>We conducted three online studies to assess how people would interpret the various privacy
rating indicators o ered by the p p email encryption system. Table 3 provides an overview of
the user test sessions, the number of participants per session as well as the focus of investigation.</p>
      <p>Session 1
Session 2</p>
      <p>Session 3
Total evaluations</p>
      <sec id="sec-3-1">
        <title>Privacy</title>
        <p>Ratings</p>
      </sec>
      <sec id="sec-3-2">
        <title>Privacy Rating Explanations</title>
        <p>42</p>
        <p>26
The rst part of the study contained a block of 10 questions which asked participants to
choose an icon which according to them best corresponds to a given privacy statement i.e.
rating (see Figure 3 upper part for an example). The second part of the study similarly asked
the participants to match an icon to a privacy rating explanation (see Figure 3 lower part).
The last part of the study asked about demographics. The 10 privacy rating statements and
explanations were drawn from the p p for Thunderbird distribution (Enigmail/p p version
2.0.12 (20190707-1417). To minimize order bias, the sequence of all questions per block was
randomized for each test participant. The order of all answer choices (icons) per question was
also randomized. The studies were administered via Qualtrics4.
3.2</p>
        <sec id="sec-3-2-1">
          <title>Participants</title>
          <p>All participants are relatively tech-savvy, with at least a Bachelor's degree. The participants of
Session 1 and 2 are based in Luxembourg and were recruited at the University of Luxembourg
via an email invitation to participate in a pilot study (Session 1) and during a lecture on
Security Engineering (Session 2). No incentive was o ered to the participants of Sessions 1 and
2. The participants of Session 3 are based in di erent European countries and were recruited
in Portugal during a workshop on User Experience in security and privacy-critical systems. As
a compensation for their participation in the study, all participants of Session 3 were o ered a
commercial license of p p for continued use of their paid apps i.e. the Outlook and Android
distributions.
3.3</p>
        </sec>
        <sec id="sec-3-2-2">
          <title>Analysis</title>
          <p>We performed a comparative analysis to understand if our participants associated icons to the
various privacy ratings and explanations in the same way as implemented by p p. If the icon
chosen by the majority of participants is the same as the one chosen by p p, the alignment
test for that rating or explanation equals \MATCH", and otherwise \NO MATCH".</p>
          <p>The Match strength refers to how many participants selected the same icon as p p. Hence,
the higher the match, the narrower the gap between what the developers wanted to communicate
via the system and what the users understood. Similarly, the lower the match, the higher the
ambiguity of the intended privacy indicator.</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Results</title>
      <p>Understanding why there is a dichotomy between what the developers wanted to convey with
the di erent privacy indicators in p p and how prospective users would interpret them, or
which privacy indicators could be better in narrowing this chasm, is not in the scope of this
investigation. Nevertheless, we hypothesize that the following elements potentially play a role:
the shapes of the indicators
the colours of the indicators
the tra c light metaphor used for the indicators
the choice of words in the statements and explanations
the perception of risk associated with the shapes, colours, metaphor and wordings of the
indicators
the clustering of risks
the understandability of the indicators
the awareness and concern about di erent scenarios and privacy ratings
(For each item, the match strength refers to the percentage of participants that
associated an icon to a statement or explanation in the same fashion as it is currently implemented
by p p.)</p>
      <p>
        It is often the case that visual input tends to dominate other modalities when it comes to our
perceptual and memorial judgements [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Colour is one of the characteristics of human visual
perception that can carry important meaning and can have an important impact on peoples
a ect, cognition, and behaviour [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. According to Elliot &amp; Maier's colour-in-context theory [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
some colour meanings and e ects are biologically-based, while others are posited to stem from
the repeated pairing of colour and particular concepts, messages, and experiences. They state
that observing colour-meaning associations over time and cultures can contribute to reinforcing
and extending the applicability of those links to objects in the broader environment, such as
signs and signals. We did not have the opportunity to perform this investigation with existing
p p users. We would be interested in comparing such results with the current ndings and
looking at the role of experience with the system on the interpretation of the privacy ratings
and indicators.
      </p>
      <p>
        Disregarding some regional variations, tra c signs and tra c lights are now found all over
the world, and their meaning is internationally recognizable. The corresponding tra c light
rating system (red, amber, green) is something we have repurposed in many di erent domains,
from nutrition labels for pre-packed products [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] to energy consumption labeling [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] and project
management status reporting [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], to name a few. In that respect, the provision of the tra c light
colour codes can serve to communicate more accurate, relevant, and comparable information
to users, as well as to transmit certain levels of risk or allow for a quick recognition of potential
hazards.
      </p>
      <p>
        Nevertheless, while signs and pictograms have been standardized in speci c areas, in many
di erent contexts harmonized communication or a shared understanding of the risk
communicated by signs, symbols, or colours cannot be taken for granted [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ]. The reasons can range
from cross-cultural di erences [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ] to varying levels of technical expertise within a speci c
domain. Research on human aspects in the context of end-to-end email encryption suggests that
non-expert users have incomplete threat models and a general absence of understanding of the
email architecture [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. As expressed in Section 1, the number of di erent situations that arise
in secure email is not so small. Deciding which ones and how many to represent graphically, as
well as, which metaphor to use, is not an easy choice. There is probably not a straightforward
answer and there is de nitely not a unique one. There are di ering views about how transparent
should systems for end-to-end email encryption be [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref20">20</xref>
        ]. In the case of Item 9, it is evident
that p p attempts to nd the balance between these two approaches: on the one hand they
would like to instill a sense of security provided by the automatic end-to-end encryption akin
to other secure messaging and emailing systems, but on the other hand, they would still like
to warn the user of potential threats such as a man-in-the-middle attack that they could be
susceptible to if they do not verify the corresponding party via a second secure channel (e.g.
by comparing the trustwords in person or over the phone).
      </p>
      <p>
        While over time, we are likely going to recognize more consistency in the symbols used
by security and privacy-critical systems, widely-available UI kits or even standardized icon
sets, in the immediate term, developers of such systems should devote an equal amount of
attention and resources to understanding their (target) users and the di erent dimensions and
requirements of their socio-technical proposition. As a starting point, developers, and especially
teams without user research/UX pro les, should inform themselves of the general paradigms
and design principles that align security and usability [
        <xref ref-type="bibr" rid="ref13 ref23">23, 13</xref>
        ], followed by more recent lessons
learnt in this highly-challenging domain that brings together the usable security, HCI and UX
disciplines. Fine-grained inspiration could perhaps be drawn from the vast body of work on
browser security indicators and warnings (e.g. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]), in particular, the incremental user-centred
approach where proposed designs and changes were validated with thousands of users. Caplin's
book [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] could potentially be a useful reference to some developers in the speci c context of
icons in computer interface design, however, as pointed out by Felt et al. "Millions of Internet
users have recently come online via smartphones without learning 'standard' iconography from
desktop browsers" [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], thus it is important to acknowledge that the expectations of users in
terms of interfaces are not necessarily associated with desktop computing and, in many cases,
obsolete metaphors.
6
      </p>
    </sec>
    <sec id="sec-5">
      <title>Conclusion and Future Work</title>
      <p>We reported on a 42-participant study of users' perceptions of email privacy ratings in the
context of pretty Easy privacy. Although our preliminary study has an evident limitation
mainly due to the limited sample size, the outcome suggests that prospective or rst-time p p
users would have a di culty understanding the privacy information communicated by p p.</p>
      <p>The ndings call for a broader and deeper investigation that would seek to assert which
design choices in terms of the privacy rating statement, explanation and visual icon (shape,
colour, metaphor etc.) would need to be reconsidered if p p would like to accurately
communicate the degree of protection that it o ers to its users as they send and receive email through
its system bearing in mind their experience, awareness and concerns. Our work has triggered
a deeper discussion at p p on the existing icon design choices and a potential overhaul of the
privacy indicators is being deliberated.</p>
      <p>From a broader perspective we believe that further and more holistic analyses of the di erent
secure communication systems would be needed in order to identify the di erent types and
degrees of security information communicated by those systems, the e ectiveness of the deployed
security and privacy indicators as well as their suitability for target audiences with di erent
characteristics and levels of expertise.</p>
      <p>We are of the opinion that despite looking trivial, this interaction experience should not
be in the way of users adopting systems for end-to-end email encryption, let alone a source of
confusion or frustration that could result in unsecure behavior or unwanted leakage of con
dential information. This is particularly relevant within an organizational setting, where policy
and culture may also contribute towards the way users go about employing end-to-end email
encryption.
7</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>Authors are supported by the Luxembourg National Research Fund through grant PRIDE15/
10621687/SPsquared, and the project pEp Security SA / SnT Protocols for Privacy Security
Analysis. We would like to thank the p p team for their collaboration, input and feedback
in this project, as well as, the participants of the Human-centered cybersecurity workshop
at CHItaly 2019 for the fruitful discussions. Last but not least, we would like to thank the
anonymous reviewers at ITASEC 2020 for their comments and suggestions for improvement.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Erinn</given-names>
            <surname>Atwater</surname>
          </string-name>
          , Cecylia Bocovich, Urs Hengartner, Ed Lank, and
          <string-name>
            <given-names>Ian</given-names>
            <surname>Goldberg</surname>
          </string-name>
          . Leading Johnny to Water:
          <article-title>Designing for Usability and Trust</article-title>
          . pages
          <fpage>69</fpage>
          {
          <fpage>88</fpage>
          . USENIX Association,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>Steve</given-names>
            <surname>Caplin</surname>
          </string-name>
          . ICON Design:
          <article-title>Graphic Icons in Computer Interface Design</article-title>
          .
          <string-name>
            <surname>Watson-Guptill</surname>
            <given-names>Publications</given-names>
          </string-name>
          , Inc., USA,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Albese</given-names>
            <surname>Demjaha</surname>
          </string-name>
          , Jonathan Spring, Ingolf Becker, Simon Parkin, and
          <string-name>
            <given-names>M Angela</given-names>
            <surname>Sasse</surname>
          </string-name>
          .
          <article-title>Metaphors considered harmful ? An exploratory study of the e ectiveness of functional metaphors for endto-end encryption</article-title>
          .
          <source>(February):</source>
          <volume>1</volume>
          {
          <fpage>12</fpage>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Rachna</given-names>
            <surname>Dhamija</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. D.</given-names>
            <surname>Tygar</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Marti</given-names>
            <surname>Hearst</surname>
          </string-name>
          .
          <article-title>Why phishing works</article-title>
          .
          <source>In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, CHI '06</source>
          , pages
          <fpage>581</fpage>
          {
          <fpage>590</fpage>
          , New York, NY, USA,
          <year>2006</year>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>Andrew J</given-names>
            <surname>Elliot and Markus A Maier. Chapter</surname>
          </string-name>
          two
          <article-title>- Color-in-Context Theory</article-title>
          . volume
          <volume>45</volume>
          of Advances in Experimental Social Psychology, pages
          <volume>61</volume>
          {
          <fpage>125</fpage>
          . Academic Press,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Andrew J</given-names>
            <surname>Elliot and Markus A Maier. Color Psychology</surname>
          </string-name>
          :
          <article-title>E ects of Perceiving Color on Psychological Functioning in Humans</article-title>
          .
          <source>Annual Review of Psychology</source>
          ,
          <volume>65</volume>
          (
          <issue>1</issue>
          ):
          <volume>95</volume>
          {120, jan
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>C. N.</given-names>
            <surname>Enoch</surname>
          </string-name>
          and
          <string-name>
            <given-names>L.</given-names>
            <surname>Labuschagne</surname>
          </string-name>
          .
          <article-title>Project portfolio management: using fuzzy logic to determine the contribution of portfolio components to organizational objectives</article-title>
          .
          <source>Paper presented at PMI Research and Education Conference</source>
          , Limerick, Munster, Ireland. Project Management Institute, Newtown Square, PA,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>EU. Regulation (EU</surname>
          </string-name>
          )
          <year>2016</year>
          /
          <article-title>679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data</article-title>
          .
          <source>O cial Journal of the European Union, L119:1{88</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>EU. Regulation (EU</surname>
          </string-name>
          )
          <year>2017</year>
          /
          <article-title>1369 of the European Parliament and of the Council of 4 July 2017 setting a framework for energy labelling</article-title>
          and
          <source>repealing Directive</source>
          <year>2010</year>
          /30/EU (
          <article-title>Text with EEA relevance</article-title>
          . ).
          <source>O cial Journal of the European Union, L198:1{23</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Michael</surname>
            <given-names>W Eysenck.</given-names>
          </string-name>
          <article-title>Cognitive psychology : a student's handbook</article-title>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>Adrienne</given-names>
            <surname>Porter</surname>
          </string-name>
          <string-name>
            <surname>Felt</surname>
          </string-name>
          , Robert W Reeder, Alex Ainslie, Helen Harris, Max Walker, Christopher Thompson, Mustafa Emre Acer, Elisabeth Morant, Sunny Consolvo, and
          <string-name>
            <given-names>U C</given-names>
            <surname>Berkeley. Rethinking Connection Security Indicators</surname>
          </string-name>
          .
          <source>the Symposium On Usable Privacy and Security (SOUPS)</source>
          ,
          <source>(Soups):</source>
          <volume>1</volume>
          {
          <fpage>14</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Batya</surname>
            <given-names>Friedman</given-names>
          </string-name>
          , David Hurley, Daniel C. Howe,
          <string-name>
            <given-names>Edward</given-names>
            <surname>Felten</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Helen</given-names>
            <surname>Nissenbaum</surname>
          </string-name>
          .
          <article-title>Users' conceptions of web security: A comparative study</article-title>
          .
          <source>In CHI '02 Extended Abstracts on Human Factors in Computing Systems, CHI EA '02</source>
          , pages
          <fpage>746</fpage>
          {
          <fpage>747</fpage>
          , New York, NY, USA,
          <year>2002</year>
          . ACM.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <surname>Simson</surname>
            <given-names>L.</given-names>
          </string-name>
          <article-title>Gar nkel. Design Principles and Patterns for Computer Systems That Are Simultaneously Secure and Usable</article-title>
          .
          <source>PhD thesis</source>
          , Massachusetts Institute of Technology,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Ralph</surname>
            <given-names>B Hupka</given-names>
          </string-name>
          , Zbigniew Zaleski, Jurgen Otto, Lucy Reidl, and Nadia V Tarabrina.
          <article-title>The Colors of Anger, Envy, Fear, and Jealousy: A Cross-Cultural Study</article-title>
          .
          <source>Journal of Cross-Cultural Psychology</source>
          ,
          <volume>28</volume>
          (
          <issue>2</issue>
          ):
          <volume>156</volume>
          {
          <fpage>171</fpage>
          ,
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Joscha</surname>
            <given-names>Lausch</given-names>
          </string-name>
          , Oliver Wiese, and
          <string-name>
            <given-names>Volker</given-names>
            <surname>Roth</surname>
          </string-name>
          .
          <source>What is a Secure Email? EuroUSEC</source>
          <year>2017</year>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <surname>Hern</surname>
          </string-name>
          <article-title>^ani Marques and Bernie Hoeneisen. pretty Easy privacy (pEp):</article-title>
          <source>Mapping of Privacy Rating</source>
          ,
          <year>2019</year>
          . IETF Internet-Draft, https://tools.ietf.org/html/draft-marques
          <string-name>
            <surname>-</surname>
          </string-name>
          pep-rating-
          <volume>01</volume>
          , Accessed:
          <volume>30</volume>
          <year>June 2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>United</given-names>
            <surname>Nations</surname>
          </string-name>
          .
          <article-title>Globally harmonized system of classi cation and labelling of chemicals (GHS) - sixth revised edition</article-title>
          .
          <source>2015. Accessed: 30 June</source>
          <year>2019</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Michael</surname>
            <given-names>I. Posner</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Mary J.</given-names>
            <surname>Nissen</surname>
          </string-name>
          , and
          <string-name>
            <surname>Raymond</surname>
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Klein</surname>
          </string-name>
          .
          <article-title>Visual dominance: An informationprocessing account of its origins and signi cance</article-title>
          .
          <source>Psychological Review</source>
          ,
          <volume>83</volume>
          (
          <issue>2</issue>
          ):
          <volume>157</volume>
          {
          <fpage>171</fpage>
          ,
          <year>1976</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <surname>Karen</surname>
            <given-names>Renaud</given-names>
          </string-name>
          , Melanie Volkamer, and
          <string-name>
            <surname>Arne</surname>
          </string-name>
          Renkema-Padmos.
          <article-title>Why Doesn't Jane Protect Her Privacy</article-title>
          ? In Emiliano De Cristofaro and Steven J Murdoch, editors,
          <source>Privacy Enhancing Technologies</source>
          , pages
          <volume>244</volume>
          {
          <fpage>262</fpage>
          ,
          <string-name>
            <surname>Cham</surname>
          </string-name>
          ,
          <year>2014</year>
          . Springer International Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>Scott</given-names>
            <surname>Ruoti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Je</given-names>
            <surname>Andersen</surname>
          </string-name>
          , Scott Heidbrink,
          <string-name>
            <surname>Mark O'Neill</surname>
            , Elham Vaziripour, Justin Wu, Daniel Zappala, and
            <given-names>Kent</given-names>
          </string-name>
          <string-name>
            <surname>Seamons</surname>
          </string-name>
          .
          <article-title>"We'Re on the Same Page": A Usability Study of Secure Email Using Pairs of Novice Users</article-title>
          .
          <source>CHI '16</source>
          , pages
          <fpage>4298</fpage>
          {
          <fpage>4308</fpage>
          . ACM,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Tonya L Smith-Jackson</surname>
          </string-name>
          and
          <article-title>Michael S Wogalter. Users' hazard perceptions of warning components: An examination of colors and symbols</article-title>
          .
          <source>Proceedings of the Human Factors and Ergonomics Society Annual Meeting</source>
          ,
          <volume>44</volume>
          (
          <issue>32</issue>
          ):
          <volume>6</volume>
          {
          <issue>55</issue>
          {6{
          <fpage>58</fpage>
          ,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <article-title>UK Department of Health and Social Care</article-title>
          .
          <article-title>Guide to creating a front of pack (FoP) nutrition label for pre-packed products sold through retail outlets</article-title>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <surname>Ka-Ping Yee</surname>
          </string-name>
          .
          <article-title>Aligning security and usability</article-title>
          .
          <source>IEEE Security &amp; Privacy</source>
          ,
          <volume>2</volume>
          (
          <issue>5</issue>
          ):
          <volume>48</volume>
          {
          <fpage>55</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>