Security and privacy
Your model file never leaves your computer.
Only the property values the rules need are sent to check them. Nothing from your model goes to an AI. Here is exactly what does leave, and where it goes.
This page lists only what the product does today. It claims nothing more.
- The model fileRead on Dana Ortiz's computerStayed
- Property values the rules needA few kilobytes, not storedSent
- Sent to the AINothing from this modelNone
During a check
Where each thing goes
Four places, read from left to right. The model file never moves past the first one.
Stays with you
- The model file, not one byte of it
- Geometry and coordinates
- Element identifiers, element names, level names
- The element-by-element detail of a result
Kept in your browser tab until you close it.
Sent, then not stored
- The property values the requirements need, under temporary references
Our server decides each requirement. It keeps only a fingerprint of the request.
Saved for your firm
- File name, size, element count, authoring tool
- A fingerprint of the file
- The result by requirement: counts and verdicts
In your firm's space. Each firm's data is kept apart.
Only what you chose
- A document you chose to upload, to be read
- Results the engine computed: requirement names, counts and trade words
Never your model file, an identifier or a name from your model.
The AI
The engine decides. The AI explains and proposes.
The AI reads a document you upload and proposes requirements. It words fix steps and a draft of the meeting summary. It never computes a score, a count or a verdict, and never says a building meets a code.
It receives
- A document you chose to upload
- Requirement names and counts
- Trade words and the project profile
- The approved requirement wording
It never receives
- Your model file or its geometry
- Element identifiers and names
- Level names
- Your email address or another firm's data
Next to every document upload: "This document is sent to our AI provider to be read. Your model is not."
Access
Who can see what
Roles are enforced in the database, not only on the screen. An action the role does not hold is refused, even if a screen showed it by mistake.
Protections
What we do today
Row-level security on every table. Automated tests try to read another firm's data and must be refused.
It decides each rule and signs a receipt. A saved result that does not match its receipt is refused.
When a permission, quota or plan check cannot be completed, the request is refused.
A random token, stored only as a fingerprint. 90 days at most. A revoked link stays revoked.
Each person may turn it on. A firm on the Business plan may require it for every member. Required for the staff of BIMgravity.
Read with your own sign-in. Our server never receives it and never contacts Autodesk.
What we do not claim
We make no claim of an independent security audit or attestation. We do not say a system is unbreakable. If we obtain an audit, this page will say what it covers and when.
Report a security issue
Tell us what you found and how to see it. Do not access other people's data. We will not act against anyone who reports in good faith.
No model data is needed: describe what you saw. A security report is read before other messages and answered within 1 working day. You can also write to our contact form.
See it on the sample model.
Run a check in your browser and read what was sent. No account.