Mobile Privacy Experience - Revision history

Tom: /* Other Material */

2023-10-25T19:27:49Z

‎Other Material

Tom at 04:56, 19 July 2023

2023-07-19T04:56:13Z

Tom: /* Other Material */

2023-07-19T04:54:20Z

‎Other Material

Tom: /* Other Material */

2023-07-19T04:52:17Z

‎Other Material

Tom: /* Assumptions */

2023-07-11T18:06:29Z

‎Assumptions

Tom: /* Assumptions */

2023-07-11T18:04:21Z

‎Assumptions

Tom at 17:45, 11 July 2023

2023-07-11T17:45:26Z

Tom: /* Context */

2023-07-09T17:20:16Z

‎Context

Tom: /* Assumptions */

2023-07-09T17:12:34Z

‎Assumptions

Tom: /* Context */

2023-07-09T17:04:07Z

‎Context

@@ Line 111: / Line 111: @@
 [[Category: Mobile]]
 [[Category: User Experience]]
 [[Category: Privacy]]

@@ Line 108: / Line 108: @@
 * Also see the wiki page on [[Mobile Driver's License Presentation]] for a use case.
 * Also see the wiki page on [[Consent for Mobile Credentials]] for details on the consent transaction.
-* Also see the wiki page on [[Mobile Driver's License Presentation]] for the way the transaction is presented.
+* Also see the wiki page on [[Mobile Driver's License Presentation]] for the way the transaction is presented in the DIF (SSI) community.
 [[Category: Mobile]]
 [[Category: User Experience]]
 [[Category: Privacy]]

@@ Line 108: / Line 108: @@
 * Also see the wiki page on [[Mobile Driver's License Presentation]] for a use case.
 * Also see the wiki page on [[Consent for Mobile Credentials]] for details on the consent transaction.
 [[Category: Mobile]]
 [[Category: User Experience]]
 [[Category: Privacy]]

@@ Line 107: / Line 107: @@
 * A new work-in-process is a page on [[Mobil Threat Analysis]] to describe what can go wrong.
 * Also see the wiki page on [[Mobile Driver's License Presentation]] for a use case.
 [[Category: Mobile]]
 [[Category: User Experience]]
 [[Category: Privacy]]

@@ Line 15: / Line 15: @@
 ## It may be that transactions or receipts need more detailed consideration.
 # Holders are allowed to configure wallets which may include Issuer or Verifier preferences.
-# Access to any data on a private mobile device by any entity, sovereign or not, without the user knowledge is unacceptable.
+# Access to any data on a private mobile device by any entity, sovereign or not, without the subject's knowledge is unacceptable.
 ==Principles==

@@ Line 18: / Line 18: @@
 ==Principles==
 # The holder is in charge of their own devices, data, settings, limitations, navigation and other behaviors.
-# The issuers hold user data that can be bundled into credentials that the user can request.
+# The issuers hold subject's data that can be bundled into credentials that the holder can request.
-## The issuers have a responsibility to the holders (and subjects) to protect access to user data.
+## The issuers have a responsibility to the holders (and subjects) to protect access to subject data.
-## The issuers must issue credentials that allow user (through their wallets) selective release of any data.
+## The issuers must issue credentials that allow holder (through their wallets) selective release of any data.
-## The issuers must not release user data to wallets that are not trustworthy.
+## The issuers must not release subject data to wallets that are not trustworthy.
 # The verifiers need some evidence of the holder (or subject) to release access to goods or services.
 ## The verifiers have a responsibility to present their identity and purpose for requesting access to data.
@@ Line 27: / Line 27: @@
 ## The wallet must convince both issuers and agents of its trustworthiness by the messages it sends.
 ## The wallet must construct consent screens based on issuer's or verifier's data requests that the holder can understand.
-## Accessibility and user preferences are always accommodated.
+## Accessibility and holder preferences are always accommodated.
 ==Problems==
 # The web is a completely open community that accepts anyone that asks to be included with no checking of Identity.
 ## No website can be trusted without some prior knowledge.
-## The user can expect to be attacked by unscrupulous providers of wallets, issuers and verifiers.
+## The holder can expect to be attacked by unscrupulous providers of wallets, issuers and verifiers.
-# Most users are unfamiliar with technology and the implications of the use of that technology.
+# Most holders are unfamiliar with technology and the implications of the use of that technology.
-# User's requests for more privacy and seldom followed up by any significant change in user behavior. This makes it easy from companies to claim that they offer privacy options that the user can enable but not ensuring that the user has any real choice.
+# Subject's requests for more privacy and seldom followed up by any significant change in Subject's behavior. This makes it easy from companies to claim that they offer privacy options that the holder can enable but not ensuring that the holder has any real choice.
-# Generally attempts to legislate privacy attract lawyers who encourage the legislature to give the lawyers a means to extract settlements from offending companies, without otherwise making any effort to actually improve the user's experience. For one example see the wiki page on [[GDPR is a scam]]. This leads to mitigations that are not at all related to user privacy concerns. The point of the GDPR was to fine multi-nationals and increase the EU revenue.
+# Generally attempts to legislate privacy attract lawyers who encourage the legislature to give the lawyers a means to extract settlements from offending companies, without otherwise making any effort to actually improve the  [[User Experience]]. For one example see the wiki page on [[GDPR is a scam]]. This leads to mitigations that are not at all related to privacy concerns. The point of the GDPR was to fine multi-nationals and increase the EU revenue.
-# Tracking of user's or their devices either in physical space or digital space can expose the full identity is a short time.
+# Tracking of holder's or their devices either in physical space or digital space can expose the full identity is a short time.
-# Aggregation of user's attributes or behaviors will expose a user's full identity in an amazingly short time online.
+# Aggregation of Subject's attributes or behaviors will expose a subject's full identity in an amazingly short time online.
 # Developers that create privacy notices are typically unaware (or unconcerned) about privacy threats.
 # Session state from one connection to another (cookies) allows tracking of the holder of the wallet.
@@ Line 75: / Line 75: @@
 ===Levels===
 The wallet must accommodate both holder experience and legal requirements. These are often incompatible and judgement is needed. The following levels are conceptual and are based on the deviation from the norm similar to a normal distribution, so one could be considered (very roughly) within one standard deviation and so on.
-# Common case the user gets one screen that contains the purpose, a user understandable identity of the verifier (and other data controllers or providers) and the proposed summary data to be released. A user gesture is required to release the data.
+# In the most common case the holder gets one screen that contains the purpose, a holder understandable identity of the verifier (and other data controllers or providers) and the proposed summary data to be released. A holder gesture is required to release the data.
-# The wallet or user decides that more information is required to be evaluated than the one screen can provide.
+# The wallet or holder decides that more information is required to be evaluated than the one screen can provide.
 # The holder wants to see the full data (and metadata) that is to be released to the verifier.
 # The holder wants (or is forced) to view the terms and conditions of the issuer or verifier.
@@ Line 89: / Line 89: @@
 ## Legibility and clarity for the vast majority of holders who might not be well educated in the language used for verifying or have a physical limitation in what they can see.
 ## Privacy labels should be standardized similar to food nutrition labels.
-# Legal requirements are seldom helpful in establishing the user consent page, but are critical in what data is available to any subject who might be one of the very few users that chose to follow-up on their concerns by drilling into the details.
+# Legal requirements are seldom helpful in establishing the a consent page, but are critical in what data is available to any subject who might be one of the very few holders that chose to follow-up on their concerns by drilling into the details.
 ## Apps need to be scrupulously careful about stating what data is collected and what is retained.
 ## Apps must make it easy to retract consent to use or store data where that is legally permissible.

@@ Line 3: / Line 3: @@
 ==Context==
-Current User Experiences with privacy notifications is demonstrably inadequate to the problems created.<ref>Lorrie Faith Cranor, ''Mobile-App Privacy Nutrition Labels Missing Key Ingredients for Success'' '''CACM 65''' No. 11 (2022-11)</ref> Mobile Phones began a campaign to label apps with consumer-friendly labels. The result was panned in papers like the New York Times and Washington Post. Which called the labels confusing and hard to identify as to their purpose.
+Current [[User Experience]]s with privacy notifications is demonstrably inadequate to the problems created.<ref>Lorrie Faith Cranor, ''Mobile-App Privacy Nutrition Labels Missing Key Ingredients for Success'' '''CACM 65''' No. 11 (2022-11)</ref> Mobile Phones began a campaign to label apps with consumer-friendly labels. The result was panned in papers like the New York Times and Washington Post. Which called the labels confusing and hard to identify as to their purpose.
 ===Assumptions===

@@ Line 6: / Line 6: @@
 ===Assumptions===
-# Issuers can be strongly identified to the user so that trust decisions are possible.
+# Issuers can be strongly identified such that holder trust decisions are possible.
 # Verifiers are similarly strongly identified and may be issuers as well.
-# Wallets are permitted to acquire credentials from issuers based on user request only.
+# Wallets are permitted to acquire credentials from issuers based on holder request only.
 # Wallets may create signed credentials on their own behalf as needed.
 ## For example statements about themselves or the holder presence.