Privacy statement
Folio Writer Cloud · last updated August 29, 2026
Folio Writer Cloud exists to let you write and edit together. It is built to know as little about you as possible, and this page says plainly what the service stores, what it can and cannot see, and how long anything is kept. There is no advertising and no third-party analytics anywhere in the app — no trackers, no pixels, no fingerprinting.
What is stored
Your projects: the documents, images, and project structure you create or upload, kept on the server so your collaborators can reach them by link. Alongside them the server keeps operational metadata — file sizes, modification times, a revision counter, and the project title chosen at creation.
End-to-end encrypted projects
Any project can be created end-to-end encrypted. A random 256-bit key is
generated in your browser and travels only in your links — it is the part after the
“.” in /p/…#token.key. Link fragments are never sent over
the network to us, so the server never has the key. Documents and the project
outline are encrypted in your browser (AES-256-GCM) before upload; live co-editing
exchanges only encrypted updates through a relay that stores and forwards blobs it
cannot open.
Honesty about the edges: even for encrypted projects the server can still see approximate sizes, timing of edits, the number of documents and collaborators connected, the creation-time title, and — if you sign in — your email. Server-side PDF/Word compilation is unavailable for encrypted projects, precisely because the server cannot read them. And the key is genuinely only in your links: if every copy of a link with the key is lost, the content is unrecoverable by anyone, including us.
Sharing model
Projects are reachable only through unguessable capability links (owner, edit, or
view). The app sends a no-referrer policy so a link's secret is not leaked
to other sites, and an optional project password can be layered on top. Public and demo
projects are the exception by design: they are listed openly, carry no owner
capability, and anything non-demo in the public space is deleted after 3 days.
Accounts
Accounts are optional — sharing and collaboration work without one. An account stores exactly one piece of personal data: your email address, used to send one-time sign-in links. There are no passwords. Usage against your plan's quota is measured in bytes, not by reading your content.
Retention and deletion
Deleting a project removes its files from the server. Public non-demo projects expire
after 3 days; demo sandboxes are wiped back to a frozen baseline daily. You can export
any project as a .folio zip at any time — there is no lock-in.
Operational data
Like any web server, the service keeps short-lived technical logs (IP addresses, request times) for abuse prevention and debugging, and applies rate limits. These logs are not used for profiling and are not shared.
Self-hosting
The strongest privacy guarantee is running the software yourself: Folio Writer Cloud ships with a Docker setup so a lab or team can host the entire service on their own machine, where none of the above ever leaves their infrastructure.
Questions or concerns: contact the operator listed at foliowriter.app.