We understand your team may have questions about using a generative AI tool like Driver, particularly regarding security. Onboarding your organization to Driver offers significant opportunities to accelerate your understanding of legacy code, port software to new hardware, reduce product time-to-market, and streamline engineer onboarding. We understand your team may have questions about using a generative AI tool like Driver, particularly regarding security. Here, we address the key questions we most frequently receive from customers.
​
At Driver, we've carefully crafted our security framework to address the intricate challenges and stringent requirements of enterprise-level security.

Driver is SOC 2 Type II compliant. This means we have a long list of security protocols in place, including data encryption, access controls, and continuous monitoring. These and more are described at trust.driver.ai. We also support our customers’ specific security requirements through different deployment models, which allows us the flexibility to meet your more specific needs.

How is our proprietary code protected?
​Your proprietary code is protected through strict access controls, data encryption during transfer and storage, and continuous monitoring for any unauthorized access, all of which are part of our SOC 2 Type II compliance protocols.

​What are the guarantees around data privacy?
We consistently monitor and enforce privacy standards to prevent unauthorized access, ensuring that sensitive information remains confidential and protected in line with industry best practices.

Are there protections against code and IP leakage?
​Yes, we have protections against code and IP leakage, including secure access controls, encryption during data transfer, and stringent monitoring for unauthorized access or unusual activity.

To learn more about Driver's approach to compliance, IP protection, copyright, and more, you can read more about working with us here and at our Trust Center here.