The short version. Your coating designs are yours and they are private to your account. We do not sell them, we do not share them with other customers, and we do not use them to train AI models or to develop coatings of our own.
Design data leaves our systems in exactly one situation: you use the Lumi AI assistant and have separately agreed to let it see your design. That is explained in section 5, and you can turn it off while still using Lumi.
OptiCoat Designer is provided by Cor Stellaris LLC (“we”, “us”). For anything in this policy — including a request to access, export or delete your data — contact privacy@cor-stellaris.com.
| Data | Why we hold it |
|---|---|
| Email address and password | To create and secure your account. Passwords are handled entirely by our authentication provider — we never see or store your password. |
| Coating designs — layer stacks, materials, thicknesses, substrates, targets, optimizer settings | This is the product. Stored so you can reach your work from any machine you sign in on. |
| Custom material definitions — refractive index and extinction data, dispersion models | So materials you have characterised are available wherever you work. |
| Equipment records — machine names, serial numbers, labs, tooling factors | To model your specific coating chambers. |
| Production measurements — uploaded spectral scans, run numbers, placement, notes | For recipe tracking and chamber calibration. |
| Recipe revision history | So a measured run can be traced back to the recipe that produced it. |
| Billing details | Handled entirely by our payment processor. Your card number never reaches our systems. |
We record feature usage only: which screens you open, which tools you run, how long an operation took, whether it succeeded, and when you reach a plan limit.
We do not record the contents of your designs in usage data. No materials, no thicknesses, no wavelengths, no spectra, no tooling factors, no machine or lab names, no file names, and nothing you type into the AI assistant.
This is enforced in software, not by policy alone: our server checks every field against a fixed list of permitted values before storing it, and discards anything not on that list.
This data stays in our own database. We do not use a third-party analytics service, so no outside company receives a record of how you use the software.
We also keep standard server logs (timestamps, request paths, error details) for security and debugging.
This distinction matters, so we state it plainly.
Designs are private to the individual account that created them. Not to your teammates, not to your team administrator, not to your organisation’s billing owner. There is no feature anywhere in the product that shows one user another user’s designs.
Equipment and process data is shared across your team if your organisation is on a team plan. Labs, machines and their tooling factors, custom materials, tracking runs, chamber calibrations and recipe revisions are visible to everyone in your organisation. A coating chamber is one physical machine, and two engineers holding different calibrations for it is a defect rather than a feature.
Within a team, any member can view and update shared equipment records. Deleting a shared record requires either being the person who created it or being a team administrator.
Lumi is optional and off until you agree to it.
When you use Lumi, your message is sent to Anthropic PBC to generate a reply, using their Claude API.
If you choose to let Lumi see your design — a separate question we ask you explicitly — the following is sent with each message: every layer’s material and thickness in order, your substrate and targets, the computed spectrum, and the name and calibrated tooling factors of the chamber you have selected.
That is your recipe. We ask before sending it, we tell you exactly what is included, and you can use Lumi with this turned off — it will answer general thin-film questions without receiving your stack.
We access the contents of your account only when:
If we ever want to use customer design data to improve the product or an AI feature, we will ask for your explicit, separate, opt-in permission first. It will be off by default, and declining will not affect your use of the service.
We use the following service providers. The full list, with what each one receives, is on our subprocessors page.
| Provider | Role | Location |
|---|---|---|
| Vercel | Serves the application | USA |
| Railway | Runs the API | USA |
| Supabase | Hosts the database | USA |
| Clerk | Authentication | USA |
| Stripe | Payments | USA |
| Anthropic | AI assistant — only with your consent | USA |
Your data is stored and processed in the United States. If you are outside the US, using the service involves transferring your data there. For customers in the UK or EEA we rely on the European Commission’s Standard Contractual Clauses; contact us if you need a copy.
The application keeps a copy of your current work in your browser so it continues to function without a network connection. This includes your layer stacks, machines, tracking runs and preferences, stored using your browser’s local storage.
This never leaves your device except through the normal syncing described above. If a different account signs in on the same browser, this local copy is erased before the new user can see anything. You can also clear it yourself through your browser’s site-data settings.
We do not use advertising or tracking cookies. Our authentication provider sets a cookie needed to keep you signed in. See our cookies and local storage notice.
| Data | Retention |
|---|---|
| Account data and designs | For as long as your account is open |
| After you close your account | Deleted within 30 days of your request |
| Usage data | 24 months. Detached from your account identity when your account closes |
| Server logs | Up to 90 days |
| Billing records | As long as tax and accounting law requires |
You may ask us to provide a copy of your data, correct it, delete it, or export it. Email privacy@cor-stellaris.com and we will respond within 30 days. We will not charge you for this and we will not ask why.
Depending on where you live you may have additional rights under the GDPR, UK GDPR or CCPA, including the right to object to processing and the right to complain to your data protection authority.
No system is perfectly secure and we do not claim otherwise. If we become aware of a breach affecting your data we will notify you without undue delay, and in any event within 72 hours of becoming aware of it.
Our security overview has the detail a security reviewer will want, including an honest account of what we have not done.
This is professional engineering software and is not directed at children. We do not knowingly collect data from anyone under 16.
If we change this policy in a way that materially affects how your design data is handled, we will tell you before it takes effect — by email or in the application — rather than by quietly changing the date at the top of this page.
Cor Stellaris LLC
privacy@cor-stellaris.com