Skip to main content
This page is for the person who reviews Quint before it goes on a fleet. Each section answers one question in brief and links to the page that holds the detail. How Quint itself is hosted and protected, and its certification status, are stated at quintai.dev/security.

What leaves the machine

Quint records what AI coding agents do on a machine and uploads that record to your workspace. Some of what it uploads is content: prompt text, the files an agent reads, the output of the commands it runs.
  • Masking is best-effort. By default, credentials Quint recognises are replaced with a marker before upload, on some capture paths, not all. Anything it does not recognise is uploaded as written.
  • The local proxy reads the requests an agent sends to its model provider. Requests from any other program on the machine to the AI provider hosts Quint intercepts pass through the same proxy, and are captured the same way when it can decrypt them.
  • The network filter, on a Mac, sees the destination, port and process of every outbound connection from every process. It uploads only those of a recognised agent session, and it does not read or modify the contents of connections.
  • AI chat sites in a browser. Quint uploads a record of the site and the process id, not the content.
  • The local audit database stays on the machine and keeps the unmasked original.
The full table, row by row, is What Quint records. The same ground, with its limits, is at quintai.dev/security.

What it installs, and what it is granted

On a Mac, Quint is two profiles and one installer. The table lists what they bring. For Windows and Linux, see Platform support. Quint records and detects; it does not stop a user with local administrator rights. See Roll out with MDM and Four ways capture happens.

Whether it interrupts anyone’s work

Every ruleset starts in shadow mode and records without interrupting anything. Arming enforcement is a step you take together with your Quint contact. Two things can act while your own rules are in shadow:
  • An Admin or Owner can terminate an agent from a session.
  • If a partner manages your workspace, a partner’s rules in enforce mode can still refuse actions while your switch is off.
See Shadow enforcement and Roles and permissions.

What turns capture off

Two policy settings, log_bodies: false and mask_secrets: false, change what is uploaded and what is masked; the table under What turns capture off says what each does. Removing the endpoint takes it off the machine and takes Quint’s settings out of the coding agents there. A machine that is not enrolled records nothing. There is no customer-side pause; see Remove a machine.

What the network must allow

The endpoint makes every connection itself, outbound: HTTPS on TCP 443, and DNS on UDP 53 when the machine’s resolver fails. The hosts, the ports and how it behaves behind a proxy or TLS inspection are on Network requirements.

Where data lives, and what separates it

  • Data lives in your workspace’s Data region. It is set when Quint places the workspace, and it does not move; changing region is a support action.
  • Every query is scoped to your workspace at the database level. No request can name another workspace; the workspace always comes from the signed-in session.
  • That separates workspaces from one another. It does not restrict Quint’s own administrative access to the database.
See Isolation. Hosting, encryption and the last point above are stated at quintai.dev/security.

How long data is kept, and how it is deleted

Retention is per class of data: divergence findings 14 days, events 14 to 45 days, sessions 365 days, the body of an event over 200 KiB, kept in object storage, 2,555 days, and some records with no automatic deletion yet. Data deleted from the database stays in backups for up to 7 more days. An Owner can file a deletion request, which “is a recorded ask, not a countdown”: it opens a request with Quint. The full table is Data & retention.

Who can sign in, and what they can see

  • Methods. Hosted SSO and Google, with an email one-time code as the fallback. There is no self-service signup.
  • MFA. Quint does not enforce MFA itself. With SSO or Google it inherits whatever your identity provider enforces. An email code is a single factor.
  • Sessions last one hour. A tab that is actively loading data renews silently; an idle tab does not. A removed member is refused immediately.
  • Not available: directory provisioning over SCIM, and IP allowlisting.
  • Roles. Four roles, enforced server-side on every call. Every member can read all workspace data.
  • Partner access. If a partner operates your workspace, the partner can hold standing access or a delegated session that reads it. You can end a session or revoke standing access under Settings › Partner access.
  • Audit. Console actions is the administrative audit log. Admin and Owner can read it, and a batch exporter can receive it as a stream.
See Members and sign-in, Roles and permissions and Compliance and audit.

How versions change, and how a machine is removed

An Admin or Owner sets the sensor version endpoints are moved to and the share of the fleet that is offered it, under Settings › Fleet › Agent rollout. Left empty, every endpoint stays on what it has. Removing the endpoint from a machine is done with your Quint contact, in a fixed order. See Workspace and retention and Remove a machine.

For the people on enrolled machines

The installer shows the full notice before it installs anything, and the notice cannot be switched off. What Quint records is written to be shared with the people whose machines are enrolled, and Quint is on my machine is written for developers on a Mac.

Something this page does not answer

Ask us: see Get support.
Last modified on November 13, 2026