A-05 · SECURITY
The only AI that doesn't read your client's drawings.
This is not a setting you switch on. It is the architecture. Project data has no path to the cloud, by design.
Local·0 KB of project data leaves the machine
§01THE BOUNDARY
Drawn as a section.
Two chambers, one gate. Everything that matters stays in the left chamber, on your machine. The cloud service in the right chamber only ever learns whether your subscription is current.
Your machineLOCAL
- Blueprints and the project files
- The code library and embeddings
- Your queries and the AI answers
- Project memory and the audit log
Stays here. Always. Works offline.
What may cross
One direction. Account only. Enforced at the API boundary.
Licensing serviceCLOUD
- Email address
- Plan and subscription tier
- Payment status
Never sees a project file or any AI content.
§02GUARDRAILS
What we do, and what we refuse to store
No telemetry in local mode.
Nothing phones home during inference. You can watch the network and see it.
Stripe handles all card data.
We never store a raw card. Account data is the only thing in the cloud.
Passwords are hashed.
If you use a password it is hashed with argon2 or bcrypt. Magic links mean you may not need one.
Your data lives in a local volume.
Project files and embeddings sit in a Postgres volume on your own disk.