Your plans are the business. Here’s how we treat them.
An estimator’s plan set is a client relationship on paper. Everything on this page is behavior you can check, not a badge.
Plans live in object storage, served by signed URLs
Uploaded plan sets and page images are stored in Amazon S3. The app reads them through short-lived signed URLs minted per request; there are no public buckets and no permanent links to your drawings.
Canadian workspaces keep their files in Canada
Plan sets, page images and exports are stored in Amazon S3. A workspace created in Canada keeps them in AWS's Montréal or Calgary region, whichever it picked at signup; every other workspace keeps them in the United States. Our database, our servers and the AI analysis all run in the US, though, so project details are processed there whatever the file region. Changing region means copying every file and checking each one arrived, so we do it for you. Just ask.
Your plans never train AI models
Detection runs against your sheets to produce your takeoff, and that is the end of it. Your drawings are not used to train our models or anyone else's.
Access is workspace-scoped
Every account is a workspace; projects belong to it and only invited seats can open them. Client share links expose a single estimate document by unguessable token, never the drawings behind it.
Signed estimates are sealed and revision-bound
When a client signs, the exact revision they signed is fingerprinted (SHA-256) and stored. Every later download serves those same bytes; a signed document is never quietly re-rendered.
Deletion on request
Delete a project and it leaves the product surfaces immediately. Want the underlying storage cleared too? Email support@bildrix.com and we'll confirm when it's done.
Card details never touch our servers
Billing runs on Stripe. We store the subscription state, not the card.
What happens to your documents.
Bid sets are competitively sensitive.
Your plan sets stay in your workspace, stored in Amazon S3. Remove a project from your workspace whenever you choose.
Detection runs through enterprise AI APIs under terms that exclude training on your data. Your plans never train AI models.
Client view structurally hides cost and margin columns. The shared page and PDF render from it, so margin can't leak.
The signed PDF is rendered once at signing, sealed and SHA-256 fingerprinted, bound to the exact revision signed. Every later download serves those same bytes.
No SOC 2 audit yet, and we’d rather say so than imply one. Ask us anything about data handling at support@bildrix.com.
No SOC 2 audit yet.
We’d rather say what is in place than imply more. Storage regions are on this page rather than available on request; if your shop needs the rest before uploading a set (data flow, subprocessors), ask us anything at support@bildrix.com and you’ll get a straight answer.