2018-10-04 Meeting notes (CR)

From 2018-10-04 call:

• If the legitimate basis is not 'explicit consent' - but rather legitimate interest, is the concept of 'data receipt' still viable?
• Mark - yes, the current CR was designed to be not confined to 'explicit consent' - so yes, the receipt concept will work for other bases for processing
  • in particular - for updates to privacy notices
• Mark Q: would it be interesting to have additional values for the 'consent type' field? A: YES! 
  • Jim: maybe this should go to the Consent Management WG?
• A lawyer at the Seattle event pointed out that it would be useful to capture the actual privacy notice that was agreed by the user.
  • OpenConsent has an alpha product that might suit the purpose
  • There is a systemic problem that needs to be addressed - and capturing the privacy notice won't actually help
  • If there is a strong need for a high value receipt, then it would be very useful to capture the actual notice text
  • So maybe the receipt could have optionality to allow for capture of the notice text.
• WG needs to take some time to discuss the UX - schedule it
  • Tom has posted some examples that could be discussed
  • Mark - OpenBanking has posted UX guidance
• Schedule specific multiple calls for this to discuss what the user should see, and how this translates into the 'receipt' concept
  • Should this WG do a spec or guidance on UX or UI?
  • Should this WG talk about what the 'receipt' means and / or represents?
  • (YES to both question)
• Andrew: suggests first design call on Thursday October 18, 2019 and then every 4 weeks to be kind to the down-under-ers.

From 2018-09-27 call:

See the data flow sketch that Andrew circulated by email

This diagram shows ALL data flows, despite the legitimate basis for processing. The idea is that given this data flow diagram, what are the functions, nouns and verbs for each of the legitimate bases?

Q: How would enforcement work?

Q: What's the difference between 'observe' and 'surveil'? A: Depends on if the user is aware of it or not.

Also see from our archives:

https://kantarainitiative.org/iain-henderson-the-personal-data-eco-system/

The 'my data', 'our data', 'their data' view

Comment Brent: in a social network, what roles do the different actors take? eg if I share an image, what role does the website take, what role do the users who can view my image take? also, how do I represent those rules where I restrict access to my data based on roles or groups I assign to my connections? how do I represent that implicit consent using consent receipts without knowing explicitly who I am granting permission to?

Comment: This picture looks very corporate - must ensure that the individual's perspective is very clear

Comment: The 'interface' for the individual should not be the 'consent receipt' itself - but rather the interaction with the service.

JLINC perspective: Alice grants permission and organization seeks consent. Alice only sees permissions.

Comment: this discussion is oriented towards 'explicit' consent. But all interaction has some level of agreement.

Iain: the highest value work item is the lexicon work