BuildQ
Security & compliance

Security for confidential project data.

BuildQ encrypts, isolates and logs access to the data rooms, models and agreements you share with us, to the standard lenders and counsel expect.

Certified & compliant

Certifications and data handling.

We meet the controls that lenders, counsel, and counterparties expect when sharing development materials, financial models, and confidential agreements.

AICPA SOC sealSOC 2 Type 1
SOC 2

BuildQ has secured SOC 2 Type 1 certification, validating the design of our security controls across access, change management, encryption, and incident response.

Trusted data storage
Tiered storage

Flexible storage options sized to data sensitivity and customer compliance requirements, from standard to dedicated workspaces.

US-based by default

BuildQ operates US-based infrastructure with regional residency options available for enterprise customers under contract.

No model training on customer data

BuildQ does not use customer data to train or fine-tune any underlying AI models.

Platform security

Access controls.

Zero-trust design

We follow Zero Trust principles: no user or system is inherently trusted. Access is always verified, time-bound, and logged.

Your approval required

Access to customer data is strictly controlled. Engineers may only access data for support-related issues with written customer approval.

Continuous security testing

Regular penetration testing covering the full platform scope, paired with an “assume breach” approach to find and fix weaknesses.

Auditable AI

Every AI inference is traceable to the source data and prompt that produced it. You can review reasoning, examine sources, and verify conclusions.

Customer controls

Settings you manage.

Data retention

Set and manage data retention periods to align with your internal policies and regulatory requirements.

Data governance

Real-time insight into who is accessing your data and when, with full audit logging.

Encryption management

Data encrypted in transit (TLS 1.2+) and at rest (AES-256). BYOK options available for enterprise customers.

User authentication

SSO/SAML integration lets you manage end-user authentication and access from your identity provider.

FAQ

All data is encrypted in transit using TLS 1.2 or higher, and at rest with AES-256. Enterprise customers can request bring-your-own-key (BYOK) configurations for additional control.

Customer data is accessible only to your authorized users. BuildQ will not access your data without explicit written consent, and only for support-related issues. We do not use customer data to train or fine-tune AI models.

Every AI inference produced in BuildQ is traceable back to the source documents and prompt that produced it. You can always review the AI’s reasoning, examine the sources it relied on, and verify its conclusions.

When your contract ends, all of your data and any dedicated storage resources associated with your account are permanently deleted. Before this happens, you may request a full export to retain anything you need.

Yes. We have a Security Addendum, DPAs, and BAA-equivalent agreements ready for execution. Contact security@buildq.ai to begin.

Serious about security?

Talk to our team.