<div dir="auto">Interesting!<div dir="auto"><br></div><div dir="auto">I suppose it depends on if it was a private email address, or one sent from public office?</div><div dir="auto"><br></div><div dir="auto">You might expect different institutions having different defaults. Think of those firms or agencies that today add large notices to emails saying: don't forward this, if you are an unintended recipient then that's bad, etc. Totally unenforceable, but it serves some legal CYA logic nevertheless. A lot of cyber laws are about *trying hard enough* to protect information in order for *further legal protections* to take hold. Enforcement could be moved to the email client, adding a "this is a special email, are you sure you want to forward it?</div><div dir="auto"><br></div><div dir="auto">I see an analogy to consent management systems (CMP). Suppose a user wants to set a bunch of preferences on their email client for uses of downstream data. Some are "necessary" uses -- operating the email server, for example. Some are not and can be "turned off"....</div><div dir="auto"><br></div><div dir="auto">Expressing that consent is intended to help people exercise their rights (in Europe, that is, especially under DGA now). But those rights are qualified by the law. If I use a CMP to prevent cookie usage beyond necessary doesn't mean that, say, law enforcement couldn't use that data with a warrant, right? There could be similar provisions for the public official. The header would mean something like consent, but there would be legal situations that supercede consent.</div><div dir="auto"><br></div><div dir="auto">This is connected to another issue which a colleague has brought to my attention some time ago, which is the strange situation we are in where a smart device "user agent" is considered to legally represent us. Why is that?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 23, 2022, 8:59 AM Niels ten Oever <<a href="mailto:mail@nielstenoever.net">mail@nielstenoever.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Adding to this discussion:<br>
<br>
What if an important policy maker puts the flag 'do-not-process' in an email header but we would have legitimate interests, because they are a policymaker/politician, to process it? This might create more confusion that it solves?<br>
<br>
<br>
<br>
On 23-09-2022 14:39, Sebastian Benthall wrote:<br>
> I also can't make the meeting, because of the PrivaCI Symposium.<br>
> <br>
> At it, Michael Froomkin pitched an argument about email privacy, mainly about how email addresses can sometimes over identify, and sometimes under identify, and arguing that there should be a (standardized) identity layer built over the email transport layer. He was initially skeptical about changing email but I think I convinced him an optional header might be doable and part of a solution.<br>
> <br>
> It might be worth giving the issue more thought. We were talking about a "do not process" flag for email, or maybe a header that explicitly consents to some processing purposes and not others. But it might be that the possibility of attributing email, linking it to other identifiers, is an important issue.<br>
> <br>
> On Fri, Sep 23, 2022, 6:42 AM Priyanka Sinha <<a href="mailto:priyanka.sinha.iitg@gmail.com" target="_blank" rel="noreferrer">priyanka.sinha.iitg@gmail.com</a> <mailto:<a href="mailto:priyanka.sinha.iitg@gmail.com" target="_blank" rel="noreferrer">priyanka.sinha.iitg@gmail.com</a>>> wrote:<br>
> <br>
> Hi,<br>
> <br>
> Me neither. Got caught up again.<br>
> <br>
> I asked about the privacy header in other groups, and there is an interesting conundrum of whether enterprise e-mail and laptop are allowed to have private e-mail or conversation.<br>
> <br>
> Especially in today's enterprise climate of hybrid work, expensive hardware, stringent network policies, large enterprises where family and friends work.<br>
> <br>
> Riccardo, looking forward to seeing you in a future meeting.<br>
> <br>
> Thanks and Regards,<br>
> -priyanka<br>
> <br>
> See you at the next<br>
> <br>
> Date: Fri, 23 Sep 2022 08:45:30 +0000<br>
> From: Riccardo Nanni <<a href="mailto:riccardo.nanni9@unibo.it" target="_blank" rel="noreferrer">riccardo.nanni9@unibo.it</a> <mailto:<a href="mailto:riccardo.nanni9@unibo.it" target="_blank" rel="noreferrer">riccardo.nanni9@unibo.it</a>>><br>
> To: "<a href="mailto:bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">bigbang-dev@data-activism.net</a> <mailto:<a href="mailto:bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">bigbang-dev@data-activism.net</a>>" <<a href="mailto:bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">bigbang-dev@data-activism.net</a> <mailto:<a href="mailto:bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">bigbang-dev@data-activism.net</a>>><br>
> Subject: [Bigbang-dev] Today's meeting<br>
> Message-ID:<br>
> <<a href="mailto:AM6PR0102MB3208C29E0C6423EB5AF88942C4519@AM6PR0102MB3208.eurprd01.prod.exchangelabs.com" target="_blank" rel="noreferrer">AM6PR0102MB3208C29E0C6423EB5AF88942C4519@AM6PR0102MB3208.eurprd01.prod.exchangelabs.com</a> <mailto:<a href="mailto:AM6PR0102MB3208C29E0C6423EB5AF88942C4519@AM6PR0102MB3208.eurprd01.prod.exchangelabs.com" target="_blank" rel="noreferrer">AM6PR0102MB3208C29E0C6423EB5AF88942C4519@AM6PR0102MB3208.eurprd01.prod.exchangelabs.com</a>>><br>
> <br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
> <br>
> Hi there!<br>
> Again, I can't make it today... I have an overlapping meeting. Sorry!<br>
> Cheers,<br>
> <br>
> Riccardo<br>
> <br>
> _______________________________________________<br>
> Bigbang-dev mailing list<br>
> <a href="mailto:Bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">Bigbang-dev@data-activism.net</a> <mailto:<a href="mailto:Bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">Bigbang-dev@data-activism.net</a>><br>
> <a href="https://lists.ghserv.net/mailman/listinfo/bigbang-dev" rel="noreferrer noreferrer" target="_blank">https://lists.ghserv.net/mailman/listinfo/bigbang-dev</a> <<a href="https://lists.ghserv.net/mailman/listinfo/bigbang-dev" rel="noreferrer noreferrer" target="_blank">https://lists.ghserv.net/mailman/listinfo/bigbang-dev</a>><br>
> <br>
> <br>
> _______________________________________________<br>
> Bigbang-dev mailing list<br>
> <a href="mailto:Bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">Bigbang-dev@data-activism.net</a><br>
> <a href="https://lists.ghserv.net/mailman/listinfo/bigbang-dev" rel="noreferrer noreferrer" target="_blank">https://lists.ghserv.net/mailman/listinfo/bigbang-dev</a><br>
<br>
-- <br>
Niels ten Oever, PhD<br>
Postdoctoral Researcher - Media Studies Department - University of Amsterdam<br>
Affiliated Faculty - Digital Democracy Institute - Simon Fraser University<br>
Non-Resident Fellow 2022-2023 - Center for Democracy & Technology<br>
Associated Scholar - Centro de Tecnologia e Sociedade - Fundação Getúlio Vargas<br>
Research Fellow - Centre for Internet and Human Rights - European University Viadrina<br>
<br>
Vice chair - Global Internet Governance Academic Network (GigaNet)<br>
<br>
W: <a href="https://nielstenoever.net" rel="noreferrer noreferrer" target="_blank">https://nielstenoever.net</a><br>
E: <a href="mailto:mail@nielstenoever.net" target="_blank" rel="noreferrer">mail@nielstenoever.net</a><br>
T: @nielstenoever<br>
P/S/WA: +31629051853<br>
PGP: 2458 0B70 5C4A FD8A 9488 643A 0ED8 3F3A 468A C8B3<br>
<br>
Read my latest article on understanding power in standardization in the Journal of Standardisation here: <a href="https://journals.open.tudelft.nl/jos/article/view/6205/5361" rel="noreferrer noreferrer" target="_blank">https://journals.open.tudelft.nl/jos/article/view/6205/5361</a><br>
<br>
_______________________________________________<br>
Bigbang-dev mailing list<br>
<a href="mailto:Bigbang-dev@data-activism.net" target="_blank" rel="noreferrer">Bigbang-dev@data-activism.net</a><br>
<a href="https://lists.ghserv.net/mailman/listinfo/bigbang-dev" rel="noreferrer noreferrer" target="_blank">https://lists.ghserv.net/mailman/listinfo/bigbang-dev</a><br>
</blockquote></div>