Your files are the whole point, so it helps to know exactly where they live and who can reach them. every app stores files on Cloudflare infrastructure behind an authenticated API, never in a third-party analytics product, and you keep control of them whether you sign in or stay a guest. This page explains how it works; the Privacy Policy , which covers every liveworkspace app, is the formal statement for the hosted service.
Where Your Work LivesFiles are saved through a single Cloudflare Worker API. The browser never talks to
storage directly.
In livediagram
Durable storage is one Cloudflare Durable Object per canvas, reached only through the API:
the canvas's tabs, comments and the images it places are stored there. Where it is filed, its
folders, share links and its History events (the last 30 days) are kept by liveworkspace's index,
the shared library behind every liveworkspace app. - Real-time state (who is in the room, live
cursors, in-flight edits) is handled by the same Durable Object, the canvas's room. It also keeps
a working record of collaborative input (answers, ideas, ticks, votes, comments and live polls) in
its own storage, so that saves made at the same moment can be merged. - Images you add are
kept by liveworkspace's media service, and a cached picture of each canvas, used for its thumbnail
and live image, in Cloudflare R2 object storage; both are served back through the same API.
Location and camera details are stripped from a JPEG before it is stored.
In livedocuments
Durable storage is one Cloudflare Durable Object per document, reached only through the API:
the document's tabs, pages, comments and the images it places are stored there. Where it is filed,
its folders, share links and its History events (the last 30 days) are kept by liveworkspace's
index, the shared library behind every liveworkspace app. - Real-time state (who is in the
room, live cursors, in-flight edits) is handled by the same Durable Object, the document's room.
It also keeps a working record of collaborative input (such as comments), so that saves made at
the same moment can be merged. - Images you add are kept by liveworkspace's media service, and
a cached picture of each document, used for its thumbnail and live image, in Cloudflare R2 object
storage; both are served back through the same API. Location and camera details are stripped from
a JPEG before it is stored.
In livehuddle
Durable storage is one Cloudflare Durable Object per space, reached only through the API:
the space's tabs and the images it places are stored there. Where it is filed, its folders, share
links and its History events (the last 30 days) are kept by liveworkspace's index, the shared
library behind every liveworkspace app. - Real-time state (who is in the room, live cursors,
in-flight edits) is handled by the same Durable Object, the space's room. It also keeps a working
record of collaborative input (reactions and the like) in its own storage, so that saves made at
the same moment can be merged. - Images you add are kept by liveworkspace's media service, and
a cached picture of each space, used for its thumbnail and live image, in Cloudflare R2 object
storage; both are served back through the same API. Location and camera details are stripped from
a JPEG before it is stored.
In livedesign
Each design's content (its tabs and everything on them) lives in its own Cloudflare Durable
Object, one per design, with its own storage. The same object runs the design's real-time room
(who is in it, live cursors, in-flight edits) and keeps a working record of collaborative input
(such as comments), so that saves made at the same moment can be merged. - Where each design is
filed and who may open it (its folder, team, share links, Trash, and its History events for the
last 30 days) is kept by liveworkspace's index, the service every liveworkspace app shares. Your
account, settings and teams are kept by liveworkspace's accounts service. - Images you add are
kept by liveworkspace's media service, in Cloudflare R2 object storage, and served back through
the same API, which checks who may see them. Location and camera details are stripped from a JPEG
before it is stored. A cached picture of each design, used for its thumbnail and live image, is
kept in the API's own R2 storage.
In liveplanner
Durable storage : each plan lives in its own Cloudflare Durable Object, which keeps its tabs,
cards, sheets and forms in its own storage. Where a plan is filed, its folders, its share links
and its History (the last 30 days) are kept by liveworkspace's index, the service every
liveworkspace app files its work in. - Real-time state (who is in the room, live cursors,
in-flight edits) is handled by the same Durable Object, one room per plan. The room also keeps a
working record of collaborative input (answers, ideas, ticks, votes and comments) in its own
storage, so that saves made at the same moment can be merged. - A cached picture of each plan ,
used for its thumbnail, live image and share-link card, is stored in Cloudflare R2 object storage
and served back through the same API. The only pictures liveplanner stores are the ones you add
yourself: to a card's Image field, or to a form as its cover or a Picture block. A form's
Search tab sends your search words from your browser straight to Openverse, the open image
search engine, which sees them and your IP address under its own privacy policy; our servers never
see the search.
Or nowhere but your own machine. A file created in Offline Mode lives only in this browser's IndexedDB. It is never stored by the API, so none of the storage above holds a copy of it, and it stays that way until you choose Sync File to move it to the cloud.
every app runs on Cloudflare. Your file content goes to another company only when you use a
feature that needs one:
Emails about your work go through the email provider. They name the file.
In livediagram, livedocuments and livedesign
A mention or an assigned action quotes a little of the comment or action (see Email
Notifications ).
In liveplanner
liveplanner's email goes out through Cloudflare Email Service too. A mention or an assigned action
quotes a little of the comment or action (see Email
Notifications ). AI tools you connect yourself,
through MCP or the CLI , read
the plans you let them reach, under their own terms.
In livediagram
Reading sticky notes from a photo sends small crops of the notes, never the whole photo, to
the reading model the deployment uses (Google's Gemini on livediagram.app). On a deployment
without a reading model the notes are read in your browser and nothing is sent. Nothing is sent
until you import a photo.
In livediagram and livehuddle
Google Drive , if you connect it, gets a copy of your
files in your own Drive, written by liveworkspace's Drive service (it holds your Google
grant, sealed, and never hands it to your browser). Image search sends what you type in the
image picker's Search tab straight from your browser to Openverse, the open image search
engine; no every app server sees it.
What Is Stored, and Who Can Read ItA file is owned by an identity. That identity is either a signed-in account or, for guests, a guest identity that liveworkspace gives your browser, which is the same in every liveworkspace app. Only the owner, people holding a valid share link , and the members of the team whose library the file is in can read a file. Opening a file you cannot access returns a plain "not found", so its contents and name are never revealed.
In livehuddle
Calls, cameras and screens. What you say, show on camera or share from your screen in a Space is never stored. It travels from your browser through Cloudflare's realtime service to the people who can hear you, and nowhere else: livehuddle's server sets up each connection but never receives the sound or picture, and nothing is recorded or transcribed.
Only when you choose. The microphone opens the first time you unmute (it starts muted), the camera when you turn it on, and a screen when you pick it, each after your browser asks. A muted microphone is released after 15 seconds with nobody else on your tab, and a screen share carries no sound.
A preview stays with you. A camera or screen turned on with no call joined shows only to you, marked Only You ; nothing is sent.
Who receives it. The people in earshot, or in the same room, hear you and see your camera and screen. From a stage, the whole tab hears you, and sees you only if the stage shows cameras. Everyone on the tab can see that you are talking, never what you say.
Never peer to peer. Your browser connects to Cloudflare, not to anyone else's browser, so other people never see your IP address.
Your character's moves, messages, status, raised hand and knocks go live to the people in the Space and are never stored.
The Privacy Policy says the same, formally.
Staying in Control
Guest by default. You can build and share files without ever creating an account. See working as a guest .
Keep it in the browser. Offline Mode keeps a file off the server entirely.
Share on your terms. Add a share password to a file or an expiry to a share link, and revoke links at any time.
Delete what you own. Deleting a file moves it to the Trash for 30 days, then removes it with its tabs, comments and share links; you can delete it permanently from the Trash sooner. Signed-in users can delete their whole account , which removes their personal files, folders, tokens and preferences straight away.
Opt out of analytics. The anonymous usage events have a switch in Settings. See What We Collect .
In livediagram, livedocuments, livedesign and livehuddle
Deleting your account also removes your images.
In livediagram, livedesign, livehuddle and liveplanner
Files in a team library stay with the team when you delete your account.
every app does not claim end-to-end encryption. Work is protected by authentication and access
controls, not by client-side encryption. Found a way around them? Please report it
privately .