You're trusting us with the inner workings of a live facility — sensor readings, documents, asset models, the whole operation. We don't take that lightly. This page lays out how we handle that data in language you can actually follow, not buried in clauses.

What we collect

Two kinds of data. The operational data you connect to your twin — sensors, documents, 3D models, calculations — and account data we need to run the service, like names, work emails, and login activity. We collect the second kind because the product can't function without it, not to build a profile of you.

What we do with it

Your operational data exists to power your twin and nothing else. We use it to run your model, answer your questions, and execute the automations your team sets up. We don't sell it, we don't mine it, and we don't train shared models on it.

Who can see it

Your data is walled off to your organization. Our staff don't browse it; access is limited, logged, and granted only when you ask us to help with something specific. Every agent action and every change is recorded and replayable, so there's always a trail.

Where it lives

We're clear about where your data is stored and which providers we rely on to run the platform. If you operate under residency or sovereignty requirements, that's a conversation we have up front, not a surprise later.