# Security at AQ

> How AQ protects customer data: separate machines and networks per organization, encrypted credentials, TLS-only database connections with daily backups, audit logging, and reviewed change control. SOC 2 Type II audit in progress.

Published November 20, 2026 · by the AQ team · Canonical: https://aq.dev/security/

Last updated: November 20, 2026

AQ runs AI coding agents for teams, so it holds code, credentials and conversations that matter. This page describes the safeguards we operate today. How we may use Customer Data is governed by our [Terms of Service](https://aq.dev/terms/) (section 4.2), and how we handle personal information is described in our [Privacy Policy](https://aq.dev/privacy/). The companies that process data for us are listed on our [subprocessors page](https://aq.dev/subprocessors/).

## Compliance

AQ is being audited for SOC 2 Type II (Security criteria) by an independent auditor. The observation period runs from November 16, 2026 to February 16, 2027. The audit is in progress: AQ is not yet SOC 2 certified, and no report has been issued.

## Separation between organizations

- Each organization's cloud machines run on their own private network, with firewall rules that block traffic from other organizations' machines. Newer organizations also get their own Google Cloud project.
- On a shared machine, every person runs under their own operating-system account.
- Production runs on Google Cloud in the United States.

## Network and administrative access

- Administrative SSH access to our production servers is possible only through Google Identity-Aware Proxy. No SSH or remote-desktop port on our production servers or our shared customer-machine network is open to the internet.
- Web traffic to aq.dev is served over HTTPS through Cloudflare; plain HTTP requests are redirected to HTTPS.
- Our GitHub organization requires two-factor authentication for every member.

## Data protection

- Our production database accepts only encrypted (TLS) connections.
- The database is backed up daily, with point-in-time recovery for the last 7 days. Backups are stored in Google Cloud's United States multi-region.
- Database activity is audit-logged, including every connection.
- Tokens for the accounts you connect and the secrets you save in AQ are encrypted with AES-256-GCM before they are stored and are never returned by any AQ API. Repository environment variables are also encrypted with AES-256-GCM.
- When a saved secret appears in an agent transcript, AQ replaces it with a placeholder.
- Our production secrets live in Google Secret Manager, and access to them is audit-logged.

## AI agents and connected accounts

- For each connected account, you choose what each tool may do: allow it, ask you first, or turn it off.
- Agents act on your connected accounts only within the permissions you set.

## Change control

Since November 20, 2026, every change to AQ's code reaches the production branch only through a pull request that passes all of the following, with no bypass for anyone, administrators included:

- Required automated checks: the build, unit tests, browser tests and smoke tests.
- An independent AI code review of every change, done by a model from a different vendor than the agent that wrote it.
- Owner approval for code that moves money and for database changes that change who can access data.

## Vulnerability management

- Dependabot alerts and secret scanning (with push protection) are on for AQ's code repository.
- Our dependencies and runtime versions are checked for known vulnerabilities every six hours.

## Status page

A public status page is coming. It is not live yet.

## Reporting a vulnerability

Email [security@aq.dev](mailto:security@aq.dev) with the details and steps to reproduce. Please give us a reasonable time to fix an issue before you disclose it publicly.

---

About AQ: AQ is where teams put AI agents to work on everything they do: code that lands as a reviewed pull request, bots that run the jobs that repeat, and an assistant that starts each day, all on the agents and subscriptions they already have, like Claude Code and Codex, on private cloud machines of their own or on their own Mac. Start at [aq.dev](https://aq.dev/).
