Your documents.
Where files sit, how long they stay, how to delete them, and what leaving looks like.
Data & retention
Where your documents go
Marapone is a hosted service. Your documents are uploaded to infrastructure we operate, in the browser and in the mobile app alike, and there is no configuration that keeps processing on your own machines. Everything below is about what happens to those documents once they are with us, not a claim that they never left.
Who reads them
Our own model, on our own hardware, in a workspace scoped to your account. There is no client for OpenAI, Anthropic, Google or any hosted model provider in the codebase, so there is no code path that could send a drawing or an RFI to one. Nothing of yours is pooled with another firm’s or used to train anything.
How long they stay
For as long as the project exists, unless you set a shorter retention window. Deleting a project removes its documents, its extracted data and any project-specific derived artefacts. Operational logs record that a job ran, not what was in it.
Deleting everything
Self-serve, from your account: erase your data or close the account entirely. If you would rather we did it and confirmed in writing, ask.
For your IT reviewer
We will sign a DPA, name our infrastructure providers and set your retention window before you commit to anything. The security pack is one document written for exactly that review, and Trust lists what the architecture rules out and how to check each one yourself.