> 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/data-export-deletion-and-switching.md). # Data export and switching Request a data copy, account closure, personal-data deletion or a move from Kilo, and understand the result you should receive. Before leaving Kilo, decide which information you need to keep and which you want removed. A company moving its device deployment may need readings, device settings, rules and dashboards. A person asking for their personal information to be erased is making a different request. ## Choose the outcome you need | Your goal | What to ask for | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | Save information for your own use | A copy or export, identifying the records and dates you need. A query download may cover only part of a deployment. | | Move to another provider or your own systems | Service switching, with the data, formats, destination and access needed during the move. | | End a company service | Account or service closure, and the applicable return or deletion of the company's information. | | Exercise a personal privacy right | The specific right, such as access, correction or erasure, and the information involved. | | Remove an assistant conversation | Conversation deletion. Include a request about related provider copies if those are part of your concern. | Cancelling a paid subscription concerns billing and service access. It does not by itself confirm that personal information has been erased. Closing an account does not currently automate complete conversation and cross-system deletion. The [data and format guide](/data-and-export-formats.md) lists the information to consider, documented retrieval methods and their limits. ## Send the request 1. Email **info \[at] kiloiot.de** (replace `[at]` with `@`). Identify the service and the outcome you want. 2. Describe the accounts and information involved. Keep passwords, customer exports and unnecessary personal details out of the initial message. 3. Confirm your authority to act for the person or organisation. For company data, identify the person authorised to instruct its return or deletion. 4. For a move, agree the data, format, secure transfer route and applicable transition and retrieval arrangements before removing access you still need. Check that the returned information is usable. 5. Keep the final response. It should distinguish what was returned or deleted from any remaining records, their reason for retention and further action. A personal-data erasure request does not require you to switch providers. Its legal timing is separate from an ordinary closure process. The [privacy guide](/privacy-and-data-protection.md) explains how to exercise those rights. This guidance adds no fee or contractual restriction; the [Terms of Service](https://kiloiot.io/terms-of-service/) and applicable law govern the service arrangements. ## Understand retained copies A complete result considers the information in active systems, copies already sent to providers and backups. Backups can expire on a separate cycle; they are not necessarily rewritten when one record is deleted. Deleted information must be kept out of ordinary use and must not reappear when a backup is restored. Some necessary records may remain for a specific legal duty or legal claim. The response should identify the relevant record category and reason. A tax record does not justify keeping every conversation or device reading. A reading falling outside your plan's available history is also not proof that every stored copy has been erased. ## Fees and switching rights The [pricing page](https://kiloiot.io/pricing/) lists the standard monthly plans. The standard Terms do not specify a switching charge or early-termination penalty. They also refer to annual, usage-related and individually agreed charges; your accepted Order and disclosed terms must identify any that apply to your service. Ask for an itemised explanation before agreeing a move. This page introduces no fee. The EU Data Act limits switching charges before January 12, 2027 to costs directly linked to the move and prohibits switching charges from that date. These limits are separate from ordinary service charges. Applicable law also protects the transition and time to retrieve data; ordinary account closure must not remove that opportunity. See [Data Act Articles 25 and 29](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng). ## Processing arrangements Where Kilo handles personal information on your organisation's instructions, [the processing agreement](/processing-agreements.md) also needs to address return, deletion and supplier copies. Coordinate that choice with switching and any privacy request; these processes have different scopes and legal triggers. --- # 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/data-export-deletion-and-switching.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.