> For the complete documentation index, see [llms.txt](https://docs.courtaid.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.courtaid.ai/account-and-billing/deleting-your-account.md).

# Deleting your account

You can permanently delete your CourtAid account and data at any time. This page explains exactly what happens.

## How to delete your account

1. Click your name at the bottom of the sidebar and choose **Settings**.
2. In **Account**, click **Manage sign-in and security**.
3. Go to the **Security** tab and scroll to **Delete account** at the bottom.
4. Type `Delete account` to confirm. You may be asked to re-enter your password.

## What happens immediately

The moment you confirm:

* **You are signed out and can no longer sign in.** Deleting your account removes your login straight away, and this cannot be undone. If you want to use CourtAid again later, you will need to create a new account.
* **Your subscription is cancelled.** You are not charged again. Because access has already been provided for the period you paid for, there is no refund for the remainder of that period.
* **Your team seat is freed** (if you belong to a team), and your team's shared query allowance adjusts accordingly.

## What is erased

Within 30 days of deletion, everything you created is permanently removed from our database, file storage and search index:

* Matters and their documents
* Uploaded files (originals and searchable copies)
* Chats and their history
* Comparisons, chronologies, tabular reviews and drafts

During that 30-day window your data is kept but frozen and unreachable. This is a short safety net: if you deleted your account by mistake, contact support and we may be able to help. It is **not** a way to sign back in — your login is gone the moment you confirm.

> **A note about shared links.** If you previously shared a direct link to an uploaded document with someone, that link may keep working until your files are deleted at the end of the 30 days. If you need something removed immediately, contact support and ask for immediate deletion.

## What we keep

For legal and accounting reasons, a small amount of information is retained:

* **Invoices and payment records**, held by our payment provider (Stripe) — we are required to keep financial records for several years.
* **Anonymous usage totals** with no personal information attached.

## If you are on a team

* **A regular team member** can delete their own account at any time — it frees a seat and adjusts the team's shared allowance. Your colleagues' matters and work are not affected.
* **If you added a document to a colleague's matter,** that document stays with the colleague (it is transferred to them), so their chronology or draft is not broken.
* **If you are the team's admin,** hand over admin rights to another member (or close the team) before deleting, so your team is not left without an administrator.

## Need help?

If you want to download your data before deleting, or you need an immediate deletion, contact support at <help@courtaid.ai>.


---

# 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.courtaid.ai/account-and-billing/deleting-your-account.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.
