> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/privacy-documentation/frequently-asked-questions/can-jentis-provide-a-standard-description-for-privacy-policies.md).

# Can JENTIS provide a standard description for Privacy Policies?

The wording in the Privacy Policy used to describe data processing via JENTIS SaaS is determined by the Customer’s specific JENTIS configuration. Here is an example of a privacy notice that may be used as the basis to describe JENTIS:

*“For the purpose of analysing the user behaviour of customers and for the purpose of website optimisation, we use the services of* [*Jentis GmbH*](https://www.jentis.com/en/;) *(Schönbrunner Strasse 231, 1120 Vienna) (“JENTIS”).*

*The JENTIS First-Party Cookies are set and used to collect web analysis data, which is processed by JENTIS on our behalf and used to generate aggregate statistics about your visit. The purpose of these statistics is to measure reach and/or analyse visitor numbers, analyse the success of marketing campaigns, improve the user-friendliness of the website, and optimise content.“*

This example above is referenced for educational purposes only and cannot be used as a copy-paste snippet. The Customer must define the wording for their Privacy Policy in accordance with the specific configuration in JENTIS SaaS and in consultation with the Data Protection Officer (DPO), in particular considering collected data, applied functions (e.g. pseudonymisation) and applicable legal basis.


---

# 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.jentis.com/privacy-documentation/frequently-asked-questions/can-jentis-provide-a-standard-description-for-privacy-policies.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.