> 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/product-information/legal-glossary.md). # Legal Glossary Here is a list of product specific terminology that we are using in our configurations: * **Account** Account refers to a customer’s profile within JENTIS SaaS. The customer (“Account owner”) creates an Account, defines an Admin, and manages other Account users within it. Within an Account, containers are created to organize and manage data capture activities. * **Container** Container is a component within an Account that is associated with a specific domain. It hosts all the consents, vendors, tools, and tags for that domain. Multiple containers can be created per Account, but each container is dedicated to a single domain (*see **JENTIS Container Manager**)*. * **Consent configuration** Consent configuration refers to the settings managed by the Account owner to control consents for each Container. This includes configuring consent for each vendor, tool, and tag within the Container (*see **JENTIS Consent Manager**)*. * **Vendor** Vendor is a third-party destination where the Account owner sends data. Consent settings can be configured at the vendor level. * **Tool** Tool sets the criteria for sending data to a vendor based on consent decisions of a data subject, data substitutions, and / or even specific campaign goals. The Account owner configures tools to handle different tracking scenarios. * **Trigger** Trigger defines when to send data to a destination. The Account owner configures triggers to determine the specific conditions and timing for data transmission. * **Tag configuration** Tag configuration involves assigning one or multiple tags to each Tool. These tags correspond to specific data subject interactions, enabling the Account owner to align data transmission in specific Tools with appropriate consent permissions (*see **JENTIS Tag Manager**)*. --- # 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/product-information/legal-glossary.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.