01CONTROL GROUP
Account access
- BuildBid uses authenticated user sessions for signed-in product access.
- Estimate and billing features are tied to account state rather than anonymous public editing.
BuildBid security overview
This page is intentionally conservative. It describes current product patterns we can support from the codebase and operating model, without pretending the product has controls that are not yet documented.
PLAIN-LANGUAGE SUMMARY
Data use for uploaded plans
- Your uploaded plan files are tied to your account and are used to run your estimates. We do not sell them, and we do not share raw files with other customers.
- Corrections you make to AI-generated estimates (unit costs, quantities, classifications) do feed an aggregated community pricing index that benefits other users. That index never contains your raw documents or project names.
- A documented opt-out for the shared pricing index is on the roadmap. Until it ships, if you need a no-training posture, contact us before uploading sensitive work.
02CONTROL GROUP
Uploads and storage
- Uploaded project files are processed through application APIs and cloud storage flows used by the product.
- Large-file flows may use signed upload URLs so files can be transferred directly to storage without routing the entire file through a normal request body.
03CONTROL GROUP
Payments
- Billing and checkout flows are handled through Stripe.
- BuildBid does not present itself as a direct card vault and should not be described that way.
04CONTROL GROUP
Operational reality
- BuildBid is an actively evolving product. Security controls should be discussed in terms of current implementation, not aspirational certifications.
- If your procurement team needs formal attestations, request the current evidence directly instead of assuming enterprise controls that are not explicitly documented.