Google Analytics trackers in contact-tracing app code ‘risks re-identification’

  • 15 May 2020
Google Analytics trackers in contact-tracing app code ‘risks re-identification’

Users of the NHS contact-tracing app could be re-identified due to the code including Google Analytics tracking, a coder has said.

The appā€™s code was made available on GitHub on 7 May, four days after its trial on the Isle of Wight was announced.

NHSX has always maintained the code would be made publicly available, but currently only the front-end code has been published.

The team behind the app have done a ā€œreally good jobā€ within a short space of time ā€œparticularly given some of the technology constraintsā€, but there were some issues with the code, open source advocate Rob Dyke told Digital Health News.

Namely, the developerā€™s decision to use Google Analytics tracking to trace users.

ā€œFor all of the ā€˜this is supposed to be anonymousā€™, the cut of the code that was released did include Google Analytics tracking, and a few other trackers that were in there,ā€ Dyke said.

ā€œSome of them you couldnā€™t really get around because you need to have a degree of tracking otherwise itā€™s not a track and trace app. But the sort of tracking I would expect would be wholly within the architecture of the application.ā€

Using Google Analytics tracking could enable a user to be reidentified, Dyke said, although itā€™s not a ā€œhuge riskā€ but more of an ā€œannoyance and a disappointmentā€.

The tracker could be used by people within the NHS who had access to the system to reidentify the device and possibly the user, but was unlikely to be used by malicious attackers.

ā€œIn particular, if a user clicked on the privacy policy, ironically, it would use tracking identifiers including some status notifications, such as if the individual had had a notification from the back end,ā€ he told Digital Health News.

ā€œSo it seemed to me that it would pass the tracking ID, plus some status information, to Google Analytics which would have included the exact device, type, the IP address the user was calling from ā€“ the usual stuff that Google Analytics gives you.

ā€œAnd it would have allowed you to be linked from your app to the privacy policy and if you went anywhere else on the NHS estate, that tracking cookie would have followed you all the way through.ā€

Not-so-open source

Dykes biggest concern with the appā€™s code was that it was not developed in the open, despite NHSX committing to being open and transparent in its development of the contact-tracer.

The organisation has been an advocate for, and previously committed to, open sourcing its work.

ā€œThis is an organisation that says theyā€™re going to develop in the open and this was not developed in the open,ā€ Dyke said.

ā€œWe had an army of volunteers for the NHS to do things like shopping and delivering, but you could have had an army of people contributing to this code as well.

ā€œIt shows, for me, that they missed an opportunity to actually live their behaviours and values around open source.ā€

Instead, NHSX ā€œdumpedā€ 950 files on GitHub rather than showing itā€™s incremental development.

By 11 May more than 700 people were actively watching the iOS and Android code respectively and eight developers had contributed new code to fix bugs in the original system.

ā€œBecause itā€™s a dump of code it doesnā€™t have the things that would make it easier for developers to engage with, like automated testing. We donā€™t even have a back-end yet to test against,ā€ Dyke added.

ā€œThere are a lot of expertise and a lot of really good willed people who would love to be getting involved, but because it wasnā€™t open from the beginning itā€™s going to be harder for them.ā€

[themify_box icon=”info” color=”gray”]

More on Covid-19 contact tracing apps

[/themify_box]

Apple and Google or NHSX

NHSX has faced fierce criticism on its decision to differ from Apple and Googleā€™s approach to contact tracing.

Choosing a ā€˜centralisedā€™ approach poses a greater risk to privacy through mission creep, potential reidentification and malicious use, experts have warned.

Reports have surfaced that NHSX is working on a second app based on Apple and Googleā€™s technology, with privacy concerns being sourced as a reason the organisation changed its stance.

Dyke predicts NHSX would have to switch to Apple and Googleā€™s approach to reduce privacy concerns and encourage uptake.

ā€œAt the moment the app is not available in the app stores, the only way to install it is manually which requires you to change a setting on your phone to say ā€˜allow installs from non-trusted sourcesā€™,ā€ he told Digital Health News.

ā€œA leaflet comes through your door and you scan a QR code or you visit a URL and that has a webpage where you can download the app.ā€

It will only be available on the app store if Apple and Google accept it, he added.

Subscribe to our newsletter

Subscribe To Our Newsletter

Subscribe To Our Newsletter

Sign up

Related News

Getting the best out of population health requires learning health systems

Getting the best out of population health requires learning health systems

A rapidly evolving digital infrastructure offers potential for population health speakers told a session at Digital Health Rewired24 earlier this month.Ā 
Digital Health Coffee Time Briefing ā˜•Ā 

Digital Health Coffee Time Briefing ā˜•Ā 

Today's briefing includes a House of Commons science committee calling for further development of bacteriophages and Epic planning a wave of AI innovations.
NHS expands use of Covid-19 research platform to find new treatments

NHS expands use of Covid-19 research platform to find new treatments

The NHS is to expand the use of a research platform behind the roll-out of new Covid-19 treatments to help drive advances for other major…