# Security and data handling — Bidroq

Canonical page: https://bidroq.com/security
Last reviewed September 2026.

Every line below is a commitment.

## 01 · Sign-in and access

Sign in with Google, Microsoft, or a code sent to your work email. No passwords. The first person from your company creates the account. Everyone after that is approved by someone already inside.

Three roles: Owner, Admin, Estimator. Remove a user and every one of their sessions ends at once.

Mailbox credentials, portal sessions and access tokens are stored in an encrypted vault (AES-256-GCM) whose key is held outside it.

## 02 · Storage and isolation

Documents live in private storage on our hosting platform and, where object storage is enabled, in a private S3-compatible bucket. Neither is publicly addressable.

In transit, everything is TLS. At rest, the credential vault is encrypted by Bidroq and documents, database and object storage are encrypted by the hosting platform under its published standard.

Every request carries your company from the session and every query is scoped to it; no request can reach another company's data.

A read that is interrupted resumes where it stopped.

## 03 · AI models and training

Bidroq never trains models on your documents. There is no training or fine-tuning path in the product. What Bidroq learns is stored as your estimators' corrections and rules, never as model weights.

Document text and drawing pages are sent to our model providers to be read. Your account can run inside your own Microsoft Azure AI account, in which case documents are processed under your own provider agreement and region.

## 04 · Retention and deletion

| Account state | What happens |
|---|---|
| Trial, active | Everything retained. |
| Trial ended, no plan | Readable and downloadable for 30 days, then purged (day 60 after sign-up). |
| Paid | Retained for the life of the account. |
| Cancelled or lapsed | Readable for 30 days, then purged. |
| Deleted by the account Owner | Purged within 30 days; backups within 60. |

Deleting a package deletes the read that came from it. Purge covers documents, rendered pages, generated files, caches, memory and stored credentials. Audit and billing records are kept seven years with no document content.

## 05 · Who can see your documents

Your pricing, production rates and bid history are visible to your company only.

Bidroq staff reach an account only through a staff sign-in that requires a stated reason and writes to your audit log, which your Owner and Admins can view and export. Named engineers hold hosting access to the database and storage for operations.

Every sign-in, user change, connection, rule change, document opened, download, deletion and approval is written to the audit log.

## 06 · Subprocessors

| Provider | Purpose | Location |
|---|---|---|
| Railway | Application hosting, database, file storage | On request |
| Google | Gmail and Drive connections; sign-in | United States |
| Microsoft | Outlook and Microsoft 365 connections; sign-in; Azure AI option | United States |
| Stripe | Subscription billing | United States |
| Model providers | Reading documents and drawings, the assistant | See note |
| Transactional email provider | Sign-in codes, invitations, receipts | United States |

Model providers and the transactional email provider are named here once the routing decision and the provider contract are final.

## 07 · Cost transparency

AI cost is tracked per bid, so the cost of reading a given package is visible rather than pooled. On accounts running inside the customer's own cloud AI account, that spend appears on your own provider bill.

## 08 · Reporting a security issue

Write to security@bidroq.com. We acknowledge within two business days. Include the account, the package and what you saw.

A security.txt file is published at /.well-known/security.txt.