> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/app-basics/privacy.md).

# Privacy

GDPR: Set company statement goals for privacy, used data sources, related subprocessors and create PDF's for users to confirm before entering the applications.

**Generate Privacy Policy**&#x20;

Any2info offers the possibility to tailor privacy statements that meet the requirements of GDPR. Therefore you can edit:

* Statement goals
* Data sources
* Subprocessors

After you have completed the content as mentioned above you have to **generate a privacy policy PDF** document. This document must be confirmed by each user entering the application(s) fo the first time.

Also after adjustments in the content of the privacy statements a new PDF document must be generated.

![](https://870194474-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M_kE41Rl4pOtwKfvvQq%2F-MaUmruhmdVGhhorNSMJ%2F-MaUnBfpCYaoMtHxZf3f%2FPrivacy%20statements.png?alt=media\&token=3eb60e80-d9f1-47fd-8033-83107918f63e)


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/app-basics/privacy.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.
