Ben Kreuter RWC 2017

Channel:Real World Crypto · Length:28:11 · Published:2017-02-02 · Views:1097

Watch on YouTube

Summary

A Real World Crypto 2017 talk by a Google engineer on using private set intersection to match ad views with in-store purchases. It describes privacy-preserving matching that avoids exposing personal transactions.

Why HN recommends it

Cited in threads about Google's purchase tracking as the technical source for how the matching might work.

According to what they presented at a crypto conference, they went to great pains to avoid capturing personally identifiable transactions. — HN, 2018

Cryptography · Privacy, surveillance & cybercrime

Subtitles (excerpt)

hi so I'm Ben crater and we'll talk about how we've been using MPC at Google before I begin I'd like to say every time I tell people in this community hey we're doing this you know we're doing MPC at Google everyone gets really excited and starts saying oh are you using garbled circuits or using gmw and then I have to disappoint everyone and say nope and actually we're going to talk a bit about why I think probably the most interesting part here is what is separating the academic work from the work that companies like Google are doing in this field so start with that then I'll talk about two applications that sort of illustrate two different scenarios in which this is being used so we have a business-to-business application and an application on consumer devices on smartphones so let's start with this separation why is research going one way and everything else seems to not be going that way so at a high level the academic view of MPC has been mostly looking at these generic protocols so these these protocols where you can take any any polynomial-time functionality and compile it down into something that you can then run between many parties and it's very nice if you're a developer if you have a system like that or

On Hacker News

IIRC, this was announced as part of a program that uses double-blinded crypto that allows google to perform matching against this data in aggregate (Set intersection knowledge), but not individually identity of what a given user purchased, at the same time preventing the merchants from learning the identities of individuals either. According to what they presented at a crypto conference, they wen… — cromwellian, 2018-03
> Google buys your credit card purchase data. A more accurate explanation of the scare quote: [LINK] > IIRC, this was announced as part of a program that uses double-blinded crypto that allows google to perform matching against this data in aggregate (Set intersection knowledge), but not individually identity of what a given user purchased, at the same time preventing the merchants from learning … — vatueil, 2018-03
It's actually not given to Google in a user identifiable way. I am not privy to the details, but an overview was presented at a crypto conference: [VIDEO] It looks to me like a form of homomorphic encryption where both the aggregate consumer transactions (people bought X at merchant M), and the aggregate Google ad information (people saw ad for X at merchant M) are encrypted and the set intersect… — cromwellian, 2017-07
A Googler gave a talk at Real World Crypto in January describing a system that might back this. The relevant part of the talk starts around the 10 minute mark: [VIDEO] In short, they're able to compute the intersection of the set of users who have viewed an ad with the set of people who purchased a product in a store, without either party disclosing their side of the set. — russell_h, 2017-05

Related videos