> 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/privacy-and-data-protection.md). # Privacy and data protection Understand personal information in Kilo, make a privacy request, and distinguish account closure from completed deletion. Kilo uses information about people to provide accounts, answer enquiries and operate connected-device services. Device readings can also be personal information: for example, a named worker's location or a sensor record showing when someone enters a room. CHIRP USA LLC operates the Kilo platform. The [Privacy Policy](https://kiloiot.io/privacy-policy/) explains the company's processing and your rights. If your organisation decides to collect information about other people, it also needs a lawful purpose, suitable access restrictions and clear information for those people. ## Make a privacy request Email **info \[at] kiloiot.de** (replace `[at]` with `@`). In your message: 1. Identify the service or account and your relationship to it. 2. Say what you need: a copy of personal information, a correction, deletion, restricted use or another privacy right. 3. Describe the relevant information without attaching passwords, customer exports or unnecessary identity documents. 4. If you are acting for someone else or for an organisation, explain your authority. We may need proportionate additional information to verify it before disclosing or changing information. Where the European Union's General Data Protection Regulation (GDPR) applies, the response about action taken is due without undue delay and normally within one month of receipt. Any necessary extension must be explained within that first month. Qualifying deletion must happen without undue delay; the response deadline is not a waiting period. If a request cannot be fulfilled, the response must explain the reason and the applicable complaint options. ## Understand the outcome A privacy request, cancelling a subscription and closing a login are different actions. Closing an account does not currently automate complete deletion of conversations and information across every system. Ask for the outcome you need and keep the response, including any records that remain, why they remain and the next step. Read [Data export and switching](/data-export-deletion-and-switching.md) before moving company data or ending a service. That guide also explains provider copies and backups. ## Before introducing sensitive information Check the processing agreement, providers, locations and any restrictions needed for your deployment. An AI provider may receive your messages and information retrieved to answer them. Review its retention and model-training terms; disconnecting an application does not erase information already sent to it. See [AI assistant privacy](/ai-assistant/privacy.md). Camera use needs its own decisions about the people recorded, purpose, access and retention. See [Video and privacy](/video-and-kilo-lens.md). ## Processing arrangements If your organisation will use Kilo to handle information about other people, read [Processing agreements](/processing-agreements.md) to prepare the service scope, responsibilities and safeguards needed for that arrangement. --- # 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/privacy-and-data-protection.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.