Skip to content

Administer

Security and data handling

Driver reads the repositories and connected sources made available to the investigation. Administrators control source grants, Jira project access, and credentials for documentation connections.

Source and investigation data

  • Code access. Connect the repositories Driver should read through your supported code host. Scope the app or token to the intended repositories and review source permissions in Driver.
  • Investigation context. Driver uses connected source, ticket context, documentation, and information you supply to produce findings. Review source citations before acting on a result.
  • Data ownership. You own your data and the work Driver produces from it. Driver does not use your data to train AI models.
  • Credentials. Use scoped credentials for connected services. Agent connection credentials are encrypted and are not displayed after saving; rotate a credential if it is exposed.
  • Jira automation. Administrators choose which Jira projects investigate newly created tickets. The automated findings are posted on the ticket. Continuing in Driver starts a private conversation from that report.

See Access control for people, teams, and machine scope, and Automatic Jira investigations for the on/off control.

Deployment and private networking

Driver is available as a multi-tenant service and through enterprise deployment arrangements. Contact Driver about single-tenant deployment, private networking, and IP restrictions for environments with additional access requirements.

Bring your own model is an Enterprise option for running on your provider. Contact Driver for the supported configuration and deployment details.

Security information

Driver’s security policies and compliance materials are available through the Trust Center. Contact security@driver.ai for security questions or the documents your organization needs to review.