Security & data
Your model is solved on your own machine
Before a firm approves a browser tool, someone has to answer where the data goes, who can read it and how to get it back. This page answers that in plain language. The privacy policy is the binding version.
- Solving never leaves your machine
- The finite element core is C++ compiled to WebAssembly and runs in your browser on your own CPU. There is no solve server, so there is no queue to sit in and no copy of your model on a compute node.
- Data leaves only to sync
- Project data leaves the device to sync, back up and share — and only when you are signed in. Everything travels over TLS, and stored projects and backups are encrypted at rest.
- Stored in the European Union
- Application hosting, project storage and backups are in the EU. Backups run continuously and are held alongside the primary data, under the same terms.
- Access is limited to the operator
- Access to production data is limited to the operator named in the imprint, is used only for support and maintenance, and is not granted to anyone else.
The split
What stays on your device, what goes to our servers
Computing your model happens on your machine; keeping it safe, shared and available involves our servers.
Stays on your device
- The finite element solve itself — assembly, factorisation, recovery
- Meshing, results, diagrams and contours
- Design checks and report generation
- A working copy of every project you have opened here
- Everything you do while offline, until you reconnect
Syncs to our servers
- The project: geometry, sections, materials, loads, results and the edit history the document is built from
- Your account — email, display name, password hash, preferences
- Billing details, with the card number held by Stripe and never by us
- Support messages, including any model you attach to one
- Technical logs — IP, browser, timestamps, error traces — kept 90 days
The full Article 13 table — every category, its legal basis and how long it is kept — is in the privacy policy.
Controls
What is in place
Elementarium is a small, independent product without a compliance certification. Here is what is actually in place, so you can judge whether it meets your requirements.
- In transit and at rest
- TLS everywhere; stored project data and backups encrypted at rest.
- Passwords
- Stored as salted hashes. They cannot be recovered, only reset.
- Per-project access
- Projects are shared by invitation, with Owner, Editor and Viewer roles. A reviewer can interrogate everything and change nothing.
- An audit trail by default
- Every change is a versioned entry. "Who changed the rafter section, and when" is a question the history answers.
- Your project file, without asking
- Download the .elproj project file and print a report on any plan, at any time. IFC, SAF and table export are on Pro.
- Deletion is permanent
- Delete a project and it goes; it is purged from backups within 30 days. Accounts follow the same rule, 30 days after closure.
- Backups
- Continuous
- held in the EU beside the primary data
- Backup purge
- 30 days
- after you delete the project
- Technical logs
- 90 days
- IP, browser, timestamps, error traces
- Your work, offline
- Always available
- a network outage does not stop your work
Stated plainly
What we do not do with your models
Your models are your client's confidential design information.
- Your models are not used to train anything.
- Your models are not sold, rented or shared with advertisers.
- Google Analytics runs on this site and in the app only if you accept it, and records page views and clicks — never model content.
- Nothing in the app reports what you model. An error report carries the error, the browser and your account id, nothing else.
Subprocessors
Everyone who touches your data on our behalf
The complete list, kept current. A vendor is added to this table before it is added to the stack.
| Processor | What it does | Where |
|---|---|---|
| DigitalOcean, LLC | Application hosting, project storage, backups | European Union |
| Stripe Payments Europe, Ltd. | Subscription payments, invoicing, fraud prevention | Ireland (EU), with onward transfers under Stripe’s own safeguards |
| Plus Five Five, Inc. | Account email — sign-in links, receipts, service notices | European Union |
| Google Ireland Limited | Google Analytics on this site and in the app — only after you consent | Ireland (EU), with transfers to the USA under Standard Contractual Clauses |
| Functional Software, Inc. (Sentry) | Error reports from the app — the error, the browser and your numeric account id; no email, IP address or model content | Germany (EU data region); a US company, with transfers under Standard Contractual Clauses |
Last reviewed 14 October 2026
Reporting a vulnerability
Report it to us first
There is no bug bounty programme. A report is read by a person, a fix takes priority over planned work, and you get public credit if you want it.
[email protected]If a breach ever puts your rights at risk, we notify the supervisory authority within 72 hours and tell you directly — that commitment is in the privacy policy, not just here.
What we ask of you
- Tell us what you found and how to reproduce it, before telling anyone else.
- Give us a reasonable window to fix it — we will tell you how long we need.
- Do not access, modify or retain data belonging to anyone but yourself while testing.
- No denial-of-service testing, no social engineering of us or our subprocessors.
Report it in good faith and stay inside these lines, and we will not pursue you for it.