> For the complete documentation index, see [llms.txt](https://docs.zingg.ai/zingg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zingg.ai/zingg/versions/community-v0.3.3/security.md). # Security And Privacy Zingg models are built on your data, deployed within your network. No data leaves your environment. However, Zingg does collect usage metrics and writes it to Google Analytics. This is done to understand and improve user experience. Please be assured that **Zingg does not capture any user data or input data and will never do so.** The following details are captured: * **Data source type:** type of data format e.g. csv, snowflake * **Fields count:** number of fields used for training * **Total Data count:** for match phase, number of total records * **Execution Time:** execution time of the program * **Matched and Nonmatched records count:** for train phase, number of matched and nonmatched records If you do not wish to send this data, please set collectMetrics flag to false in the configuration json while running Zingg. No usage data is being collected in the 0.3.0 release --- # 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.zingg.ai/zingg/versions/community-v0.3.3/security.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.