Summary: BlockWerk is engineered client-first. Your block diagrams, simulation models, and parameter configurations are processed inside your web browser via WebAssembly (WASM) and stored in your local browser storage (IndexedDB). They leave your device only when you use a feature that sends them: sharing a diagram (section 2), the AI assistant, the MCP server or collaboration (section 4), the feedback form, or a session recording you allowed, which can show your canvas (section 3).
1. Client-Side Simulation Architecture
BlockWerk runs its numerical simulation engine (compiled from Rust to WebAssembly) locally on your device. When you run a simulation, build a diagram, or analyze signals:
- All differential equations, parameters, and matrix operations execute within your browser tab.
- No simulation data or diagram topographies are sent to external cloud servers during standard operation.
- Project files remain saved strictly within your browser's IndexedDB storage.
2. Diagram Sharing
If you choose to share a diagram using the "Share" feature, your browser encrypts the diagram with a fresh random key (AES-256-GCM) before anything leaves your device. Only the encrypted data is stored on our hosting provider (Netlify); the key is placed in the part of the link after the #, which browsers never send to a server. We therefore cannot read a shared diagram, and neither can anyone without the full link.
- A short link stops working after 365 days. The encrypted data is deleted when an expired link is next requested; until then it stays stored, unreadable without the full link. Because links are cached for up to a day, a link can keep working for up to a day after it expires.
- To prevent abuse of the storage, the total number of new links per day is capped, and rapid repeated requests from one address are refused by our hosting provider at the network edge. We keep no counter or other record per visitor.
- If short-link storage is unavailable or the day's cap is reached, BlockWerk falls back to a self-contained link that carries the compressed diagram in the address itself. Such a link is not encrypted: anyone who has it can read the diagram, and like any web address it appears in our hosting provider's server logs when it is opened. The embed code uses this form unless you choose the short link.
3. Analytics & Telemetry
To measure application performance, detect solver errors (such as algebraic loops or numerical divergence), and understand how BlockWerk is used, BlockWerk uses PostHog EU Cloud (Germany) in three levels. Only the first runs without your consent; the other two are separate choices you make in the consent banner or in the in-app Privacy Settings.
- Level 1 — Cookieless basic statistics (always on, legitimate interest): page views, referring site, technical errors (such as JavaScript exceptions and load performance), clicks that had no effect, and whether a visit reached a few milestones (a first action, a simulation started, a simulation finished). PostHog runs in Cookieless Mode for this: it writes no cookies and nothing to your browser storage. A daily-rotating hash calculated on PostHog's EU servers tells visits apart without storing your raw IP address. This level keeps running when you choose "Decline"; usage milestones then stop. Under European ePrivacy rules (Dutch Telecommunicatiewet art. 11.7a) and GDPR Art. 6(1)(f), this minimal-impact processing relies on legitimate interest. To stop it as well, visit the application once with
?optout=true.
- Level 2 — Usage analytics and error reports (consent): which features and block types you use (e.g. C++ code export, Bode stability analysis), solver error reports and crash reports. Only with this consent is a random identifier saved to your browser storage (
localStorage) to recognise returning visits.
- Level 3 — Session recordings (separate consent, only together with level 2): a recording of what you do in BlockWerk — mouse movement, clicks and the canvas, which can show your diagram. Input fields, the AI chat and code editors are masked. Visitors who accepted analytics before 19 November 2026 were never asked about recordings: for them recording stays off until they say yes. BlockWerk may ask once more right after a simulation fails or the app crashes, or you can tick the box in the feedback form; both turn on level 2 as well.
- Crash Reports (level 2): an application crash sends the error message, stack trace, and a diagram summary (block count, connection count, and block types) to PostHog. Parameter values and proprietary model contents are never included.
- Feedback form: when you send the in-app feedback form, its contents (type, rating, title, message and, if you leave that box ticked, a diagram summary with numeric parameter values but no text) are sent to PostHog. This happens because you choose to send it, also without analytics consent; without consent it is sent cookieless and without an identifier.
- Consent & Opt-Out Control: you can grant, decline, or change each choice at any time in the in-app Privacy Settings (Help menu). Withdrawing consent stops level 2 and 3 immediately and deletes the identifier from your browser storage.
- Netlify (Hosting & Server Logs): Our application is hosted on Netlify. For security, DDoS protection, and basic network availability, Netlify automatically collects standard server logs which may include IP addresses. These are kept for a limited time (typically under 30 days) as part of essential infrastructure operations.
4. AI Assistant, MCP Server & Collaboration
Some optional features do leave your browser. Each is used only when you invoke it:
- In-app AI Assistant: your chat messages and the diagram context the assistant needs are sent through our server function (hosted on Netlify) to Google's Gemini API to generate a reply. We do not store these conversations; Google processes them under its Gemini API terms. Requests are rate-limited by Netlify at the network edge; we keep no record of your address.
- Remote MCP server (
blockwerk-mcp-worker.blockwerk.workers.dev, hosted on Cloudflare Workers in Cloudflare's global network): when an external AI assistant such as Claude or ChatGPT connects to BlockWerk, it sends the tool calls it makes — diagram structure, block parameters and simulation settings. We use no account, name or email address for this.
- Without pairing, the server keeps a scratch diagram for that connection in Cloudflare storage. It is identified by the connector id in the URL, or otherwise by a salted hash of your IP address and browser user agent; the raw IP address is not stored. The scratch diagram is deleted automatically after 24 hours without a call.
- With pairing (the Connect AI panel), tool calls are forwarded end-to-end encrypted through our relay (PartyKit, on Cloudflare) to your own open BlockWerk tab and executed there. The relay cannot read them. To route them, a pairing record linking your device token to your session is kept on Netlify. It holds no IP address or other identifying data, only that random token and the session id. It stops working after 2 hours and is deleted when it is next requested, or at once when you revoke the token from the same panel.
- Cloudflare keeps short-lived request logs for operating and debugging the server.
- Your AI provider: what you type into Claude, ChatGPT or another assistant, and what our tools return to it, is handled under that provider's own privacy policy.
- Real-time collaboration: when you start or join a shared session, diagram changes are relayed between participants through our PartyKit server (on Cloudflare).
- Local Agent API: commands sent through the in-page scripting API execute in your browser only.
5. Data Retention & User Rights
Because your data is saved locally in your browser's IndexedDB:
- You have complete control over your files. Clearing your browser cache or IndexedDB deletes local projects.
- We do not store IP addresses ourselves. Rate limits are enforced by our hosting provider at the network edge, and only the providers' short-lived server logs (sections 3 and 4) contain addresses.
- MCP scratch diagrams are deleted after 24 idle hours, and pairing records expire after 2 hours, as described in section 4. We sell no data and share none with third parties beyond the service providers named on this page.
- To have server-side data removed sooner, or for any other privacy request, email the address in section 7.
- You can export and import your projects anytime as standard JSON files via the
exportJson() / loadJson() functions.
6. Children's Privacy & Educational Use (Under 18)
BlockWerk is actively used in secondary schools, technical academies, and universities by students, educators, and young engineers. Because BlockWerk is built with a client-side WebAssembly architecture:
- We do not require user accounts, passwords, names, email addresses, or dates of birth to use the platform.
- We do not knowingly collect or solicit personal identifiable information (PII) from children or students under the age of 18 (or under 13/16 depending on local jurisdiction).
- Simulation models, homework exercises, and diagrams created by students are stored inside the local web browser's IndexedDB on their own personal or school-provided device. They leave that device only through the features listed in the summary above, such as sharing a diagram or a session recording they allowed.
- Parents, guardians, and educators with any questions regarding student data protection or classroom usage may contact us directly at blockwerk.tech@outlook.com.
7. Who Is Responsible & Your Rights (GDPR)
The controller for the processing described on this page is Rik de Boer, who runs BlockWerk as a private individual in the Netherlands. Contact: blockwerk.tech@outlook.com.
- Legal bases. Product telemetry and crash reports (section 3) rely on your consent, which you can withdraw at any time in the in-app Privacy Settings. Server logs and edge rate limiting rely on our legitimate interest in keeping the service secure and available. The AI Assistant, the MCP server, collaboration and short links process data to provide a feature you choose to use.
- Service providers. Netlify (hosting), Cloudflare (MCP server and collaboration relay), PostHog (telemetry, EU) and Google (Gemini, only when you use the AI Assistant) process data on our behalf as described above. Some of them may process data outside the European Economic Area; they do so under the safeguards in their own data processing terms, such as the EU Standard Contractual Clauses.
- Your rights. You may ask for access to, correction or erasure of, or restriction of processing of personal data about you, object to processing based on legitimate interest, and receive data you provided in a portable form. Because we hold almost nothing that identifies you, we may need details from you to find it. Email the address above; we answer within one month.
- Complaints. You can lodge a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens, or with the authority in your own EU country.
- No decisions about you are made by automated means.
8. Security Contact
If you discover a potential vulnerability or have security/privacy concerns, please contact our team at blockwerk.tech@outlook.com or refer to our security.txt.