Your drawings stay where they belong.
TrueQty is designed for in-region deployment. Drawing analysis runs on models we host and operate ourselves, in-region — and the two paths that could send a drawing to a model abroad are off unless you switch them on.
Below is what is implemented today, and — just as important — what we are not claiming yet.
One chain, four links, and each one stated separately.
Residency is not a single switch. It is a chain, and a chain is only as good as the link nobody checked. So each link is marked with its actual state rather than described in aggregate.
- 01Your projectUAE
Your tender, your drawings, your client's NDA.
- 02Deployment regionUAE
The application is deployed and runs in-region.
Implemented - 03StorageUAE
Designed for in-region storage. End-to-end verification in progress.
Verifying - 04InferenceUAE
Default detection runs in-region on models we operate. Two escalation paths can send data out; both are off by default.
Conditional
Marked with the same states this platform uses for quantities · verified means evidenced · flagged means open
What is built, and nothing else.
Each item below is in the product now. Anything not on this list is not being claimed on this page, whatever the roadmap says.
- Verified
In-region deployment
The application is deployed in the UAE region rather than served from elsewhere and pointed at this market.
- Verified
In-region detection by default
Drawing analysis runs on models we host and operate ourselves, in-region. The deterministic paths — CAD layers, text, geometry, template matching — never leave the country.
- Verified
Tenant isolation
Each customer's projects, drawings, observations and quantities are isolated from every other tenant's. One client's tender is never visible to another.
- Verified
Audit trail
Every observation, verification, correction, rule execution and approval is recorded against a user and a timestamp — the same record that lets a quantity be opened backwards.
- Verified
Access control
Role-based access across projects, drawings and approval rights. Who may verify and who may approve for pricing are separate permissions.
The part most vendors leave out.
We ask engineers not to trust an unverified quantity. It would be strange to then ask you to trust an unverified claim.
- Not claimed
“No drawing is ever sent to a model outside the UAE”
Not claimed as an absolute, because two paths can do it and the honest thing is to name them. A scanned sheet with nothing machine-readable left in it can be escalated to a hosted vision model to locate symbols; a riser diagram our own reader cannot resolve can have its text labels escalated the same way. BOTH ARE OFF BY DEFAULT — with them off, no part of a drawing leaves. A third path sends a short text excerpt from an uploaded file's first page to sort it into drawing, specification or bill, and runs only where our own rules could not place it. Every one of these calls is logged with what was sent and to which model, so the question “has anything of mine ever left” has an answer rather than an assurance. The detail is in clause 4 of the privacy policy.
- Not claimed
“No data leaves the country”
We do not claim this, and will not until we can evidence it. An end-to-end residency guarantee has to hold for storage, inference, logs, backups, monitoring and authentication — every link, not the visible ones. Deployment is in-region today and detection runs in-region by default; billing and transactional email necessarily do not, and the remaining links are being verified. Until all of them are, the honest description is designed for in-region deployment, and that is the wording we use.
- Not claimed
A contractual residency guarantee, today
If your tender or your client requires a signed data-residency commitment now, say so at the start. We will tell you plainly whether we can meet it rather than discovering the answer during procurement.
Most tools that read a drawing send it somewhere else to be read.
A general-purpose model hosted in the United States is the default architecture for document AI, and for a great deal of software that is a perfectly reasonable decision. For a tender package under an NDA, on a project in this region, it is a question your client is entitled to ask — and “it goes to a vendor’s model abroad” is a difficult answer to give in a procurement meeting.
We host and run our own models, in-region. Your drawings are read by a system we operate, in the region the project is in. That is the part we can state plainly today, and it is the part that matters most.
The rest of the chain is being verified link by link, and this page will say so the day it changes — not before.