VisualQ Capture — Privacy Policy

Data we collect

• DOM interaction metadata during an active recording session: element selectors, accessible names, roles, attributes, page URLs, and timestamps.
• Text you type into form fields while recording (transmitted to VisualQ to generate FRT test steps).
• Secret field names you record (for example a login password field label) — never the secret values, which are configured separately in VisualQ Environments.
• Pairing session identifiers, project identifiers, and API base URL stored locally after you connect with a VisualQ pairing code (VQ-XXXX).
• Optional authenticated session state (cookies and storage state) when you explicitly choose to save a login session for FRT replay.
• Screenshots of the active browser tab when you run Detect or Say steps that require vision planning (full-page or viewport capture, depending on your choice).
• Download events on the active tab when a recorded step expects a file download.

Data we do not collect

• Browsing history or page content outside an active recording session you started on your paired target site.
• Keystrokes, clipboard content, or form values outside the Extension’s recording flows.
• Advertising identifiers, cross-site tracking, or analytics unrelated to VisualQ recording.
• Sale, rental, or sharing of your data with third-party advertisers or data brokers.

Why we request permissions

• storage — persist pairing session and in-progress steps between browser restarts.
• activeTab — access the tab you are using when you click the Extension icon to pair or record.
• tabs — coordinate capture state across tabs on your paired target domain.
• scripting — inject the recorder UI on the target site after you pair with an explicit pairing code.
• Host access to visualq.ai — communicate with your VisualQ workspace API (pairing, detect, confirm, library).
• Optional broad host access (http/https) — requested only for the specific customer site domain you choose when pairing; not granted for all websites by default in the published Extension.
• cookies — read session cookies when you explicitly save an authenticated login session for replay.
• debugger — attach briefly to the recording tab to capture screenshots for vision-assisted steps.
• downloads — detect when a file download starts during a recorded step.

Service providers

• VisualQ (visualq.ai) — hosts the API and workspace where your recorded scenarios are stored under your account.
• Cloud infrastructure used by VisualQ (for example hosting and database providers in the EU) — processes data only to operate the VisualQ service you use.
• Google Chrome Web Store — distributes the Extension; governed by Google’s policies when you install from the Store.

How we use data

Recorded interactions, screenshots, and session metadata are transmitted over HTTPS to your VisualQ workspace API to build, confirm, and replay FRT scenario steps. Data is used solely to provide VisualQ testing features that you explicitly start. We do not use Extension data for advertising or unrelated profiling.

Local storage

The Extension stores your API base URL, pairing session token, in-progress step stack, and related session preferences in chrome.storage.local on your device until you click Disconnect in the popup or the server session expires. Screenshots used for vision planning are sent to VisualQ for the active step and are not retained locally beyond the recording workflow unless your workspace settings say otherwise.

Cookies and authenticated sessions

When you explicitly save an authenticated session for FRT replay, the Extension reads cookies for the active tab on the domain you are recording and sends that session state to your VisualQ workspace over HTTPS. This happens only during an active session you control. We do not read cookies on unrelated sites or without your action.

Screenshots and debugger permission

The Extension uses Chrome’s debugger API only on the tab you are recording to capture screenshots for AI-assisted Detect and Say steps. The debugger is attached briefly for each capture and detached immediately afterward. Screenshots are sent to VisualQ’s API for step planning; they are not used for advertising. You can choose viewport-only capture when a UI state (for example an open menu) must not be disturbed by page scrolling.

Secrets and sensitive fields

When you record a secret step, the Extension stores only the field name or key identifier. Actual secret values are never stored in the Extension. You configure values per environment in VisualQ → Settings → Environments → Secrets, where they are encrypted server-side and resolved at test execution time.

Retention and deletion

Server-side recorder session data expires automatically after your pairing session ends or times out. Click Disconnect in the Extension popup to clear local session data on your device. Scenario and project data retained in your VisualQ workspace follows your account settings and our main Terms of Service. To request deletion of account data, contact support@visualq.ai.

Your rights

Depending on your location, you may have rights to access, correct, delete, or restrict processing of personal data held in your VisualQ account. To exercise these rights, contact support@visualq.ai. If you are in the European Economic Area, you may also lodge a complaint with your local data protection authority.

Children

VisualQ Capture is a professional testing tool not directed at children under 16. We do not knowingly collect personal data from children.

Changes to this policy

We may update this policy when the Extension or applicable law changes. The “Last updated” date at the top of this page will reflect the latest version. Continued use of the Extension after an update constitutes acceptance of the revised policy.

Contact

Questions about this policy or Extension data practices: support@visualq.ai