Privacy

This describes how the application actually handles your files today, not a legal template.

What happens to an uploaded file

When you run a workflow, your files are validated (type, size, filename) and written to a temporary, per-request directory on the server. Each registered tool reads only the files it needs from that directory and writes its output back into it. Nothing is sent to a third-party AI service, and no hosted language model sees your file contents. The workflow planner only ever sees your typed instruction and your files' names/types/sizes, never file contents.

How long files are kept

Uploaded files and workflow outputs live only in that temporary directory. A background process removes job directories older than 30 minutes, and results are meant to be downloaded shortly after a workflow finishes, not stored indefinitely.

Limits

Individual files up to 50 MB, up to 200 MB total per request, across up to 30 files. Only PDF, JPG, PNG, WebP, DOCX, and plain-text files are accepted; anything else is rejected before it reaches any processing step.

What we don't claim

We don't describe this as end-to-end encrypted or as never touching a disk. Files are written to temporary server storage to be processed, which is a normal and necessary part of running the tools you request. If you're handling highly sensitive documents, weigh that against any tool that processes files on a server you don't control, including this one.