Privacy Policy
Last updated: 29 August 2026
BPMN Builder is a free, personal side project — a demo of a semantic BPMN 2.0 editor. It is not a commercial service. This page describes exactly what it stores, where that data goes, and how to get it deleted. It is written from the actual source code, which is public at github.com/Perlitten/bpmn-builder.
Who is responsible
This project is operated by Andrei Domashkevich, an individual based in Cyprus. For any privacy question or request, write to privacy@bpmnbuilder.com.
Why sign-in is required
You need a Google account to open the editor. This is not there to collect data about you — it is the abuse control for a small project: it keeps the editor and the AI feature from being used anonymously by bots and automated traffic. The public landing page, including the live demo diagram, works with no sign-in and stores nothing about you.
What is stored
| Data | Where it comes from | Why |
|---|---|---|
| Google account ID, email address, display name, profile picture URL | Returned by Google when you sign in | To recognise you on return visits and to keep your diagrams separate from everyone else's |
| Session record: a hash of your session cookie, your user ID, an expiry timestamp | Created when you sign in | To keep you signed in for 14 days |
| Your diagrams: name, description, BPMN XML, derived layout data, version, timestamps | Whatever you create, import, or edit | This is the product |
| Feedback messages, if you send any, with the page and diagram they were sent from | The in-app feedback form | So I can act on them |
| IP address | Your browser, seen by the hosting provider | Server logs and rate limiting. Not stored in the application database. |
What is not stored
-
Your Google access token is never saved. It is used once, in memory, to read your
name, email, and picture from Google, and is then discarded. The app never asks for access to your
Gmail, Drive, Calendar, contacts, or anything else — the only permissions requested are
openid,email, andprofile. - Your password. There isn't one. Sign-in is entirely handled by Google.
- Your session cookie itself. Only a SHA-256 hash of it is stored, so the database cannot be used to impersonate you.
- Analytics, tracking, advertising, or profiling data. There is no analytics tool, no tracking pixel, no ad network, and no third-party script of any kind on this site.
The AI assistant sends your process to a third party
Read this before putting anything sensitive into a diagram.
When you use the AI Architect, the following is sent to an external AI provider — currently
NVIDIA (integrate.api.nvidia.com) or Google (Gemini API), depending on configuration:
- the name of the process you are editing;
- the message you typed and the recent messages in that chat;
- the full semantic graph of the diagram — every step, gateway, branch, role, and pool name.
In other words, the wording of your process steps leaves this service. That provider processes it under their own terms and privacy policy. Diagram geometry and BPMN XML are not sent. If you never open the AI Architect, nothing about your diagram is sent anywhere.
Who else touches the data
| Provider | Role | What they see |
|---|---|---|
| Sign-in | That you signed in to this app. Your profile picture is also loaded directly from Google's servers while you use the app, so Google sees your IP address when it is displayed. | |
| Vercel | Application hosting (region iad1, United States) |
Request logs, including IP addresses and requested URLs |
| Neon | Database hosting (European Union) | Everything in the table above, at rest |
| NVIDIA or Google | AI model provider | Only what is listed in the section above, and only when you use the AI Architect |
Nothing is sold, rented, or shared with anyone else. There are no marketing emails — the app never sends you email at all.
Cookies and local storage
This site sets two cookies. Both are strictly necessary to sign you in, and neither is used for tracking, so there is no cookie banner to click through.
| Cookie | Purpose | Lifetime |
|---|---|---|
bpmn_session | Keeps you signed in. HTTP-only, Secure, SameSite=Lax. | 14 days |
bpmn_oauth_state | Protects the sign-in redirect against forgery. | 10 minutes |
The editor also uses your browser's local storage to hold unsaved diagram edits, so that a dropped connection or a closed tab does not lose your work, and a flag remembering that you have seen the editor introduction. Both stay on your device and are never transmitted anywhere. Clearing your browser data removes them.
How long it is kept
- Sessions: 14 days, then they expire.
- Diagrams: until you delete them, or until you ask for your account to be removed.
- Account record and feedback: until you ask for removal.
- Hosting logs: for whatever period Vercel retains them, which is short.
This is a side project and may be shut down at any time. If that happens, the database is deleted with it. Export anything you care about — the editor has BPMN, SVG, PNG, and PDF export built in.
Your rights
You can ask for a copy of your data, ask for it to be corrected, or ask for all of it to be deleted. Deleting individual diagrams works from the app. Deleting your whole account is not yet a button in the interface — email privacy@bpmnbuilder.com and I will delete your account record, sessions, diagrams, and feedback. I will confirm when it is done.
If you are in the EU or UK, you also have the right to object to processing and to complain to your national data protection authority; the authority for this project is the Cypriot Office of the Commissioner for Personal Data Protection. The legal basis for the data described here is the legitimate interest in running a functioning, abuse-resistant demo, and — for the diagrams themselves — the performance of the service you asked for.
Children
This project is not intended for anyone under 16.
Security
Traffic is HTTPS-only. Session cookies are HTTP-only and cannot be read by JavaScript. Diagrams are scoped to their owner and are not readable by other signed-in users. That said, this is a personal project without a security team behind it: please do not store anything confidential here. If you find a vulnerability, the reporting process is in SECURITY.md.
Changes
If this policy changes, the date at the top changes with it, and the previous version stays in the public git history of the repository.