The DP-3T algorithm for contact tracing (with Nicky Case)
Based on 3Blue1Brown's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Asymptomatic contagiousness creates a gap that symptom-based isolation alone cannot close.
Briefing
Digital contact tracing aims to stop COVID-19 transmission during the window when people are contagious but not yet showing symptoms. Widespread testing and fast self-isolation help once symptoms appear, but the virus still spreads through contacts made while someone is asymptomatic. The core challenge is doing something faster than interviews—without turning public health into mass surveillance.
DP-3T-style approaches address that tension by using cryptography to alert people who were near an infected person, while keeping location and identity private. Instead of relying on GPS or phone geolocation histories, each phone periodically broadcasts short, uniquely pseudo-random “gibberish” messages over Bluetooth. These messages are designed to reveal nothing about who is transmitting them and nothing about where they are—no GPS data, no personal identifiers. The uniqueness matters: if two phones stay close long enough, they exchange and record each other’s random identifiers.
In the example, Alice and Bob both run compatible privacy-first tracing apps. Every five minutes, Alice’s phone emits pseudo-random strings to nearby devices and simultaneously listens for similar strings from others. If Alice and Bob remain close for more than five minutes, their phones exchange the relevant random identifiers and store what they sent and received for the last 14 days. Because the identifiers are random and contain no location or identity information, Alice’s privacy is protected from Bob, and Bob’s privacy is protected from Alice.
When Alice later develops symptoms and tests positive, her app uploads only the random identifiers she has broadcast to a hospital database. The upload uses a one-time passcode provided by her doctor to prevent spam and unauthorized submissions. Crucially, the hospital stores only meaningless random strings: it learns nothing about Alice’s identity, where she was, who she met, or even how many people she encountered. The hospital’s role is limited to distributing a list of identifiers associated with confirmed cases.
Bob’s phone periodically checks that hospital list. If Bob’s phone finds that it has previously seen any of the newly reported random identifiers within the last 14 days, it concludes that Bob was in contact with someone who tested positive and can warn him to self-quarantine. That warning interrupts further transmission chains before the virus can spread widely.
The takeaway is that contact tracing can be “one step ahead” of the virus by alerting recent contacts based on cryptographic identifiers rather than tracking real-world location histories. Open code and the ability to verify behavior are presented as key to building trust without requiring users to blindly accept surveillance claims.
Cornell Notes
Privacy-first digital contact tracing can reduce COVID-19 spread by notifying people who were near an infected person while avoiding location tracking. Phones broadcast pseudo-random Bluetooth identifiers every few minutes; these contain no GPS data and no identity information. Each phone stores the identifiers it sent and received for a rolling window (14 days). When a user tests positive, a hospital database receives only the user’s random identifiers using a one-time passcode to prevent spam. Other phones download that list and warn users if they previously encountered matching identifiers, enabling self-quarantine without revealing anyone’s identity or movements.
Why does symptom-based isolation alone fail to stop transmission?
What replaces GPS and identity in the DP-3T-style approach?
How do Alice and Bob’s phones create a record of contact without learning who the other person is?
What happens after Alice tests positive, and what does the hospital learn?
How does Bob get warned, and how does that stop transmission?
Review Questions
- How does the system ensure that uploaded data from a positive case does not reveal identity or location?
- What specific role does the hospital database play in the alert process, and what does it avoid learning?
- Why is the 14-day storage window important for matching exposure to later test results?
Key Points
- 1
Asymptomatic contagiousness creates a gap that symptom-based isolation alone cannot close.
- 2
DP-3T-style tracing uses Bluetooth pseudo-random identifiers instead of GPS or geolocation histories.
- 3
Random identifiers are designed to contain no identity or location information, protecting privacy between nearby users.
- 4
Phones store sent and received identifiers for a rolling 14-day window to match exposures to later positive tests.
- 5
A one-time passcode from a doctor helps prevent spam and unauthorized uploads to the hospital database.
- 6
The hospital distributes lists of identifiers tied to confirmed cases, without learning who was where.
- 7
Matching previously seen identifiers lets users quarantine based on exposure risk rather than surveillance.