Privacy Policy for HTC Action Capture

This Privacy Policy is specific to the HTC Action Capture application and describes how the application collects, uses, stores, and protects user information. It is separate from the standard Privacy Policy and applies exclusively to the HTC Action Capture application.

HTC Action Capture / User Analytics ("Extension", "we", "us", or "our") is a browser-based tool designed for authorized software testing, training, test automation, knowledge capture, debugging, and quality-assurance activities within client-approved business applications and designated training/test environments.

The Extension is intended to be used by authorized engineers, developers, testers, and other designated personnel. The application is designed to use test, training, sample, synthetic, masked, anonymized, or otherwise authorized non-production data, rather than data directly entered by customers in production systems.

1. Intended Users and Use

The Extension is intended for use by authorized personnel, including:

• Software engineers.
• Quality-assurance engineers.
• Test engineers.
• Developers.
• Automation engineers.
• Other personnel authorized by the applicable client or organization.

These users enter or interact with data for training, testing, automation, debugging, and application-development purposes.

The Extension is not intended to collect information directly from customers or to monitor customer browsing activity.

2. Approved Applications and Environments

The Extension is intended to operate only within client-approved business applications and authorized training/test environments.

The applications used with the Extension should contain test, sample, synthetic, masked, anonymized, or otherwise authorized non-production data.

The Extension is not intended for use with production customer data or live customer transactions.

It is also not intended to monitor general internet browsing or unrelated personal websites.

3. Information the Extension May Capture

When recording is enabled within an approved training or test application, the Extension may capture information associated with interactions performed by the authorized user, including:

• Clicks: Buttons, links, icons, inputs, and other clickable elements.
• Text input: Text entered by the engineer or tester into supported fields.
• Dropdown selections: Selected values or options.
• Navigation information: URLs associated with pages visited within the approved application.
• Hover interactions: Hover activity over supported interactive elements.
• Additional manually configured actions: Such as double-click, right-click, scroll, keypress, upload, wait, assertion, and manually added actions.
• Page and element metadata: Selectors, XPath expressions, HTML tag information, DOM attributes, displayed text, input values, URLs, file paths associated with upload actions, and timestamps.
• Screenshots: Screenshots of the active test/training application when the authorized user explicitly invokes the Screenshot function.

The exact information captured depends on the application, the user's interactions, and the recording features enabled.

4. Nature of the Data

The Extension is designed to capture engineer-generated test and training activity, rather than information submitted directly by customers.

For example, an engineer may enter a test customer name, test account number, sample address, or other synthetic test information into the training application and the Extension may capture that interaction as part of the test flow.

Where possible, organizations should use synthetic, masked, anonymized, or otherwise non-production data for these activities.

The use of real customer information is not the intended purpose of the Extension.

5. Purpose of Data Collection

Captured information is used for authorized:

• Application training.
• Software testing.
• Test-case creation.
• Test automation.
• AI-assisted test generation and execution, where authorized.
• Knowledge capture.
• Application workflow documentation.
• Debugging and troubleshooting.
• Visual verification.
• Bug reporting and reproduction.

Recording is explicitly initiated by the authorized user through the Extension's Record function.

The user can:

• Start and stop recording.
• Review captured actions.
• Edit captured actions.
• Delete individual actions.
• Clear the current recording session.
• Export captured test actions where permitted.

Screenshots are captured only when the user explicitly selects the Screenshot function.

7. Data Storage and Export

Captured action data may be temporarily stored using browser storage mechanisms used by the Extension.

Authorized users may export captured actions as JSON or copy them to the clipboard for approved testing and training purposes.

Screenshots may be downloaded to the user's configured Downloads location.

Exported data, screenshots, and copied information should be handled according to the applicable client's security and data-retention requirements.

8. Data Transmission and Connected Services

Where the Extension is configured to transmit captured information to an approved enterprise backend, AI service, test automation platform, or other client-authorized service, the captured information may be processed by those services for the purposes described in this Privacy Notice.

Such processing should be limited to services approved for the applicable client environment.

Where a deployment does not transmit captured information outside the browser, captured information remains within the local browser environment until the authorized user explicitly exports or transfers it.

9. Data Sharing

The Extension is not intended to sell captured information or use captured information for advertising.

Captured information is intended to support authorized training, testing, automation, knowledge capture, debugging, and related engineering activities.

Where the Extension integrates with client-approved systems or services, captured test and training information may be processed by those systems as required for the configured functionality.

10. Security and Sensitive Information

Users should follow the applicable client's security and data-handling policies.

The Extension should not be intentionally used to capture:

• Production customer information.
• Customer authentication credentials.
• Passwords.
• Payment-card information.
• Production account credentials.
• Other sensitive production information.

If sensitive or production information is inadvertently captured, it should be handled according to the applicable client's security and incident-management procedures.

11. Client Responsibilities

The applicable client or organization is responsible for:

• Approving the applications and domains where the Extension may be used.
• Identifying appropriate training and test environments.
• Authorizing engineers and other personnel to use the Extension.
• Providing appropriate test or training data.
• Establishing applicable security, privacy, and retention requirements.
• Ensuring that users are appropriately trained and authorized.
• Ensuring compliance with applicable contractual, regulatory, and organizational requirements.

12. Data Retention and Deletion

Authorized users can clear the current recording session using the Extension's Clear functionality.

Exported JSON files, screenshots, clipboard contents, and information transferred to other approved systems may remain outside the Extension and should be managed according to the applicable client's retention and deletion policies.

13. Changes to This Privacy Notice

This Privacy Notice may be updated periodically to reflect changes to the Extension, its functionality, deployment model, or applicable requirements.

14. Contact Us

If you have any questions regarding this Privacy Policy, please contact your extension administrator or support contact.