Privacy Policy

Last updated: 21 June 2026

The short version. Diagramforce has no servers of its own, no user accounts, no cookies, and no analytics or tracking. It runs entirely in your browser. Your diagrams stay on your device - and, only if you choose, in your own Google Drive. Diagramforce never sees, collects, sells, or transmits your diagrams or personal data.

1.Who this policy covers

Diagramforce is a free, open-source, browser-based diagram editor created by Mateusz Dąbrowski and served as static files at diagramforce.mateuszdabrowski.pl. This policy explains what happens to your information when you use it. Because there is no backend and no account system, there is very little to explain - most of what follows describes data that simply never leaves your control.

2.Data stored on your device

Diagramforce saves your work and preferences in your browser's local storage on your own device. This includes your open diagrams and tabs, any diagrams you save by name, your theme choice, your custom templates (which also sync to your Google Drive when you connect it), brand colours, and - if you connect Google Drive - your Google sync settings and the file IDs of diagrams the app has created or opened for you.

This data stays in your browser. It is not transmitted to Diagramforce or any third party.
Diagramforce uses no cookies.
You can erase it at any time by clearing your browser's site data.
Local storage is per-browser and per-device. Private/incognito windows discard it when closed.

Share links

When you create a standard Diagramforce link, the entire diagram is compressed into the link itself (the part after the #). The link is built in your browser, and the part after the # is, by web standards, never sent to a web server. However, anyone who has the link can open the diagram, so treat a share link like the diagram itself: if you post it publicly it may be copied, cached, or indexed by others. A standard link is a frozen snapshot and cannot be revoked once shared.

If you connect Google Drive you can instead create a Google Drive link (a short link to a live file in your own Drive - see §4) or a group link that reopens every diagram in a tab group. Unlike a standard link, these point to live files you control: you can change who can open them, or stop sharing them, through Google Drive.

Exports

When you export a diagram (JSON, PNG, SVG, or GIF), the file is generated in your browser and saved wherever you direct your browser to put it. You control it entirely.

4.Google Drive integration (optional)

Google Drive sync is off by default. You only ever involve Google if you explicitly connect it.

Limited access. When you connect, you authorise Diagramforce with Google's drive.file scope. Under this scope the app can access only the files it creates, or files you explicitly open with it through Google's own file picker. It cannot see or touch anything else in your Drive.
Your Drive, directly. Diagrams are stored as ordinary files in a Diagramforce folder in your own Google Drive; your custom templates library is synced to a single file in the same folder. They move directly between your browser and Google. Diagramforce has no server in the middle and never receives or stores them.
Sharing. If you share through Drive, you choose who can open it - a public link, anyone in your organisation, a team Shared Drive, or specific people (with view access, or edit/“collaborate” access) - using Google Drive's own sharing controls. You can also share a whole tab group as a single public link. Choosing editable/collaborate sharing creates an additional copy file in your own Drive that the recipient can edit.
Opening a diagram shared with you. If you open an editable (collaborate) diagram someone shared with you and edit it, Diagramforce keeps a private backup copy in your own Drive so you don't lose your work if the owner later revokes access. If you open a view-only (copy) diagram and edit it, your changes are saved as a new copy in your own Drive (the original is untouched). These files live only in your Drive, and Diagramforce never receives them.
Inviting specific people. When you invite named people, the email addresses you enter are sent to Google Drive to grant them access, and Google sends each person a notification email. Diagramforce does not store those addresses on any server (there is none).
Organisation sharing and your email. Only if you choose the “Organisation” sharing option, the app asks once - with a separate, explicit consent - for the openid/email scope to read your email address. This is used solely to determine your Google Workspace domain so the link can be limited to your organisation. Your email is not stored on any server and is not used for anything else. If you never use Organisation sharing, this is never requested.
Revoke anytime. You can withdraw Diagramforce's access at any time from your Google Account permissions, and delete any files it created from your Drive.

Your use of Google Drive is also governed by Google's Privacy Policy and your own agreement with Google. Diagramforce's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Diagramforce does not transfer, sell, or use Google user data for advertising, and does not allow humans to read it.

5.Hosting & technical logs

The app is delivered as static files from GitHub Pages (GitHub, Inc.), served through Cloudflare. As with visiting any website, these providers automatically process standard request metadata - such as your IP address, browser type, and the files requested - purely to deliver and protect the site. Diagramforce adds no analytics, advertising, tracking pixels, or fingerprinting on top. See the GitHub and Cloudflare privacy policies for how they handle that metadata.

All third-party libraries the app uses (JointJS, the Salesforce Lightning Design System, pako, and gifenc) are bundled and served from the same domain - no third-party CDN is contacted while you use the app. Google's servers are contacted only if you use the optional Drive features.

6.What we never do

No user accounts and no sign-up.
No analytics, tracking, advertising, or fingerprinting.
No cookies.
No selling or sharing of personal data.
No server-side storage of your diagrams - Diagramforce has no application server.

7.Your control & rights

Because your data lives on your device and in your own Google Drive, you are in direct control of it at all times. You can clear your browser storage, delete your Drive files, and revoke Google access whenever you like. Diagramforce holds no copy of anything to request, export, or delete on your behalf. Where data-protection laws such as the GDPR apply, the practical effect is that you already hold and control your own data.

8.Children

Diagramforce is a professional tool not directed at children, and it knowingly collects no personal data from anyone - including children.

9.Changes to this policy

We may update this policy from time to time. The “Last updated” date at the top always reflects the current version. Significant changes will be reflected here on this page.

10.Contact

Questions about this policy can be raised by contacting Mateusz Dąbrowski on LinkedIn, or via the project's GitHub repository. There is no data to control, so there is no data controller in the usual sense; the person otherwise responsible for this site is Mateusz Dąbrowski (Poland).