> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/ai-assistant/privacy.md). # Privacy and Security Understand what Kilo AI conversations contain, where model requests go, and how conversation deletion differs from account closure. The Kilo AI Assistant uses your questions and relevant platform information to help with your connected devices. For example, a question about a cold room may include its device name and temperature readings in the request sent to the AI model. This page explains the information involved and the choices you control. ## Account access and action confirmations The built-in assistant uses your signed-in account and selected organization for its requests. Choose the correct organization and review its members and permissions before delegating work. Read any **Confirm Action** prompt before approving a change to devices or data; choose **Cancel** if the proposed action is not what you want. Routine setup can proceed without a separate confirmation. If the assistant returns information or proposes an action outside the access you expect, stop that task and contact **info \[at] kiloiot.de** (replace `[at]` with `@`). ## What a conversation can contain Conversation history can contain your messages, answers, timestamps and information retrieved by the assistant, including device names, readings, rules and alarms. It lets you return to earlier work. Even though chat is not a full archive of device history, a reading included in a conversation can remain part of that conversation. Anything you type can become conversation content. Keep account passwords, payment details and unrelated secrets out of chat. Enter a model-provider API key in the dedicated settings described in [Managing chats and AI access](/ai-assistant/managing-chats-and-ai-access.md). ## Where the information goes An AI model provider is the service that runs the model used to answer your request. Your messages and the information retrieved for the answer can reach that provider. * **Kilo's configured provider:** the integrated route uses OpenRouter, which forwards requests to the selected model. * **Your own provider credentials:** the selected provider processes the request under the arrangement associated with your credentials. Check its retention, training and location terms. * **Your own model endpoint:** the configured address determines where model requests are sent. This does not remove Kilo's own conversation handling. Selecting Ollama's hosted address is different from entering an endpoint you operate yourself. * **An external AI application:** an application connected through the [MCP server](/api/mcp-server.md) can send retrieved information to the providers it uses. Review that application's access and privacy settings separately. Provider settings and agreements can differ. Before using information subject to confidentiality or location restrictions, confirm that the chosen arrangement meets them. Disconnecting an application does not erase information it already received. ## Deleting a conversation or closing an account Conversation deletion and account closure are separate actions. Use the chat-management instructions for an individual conversation. Closing an account does not currently automate complete deletion of conversations and related copies across every system. For a personal-data request or a result covering provider-held copies, email **info \[at] kiloiot.de**. Identify the relevant account and the outcome you need without resending the conversation's sensitive contents. The response should explain the result and any records that must remain. Read [How Does Kilo Handle Personal Data?](/trust-security-compliance/privacy-and-data-protection.md) for your rights and [How Do I Export My Data or Leave Kilo?](/trust-security-compliance/data-export-deletion-and-switching.md) for company data, retained records and backup handling. --- # 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.kiloiot.io/ai-assistant/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.