> For the complete documentation index, see [llms.txt](https://legal.clausebase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.clausebase.com/temporary-data.md).

# Temporary data

The platform keeps certain data stored for a short while, for operational reasons. 

## Converted PDF-files

The conversion of PDF-files is quite resource-insensitive and may even take several minutes for PDF-files with many pages and/or poor quality (e.g., scans). Moreover, the same PDF-file is often simultaneously used in different corners of the platform during the same day.

For this reason, PDF-files that are converted into an MS Word-file internally, are temporarily stored on the ClauseBase-server for 8 hours since their last usage.  This is currently the case for PDF-files that are uploaded in Doc Chat, Multi Document Table, Truffle Hunt, Text Compare, Bulk Compare, Bulk Operations and Summarise. 

## Rendered PDF/DOCX files

When a document/binder is converted into a PDF/DOCX-file, then the resulting file is stored between 60 - 120 seconds on the ClauseBase-server in order to allow for downloading that file. Afterwards it is deleted.


---

# 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://legal.clausebase.com/temporary-data.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.