[Music]
hi welcome to this special I 80 note
panel the platform's way in privacy
exposure notification and contact
tracing the past few months have been
uncharted territory for all of us and
that really means all of us citizens of
the world as we deal with the covet 19
pandemic this crisis has far-reaching
implications for Public Health primarily
of course but also for the economy and
for society writ large
it also has brought a wave of new issues
and implications for us privacy
professionals is issues such as working
or studying from home on virtual
platforms returning to the office trying
to keep employees safe while protecting
their rights and privacy health care
research and much much more as we work
through all of these issues technology
is a valuable tool that can and should
aid policymakers and public health
officials fight the pandemic one central
issue that we have seen is the testing
tracking and tracing of new patients of
course contact tracing is an age-old
practice as Nicole will later elaborate
public health officials have deployed it
for many many years
but now technology can digitally assist
in identifying individuals who were
exposed to the virus and alerting them
to get tested and to quarantine as
providers of the dominant operating
systems for a vast majority of
smartphone users Google and Apple have
been at the forefront of this discussion
and they came together to remove
barriers from and to enable the
development of exposure notification
applications
it's a special privilege for us to host
the leading privacy officer
at both Apple and Google in one session
respectively Janne Horvath from Apple
and Keith Enright from Google and that's
an even greater privilege for us to have
this session moderated by Nicole Wong
who has a long illustrious career in
privacy and tech policy formerly the
deputy chief technology officer for the
United States and the Obama
administration so with this I will hand
it over to you Nicole perfect thank you
so much and thank you for hosting this
conversation it's a it's a fascinating
topic and a deeply challenging and
uncertain time so I'll just be
facilitating our discussion but truly my
two friends Keith and Jane need very
little assistance from me I have the
privilege of working with both of them
what seems like several lifetimes ago
when I was at Google you know when we
chisel privacy policies from stone
tablets and things like that but it's a
delight to have this reunion with both
of you today and to see you and your
companies working together on this
really important joint project so maybe
to start I'll do a little bit of a set
up and then I'm gonna let both of you
talk about the work we expose your
notification system from Apple and
Google and we're gonna need a shorthand
for that at some point in this
conversation is a tool to improve the
ability of public health agencies to do
contact tracing so for those who aren't
steeped in that topic it might be worth
a couple minutes to explain why that's
important as Omar said in the
introduction contact tracing is not new
it dates back to the 19th century
it was used to identify the actual
typhoid mary
in 1907 as the source of the outbreak of
the disease disease in new york it's
particularly useful for methods of
diseases that are transmitted by
droplets in the air or by direct human
contact hence it's important today with
the transmission of coded 19 but it was
also used in the campaign to eradicate
smallpox which was finally done in 1979
the SARS outbreak in the US and 2003
the Ebola outbreak in Africa in 2014 in
she´ll when someone's diagnosed with one
of these highly contagious diseases the
diagnosis is shared with the patient and
her doctor and also the local public
health agency and then that agency
assigns a contact tracer to followup
with the patient about her symptoms her
close context during the period of
infection and to come up with an
isolation plan and then the tracer goes
and finds all of that patients contacts
to see if they are also ill and to
monitor them for some period of time for
possible infection so that's it in a
nutshell I think it's also important to
know that the tracing is just one part
of a three-prong public health program
which we've now heard repeatedly in
recent months test trace and isolate and
so here with your joint project Jane and
Keith we're focused on that trace part
of the strategy so with that background
why don't we start first with an
explanation of the Apple Google exposure
notification system and what it does
great Nicole thank you so much and it is
a pleasure to be on a panel with the two
of you and I also want to thank the ia
pp for hosting this panel Nicole gave a
little background on what contact
tracing is and as you were listening it
really involves a lot of contact tracer
ask a person who they've been in contact
with but we all recognize the reality of
the world that we live in today we come
into contact very often with people we
don't know and and so early on in the
pandemic there was a lot of thought of
how could cell phone data be used to do
contact tracing and and there were a
number of reach outs from public health
authorities to both Google and Apple and
and in people were looking at existing
technologies that the telephones had
including location including Bluetooth
and and none of those were really the
right thing and so we realized that we
need we could use Bluetooth technology a
modified version and a more privacy
friendly
a Bluetooth to help with the contact
tracing and in a minute I'll walk you
through a schematic that shows exactly
how this works but essentially we
developed exposure notifications which
is a type of Bluetooth that allows for
you to receive notifications on your
phone do we have the presentation up so
they allow you to receive notifications
on your phone if you test positive the
important thing here and it's something
that Keith will discuss in more detail
when we talk about the privacy features
is we had a decision to make whether we
wanted to share whether this technology
was going to basically send these
indicators to a centralized place or
whether we could use device processing
and thereby more be more privacy
friendly so exposure notifications uses
device side processing and so all of
your contacts or potential exposures are
actually stored on your device and only
when you are diagnosed do is a report
made to the Public Health Authority
again as I was saying earlier it's
really meant to augment the existing
contact tracing efforts it's an attempt
to help find all of those people that
you actually couldn't identify to about
Public Health Authority when you went in
for a post Cova diagnosis to tell them
all the people that you had been around
and then the most important thing here
is we are working very very closely with
the public health authorities on this so
Google and Apple have developed a
technology and it's a technology that
will allow if you are sitting it doesn't
matter whether you have an iOS device or
whether you have an Android device you
will be able to exchange these exposure
keys and so they're interoperable but
the public health authorities are going
to decide how the notifications will be
triggered what the next steps are to
advise someone who's been possibly
exposed and how to reach exposed
individuals for further contact in
containment initiatives next slide
please so how will exposure
notifications work this shows a graph of
potential people coming into contact we
have two slides with a schematic that
walk through a potential exposure next
slide so Alice and Bob are sitting on a
park bench they've been out for a walk
they don't know each other and but there
they're not sitting like more than six
feet apart and they're sitting there for
a bit of a bit of time and Bob is then
subsequently diagnosed with covin 19:00
and as part of the process he actually
has to enter the test result into the
app from the Public Health Authority so
I need to back up a little bit so the
important thing is Alison Bob have
already downloaded the public health
authorities exposure notification app
since I live in San Mateo County we will
assume maybe it's the California
exposure notification app that each one
of them has downloaded so and they're
carrying their phones in their pocket so
Bob is diagnosed he enters those results
into the California app and this is all
hypothetical because we don't have that
happy yet and he interests the test
results in to his Public Health
Authority and when Bob and Alice were
sitting on the park bench their phones
were actually exchanging beacons to show
that they had been in contact with each
other and you can see in this schematic
that they were in contact with each
other about 15 minutes so each phone
exchanges our exposure notification keys
and they stay on device so when Bob is
then test test positive
he enters it into the Public Health
Authority and with Bob's consent meaning
he will actually have to take an
affirmative action to say that he wants
to upload the last 14 days of his keys
to the Public Health Authority for two
server of the Public Health Authority
next slide please so Alex continues her
day unaware that she's been near a
potentially contagious person but her
phone is busy periodically downloading
the Bluetooth beacon keys of everyone
who has tested positive for Kovan 19 in
her region and if a match is found and
here a match is found with bob's random
bluetooth identifier and so her phone
says ah got a match and the app then
triggers a notification that
notification is something that has been
written by the Public Health Authority
here is just an example alert you've
recently come in contact with someone
who's tested positive for koban 19 tap
for more information and Alice's phone
will receive a notification with
information about what to do next
now Keith is going to talk about some of
the privacy protections that we've built
into this technology Keith thanks Jane
next slide please
so just sort of elaborating a little bit
on what Jane has already said when the
hope in crisis surface there was a
tremendous amount of energy inside of
Google and I'm sure inside of Apple as
well at all levels of the company trying
to determine how we could help what
could we do to leverage our skills the
things that we do well to assist public
health authorities in responding to this
crisis as efficiently and effectively as
they could initially we received a lot
of inbound questions about location data
like maybe you would be able to use
location data to support contact tracing
and it turned out that wasn't actually
the the right data step for a whole
bunch of reasons it's not complete
enough it's not accurate enough and
obviously there are very strong privacy
concerns associated with location
information that could be derived from
somebody's device but serendipitously in
a bunch of places roughly in parallel
folks started talking about Bluetooth
proximity as a potential Avenue for
supporting contact tracing efforts
through some sort of elevated exposure
notification
so we were having conversations with
experts in academia and in other areas
and came to our friends at Apple and
kicked off this conversation but okay
maybe we can collaborate maybe there's
something we would be able to do that
would allow us to expand the speed and
the scope of exposure notification in a
way that was optimized for privacy
protection and that was really the
mission that we took on we knew we can't
solve the problem of contact tracing we
can't deliver that that is up to public
health authorities they've been doing it
for a very long time as Nicole was
laying out what we can do is try to
leverage the unique capabilities of
technology so that we can allow contact
tracing to get better data faster and
allow sort of that information to be
used to notify people who have been
exposed more efficiently based on
criteria that are set by their Public
Health Authority so they can respond
responsibly and hopefully we can slow
the spread of the virus and and help get
people back to work and get the economy
moving again
some of the key decisions that we were
making in the course of the early design
phases of this it was absolutely
essential to us that users have to
explicitly consent to turning on
exposure notifications and we want to
make sure that they have the ability to
turn them off at any time user control
was essential to this we did not want to
create a system that was not completely
transparent and persistently under the
control of the user we also wanted to
make sure from the beginning that this
doesn't collect or use device location
information including for users who have
tested positive so we've gone to great
lengths to ensure that all of the apps
that call the api's that are making
available adhere to some strict
guidelines that we have issued that
prohibit them from collecting or using
device location information we also want
to make sure that users themselves
decide whether they want to report a
positive diagnosis this isn't something
that's automated users remain in control
user identities won't be known to other
users so this technology and its core is
fundamentally anonymous especial
really to Google and Apple we do not
know a users diagnosis we do not know
their identity by virtue of them using
this technology the key design feature
perhaps beyond everything else that has
been to the focus of most of the
external discussion around this has been
our decision to be sure that matching
for exposure notification is done on the
device under the users control there
were alternative designs that were
proposed and we're very actively
discussed where you had central servers
that were doing more of that processing
and more of that association of
diagnosis keys with individual users we
put it back hard on that and we felt
strongly that all this exposure
notification information being done on
device but the processing being done
under these sort of strict control of
the user was an essential design feature
to optimize for the privacy of the
system the systems only to be used for
exposure notifications by public health
authorities and it's not going to be
monetized though hopefully this would go
without saying but you know it's worth
saying explicitly our intention here was
to be very very rigorous and very strict
in only allowing these api is to be
called based on recognized authorized
public health authorities who are
designing apps for this specific purpose
and of course none of this information
is going to be used for anything that
makes any revenue for Google or for
Apple finally for this slide Google and
Apple we intend to disable this exposure
notifications on a regional basis when
it's no longer needed so we will remain
in close partnership with the national
health authorities and when the
president crisis has passed and we do
not feel this technology as necessary
anymore to contain coded 19 we intend to
shut it down next slide please now in
furtherance of that relationship with
public health authorities we've really
put a lot of thought into the policies
of procedures that will govern the way
that these api's will be made available
and how they can be used users as I said
or they have to explicitly consent to
turning on exposure notifications they
also will only be consenting for
purposes of these specific apps that are
created by or for government public
health authorities and the use of the
data that source by these api's is
strictly limited to be used for coded
19:00 response efforts as I had said
these apps must require the consent for
users before the app can use exposure
notification users are choosing to
download these apps themselves and once
the apps are installed they have to
operate within these restrict
constraints that are been defined for
them again even after the app has been
installed the app has to require users
to consent before sharing a positive
test result and as part of that that
notification sharing the Associated keys
with their device back to the Public
Health Authority there's a privacy by
design principle that's at the core of
this technology and we're requiring that
apps only collect the minimum amount of
data necessary and only use that data
for their code 19 response efforts all
other uses of that data including for
things like targeted advertising or
anything else that was intended to
generate revenue are strictly prohibited
and will not be allowed as part of this
technology's kind of use in deployment
one really important point to emphasize
is that we are prohibiting apps from
seeking permission to access location
services and again there was that early
design decision as to whether location
information would be necessary
for exposure notification we have
instead decided to focus on Bluetooth
proximity and we are prohibiting apps
from seeking permission to also access
location service information from the
device and appending it to the Bluetooth
proximity data order any kind of
identity information then finally the
use of these API is actually going to be
restricted to one app per country a
country is a little misleading we
actually mean as per jurisdiction per
Health
authority this is to promote a high user
adoption and avoid fragmentation we want
to do everything that we can to optimize
this entire system or trust we recognize
that people are going to be reasonably
skeptical before installing an
application it's going to be doing these
things so we want to make sure that we
are creating the simplest possible
framework subject to these really
rigorous and very strict constraints and
then we want to put national health
authorities in the driver's seat in
terms of controlling which app is going
to be approved within their jurisdiction
and some of the ways that app is going
to operate as to users that are
operating within that region so we want
to minimize the number of apps with a
minimum rational number for the number
of health authorities that we're dealing
with to maximize adoption and make this
deployment as useful
excellent well thank you both and that
was a really great explanation and I
appreciated the the sort of focus on the
design choices but let's let's take a
little deeper there because we we're
talking to a set of privacy
professionals so maybe some of the
tactics around that actual process of
design right not only to meet the need
from a public health standpoint but also
the design from a privacy standpoint so
I'm thinking of things like um who
helped you figure out that like six feet
would be the right distance to determine
whether there's going to be an infection
and how did you think about that in
terms of putting the design on the table
and talk more about the difference
between location which I think has been
historically the way contact tracing as
a mental model thought about it versus
like the proximity distancing so like
maybe talk a little bit about that
design process and did they start
separately in each of your companies and
then you converged or did you go gather
together at the same time so to answer
the last question first I think we had
all we've been in a lot and it also and
she's the first basically we were in
contact with the public health
authorities early on and as Keith said
in his room
both companies wanted to see what we
could do to help out with the pandemic
and we have been in discussions with a
lot of health authorities that were
early early considering the expose
contact tracing and whether cellphones
could be helpful we you know recognize
that we are we are not experts and we do
have experts on staff both companies
have medical doctors on staff that work
on our health project so they were very
very influential in the design we also
reached out to the CDC European
authorities data protection we briefed
the Irish and the UK and data protection
authorities throughout Europe and the
APAC region very early on to talk to
them about the privacy features and it's
really been trying to figure out how to
balance what we want to be a very
private technology but still make it
useful and you know there have been a
number of different press reports that
are challenging whether we are to
private which is is an interesting place
to be but you know the other thing that
needs to be considered if we are less
private and I think we're seeing that
play out right now if we're less private
less people will download the app so you
have to reach the right balance between
privacy and effectiveness so hopefully
we'll get a big uptake in people using
it and keep I'm sure you have more to
add yeah I agree with all that I think a
couple things that I would buy one is
clearly we recognized coming out of the
gate here that we are not a company
whose core competency is epidemiology or
virology so I think I think we approach
this with an appropriate level of
humility we had leading researchers from
medical schools around the world coming
to us it was a really interesting moment
where we had this unsolicited but
serendipitous engagement from leading
thinkers across all fields that were
relevant to what we were what we were
thinking through we had some of the
world's leading cryptographers come out
to us for sharing their research
sharing their thinking saying we think
that there is a way that you might be
able to help but we would like to share
our research and share our perspective
so that you're doing it in the most
secure
anonymized fashion possible so there
were these tremendous dialogues between
the Google research team the Apple
engineering team the various academics
around the world where we were kind of
checking challenging some of the
assumptions that's been interesting and
fascinating the other point that kind of
I want to push a little bit from what
Jane had said is I I think we are
confident that what we are trying to do
here will be helpful but again we need
to approach what comes next with an
appropriate level of humility right we
are we are moving in somewhat uncharted
waters we are trying to apply the
benefits of technology to a
well-established to drift to traditional
methodology of contact tracing and we
will adjust course as we go we will
improve as we learn but there are there
were all sorts of decision points along
the way one that I want to make sure we
don't presume is that privacy and
efficacy have actually been in tension
because nothing I have seen to date
supports the proposition that privacy
and efficacy are going to be in tension
Jane is exactly right that penetration
ubiquitous adoption all of that those
are presumptively going to be really
important in this being effective but
I'm also seeing research suggesting that
even with relatively low adoption rates
contact tracing and by extension
exposure notification might have
substantial public health benefits
there's a great deal that we don't know
and I think we are going to be learning
right alongside the public health
community and others as we go along
through this journey and continue
optimizing our approach to try it it
seems like one of the defining
differentiators for for your API versus
other models is is centralized versus
decentralized matching and it helped me
out because I'm not sure I totally
understand each each one involves some
centralized server but but for the
Google Apple one its
it's like the limitation of matching is
really about hosting positive cases that
are consented to put be put into that
centralized server right versus tell me
more about what the other model is like
is it that other public health
authorities who decide they want a
centralized server have more information
about the user and maybe talk a little
bit about the pros and cons there so
with the centralized approach if we look
back to Bob and Alice in our schematic
as Bob and Alice are sitting on the park
bench with a centralized approach those
exposures are being sent up to a central
server to mediate regardless of whether
either Bob or Alice had koban there
would be a server that was just
essentially keeping contact keeping
track of all the people that you had
come into contact with and could
potentially have been exposed to so then
when Bob subsequently gets diagnosed
with Kovac the centralized server will
do the matching and then send down a
notification to Alice that she may have
been exposed and and generally in a
centralized approach they could or may
know the identities of the people that
are exposed there's more and I think
there have been there's been a lot of
work on the centralized approach to
minimize the privacy impact as well to
be quite fair on on our approach there
are keys that are sent up to the server
but they are sent up to the server only
on consent of Bob because remember bob
was the one that had the positive
diagnosis he worked with the public
health authorities at the point that he
wanted to notify the people that he had
come into contact with he made the
decision to send those keys up and so
there's a lot more control and Trust put
in the individual and the exposure
notifications model but because we you
know we think if you give people
transparency and control they will do
the right thing that is why we went with
the model that we
went with because the centralized model
does have the potential and I'm not
saying that it always does to build a
social graph of everybody you've been in
contact with yeah as Jane acknowledges
one of the things that struck me across
the course of the project was they were
very thoughtful very reasonable privacy
conscious people on the other side of
this debate around centralized versus
decentralized and they sincerely sort of
believe that there are performance
benefits for the centralized model of
having access to more information by the
Federal Health Authority we'll do
certain things more effectively we
didn't see evidence of that and when we
weighed the potential privacy risks of
the data being repurposed to assemble so
a contact graph that we thought was a
potentially sort of significant privacy
risk that we wanted to mitigate and from
everything that we saw we felt like we
could deliver all of the efficacy
benefits of the model by at the
distributed system where that processing
with some device is opposed by a
centralized server we we committed to
the course of decentralization and at
this point it feels like that's where
the center of gravity is you know the
debate continues to shift and they're
still alive the external discussion
there are envelope jurisdictions that
remain to pursuing the centralized
approach but most jurisdictions are now
leaning towards the decentralized
approach and are signing on with our API
which you know we're taking as a signal
of validation that you know we're
weighing the equities and the privacy
risks here really that's great I think
you both gestured to some of the like
limitations that might come with this
right so one of them is just smartphone
penetration might limit how many people
actually adopt this there could be bias
in the population of who has smartphones
I think that the most recent data is
like really old people and low-income
people have are less likely to have a
smartphone not by huge ones but like 10
to 12 percent I think less than the
general population so those are actually
as it turns out the most vulnerable of
the puppies
shins for COBIT so that's that's an
important thing to think about but it
also strikes me that like and this is
putting a little bit of my public policy
hat on right one of the biggest
limitations may be the technical
capacity of any given public health
authority to know how to it because as I
understand it you're gonna put them
through some sort of verification
criteria and let's put a pin in that and
talk about what that criteria will look
like but also they have to actually
develop the app host the data maintain
it and then follow up with the tracing
which is a lot for at least in our
country and to ask public health
authorities who have been many of which
have been defunded over decades so could
you talk a little bit about like let's
go to like the public health authorities
that you've met with the criteria you
you think about when when deciding
whether to license the API to them and
some of the challenges they may face
taking on the framework so on that on
the subject of the public health
authorities and how we decide we have a
special review group that's looking at
these applications by public health
authorities and you know we want to make
sure there they are the public health
authority for the region one of the
things that is still being discussed
across the globe when people are looking
at using exposure notifications is as as
Keith focused the exposure notification
will be able to be used by one country
or one region but there can be multiple
entities in a region using the en API so
figuring out who the authorized Public
Health Authority is and again it's a lot
of outreach it's a lot of discussions
and in talking and putting you know our
technologists on on the phone with
public health authorities to help them
discussing some of these issues you know
we've been trying to be as helpful as
possible recognizing that we are not
Public Health
experts yeah agree with all that they
think responding to the front half of
your question to call there are an array
of public policy challenges associated
with this many of which I've come to
understand better than I ever expected
to and still don't understand half as
well as I should sadly we are not well
positioned to solve right like many of
the challenges around disproportionately
affected populations and access to
technology and access to connectivity I
think there's a lot there what we are
focusing on is making the api's as
effective and as safe and as privacy
productive as possible and then working
with the public health authorities to
support them in implementing the api's
in whatever app I think they're learning
from each other as well like we're
seeing a great deal of interaction
Public Health Authority to Public Health
Authority which is encouraging and
hopefully that will also have knock-on
effects across governments generally
which may you know shine light on some
of the other adjacent issues that I
think they're going to need to think
about to maximize the effectiveness of
the work but in the short term medium
term getting the api's sort of optimized
getting them deployed as widely as
possible in apps that are functioning as
intended in as many jurisdictions around
the world as possible and then focusing
on promotion and adoption I do think
there is a significant impediment to
this which is making the message simple
enough and compelling enough and
transparent enough that users can make
an informed decision saying I want to
install this because it is the right
thing for me and for my family and for
my neighbors and for my society for the
people around me and this is actually
going to reduce a material risk
that's a hard lift right like holding
people's attention long enough and
communicating all of the essential
information don't help them feel like
they're making a fully informed choice
to install this app to enable the app
and then to subsequently consent to to
exposure notification there's a lot to
do there and we're focusing right now on
working with National Health Authority
to them to do that bit as effectively as
they possibly can if we can do that
which is a substantial if that I think a
lot of these significant adjacent
problems will come into focus and then
folks can begin diverting their
attention there's at least one maybe two
bills in in the federal Congress on data
collected in the process of the coded
response and I think certainly in Europe
a lot of the data protection authorities
you know issuing guidance about how do
we start collecting data particularly in
workplaces about kovat exposure is there
something into either of your minds that
public policymakers ought to be doing to
make this better clearer more protective
what what are you seeing out there that
feels like the right thing to make this
go faster I think you know one of the
things this points out is the fact that
the US doesn't have an omnibus privacy
law yet and that's something that we've
been very supportive of I think within
Europe we see the Commission the
European data protection board and the
DPA is all working within the framework
of gdpr and so there are guidelines
there that are hopefully giving more
consumer trust and I think within the US
and one of the reasons we're seeing
bills in the US is because the the real
thing that's going to help in in making
this work is consumer trust and people
are worried about secondary uses of data
and as Keith made clear Apple and Google
don't have the data the data will be
sent up the public to the public health
authorities and there are state laws and
health laws that will cover some of this
but you know I think that the main goal
here is to give consumer trust and agree
with what Jane is saying one other thing
that I would emphasize is we talked
about COBIT privacy specific legislation
and how that dovetails with this notion
of a much needed general federal omnibus
privacy law it's important that we don't
lose sight of the fact that here at
issue it's primarily government agencies
gaining access
certain types of information so we need
to make sure that whatever privacy
protections we're providing our privacy
protections as to government entities
like this is not a situation we're
actually talking about substantially
creating a new privacy risk from private
sector companies this is something where
we need to make sure protections are
being expansively applied so the users
are getting strong rights and
protections relative to government
access and user data in our last couple
of minutes is there is there another
phase to this project for you I like
seeing you guys work together I missed
that and and what else what other any
other innovations that you either of
your companies are planning or any other
last thoughts on this issue well I mean
I think the the as we've made really
clear we're talking about public health
authorities a lot and there are
different needs across the world and so
we're looking at different
recommendations taking in a lot of
feedback discussing ways to address
different issues so we are still
developing Keith and I are still
coordinating quite a bit and but I don't
think though I don't see any change in
the core privacy commitments we've made
the technology may evolve yeah I mean
that going to have I have been supremely
grateful or the privilege and
opportunity to work with Jane again
she's been a friend and mentor for a
very very long time so great this is
this crisis has presented us with
opportunities to sort of think top to
bottom about different ways that we can
help solve some of these societal
problems in ways that our privacy
protective I mentioned at the beginning
that one of the initial initial
approaches was how location data might
be useful in responding to this crisis
and our initial reaction was not the
right data no privacy risks were
overwhelming we actually had teams in
parallel with this spinning on that
particular problem which resulted in
something we called the mobility
mobility reports where we took
anonymized aggregated data sets and made
them available to public health
authorities in different contexts which
allowed them to do things like interpret
the
patterns to hospitals so that they could
understand like we're were they're
actually actually seeing traffic spikes
how can they be allocating some finite
Public Health resources in a way to
deliver maximum benefit the fact that we
have the ability to do that in a more
privacy protective way than was ever
possible before just another example of
the way this sort of thing can drive
innovation that can drive positive
outcomes great well this has been
wonderful for me to have an opportunity
to hang out with both of you again um
and so just in closing for you and your
families stay healthy and well you as
well thanks so much thank you
[Music]