Last updated: 24 June 2026.
livediagram is built to need as little of your data as possible, and the whole codebase is public so you can check that for yourself. This policy explains what the hosted service at livediagram.app does with your data. If you self-host livediagram, you are responsible for your own deployment and this policy does not apply to it.
What we store
- Your diagrams. The content you create is saved so it is there when you come back, and so the people you share it with can see it. It is stored in our database on Cloudflare.
- Images you upload. Images placed on a diagram are kept in Cloudflare object storage and served back through the same API. Before a JPEG is stored, identifying metadata such as GPS location and camera details is stripped from it, so it never reaches anyone you share the diagram with.
- A browser id. If you use livediagram without an account, we keep a random identifier in your browser's local storage to link diagrams to your browser. It is not tied to your name or email.
- Account details, if you sign in. Sign-in is handled by our authentication provider, Clerk. If you create an account we receive your email address, and, if you choose Google sign-in, basic profile details from Google. We use these only to identify your account.
- API tokens, if you create them. If you create an API token to call the API from your own scripts, we store a one-way hash of it (never the token itself), its name, and a last-used timestamp, so the token can be verified and you can see when it was last active. Tokens are a signed-in-only feature, expire after six months, and are deleted when you delete your account.
- Basic operational logs. Our host, Cloudflare, keeps standard request logs that help us run the service securely.
What we do not do
We do not use tracking pixels, advertising, or third-party analytics SDKs. We do not sell your data, and we do not build advertising profiles. The repository is public, so what runs is what you can read.
Anonymous product analytics
To understand which features actually help, we record anonymous, first-party product events, for example "a diagram was created" or "a square was added". Each event is just three fixed labels: a category, an action, and an optional type like "Square" or "Edit". They never include anything that identifies you or your work: no names, no diagram or element content, no account id, no IP address.
We collect this ourselves, store it in our own database, and use no third-party analytics vendors. The data is never sold or shared, and the only place it goes beyond our own use is our public telemetry dashboard, where you can see exactly the same anonymous totals we do. You can turn it off for your browser at any time from Settings (see What We Collect).
Cookies and local storage
We use local storage to keep your browser id and your preferences. When you sign in, Clerk sets cookies to keep you logged in. We do not use advertising or tracking cookies.
Service providers
We rely on a small number of providers to run the service:
- Cloudflare, for hosting, database storage, and image storage.
- Clerk, for authentication (only if you sign in).
These providers process data on our behalf so that we can run the service.
Sharing and visibility
Anything you put on a diagram you share becomes visible to people who have the share link. You can protect a link with a password or give it an expiry, and revoking a link stops further access through it. See Share Link Security.
Keeping and deleting your data
You can delete any diagram you own at any time. You can also delete your account, and the data associated with it, yourself from your account settings.
Children
livediagram is not directed at children, and we do not knowingly collect data from children.
Changes
We may update this policy from time to time. The date at the top of this article reflects the latest version.
Contact
For privacy questions or requests, reach us at hello@livediagram.app.
Was this article helpful?