> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/data-encryption/data-classification.md).

# Data Classification

Once you have [setup data encryption](/data-encryption/encryption-setup.md) on your ngSurvey installation or on your survey you will be able to define one of the following classification for the data you would like to encrypt.

* [Internal](/data-encryption/data-classification/internal.md) data will be encrypted at the database level but available in clear to users having access to the survey using the ngSurvey administration interface. (medium)
* [Sensitive](/data-encryption/data-classification/sensitive.md) data will be encrypted at the database level but available in clear to the survey owner using the ngSurvey administration interface. (high)
* [Restricted](/data-encryption/data-classification/restricted.md) data will be encrypted at the database level using a PGP public key. Data can only be decrypted using the corresponding private PGP key and pass phrase. (very high)

{% hint style="info" %}
You can switch from one or the other classification at any time however encryption will only be applied to newly collected data, any existing data will remain in its original state encrypted or not. 
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ngsurvey.com/data-encryption/data-classification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.