> For the complete documentation index, see [llms.txt](https://prep.pathcheck.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prep.pathcheck.org/privacy-preserved-ai-for-healthcare/exposure-notification-for-automated-contact-tracing-download-only-solution.md).

# Exposure Notification for Automated Contact Tracing (Download only solution)

![](/files/-MYPuoQ9RrAnR2xjW2Wy)

For an on-device solution in exposure notification, an infected phone and healthy phones would exchange Bluetooth keys.  Only the infected phone uploads the Bluetooth keys to the server, and then all the other healthy phones download this global key file locally to their phone and see if there's an overlap between the keys that they have and the keys downloaded from the server. As you can see, because it's an on-device calculation and download only, the server does not know anything about John or his contacts. At the same time, if somebody did receive an exposure alert, the server does not know who exactly got the exposure alert.

We have an official exposure notification app deployed in 7 places, details can be found in the link below.

{% embed url="<https://www.pathcheck.org/en/covid-19-exposure-notification-app>" %}

![](/files/-Ma-ztMCv_XQJGKiuYUY)

{% embed url="<https://youtu.be/GXr7TxD7QKA>" %}

{% embed url="<https://youtu.be/eoLE9OXvxiU>" %}

**References**

* [**Apps Gone Rogue: Maintaining Personal Privacy in an Epidemic**](https://arxiv.org/abs/2003.08567)
* [**Comparing manual contact tracing and digital contact advice**](https://arxiv.org/abs/2008.07325)
* [**Proximity Sensing: Modeling and Understanding Noisy RSSI-BLE Signals and Other Mobile Sensor Data for Digital Contact Tracing**](https://arxiv.org/abs/2009.04991)
* [**Proximity Interference with Wifi-Colocation during the COVID-19 Pandemic**](https://arxiv.org/abs/2009.12699)
* [**Spatial K-anonymity: A Privacy-preserving Method for COVID-19 Related Geo-spatial Technologies**](https://arxiv.org/abs/2101.02556)
* [**COVID-19 Contact-Tracing Mobile Apps: Evaluation and Assessment for Decision Makers**](https://arxiv.org/abs/2006.05812)
* [**Contact Tracing: Holistic Solution beyond Bluetooth**](http://sites.computer.org/debull/A20june/p67.pdf)
* [**Contact Tracing to Manage COVID19 Spread – Balancing Personal Privacy and Public Health**](https://www.mayoclinicproceedings.org/article/S0025-6196\(20\)30424-9/fulltext)
* [**The Architecture of Trust in Contact Tracing**](https://f.hubspotusercontent40.net/hubfs/8097148/documents/evaluating-contact-tracing-apps.pdf)
* [**Adding Location and Global Context to the Google/Apple Exposure Notification Bluetooth API**](https://arxiv.org/abs/2007.02317)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://prep.pathcheck.org/privacy-preserved-ai-for-healthcare/exposure-notification-for-automated-contact-tracing-download-only-solution.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
