User Notice: Difference between revisions
Jump to navigation
Jump to search
| (4 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* [https://dl.acm.org/doi/10.1145/2638728.2641681 Usable consents: tracking and managing use of personal data with a consent transaction receipt] was published by Mark Lazar and Mary Hodder on 2014-09 at UbiComp '14 | * [https://dl.acm.org/doi/10.1145/2638728.2641681 Usable consents: tracking and managing use of personal data with a consent transaction receipt] was published by Mark Lazar and Mary Hodder on 2014-09 at UbiComp '14 | ||
* [https://kantarainitiative.org/confluence/display/infosharing/2014/07/13/Open+Notice+Registry+Data+Flows Open Notice Registry Data Flows] was contributed to the Kantara Consent and Information Sharing work group by John Wunderlich on 2014-07-13) | * [https://kantarainitiative.org/confluence/display/infosharing/2014/07/13/Open+Notice+Registry+Data+Flows Open Notice Registry Data Flows] was contributed to the Kantara Consent and Information Sharing work group by John Wunderlich on 2014-07-13) | ||
* Dazza Greenwood opened Open Notice project at MIT law on 2014-09-12 with great fanfare, but little progress was made after the grand goals were established. The only remaining evidence is this [https://github.com/OpenNotice/ConceptualArchitecture this Bithub repository'] | |||
==Problems== | ==Problems== | ||
* Users are not used to receiving and maintaining information about their accounts online. In general they relay on getting state of their account by going online, typically to the merchant that maintains an account for them. | * Users are not used to receiving and maintaining information about their accounts online. In general they relay on getting state of their account by going online, typically to the merchant that maintains an account for them. | ||
* No amount of grand designs or lofty goal have made any impact on the user's ability to see their account status at website. The users seem to have little incentive to take any effort to take control of their own data. | |||
==Solutions== | ==Solutions== | ||
* Giving user's more control of their own information must be included in some other value proposition before users will take any effort to exert their own control. | |||
==References== | ==References== | ||
[[Category:Glossary]] | [[Category:Glossary]] | ||
[[Category:Notice]] | |||
Latest revision as of 16:16, 27 May 2020
Full Title or Meme
User's have the right to notification of disclosures of the private information.
Context
- Privacy regulations now require Data Controllers to notify the users or
- the Consent Receipt should be considered as the initial messaged from the Data Controller to the user.
- User recovery and redress is dependent on no User Notice for operations.
Open Notice
The effort that resulted in the* Consent Receipt was the first of open notice messages.
- Usable consents: tracking and managing use of personal data with a consent transaction receipt was published by Mark Lazar and Mary Hodder on 2014-09 at UbiComp '14
- Open Notice Registry Data Flows was contributed to the Kantara Consent and Information Sharing work group by John Wunderlich on 2014-07-13)
- Dazza Greenwood opened Open Notice project at MIT law on 2014-09-12 with great fanfare, but little progress was made after the grand goals were established. The only remaining evidence is this this Bithub repository'
Problems
- Users are not used to receiving and maintaining information about their accounts online. In general they relay on getting state of their account by going online, typically to the merchant that maintains an account for them.
- No amount of grand designs or lofty goal have made any impact on the user's ability to see their account status at website. The users seem to have little incentive to take any effort to take control of their own data.
Solutions
- Giving user's more control of their own information must be included in some other value proposition before users will take any effort to exert their own control.