> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/~/changes/EDXkAXJ2BnUpKbwo76Y3/privacy-and-security/privacy.md).

# Privacy

## Overview

The right to privacy is a fundamental right in many contexts. Privacy protection or preservation can be ensured in an application by adopting a privacy friendly design stance.

## What is privacy and privacy protection?

Privacy takes many forms. From an identity system perspective, the confidentiality of identity information and anonymity when using the identity offers privacy.

MOSIP views the identity system as a custodian of the individual's data. This data has to be protected in order to protect the individual from privacy and security risks. Privacy protection measures include [data protection](/1.2.0/~/changes/EDXkAXJ2BnUpKbwo76Y3/privacy-and-security/data-protection.md), transparency, user control, confidentiality, selective disclosure, user anonymity and intrusion protection.

## Privacy design elements

MOSIP addresses privacy design at four levels.

1. Functional privacy
   * Selective disclosure
   * Anonymization
   * Need to know
   * Encryption
   * Tokenization
2. Security
   * [Data security](/1.2.0/~/changes/EDXkAXJ2BnUpKbwo76Y3/privacy-and-security/data-protection.md)
   * Trusted applications
   * Access control
3. User centricity
   * User control
   * Consent
   * Usability
   * Inclusion
4. Transparency
   * Openness
   * Verifiability
   * Governance

These design principles have resulted in features as well as development practices in MOSIP that enhance privacy protection. A typical example for a practice is how PII (Personally Identifiable Information) is dealt with when creating application or audit logs. An example of a feature is how our [Datashare policies](/1.2.0/~/changes/EDXkAXJ2BnUpKbwo76Y3/partners.md#partner-policies) allow selective sharing of information.


---

# 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://docs.mosip.io/1.2.0/~/changes/EDXkAXJ2BnUpKbwo76Y3/privacy-and-security/privacy.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.