<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello all,</p>
    <p>Not sure if I'm qualify to comment on it since I never an ICANN
      fellow but super agree with Dina and Cedric. <br>
    </p>
    <p>I do not think FB or WhatsApp etc are optional or should be
      voluntarily to join the group when all the important info shared
      over there - experience with APIGA & some fellowship
      programmes, while the mentors/coaches are sharing the tasks and
      info there. If you're not in the group, you might be missing
      something else important. <br>
    </p>
    <p>For APrIGF, we do have the whatsapp group, but it's for casual
      chats and bonding - that I would call it something voluntarily and
      optional. Our secretariat shares the info and task over
      mailing-list, no personal info shared on the list etc. <br>
    </p>
    <p>Besides, that's also lotsa good & free open source platforms
      in the market to use for grouping thing such as mattermost. I do
      agreed with Dina that the fellowship committee need a workshop on
      this, I mean, not only them but group like us in NCUC also. :)</p>
    <p>2 cents.</p>
    <p>Cheers,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 11/08/2017 12:01 AM, Seun Ojedeji
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAD_dc6gN=7mGfJzzyZp2-qWPwSh4nF8GoZcyEVeGXoBgG-kDMw@mail.gmail.com">
      <div dir="auto">Hello,
        <div dir="auto"><br>
        </div>
        <div dir="auto">If I recall correctly, I don't think ICANN
          flicker site requires login details.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">As to the fellowship Facebook, WhatsApp et all I
          do think those are optional hence it should be expected that
          anyone that opts in do so voluntarily.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Ofcourse I am speaking as an alumni hence some
          things may have changed lately.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Regards<br>
          <br>
          <div data-smartmail="gmail_signature" dir="auto">Sent from
            my mobile<br>
            Kindly excuse brevity and typos</div>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Nov 7, 2017 4:47 PM, "Stephanie
          Perrin" <<a href="mailto:stephanie.perrin@mail.utoronto.ca"
            moz-do-not-send="true">stephanie.perrin@mail.utoronto.ca</a>>
          wrote:<br type="attribution">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF">
              <p><font size="+1"><font face="Lucida Grande">Dina</font></font></p>
              <p><font size="+1"><font face="Lucida Grande">I totally
                    agree with you and Cedric, and suggest you file a
                    complaint to the new ICANN privacy officer.  Happy
                    to help draft it!</font></font></p>
              <p><font size="+1"><font face="Lucida Grande">Stephanie
                    Perrin</font></font></p>
              <p><font size="+1"><font face="Lucida Grande">PS I had
                    already complained to ICANN years ago that they
                    should not be using the outlet they use for posting
                    their professional photos of ICANN meetings, as it
                    demanded you join and provide a cellphone number. 
                    Unacceptable.  (Unfortunately, I cannot remember
                    what app they were using, nor can I find it on the
                    site with a couple of quick searches.)</font></font><br>
              </p>
              <br>
              <div class="m_8702831496277623354moz-cite-prefix">On
                2017-11-06 15:22, Cedric Laurant wrote:<br>
              </div>
              <blockquote type="cite">
                <pre>Unbelievable! This violates the most basic data protection principles.

Thomas, I support your indignation and recommendation.

And relying on tools such as Facebook and WhatsApp shows how inexcusably
unaware of privacy issues the organizers of that Fellowship Program are.

Cédric
---
On 11/6/17 13:41, thomascovenant wrote:
</pre>
                <blockquote type="cite">
                  <pre>Dear all,

I want to point out an issue that is important to me: privacy.

Today the Fellowship Program sent out an email containing an attachment
with coaches' and fellows' private details: name, surname, home address
and phone number.

I see this as gross privacy violation.

I have not given my consent to share my personal details - I expect
every single person on the list to be asked for permission before doing
that. I expect to know exactly who these details will be shared with.

During this round, program has heavily relied on Facebook, Whatsapp
(owned by Facebook) and Google.

I am extremely frustrated by lack of basic privacy awareness within the
Fellowship Program.

I will follow up with TTF to propose an online privacy workshop for
those in charge of the Program, together with the request to review
tools and how fellows' information can be stored and handled in a secure
way.

Respecting privacy of others on this list,

thomas / Dina Solveig Jalkanen



______________________________<wbr>_________________
Ncuc-discuss mailing list
<a class="m_8702831496277623354moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org" target="_blank" moz-do-not-send="true">Ncuc-discuss@lists.ncuc.org</a>
<a class="m_8702831496277623354moz-txt-link-freetext" href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" target="_blank" moz-do-not-send="true">https://lists.ncuc.org/cgi-<wbr>bin/mailman/listinfo/ncuc-<wbr>discuss</a>

</pre>
                </blockquote>
                <br>
                <fieldset
                  class="m_8702831496277623354mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
Ncuc-discuss mailing list
<a class="m_8702831496277623354moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org" target="_blank" moz-do-not-send="true">Ncuc-discuss@lists.ncuc.org</a>
<a class="m_8702831496277623354moz-txt-link-freetext" href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss" target="_blank" moz-do-not-send="true">https://lists.ncuc.org/cgi-<wbr>bin/mailman/listinfo/ncuc-<wbr>discuss</a>
</pre>
              </blockquote>
              <br>
            </div>
            <br>
            ______________________________<wbr>_________________<br>
            Ncuc-discuss mailing list<br>
            <a href="mailto:Ncuc-discuss@lists.ncuc.org"
              moz-do-not-send="true">Ncuc-discuss@lists.ncuc.org</a><br>
            <a
              href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.ncuc.org/cgi-<wbr>bin/mailman/listinfo/ncuc-<wbr>discuss</a><br>
            <br>
          </blockquote>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Ncuc-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Ncuc-discuss@lists.ncuc.org">Ncuc-discuss@lists.ncuc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss">https://lists.ncuc.org/cgi-bin/mailman/listinfo/ncuc-discuss</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>