> For the complete documentation index, see [llms.txt](https://docs.ojin.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ojin.ai/getting-started/data-deletion.md). # Data Deletion You can ask us to delete your Ojin account at any time. ## How to request deletion From the dashboard, go to **Settings → Account** and use **Request deletion**. That sends the request to our team directly. We run a few internal checks, delete your account, and email you to confirm once it is done. ## What gets deleted Deletion removes your **Ojin login** and cancels any pending invitations to join an organization. You can no longer sign in with it. If you sign up again later with the same email address, you start over with a new, empty account. Ojin accounts belong to an **organization**, and the organization is not deleted with your login. Its agents, model configurations, API keys, uploaded assets, knowledge and session records stay in place, because they belong to the organization rather than to you. Colleagues in the same organization keep working as before. **Where you are the only member of your organization**, we also end its paid plan so it does not renew. Usage of the organization's API keys or published agents is still billed as usual. ## What we have to keep We cannot delete everything, and we would rather say so than promise otherwise. Ojin is operated by Journee Technologies GmbH, a German company, and German law (§147 AO / §257 HGB) requires us to retain **invoices and accounting records for ten years**. The GDPR recognises this: the right to erasure does not override a legal retention obligation (Art. 17(3)(b)). In practice this means your organization's invoices are kept, together with the billing customer record they are attached to, which carries the name, email address and postal address used for billing. **Where nobody else is a member of your organization or holds a pending invitation to it**, we replace the billing contact email on that record, with us and with our payment provider, by an address of our own, so billing notices no longer reach you. Otherwise, billing notices for the organization can still go to that address. Our payment provider likewise retains a record of past charges. We also keep a **record of the deletion request itself** and what we did, as the evidence that we handled your request properly. Data-protection rules expect us to be able to show that, so this record outlives the account it refers to. Anything we retain for these reasons is kept for that purpose alone and is not used to operate the product or to contact you. The one exception is billing: where your organization still has other members or pending invitations, its billing notices keep going to the billing contact on file. ## How long it takes We respond to deletion requests **within 30 days of receiving them** and usually complete them in that time. ## Questions Email . --- # 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.ojin.ai/getting-started/data-deletion.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.