User Consent - Revision history

Tomjones: /* General References */

2020-10-30T00:14:53Z

General References

← Older revision		Revision as of 00:14, 30 October 2020
Line 106:		Line 106:
	[[Category:User Experience]]		[[Category:User Experience]]
	[[Category:Privacy]]		[[Category:Privacy]]
			[[Category:Profile]]
	[[Category:Glossary]]		[[Category:Glossary]]

Tomjones: /* Expectations of a Good User Consent Experience */

2020-10-07T04:56:22Z

Expectations of a Good User Consent Experience

← Older revision		Revision as of 04:56, 7 October 2020
Line 16:		Line 16:
	For a good [[User Experience]] the request MUST be in a form that the user can read and understand in only a few seconds.		For a good [[User Experience]] the request MUST be in a form that the user can read and understand in only a few seconds.

	For example if a large number of data categories are required by the web site, there must be some way to abstract the categories into a small number that are clear to most users. For example the [https://developer.android.com/guide/topics/permissions/overview#perm-groups Android ~~Persions~~ list uses groups.of permissions] to reduce the cognitive load on the user.		For example if a large number of data categories are required by the web site, there must be some way to abstract the categories into a small number that are clear to most users. For example the [https://developer.android.com/guide/topics/permissions/overview#perm-groups Android Permissions list uses groups.of permissions] to reduce the cognitive load on the user.

	==The Problem==		==The Problem==

Tomjones: /* Expectations of a Good User Consent Experience */

2020-10-07T04:55:29Z

Expectations of a Good User Consent Experience

← Older revision		Revision as of 04:55, 7 October 2020
Line 16:		Line 16:
	For a good [[User Experience]] the request MUST be in a form that the user can read and understand in only a few seconds.		For a good [[User Experience]] the request MUST be in a form that the user can read and understand in only a few seconds.

	For example if a large number of data categories are required by the web site, there must be some way to abstract the categories into a small number that are clear to most users. For example the [https://developer.android.com/guide/topics/permissions/overview#perm-groups Android Persions list uses groups.of ~~permission~~ to reduce the cognitive load on the user.		For example if a large number of data categories are required by the web site, there must be some way to abstract the categories into a small number that are clear to most users. For example the [https://developer.android.com/guide/topics/permissions/overview#perm-groups Android Persions list uses groups.of permissions] to reduce the cognitive load on the user.

	==The Problem==		==The Problem==

Tomjones: /* Expectations of a Good User Consent Experience */

2020-10-07T04:54:56Z

Expectations of a Good User Consent Experience

← Older revision		Revision as of 04:54, 7 October 2020
Line 13:		Line 13:
	# The user can terminate the relationship with the web site at will and no [[User Private Information]] will be used for any new sharing or transactions after the termination.		# The user can terminate the relationship with the web site at will and no [[User Private Information]] will be used for any new sharing or transactions after the termination.
	# The user can recall what their relationship is or should be with the web site at any time based on information in their possession.		# The user can recall what their relationship is or should be with the web site at any time based on information in their possession.

			For a good [[User Experience]] the request MUST be in a form that the user can read and understand in only a few seconds.

			For example if a large number of data categories are required by the web site, there must be some way to abstract the categories into a small number that are clear to most users. For example the [https://developer.android.com/guide/topics/permissions/overview#perm-groups Android Persions list uses groups.of permission to reduce the cognitive load on the user.

	==The Problem==		==The Problem==

Tomjones: /* Expectations of a Good User Consent Experience */

2020-10-07T04:49:17Z

Expectations of a Good User Consent Experience

← Older revision		Revision as of 04:49, 7 October 2020
Line 7:		Line 7:
	* While this example only considers user attributes that are provided by the user or by some [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute Provider], other sources are likely to occur in real-world scenarios.		* While this example only considers user attributes that are provided by the user or by some [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute Provider], other sources are likely to occur in real-world scenarios.
	===Expectations of a Good User Consent Experience===		===Expectations of a Good User Consent Experience===
	# The user understands exactly what legal entity (and possibly which brand) is represented by the web site.		# The user understands exactly what legal entity (and possibly which brand) is represented by the web site. (In this context a brad or dba can acquire legal status to be considered an entity.
	# The user gets to select which of their identifiers they wish to use with the web site.		# The user gets to select which of their identifiers they wish to use with the web site.
	# The user understands what [[User Private Information]] is requested by the web site and which specific items are required to do transactions with the web site.		# The user understands what [[User Private Information]] is requested by the web site and which specific items are required to do transactions with the web site.

Tomjones: /* References and Coordination */

2020-07-25T17:30:43Z

References and Coordination

← Older revision		Revision as of 17:30, 25 July 2020
Line 86:		Line 86:

	==References and Coordination==		==References and Coordination==
			* See also wiki page on [[Consent Grant]].

	===Health Care Specific===		===Health Care Specific===
	*Emergency Override is required by health care workers in Emergency Rooms or Ambulances that need specific information to save the subject's life.		*Emergency Override is required by health care workers in Emergency Rooms or Ambulances that need specific information to save the subject's life.

Tomjones: /* References and Coordination */

2020-07-10T19:59:56Z

References and Coordination

← Older revision		Revision as of 19:59, 10 July 2020
Line 80:		Line 80:
	*Authentication protocols, such as OpenID Connect, require user consent before any information is released to relying parties. This method improves user security and is becoming increasingly common.		*Authentication protocols, such as OpenID Connect, require user consent before any information is released to relying parties. This method improves user security and is becoming increasingly common.
	*From a user experience perspective, perhaps the most successful user consent process is provided by the cell phone operating systems that have created categories of access that seem to have just the right level of specificity that they are both understood by the user and effective in limiting access to [[User Private Information]]. The phone operating systems are also reasonable about giving the users control to change these permissions for the cell phone apps. While most users are unaware of their ability to change the accesses, at least they do exist.		*From a user experience perspective, perhaps the most successful user consent process is provided by the cell phone operating systems that have created categories of access that seem to have just the right level of specificity that they are both understood by the user and effective in limiting access to [[User Private Information]]. The phone operating systems are also reasonable about giving the users control to change these permissions for the cell phone apps. While most users are unaware of their ability to change the accesses, at least they do exist.

			===Extraordinary Access===
			* Also known as emergency access it typically refers to access granted to data by a sovereign (state) power to preserve life or property.
			* While not explicitly a [[User Consent]] scenario, the out come of this type of access should include creation of the sort of [[User Notice]] that is mandated by the other use cases.

	==References and Coordination==		==References and Coordination==

Tomjones: /* The Context */

2020-07-10T19:54:18Z

The Context

← Older revision		Revision as of 19:54, 10 July 2020
Line 3:		Line 3:

	==The Context==		==The Context==
	The working assumption is that users would like to have more control over how their [[User Private Information]] is handled than was possible prior to 2019.		*The working assumption is that users would like to have more control over how their [[User Private Information]] is handled than was possible prior to 2019.
			* Users are represented on the Internet by [[User Agent]]s that communicate with relying parties and a variety of [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute providers].
	Users are represented on the Internet by [[User Agent]]s that communicate with relying parties and a variety of [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute providers].		* While this example only considers user attributes that are provided by the user or by some [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute Provider], other sources are likely to occur in real-world scenarios.

	While this example only considers user attributes that are provided by the user or by some [https://tcwiki.azurewebsites.net/index.php?title=Identifier_or_Attribute_Provider Identifier or Attribute Provider], other sources are likely to occur in real-world scenarios.
	===Expectations of a Good User Consent Experience===		===Expectations of a Good User Consent Experience===
	# The user understands exactly what legal entity (and possibly which brand) is represented by the web site.		# The user understands exactly what legal entity (and possibly which brand) is represented by the web site.

Tomjones: /* Introduction */

2020-07-10T19:53:19Z

Introduction

← Older revision		Revision as of 19:53, 10 July 2020
Line 1:		Line 1:
	==Introduction==		==Introduction==
	The page describes some ways how identity ecosystems might enable and track ~~user consent~~ for compliant sites in a manner that the average user might be able to understand and tolerate.		The page describes some ways how identity ecosystems might enable and track [[User Consent]] for compliant sites in a manner that the average user might be able to understand and tolerate.

	==The Context==		==The Context==

Tomjones: /* Health Care Specific */

2020-04-17T01:03:31Z

Health Care Specific

← Older revision		Revision as of 01:03, 17 April 2020
Line 85:		Line 85:
	==References and Coordination==		==References and Coordination==
	===Health Care Specific===		===Health Care Specific===
	Emergency Override is required by health care workers in Emergency Rooms or Ambulances that need specific information to save the subject's life.		*Emergency Override is required by health care workers in Emergency Rooms or Ambulances that need specific information to save the subject's life.
			* The wik page [[Patient Consent]] Provides more detail

	===General References===		===General References===