Security · Privacy · Data residency

Your data stays in the United States.

Your bids, contracts and sub proposals stay on US infrastructure, isolated per customer, and are never used to train AI models. Our compliance program is underway, starting with the SOC 2 Type II audit, and the readiness summary is available under NDA.

Hosting
US only, primary region us-east-1
Encryption
AES-256 at rest, TLS 1.3 in transit
AI training
Never on customer data
SOC 2 Type II
Audit underway
01Your data

Where does your data go, and who can use it?

Three rules apply on every plan.

01

It stays in the US

Storage and inference run on US infrastructure, primary region us-east-1, with failover inside the United States.

02

It never trains a model

Your documents and outputs never train BAU AI models or any third-party model. Foundation models run under enterprise terms that prohibit retention beyond the request. This is a contract term.

03

No one reads it

No one at BAU AI reads customer documents in normal operations. Support access is opt-in, time-bound, and logged. Nothing is shared with ad networks or data brokers.

02In place today

What is in place today?

These run now, on every plan, without waiting for the audit report.

01

Tenant isolation

Each customer's documents are processed and stored in a logically isolated environment. Cross-tenant access is blocked at the data, application, and audit-log layers.

  • Logical isolation on every plan
  • Dedicated single-tenant deployment on Enterprise
02

Encryption and keys

All storage is encrypted with tenant-specific keys.

  • AES-256 at rest, on storage and database
  • TLS 1.3 on every connection
  • Customer-managed keys on Enterprise
03

Access and audit trail

Least-privilege roles, with privileged access reviewed quarterly. Every action is logged with user, time, document, and citation.

  • Audit trail exports as PDF, JSON, or CSV
  • SSO (SAML 2.0, OIDC) and SCIM provisioning on higher plans
04

Retention and deletion

You set retention, from 30 days to indefinite. Backups are encrypted and aged out per your policy.

  • Hard delete on demand
  • Export of data, findings, and audit trail when you leave
  • Deletion confirmed in writing within 30 days
03Audit window

What is still in the audit window?

Our SOC 2 Type II audit is underway. SOC 2 is an attestation report, not a certification. When you compare vendors, ask each one for the report itself, its type, and the period it covers.

SOC 2 Type II
Audit in progressCriteria: Security, Availability, Confidentiality. The report is shared under NDA once issued. A readiness summary is available now.
Compensating controls
Active todayEncryption, tenant isolation, quarterly privileged-access review, annual third-party penetration test (last engagement Q1 2026), and a documented incident response plan: critical incidents acknowledged within 1 hour, resolved within 24 hours.
US data residency
LiveStored and processed in the United States. No cross-region transfer.
CCPA and CPRA
In placePersonal information handled per CCPA and CPRA: right to delete honored, no sale of personal information.
Section 889
DocumentedNo Section 889 listed components in the stack. Documented for federal-adjacent procurement.
Sub-processors
On requestFull list on request. Material changes notified 30 days in advance.
04Security packet

How do you get the security packet?

Procurement, IT, and counsel get written answers, not a slide deck.

Request the security packet
01

Send your questionnaire

Email it, or your list of questions, to tushar.adsul@bauai.co.

02

Get the documents under NDA

The SOC 2 readiness summary and compensating controls, plus the sub-processor list.

03

Get answers in writing

We answer in writing, usually within one business day.

05AI controls

How is the AI kept in check?

Agents do the first pass. The decision to bid, sign, or award stays with a person.

Cited

Every finding cites clause and page

Each finding traces to the document, section, clause, and page.

Untrusted input

Documents cannot give orders

Agents do not follow instructions embedded in documents, and tool use is gated by allow-lists. Low-confidence reads surface as questions, not silent guesses.

Human

People make the calls

Every finding can be edited, dismissed, or overridden, and overrides are logged. No autonomous bid submission, contract signing, or award.

06Enterprise

What changes on Enterprise?

For owner-driven, federal-adjacent, and large general contractor work with stricter infosec requirements.

Request Enterprise pricing
Dedicated

Single-tenant cloud

A dedicated deployment with its own resources and database, separate from other customers.

Your cloud

Your cloud account or on-premise

Runs in your cloud account or on your infrastructure, with customer-managed keys and inference.

Paper

Data processing agreement

A DPA is part of every Enterprise agreement.

07Security FAQ

Does BAU AI train AI models on our bid data?

No. Your documents and outputs never train BAU AI models or any third-party model. Foundation models are used under enterprise terms that prohibit retention beyond the request.

Where is our data stored and processed?

In the United States. US tenants run on US infrastructure, primary region us-east-1, with US-only storage and inference. Bid data does not move across regions.

Can we see your SOC 2 Type II report?

The audit is underway and covers the Security, Availability, and Confidentiality criteria. Until the report is issued, we share a readiness summary and a description of active compensating controls under NDA. SOC 2 is an attestation, not a certification.

Will you complete our security questionnaire?

Yes. Send it to tushar.adsul@bauai.co and we answer in writing, usually within one business day. Supporting documents are shared under NDA.

How do SSO and user provisioning work?

SSO runs on SAML 2.0 or OIDC, and SCIM provisioning works with Okta, Microsoft Entra, and Google Workspace. Both are included on higher plans; the pricing page shows which.

Can we run BAU AI in our own cloud or on-premise?

Yes, on Enterprise. A dedicated single-tenant deployment in your cloud account, or on-premise with customer-managed keys and inference, keeps data, keys, and the model boundary inside your infrastructure.

How do you handle prompt injection in uploaded documents?

Inputs are treated as untrusted. Agents do not execute instructions embedded in documents, tool use is gated by allow-lists, and outputs are scoped to the calling tenant. Citations are checked against the source before a finding is shown.

What happens to our data if we leave?

You export your data, findings, and audit trail in machine-readable formats. We hard delete on request and confirm it in writing within 30 days.

Security review

Bring your security review. We answer in writing.

Send your questionnaire. Written answers, usually within one business day.

Looking for the full, legally binding privacy policy?