# Unique parts of our solution

Our strategy is similar to what some Asian countries used to combat the pandemic with invasive data-rich, decision making, and enforcement. Although, our solution is completely privacy preserved and ***does not let any data be shared/stored in the raw form***. While most public health solutions try to create tools for PHAs and a top-down ‘command and control’ solution, we take the bottom-up approach. We solve the problems in **technology, trust,** and **open innovation**. We are inspired by Mozilla, one of the few large-scale consumer-facing open-source software projects focused on privacy.

&#x20;Our effort is innovative and unique for three reasons.&#x20;

1. **Tech:** Unlike other organizations that use consent and anonymity as a poor substitute for privacy, we use the NoPeek approach developed at MIT. The set of NoPeek algorithms are computationally hard to breach and are being rigorously reviewed with mathematical proofs for cryptographic guarantees. We believe consent and anonymity-based approaches are prone to data security breaches. Governments are unwilling to let private for-profit or non-profit players deploy a solution for their citizens with such security risks.
2. **Trust:** Unlike commercial solutions with vendor lock, sensitive health data and guidance require transparent, unbiased, open-source solutions.&#x20;
3. **Open Innovation:** Similar to Mozilla foundation, our open-source software is an open and transparent innovation platform drawing talent and partnerships for growth.


---

# Agent Instructions: 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:

```
GET https://prep.pathcheck.org/solution/unique-parts-of-our-solution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
