Privacy policy

Live Diagrams at livediagrams.dev · effective 22 October 2026

Live Diagrams is a free, open-source tool for drawing distributed-systems diagrams and watching messages flow through them. It's made by Latch Kostov and runs entirely in your browser. There is no Live Diagrams server, no account and no database. The short version: your diagrams stay in your browser unless you choose to save them somewhere else, and we never receive them.

Jump to: Your diagrams · Google Drive · OneDrive · Dropbox · Your company's own copy · Confluence · Claude skill · Contact

Your diagrams

Diagrams you make or open are kept in your browser's local storage on your device. They're never uploaded to us. Embeds write nothing to this browser's storage. Delete a diagram in Your diagrams (its AI conversation goes with it), or delete everything with File → Privacy → Clear everything on this device…: every diagram, your edits to examples, AI conversations and settings that Live Diagrams keeps in this browser. Files you saved or exported stay where they are.
Save and Open use files on your device, which only your browser touches.
Interactive HTML (File → Share… → Interactive HTML…, the first way out it lists; also File → Export as) is made in your browser and downloaded to your device; it's never uploaded to us. The file holds everything it shows (the diagram, its simulations, icons and fonts) and makes no network requests when opened: not to this site, not for fonts, not to anyone. It writes nothing to the browser's storage. Anyone who has the file can open it, so keep it where your team already controls access, or require a password.
Interactive HTML with a password (Require a password in the same dialog) encrypts everything in the file that belongs to the diagram (its title, labels, notes, simulations and banner) the same way as a link with a password, below. The file's page title says only "Diagram (password protected)", even once it's open (browsers keep page titles in their history), and its name adds a few random letters. Opening it asks for the password and decrypts in the browser, offline; the password is never stored or sent anywhere, and it can't be recovered, so a lost password means exporting again. Anyone with the file and the password can open it, so send the password separately.
Embeds your own app supplies (File → Share… → Embed in your app…) show a diagram inside your website or intranet without putting it anywhere public. Your page fetches the diagram from your own server, with your own sign-in, and hands it to the viewer frame from this site in the browser. The diagram then exists only in that page and in the frame's memory while it's open: it's never put in a URL, never written to the browser's storage and never sent to us. This site only serves the viewer's code; it has no way to see what it draws. The viewer talks only to the page that embeds it, at the address that page names.
Links with a password (File → Share… → Link with password…) carry the diagram encrypted (AES-256-GCM, with a key derived from your password by PBKDF2-SHA-256 at 600,000 iterations). The encryption and decryption happen in your browser; the password and the readable diagram are never sent anywhere. Anyone with both the link and the password can open it, so send the password separately. Once opened, the encrypted part is cleared from the address bar, though your browser's history may still list the address as it was first visited.
Share links (File → Share… → Public link or embed → Share link…, last and folded away, like the public embed) carry the diagram inside the link, after the #. Browsers never send that part to a server, so the diagram travels only to whoever you send the link to. Anyone who has the link can open the diagram, and chats and email keep it, so use a link with a password for anything internal. Opening a link takes the diagram out of the address bar, but your browser's history (and any history sync) may still list the link as it was first visited.
Edit together (File → Share… → Edit together…, where this copy offers it) lets people edit a diagram at the same time. The browsers in a room connect directly to each other, and the diagram travels between them end-to-end encrypted, under a key that's only in the room's link (after the #, so never sent to a server). Everyone in the room can see your IP address. So can the services that introduce the browsers to each other: on livediagrams.dev, two public matchmaking services (tracker.openwebtorrent.com and tracker.webtorrent.dev) and Cloudflare's STUN server, run by other people. They never see the diagram, the link or any key. The dialog that starts or joins a room says so first. Nothing of a room is sent to us. While you're in a room, an encrypted copy is kept in your browser so a reload loses nothing; Clear everything on this device removes it. Anyone with a room's link can edit, so send it like a password.
AI features act only when you use them. Chrome's built-in model runs on your device. An AI agent in your browser, or a chatbot you paste a prompt into, sees a diagram only when you ask it to; that's your own tool, under its own terms. Live Diagrams never sends your diagrams to an AI service itself, and never uses them to train AI models. Dictation (the mic) uses your browser's own speech recognition: in Chrome that's usually Google's speech service, which receives the audio, unless the browser can recognise speech on the device. While it does, a line by the mic says so ("What you say may be sent to Google's speech service", naming the browser's maker), every time.

Private diagrams

For work diagrams, or anything you'd rather keep to yourself, mark a diagram Private (File → Privacy → Private diagram, or turn on New diagrams are private, which the first import of an infrastructure file offers once). A lock beside its title shows it's on. A private diagram:

can't be shared as a link or embedded by link, so it never ends up in a URL, a chat or your browser history (its simulations' names stay out of the address bar too, and a link made some other way won't show in an embed). It can still be embedded in your own app the private way, where your page supplies it (see above);
isn't saved to Google Drive, OneDrive or Dropbox, and Google's scripts aren't loaded for it: opening the File menu while it's open loads nothing from Google;
can't be edited together: it has no room, and a diagram that turns private while it's in one leaves the room;
is off-limits to AI: the page offers no tools to AI agents while it's open, and Copy for AI and copied prompts are off. Chrome's built-in model runs on your device, so you can allow it for a private diagram; dictation then works only where your browser recognises speech on the device too.
stays private when you duplicate it, copy its nodes into another diagram, or export it and open the file again (the file says "private": true).
can still be exported as a file, an Interactive HTML file included (with or without a password): that's your own action, like saving it to this device.

What Private can't do, honestly:

A file you export or save to this device is yours to send anywhere. Private stops the app from sharing, not you.
Your browser's extensions can read any page they're allowed on, this one included. Use a browser profile without extensions you don't trust for sensitive work.
Diagrams are kept unencrypted in your browser's storage on this device. Anyone who can use your device and browser profile can open them, so lock your device and avoid shared profiles.

Live Diagram for Confluence

The free Confluence Cloud app views and plays a diagram stored as a page attachment. It uses the signed-in reader's own permissions through Atlassian's Forge bridge. Configuration lists this page's attachment metadata and reads the selected diagram to offer its simulations. When an editor chooses a local file, the app validates it in the browser and uploads or replaces it in Confluence only on that editor's action.

Diagram content stays in browser memory while open and in the Confluence attachment; it is not copied into macro settings. The page stores only the attachment ID, selected simulation, height and theme. There is no independent app database, Forge app storage or persistent browser cache. Attachments and settings follow Confluence's data residency, version history, migration and retention controls. Uninstalling the app does not delete your Confluence attachments or their history; manage or delete them in Confluence.

The app's resources are hosted on Atlassian Forge. The macro sends no data outside Atlassian services and your browser: no requests to livediagrams.dev, no outbound links, no analytics and no additional third-party services. Normal Confluence attachment requests still happen. It requests no profile or email APIs and processes no personal data beyond what Confluence provides to render the page and the selected attachment, which may itself contain personal data. The publisher receives no copy and logs no diagram content. Atlassian's own platform operations remain subject to its policies.

The scopes are read:attachment:confluence, for listing and reading the page's attachments, and write:confluence-file, for explicitly uploading or replacing a diagram. Both use your Confluence permissions. The macro cannot bypass page restrictions or upload as a different app identity. Playback starts only when you press Play.

See setup and troubleshooting or ask for support on GitHub. Support issues are public: never attach private or work diagrams, and remove personal or confidential details from screenshots. Visiting documentation or GitHub is a separate action outside the macro.

Live Diagrams skill for Claude

The Live Diagrams skill (also listed as a plugin in Claude's directory) helps Claude draw diagrams for you. Its scripts run on your own machine, with Node.js, only when Claude runs them for a request of yours: they read the diagram files you give them and write the files you ask for, such as a diagram file or an Interactive HTML file. They make no network requests, collect nothing about you, and have no account, telemetry or server of their own. The publisher receives nothing and keeps nothing.

Interactive HTML made by the skill is built locally and behaves exactly like the one made in the app (above): it makes no network requests when opened.
A password-protected HTML file uses a password you type when asked, or one you set in the LIVEDIAGRAMS_HTML_PASSWORD environment variable. It is used only to encrypt that file on your machine; it is never stored, logged or sent anywhere.
Share links are only printed for you, and only when you ask for one; making one sends nothing anywhere. They work like the share links above, so anyone with the link can read the diagram. The skill refuses to make a link for a private diagram.
Claude itself sees the diagrams and requests in your conversation under Anthropic's own terms and privacy policy, as with anything else you share with it. Never put secrets, credentials or personal data in a diagram.

No analytics, no ads, no tracking

Live Diagrams has no analytics, no tracking pixels, no ads and no cookies of its own. We don't sell, rent or share anyone's data, because we never receive it. Fonts and icons are served from this site, not from a third party.

A strict Content-Security-Policy means the page can only talk to this site and the storage providers you connect (Google Drive, OneDrive, Dropbox). Your browser enforces it: no other site's scripts can run here, and the page can't send anything anywhere else. Links you follow tell other sites only that you came from livediagrams.dev, never which diagram or page.

The site is static files hosted on Vercel. Like any web host, Vercel handles the requests your browser makes for those files (including your IP address) to deliver and protect the site. Live Diagrams doesn't receive or keep those logs for any other purpose.

Cloud storage (only if you choose it)

Where the File menu offers Google Drive, OneDrive or Dropbox, you can save to and open from your own account there. Nothing of your diagrams is sent to one until you pick it. For all three:

You sign in on the provider's own page, in a pop-up. Live Diagrams never sees your password.
Your browser talks to the provider directly. Your files and the access token never pass through any Live Diagrams server (there isn't one), and we never receive a copy.
The access token is kept only in the open tab's memory, is sent only to the provider that issued it, and is gone when you close or reload the tab. It's never written to your browser's storage.
Live Diagrams remembers which file a diagram was saved to or opened from (the provider, the file's id and name, in your browser's storage), so Save goes back there. A diagram you open is kept in Your diagrams in this browser, like any other.
Live Diagrams asks for the smallest access each provider offers, and reads no profile, email address, contacts or other files.

Google Drive

What we access. Only the drive.file scope: the files you create with Live Diagrams or pick yourself in Google's file picker. Live Diagrams can't see, list or change anything else in your Drive, and it doesn't ask for your Google profile or email address.
How it's used. To save the diagram you're working on as a .diagram.json file in your Drive, to update that same file when you save again, and to open a file you picked. Nothing else.
Where it goes. File contents go directly between your browser and Google's servers. Nothing goes through our servers; we have none. Opening the File menu where Google Drive is offered loads Google's sign-in and picker scripts from Google, so a click can open them straight away (not while a private diagram is open: then they load only if you choose Open from → Google Drive); Google's own privacy policy covers what Google receives.
How it's stored. The Google access token stays in the tab's memory only and is never stored or sent anywhere but Google. A diagram you open from Drive is kept in this browser (see above), not by us.
Sharing. We don't share, sell or transfer Google user data to anyone, don't use it for advertising, don't run analytics on it, and don't use it to train AI models. No person at Live Diagrams can read it, because it never reaches us.
Revoking access. Remove Live Diagrams at myaccount.google.com/permissions. Files Live Diagrams saved stay in your Drive until you delete them there; delete the copy in this browser from Your diagrams.

Live Diagrams' use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

OneDrive

What we access. Files.ReadWrite.AppFolder: only Live Diagrams' own folder, Apps › Diagrams, in your OneDrive. Live Diagrams can't see anything else in your OneDrive. offline_access lets the open tab renew its sign-in for up to a day without asking again; that renewal token is kept in the tab's memory too.
How it's used. To save diagrams into that folder, list it when you choose Open, and read the file you pick.
Where it goes. Directly between your browser and Microsoft. Nothing goes through our servers, and nothing is shared, sold, used for ads or analysed.
Revoking access. Personal accounts: account.live.com/consent/Manage. Work or school accounts: myapps.microsoft.com, or ask your admin. Files stay in Apps › Diagrams until you delete them there.

Dropbox

What we access. An app folder only (files.metadata.read, files.content.read, files.content.write): Live Diagrams' own folder, Apps › Diagrams, in your Dropbox. Live Diagrams can't see anything else in your Dropbox.
How it's used. To save diagrams into that folder, list it when you choose Open, and read the file you pick. Dropbox's sign-in lasts about four hours; there is no long-lived token.
Where it goes. Directly between your browser and Dropbox. Nothing goes through our servers, and nothing is shared, sold, used for ads or analysed.
Revoking access. In Dropbox, open Settings → Connected apps and remove Live Diagrams. Files stay in Apps › Diagrams until you delete them there.

Your company's own copy

Live Diagrams is static files, so a company can run its own copy on its own servers, behind its own sign-in, and keep every diagram inside its network. Such a copy talks only to the company's site, never to livediagrams.dev or to us. It can be built without share links and without tools for AI agents, with new diagrams private from the start, and under the company's own name. The self-hosting guide explains how. A company's copy is run by that company, under its own policies; this policy covers livediagrams.dev.

Children

Live Diagrams isn't directed at children under 13 and doesn't knowingly collect anything from anyone.

Changes and contact

If this policy changes, the new version is posted here with a new effective date, and every change shows in the site's public source code. We'll never start using data in a new way without asking you first.

Privacy questions or requests: latch.kostov@gmail.com, or open an issue on GitHub. Issues are public; never include personal details or private or work diagrams.