BuildBetter Iterate 50% faster

Yes — BuildBetter Iterate 50% faster undergoes third-party penetration testing as part of its security program. The pentest vendor is listed on its SOC2C profile.

BuildBetter Iterate 50% faster publishes a penetration test summary on its trust center. You can request access to it through SOC2C.

BuildBetter Iterate 50% faster's SOC 2 report is available on request. Request access through SOC2C and we coordinate the company-side NDA and delivery.

Security isn't a single yes/no, but BuildBetter Iterate 50% faster is SOC 2 Type II compliant and holds SOC 2 Type I, SOC 2 Type II, GDPR, HIPAA, and undergoes third-party penetration testing. SOC2C verifies its compliance posture and shows how strongly each fact is proven.

BuildBetter Iterate 50% faster hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@buildbetter.ai or via a /security page (BuildBetter Iterate 50% faster lists a security contact).

BuildBetter Iterate 50% faster lists 17 subprocessors on its trust center, including Amazon Web Services, GitHub, Google Workspace, Linear, Vanta. Buyers use this for fourth-party risk review.

BuildBetter Iterate 50% faster hosts on AWS. Data residency details are on its trust center.

BuildBetter Iterate 50% faster's trust center is at https://trust.buildbetter.ai. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.

When provisioning a user account, users must provide personal information such as their \*\*email address, full name, and optionally, a profile photo. While using the services, authorized users can upload, import via documents and files or via integrations, or directly enter any data such as text, images, audio, video, or any other files. To best understand the data that you expect to store in BuildBetter, we recommend talking to the individuals and end-users who will be using BuildBetter. Most BuildBetter customers will store research and company data such as meetings, interview recordings, transcripts, survey responses, customer feedback, photographs, and other research and company data. The data that you enter into BuildBetter may vary depending on the use cases of your individual end-users.

We store data in Amazon Web Services (AWS) who is our primary infrastructure provider. When creating a workspace in BuildBetter, the default location for where data is stored for a Workspace is in the United States. BuildBetter can support additional countries upon request. - If you choose the United States, your workspace data will be stored in us-east-1 (North Virginia). Notwithstanding the selection you make regarding your workspace data, other categories of data (such as product analytics data, account billing and contact data, workspace URLs, access and operational logs, and support-related data) will continue to be transferred to, and stored in, the United States. Additionally, where your workspace data is processed by one of our sub-processors, this data may continue to be processed outside the region you select, depending on the location of the relevant sub-processor.

You can find our DPA at this link and MSA link).

No. Please view our AI Transparency Statement for how we deal with models, AI, training, and processing here. BuildBetter never uses your data for training proprietary and first party models. No opt-out needed. BuildBetter also does not share customer data with any other third-party for training their machine learning models, and we have separate agreements with providers for zero day retention policies when applicable. Even though we utilize third-party models to deliver AI services, we guarantee for our customers these entities do not have access to our customer data for refining or training their models. Please learn more about how we process and work with third party providers in our AI Transparency document. Your data is yours.

BuildBetter has built-in single sign-on capabilities for Google accounts, and the option to configure your own managed identity provider as a single sign-on authentication option for BuildBetter enterprise workspaces. Please reach out to [security@buildbetter.ai](mailto:security@buildbetter.ai) for more information about enabling SAML or more advanced configurations of SSO.

BuildBetter utilizes industry-standard practices concerning the encryption of data when stored and while in transmission. BuildBetter also have a documented cryptography policy that outlines the requirements for encrypting data and transmissions. Encryption at rest All data, including backups, is encrypted at-rest using AES-256 encryption. Encryption in transit Data is encrypted while moving between us and the browser with Transport Level Security (TLS) 1.2. Secure Sockets Layer Secure Sockets Layer (SSL) certificates are issued and managed through Amazon Web Services, and HTTP Strict Transport Security (HSTS) is enabled. We score an A rating on Qualys SSL Labs tests. Key management Amazon Web Services (AWS) stores and manages data cryptography keys in its redundant and globally distributed Key Management Service (KMS). AWS KMS is a secure and resilient service that uses hardware security modules that have been validated under FIPS 140-2, or are in the process of being validated, to protect your keys.

Yes. Our Soc 2 Type 2 report is available for download on this portal.

Yes. Our HIPAA compliance is available in this portal.