W3C home > Mailing lists > Public > public-credentials@w3.org > April 2020

Re: Google and Apple announce privacy-preserving contact tracing API

From: Alex Puig <alex@caelumlabs.com>
Date: Fri, 10 Apr 2020 22:04:42 +0200
Message-ID: <CAHdUGAErHKz6jkeEXszRoeGa1o4tyUW0XgHdnR2JBB_zu7_GOQ@mail.gmail.com>
To: David Booth <david@dbooth.org>
Cc: "W3C Credentials CG (Public List)" <public-credentials@w3.org>
Maybe I'm paranoid, but Google and Apple, historically, are not companies I
would trust on anything related to data privacy.

They are just a change of policies away of starting profiling me using that
data.

And if it's at OS level, how can we audit the code? Is it open source?

It's like the bully in school becoming the security guard at University :P

Alex

El vie., 10 abr. 2020 a las 22:00, David Booth (<david@dbooth.org>)
escribió:

> "Across the world, governments, and health authorities are working
> together to find solutions to the COVID‑19 pandemic, to protect people
> and get society back up and running. Software developers are
> contributing by crafting technical tools to help combat the virus and
> save lives. In this spirit of collaboration, Google and Apple are
> announcing a joint effort to enable the use of Bluetooth technology to
> help governments and health agencies reduce the spread of the virus,
> with user privacy and security central to the design."
>
> https://www.apple.com/covid19/contacttracing/
>
> Comments, particularly on the privacy aspect?
>
> David Booth
>
>
>

-- 

Alex Puig

CTO

+34 678544357

alex@caelumlabs.com

Follow us! Twitter <https://twitter.com/caelumlabs> |

linkedin <https://www.linkedin.com/company/caelumlabs/> | Newsletter
<http://newsletter.caelumlabs.com/> | Gitlab <https://gitlab.com/caelumlabs>

IMPORTANT: The contents of this email and any attachments are confidential.
It is strictly forbidden to share any part of this message with any third
party, without a written consent of the sender. If you received this
message by mistake, please reply to this message and follow with its
deletion, so that we can ensure such a mistake does not occur in the future.
Received on Friday, 10 April 2020 20:05:23 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:58 UTC