> For the complete documentation index, see [llms.txt](https://docs.getkita.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getkita.org/guides/your-schools-data-in-kita.md).

# Your School's Data in Kita

This guide explains how Kita keeps, deletes and returns your school's data. It accompanies our Data Processing Agreement, which contains our binding commitments.

### Who is responsible for what

Your school decides what pupil data goes into Kita and is the data controller. Kita is the data processor and follows your school's instructions under our Data Processing Agreement.

### What data do we keep while you use Kita

We keep pupil work, marks, feedback and progress for as long as your account is open. This lets teachers see progress across a year or a whole course. Summaries of learning progress, such as skills practised, are also kept while the account is open, so feedback stays personal.<br>

Some things are deleted automatically sooner:

<table><thead><tr><th width="411.158447265625">Data</th><th>Deleted After</th></tr></thead><tbody><tr><td>Deleted files, projects and folders (recycle bin)</td><td>30 days</td></tr><tr><td>AI usage records</td><td>13 months</td></tr><tr><td>Support chat messages</td><td>30 days after the chat closes</td></tr><tr><td>Teacher verification uploads</td><td>15 days</td></tr><tr><td>Deleted pupils, courses and groups</td><td>30 days</td></tr><tr><td>AI helper conversations</td><td>90 days</td></tr><tr><td>Detailed activity data behind progress charts</td><td>400 days</td></tr></tbody></table>

### What happens when you delete something on Kita

<table><thead><tr><th width="287.5675048828125">Action</th><th>What happens</th></tr></thead><tbody><tr><td>Remove a pupil from a course</td><td><p>Ends the pupil's place on the course. Their work stays in</p><p>the school account.</p></td></tr><tr><td>Delete a pupil</td><td>The pupil is signed out and hidden straight away, and a teacher can restore them. The<br>pupil's account and all their work are permanently deleted after 30 days. Download their work first if you need it as assessment evidence.</td></tr><tr><td>Delete a course or group</td><td>Hidden straight away and restorable. Permanently deleted with the work in it after 30 days.</td></tr><tr><td>Delete your own files and projects</td><td>They go to the recycle bin and can be restored for 30 days.</td></tr><tr><td>Delete a pupil's submission</td><td>Not possible. Submissions are protected so assessment<br>evidence is not lost by accident. Delete the pupil or the<br>course instead.</td></tr></tbody></table>

**Asking Kita to delete one person.** Your school can ask us to permanently erase a named pupil or member of staff at any time. Email <support@getkita.com>. We do it and confirm in writing within one month, usually much sooner.

### Downloading your data

Any teacher in the school can download:

* the pupil list, as a spreadsheet (CSV), from People;
* course progress, as a CSV, from the course's Student Progress page;
* marks and feedback for a lesson, as a CSV, from the lesson's marking view;
* any file, project, folder, lesson or whole course, from the content manager;
* a lesson as an export file, to reuse or share.

The lead teacher can also download the whole school in one ZIP file from School settings. It contains the pupil list, all course content, progress for every course, marks and feedback, every pupil submission including earlier saved versions, and a manifest describing the files.

Pupils can download their own files and projects.

**Requests for one person's data.** If a pupil, parent or member of staff asks your school for a copy of their data, email us and we will produce it for you within 10 working days. AI helper conversations cannot be downloaded in the product yet, so we include them on request.

### Unused accounts

If nobody in your school signs in for 24 months, we send a final notice to your school's contact. If there is still no response after 30 days, we permanently delete the account and all its data. From 1 October 2026, we will also email the lead teacher after 12 months with no activity.

### Closing your account

The lead teacher can close the account with "Delete school" in School settings, or email us.

1. You have 30 days to download anything you want to keep. We can produce a full export for you.
2. We then permanently delete all your school's data, including every pupil and teacher account and all stored files, within 90 days of your request.
3. Deleted data is removed from our backups within a further 7 days.
4. We confirm deletion in writing if you ask.

### Where your data is stored

Pupil data is stored in the UK, Ireland and Germany. All AI processing happens in the UK, using Microsoft Azure OpenAI Service. The full list of companies we use, and where they are, is in Schedule 3 of our Data Processing Agreement.


---

# 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.getkita.org/guides/your-schools-data-in-kita.md?ask=<question>&goal=<user_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.
