Page:Note-by-Chair-and-selected-documents-ordered-from-Six4Three.pdf/2

 '''1. White Lists'''

In the Six4Three documents, exhibits 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 94 and 95 include discussions on whitelisting businesses. The following are of note:

Email from Badoo to Konstantinos Papamiltidas, Director of Platform Partnerships at Facebook, 16 September 2014:

‘We have been compelled to write to you to explain the hugely detrimental effect that removing friend permissions will cause to our hugely popular (and profitable) applications Badoo and Hot or Not.

‘The friends data we receive from users is integral to our product (and indeed a key reason for building Facebook verification into our apps).’

Email from Konstantinos Papamiltidas to Badoo, 23 January 2015

‘We have now approval from our internal stakeholders to move ahead with a new API –working name Hashed Anon All Friends API. The new API as well as the relevant docs will be ready next week.

‘How would this API work…For each of the FB logged in users, the API will return:

FBIDs: App friends that logged in before your migration to V2:

App Scoped IDs: App friends that logged in after your migration to V2:

Annonymous one-way hashed IDs: Non-app friends

The API will hopefully let you understand some of the structure of the graph in order to determine which non-app friends to recommend to a given user.’

Email 5 February 2015

Konstantinos Papamiltidas–‘We have whitelisted Badoo App, HotorNot and Bumble for the Hashed Friends API that was shipped late last night.’

Email–6 February 2015

Konstantinos Papamiltidas to Badoo

‘Badoo APP ID has definitely been whitelisted…According to out logs you have already made 100 calls against this API.’