Transparent pricing: $0.05 per square foot of plans you run. See what that costs on a real house

Security

What we do with your data, plainly

To use BidLoggers you upload your price list and your builders' plans. That's a lot of trust for a young company to ask for, so here is exactly how it's handled.

Your data is isolated at the database, not the application

Every row belongs to a company, and access is enforced by row-level security policies in the database itself. A bug in application code can't leak another yard's data, because the database refuses the read regardless of what the code asks for.

Your price list is yours

Your catalog and margins are the most commercially sensitive thing you give us. They're never used to price another yard's bid, never pooled into a shared price book, and never used as training material. Directives learned from your estimators' corrections apply to your account only.

Margin never reaches the customer

The internal spreadsheet carries margin; the customer proposal does not. That's a deliberate, enforced split — the customer-facing export cannot include it.

Encryption in transit and at rest

All traffic runs over TLS. Plan sets and generated documents are held in encrypted object storage, reachable only through short-lived signed URLs scoped to your company.

Quote links are unguessable and revocable

A builder's quote page is reached by a high-entropy token rather than a sequential id, so links can't be walked. Quotes carry an expiry, and sending locks the revision so the copy a builder holds can't be altered underneath them.

Access is logged

Administrative actions on an account are recorded with who did them and when, including any support access — so there's an answer to "who changed this" that doesn't depend on memory.

Where we are honest about our stage

We are not SOC 2 certified today. Saying otherwise would be the easiest lie on this page and we're not going to tell it. The controls above are real and in place; the audit that would let us put a badge here is not something we've completed. If your procurement process requires one, talk to us about timing rather than assuming.