Re: [meetings] Utility vs Privacy for attribution proposals (#25)

@bmilekic During the process, I think the privacy and security characteristics should be discussed. Of course, when you make a product and work on privacy matter, you could get a risk of overthinking and even rewriting the law. But if we do not consider it during the process and seriously, we could get a finale product without enough privacy and security characteristics to be used or could be used only in some geo area. That would be great to make products that can be used in any area from the trial period to live release.

> Sure, and apologies for the lack of clarity. What I meant is that I think that it's easier to analyze the proposals in terms of utility that each provides, without thinking too much about their privacy and security characteristics. This does not mean that the privacy and security principles and characteristics are unimportant or that we should not consider them, just that they can be looked at and discussed in parallel.

If the product does not require specific "_help_" from the user, we can fully expand on those three points. But for example, most of the products need to store some info about the user in the browser and according to GDPR, you need to get the consent. Just taking this example and creating a product, the use and the result can be tricked. And then come to the discussion about Opt-in / Opt-out by default... Need to find the right balance in this slide but we cannot omit that.

> I initially created this issue because when I looked at @csharrison attribution reporting design space tradeoffs and considerations slides, the third slide "Privacy vs Utility" lists "timely, fine-grained, accurate" as examples of utility, and I thought it would be good to expand on those three points further, to get a more detailed view of how the proposals compare w.r.t. utility provided.

It's worth doing and we need it in order to restore the trust around advertising ecosystem

-- 
GitHub Notification of comment by anderagakura
Please view or discuss this issue at https://github.com/patcg/meetings/issues/25#issuecomment-1038862957 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 14 February 2022 09:37:17 UTC