Privacy Policy

Last Updated: November 19, 2026 | Effective Date: November 19, 2026

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:

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.

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.

4. AI Assistant, MCP Server & Collaboration

Some optional features do leave your browser. Each is used only when you invoke it:

5. Data Retention & User Rights

Because your data is saved locally in your browser's IndexedDB:

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:

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.

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.