Written for the person doing a security review. It includes what we have not done, because you would find out anyway and a vendor who tells you up front is easier to trust.
For a coating shop, the layer stack is the intellectual property, and the tooling factors represent months of calibration work. The realistic risk is not a headline data breach — it is a competitor seeing a recipe. Our controls are arranged around that.
| Designs | Private to the individual account that created them. Every database query for a design is filtered by the owning user. There is no feature in the product that shows one user another user’s designs — not for teammates, not for team administrators, not for us. |
|---|---|
| Team data | Equipment and process data (labs, machines, tooling factors, materials, tracking runs, calibrations, revisions) is shared within your organisation, by design. Any member may view and update it; deleting shared records requires ownership or a team-administrator role. |
| Tenant isolation | Enforced per request in the API, from the authenticated identity — not from anything the browser sends. |
| Authentication | Delegated to Clerk, a specialist identity provider. Sign-in happens on their infrastructure: we never see, receive or store a password. Session validity is checked on every request to our API. |
| Administrative access | Restricted to a fixed allowlist. Every administrative action on an account — plan change, account creation, account deletion — is written to an append-only audit log recording who did it, to whom, and when. |
Our Lumi assistant sends conversation content to Anthropic. Design context — the layer stack, tooling factors and chamber name — is sent only where the individual user has explicitly consented, and each user can turn design sharing off while still using the assistant. The check that enforces this sits at the single point in our code where that data could be assembled. Anthropic does not use this content to train models.
We would rather you hear this from us than discover it in a questionnaire.
| No SOC 2 or ISO 27001 | We do not hold a formal security certification. If your procurement process requires one, tell us — it affects our roadmap priorities. |
|---|---|
| No multi-factor authentication yet | An account is protected by its password alone. Our identity provider offers a second factor on a higher plan tier, which we have not yet taken. This is the honest weak point in the list: the realistic way a competitor sees your recipes is a reused or phished password, not a breach of our database. If a second factor matters to you, tell us — it is a setting rather than a rebuild, and knowing someone wants it is what moves it. |
| No third-party penetration test yet | None has been commissioned to date. |
| No application-layer encryption of design data | Designs are stored as structured data, encrypted at rest by the database host. We do not additionally encrypt them with a key we hold separately. Being straight about the trade-off: because our servers must read your designs to compute spectra and render charts, application-layer encryption would not protect against a compromise of the running service. It would protect against a stolen backup. We are willing to discuss this if it is material to you. |
| No contractual uptime commitment | We do not currently offer an SLA. Ask us before purchasing if you need one. |
| Data export and deletion are manual | There is no self-service export button yet. Email us and we will action a request within 30 days. |
| Single-region hosting | All data is stored in the United States. We do not currently offer EU or other regional hosting. |
Email privacy@cor-stellaris.com. Please give us reasonable time to fix an issue before disclosing it publicly. We will not pursue legal action against anyone who reports a genuine vulnerability in good faith and does not access or destroy other customers’ data while investigating.
If we become aware of a security breach affecting your data, we will notify you without undue delay and in any event within 72 hours, with what we know, what we are doing, and what — if anything — you need to do.
Security questionnaires, a signed data processing agreement, or a call with us before you buy: privacy@cor-stellaris.com.