Thread by @EinsteinsAttic

So, let's take a look at the latest #ContactTracing effort to emerge: pepp-pt.org - not an app, but 'components' to build apps & systems.

(There's so many tracers popping up now, it's getting like the rash of #COVID19 #SymptomSurveys that broke out last week...)

1/n

Nice to hear that @PeppPt "embrace a fully #privacy-preserving approach". So what exactly is it? (The devil, of course, is always in the detail...)

Ah! Here we are, "a brief description of our #privacy enforcing flow":
pepp-pt.org/content

/2

First, #AnonymousIdentifiers. Good. (And precisely what we recommended: medconfidential.org/wp-content/upl…)

This really is a no-brainer; anyone proposing to use persistent #deviceIDs at this point is plainly a clueless numpty. Or actively seeking to #surveille.

/3

Second, logging the #proximity #history. It'd be good to know what "#epidemiologically sufficient" means & who determines that, but storing *just* the #AnonymousIdentifiers *without* any additional info or data is definitely the way to go.

One query though: if the phone...

/4

...owner cannot even *view* the data on their own phone, who controls the #encryption key(s)? If I can't *see* what you're storing on my phone, how can I #trust it is what you say?

#GDPR #DataMinimisation brownie points for #deleting unnecessary data... but how will I know?

/5

Third, using the #ProximityHistory. This is where we start to go off the rails. "Mode 1" doesn't (appear to) allow a user to declare #symptoms, which means this entire system is predicated upon #testing.

Which is (more than) a bit of a problem if #tests are in short supply!

/6

"Mode 2" compounds things further; only if an app user's been #confirmed #CVpositive *by* the Health Authorities will they send the #key to unlock the #encrypted store on the infected user's phone. In trying to keep their data 'clean', they've (over)engineered a bottleneck!

/7

And what *exactly* happens after the #infected user gets the #key is then completely glossed over - "national trust service that #permits the #notification..." covers a multitude of sins.

It *might* be fine. But we have no way to know - which is the very opposite of #trust.

/8

Fourth is what I guess #PEPPPT see as their #USP; cross-#border coordination.

The interesting bit is in "Mode 2" - WHAT "information associated"?! (I thought we weren't doing that) & what use can the authorities in the other countries make of it, if it's truly #anonymous?

/9

Five basically passes the buck, but it'd have to.

The question is, how well different countries' "Health Authorities" are going to be able to adapt their own emergency processes to issuing #decryption keys as part of their testing efforts (assuming those are working, ofc!).

/10

Sixth & finally, some pretty strong claims!

So, in the UK, would these folk expect @NCSC to perform regular, line-by-line #audits of - and publicly #endorse - their code?!

Seems unlikely. And I hate to break it to them, but I doubt @ICOnews even has the capacity to do this

/11

I see @PeppPt also has a "#Manifesto", which I don't propose to go through blow-by-blow - other than to note they're really trumpeting their ability to do cross-border #InfectionChains... & offering to "manage the network" of national initiatives...

…b-421d-a6c6-96c63f2a159a.filesusr.com/ugd/159fc3_878…

/12

...which seems a tad "One Ring to rule 'em all".

Hmm. They're "financed through donations" - from who, exactly? List?

And, of course, though a contact tracing app really doesn't need it, they claim expertise in (amongst many other things) #AI...

*sigh*

/13

They "will" incorporate as a Swiss non-profit, but nothing about a Board, or #oversight or #governance (yet).

Plus, talk of "#OpenSource" seems a bit premature, given you can only get sight of the #code if you "join the team".

I wish 'em luck. MUCH more detail required.

/ends