TxCapture is a user‑initiated UI automation recorder designed for enterprise testing and workflow automation teams.
This Privacy Policy explains what information TxCapture collects, how it is used, and how your privacy is protected when using the Chrome extension.
TxCapture complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
TxCapture collects only non‑personal, non‑identifying interaction metadata, and only when the user explicitly clicks “Start Capture.”
This may include:
Page title
HTML element selector metadata (e.g., attributes used for UI automation)
Event types such as click, input, or change
Structured metadata needed to generate the automation file (e.g., XAML)
This temporary metadata is necessary to fulfill the extension’s single purpose:
Generate automation‑ready output from user‑initiated UI interactions.
TxCapture does not collect, access, store, or transmit:
Names or identity data
Passwords, credentials, or form values
Cookies
Session tokens
Keystrokes
Browsing history
TxCapture does not monitor pages in the background and does not track user behavior.
Only during an active capture session:
Temporary metadata is used to generate automation output (such as XAML)
The output is then downloaded locally to the user’s machine
No captured information is used for analytics, advertising, profiling, or sharing
Uses a backend API, the metadata is transmitted securely over TLS to the enterprise‑controlled backend solely for the purpose of generating the automation file.
No data is retained on the server after processing.
TxCapture follows a strict non‑retention model:
No data is stored after a capture session ends
Temporary in‑session metadata is cleared when the user clicks Stop Capture
No long‑term storage occurs in the extension, cloud, or backend
TxCapture does not:
Share data with third parties
Sell data
Use data for advertising or analytics
Send data to external services other than an enterprise’s own backend (if configured)
TxCapture requests only the minimum permissions needed:
activeTab — to access the active page during recording only
scripting — to inject capture scripts only when the user starts capture
storage — for temporary in‑session metadata
No background monitoring, host‑wide access, cookies, or browsing history permissions are used.
Users maintain full control:
Recording begins only when the user clicks Start Capture
Recording stops immediately with Stop Capture
All optional backend communications use TLS 1.2/1.3
No sensitive or identifying information is collected or transmitted
Metadata is processed in‑flight and discarded after use
For questions about this Privacy Policy or enterprise deployments, contact your TxCapture administrator or TestingXperts representative.