Privacy Policy

Last updated: June 2026

The short version

Qove records behavior, not content. We capture that an interaction happened, never what was typed. Personally identifiable information is masked in the user's browser before any data leaves it. We never receive screen recordings, DOM contents, or API request and response bodies.

What we collect

From the snippet on your site: behavioral signals such as click events, navigation, form interactions, element roles and accessible labels, and route transitions with timing. From your account: your name, work email, company, and billing details needed to provide the service.

What we never collect

Text typed into input fields, passwords, payment details, screen recordings or pixel replays, DOM content, and API bodies. Masking happens in the browser by default; nothing sensitive is transmitted to us.

How we use it

To generate and maintain your test suite, produce your journey map, run the service, and communicate with you about your account. We do not sell your data.

Where the runner executes

The Docker runner that executes tests runs inside your CI, against your environment. It has no persistent storage and no outbound access beyond what you point it at. You can inspect the image before you pull it.

Sub-processors and retention

We use a small set of infrastructure sub-processors to host and operate the service, published and available on request. We retain behavioral data only as long as needed to generate and maintain your suite, and delete it on request.

Your choices

You can request access to, correction of, or deletion of your data at any time by emailing [email protected]. For a custom install in a regulated environment, mention it on your call and we will accommodate.

This is placeholder copy pending review by counsel and is not yet a binding policy.