> 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/encryption-setup.md).

# Encryption Setup

ngSurvey can be configured either at the server level to provide [transparent encryption](/data-encryption/encryption-setup/transparent-encryption.md) using a single symmetric text based key that will encrypt and decrypt data automatically when needed or you can [secure each survey independently](/data-encryption/encryption-setup/pgp-encryption.md) using separate asymmetric  [PGP key pairs](/data-encryption/encryption-setup/pgp-encryption.md) to encrypt your data using your public key and decrypt it only on demand using your private key.

{% hint style="danger" %}
Encrypted data cannot be recovered if you loose your encryption keys.
{% endhint %}

## 👨‍💻️ Additional security considerations

Besides encrypting data within the database we also suggest securing your database at rest using SQL Server's native Transparent Data Encryption. This will make sure that any files used by SQL Server to store your data are properly secured and encrypted.

To setup TDE you may follow [Microsoft's SQL Server's official TDE documentation](https://docs.microsoft.com/en-us/sql/relational-databases/security/encryption/transparent-data-encryption?view=sql-server-ver15)

{% hint style="danger" %}
Once you have setup an encryption key new SQL connection strings, active directory passwords and system settings (mail, twilio) will be encrypted. To encrypt old values you will need to update their value back.
{% 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/encryption-setup.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.