> 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/jentis-platform-privacy-basics/jentis-platform-and-privacy.md). # JENTIS Platform and Privacy JENTIS Platform is based on privacy by design principles and offers flexible configuration options. The following simplified overview lists features that help to adequately address regulatory framework, proactively solve problems with “broken” customer journeys, effectively prevent loss of data attributed to ad-blockers and tracking protection mechanisms, as well as adequately address the quality of captured online data. For detailed information on core system components see [Product information](/privacy-documentation/product-information.md). JENTIS Platform is centered around **first-party** **data** capture and **server-side tracking**: * This technology replaces traditional (third party) tag management by mirroring user sessions on the JENTIS server (**twin browser technology**). * JENTIS Platform allows companies to capture and process data in a legally compliant way, **customizing and differentiating** data streams for first party use as well as **modification and downstream transfer** of data to third party tools. * JENTIS first-party data capture process effectively **addresses ad blockers and tracking prevention scripts**, increasing the **quality of data** collection. * With JENTIS companies **gain full control** over their data, empowering companies to manage data on their own terms (**data sovereignty**). --- # 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/jentis-platform-privacy-basics/jentis-platform-and-privacy.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.