> 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/restricted.md). # Restricted Data that has been classified as restricted will be encrypted using the public [PGP encryption key](/data-encryption/encryption-setup/pgp-encryption.md) that has been set on your survey. Restricted data is not available in clear through administration interface and is only available on-demand which requires you to provide your private PGP key with its optional pass phrase. ## ⚠️ Limitations Following limitations apply to restricted encrypted data. * No sorting. * No searching. * No tag cloud. * No sentiment processing * Not available for update when a respondent resume its survey or want to change the answers. * Not available for piping when a respondent resume its survey or want to change the answers. * Not available for conditions rules (skip, branching) when a respondent resume its survey or want to change the answers. * Not available for report filtering. * No reminders on restricted campaigns. * Can't be used to evaluate condition task triggers on answers update. * Not possible to query the clear values from the database. --- # 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/restricted.md?ask=&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.