> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/admin-guide/33/technology-overviews/telemetry.md). # Telemetry To drive product improvements, Prisma Cloud captures anonymous data about how our product is used. By default, telemetry is enabled. No information that is collected can be used to uniquely identify you or your deployment. Telemetry can be disabled any time. We never collect IP addresses, host names, user names, container labels, or image tags. Our telemetry is designed to help us understand how customers use our product at an aggregate level. For example, we detect which features are enabled, the number of containers and images in an environment, and so on. The legal terms governing telemetry can be found in the Prisma Cloud License Agreement. The Prisma Cloud License Agreement is included with the installation package. ## Disabling telemetry Disable telemetry in Console’s settings page. 1. Open Console. 2. Go to **Manage** > **System** > **General**. 3. Under **Telemetry**, set **Share telemetry on product usage with Palo Alto Networks** to **Off**. --- # 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.prismacloud.io/admin-guide/33/technology-overviews/telemetry.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.