Privacy

Your test evidence stays on your device by default

This policy covers the TabQA extensions for Chrome and Edge and tabqa.openutx.cn. Last updated October 8, 2026.

Data handled by the extension and local storage

TabQA accesses the Android device you explicitly select and processes requests, screen video, screenshots, logcat, the target app, and device information. Capture attachments are stored locally. Common authentication headers and sensitive parameters are masked. AI analysis sends relevant data as described below.

AI analysis and data transmission

Capture attachments and OCR are processed locally. AI analysis sends log text, request information, UI properties, or performance metrics to the configured service. Credential analysis may also send requests during page debugging in Free; see the privacy policy. The default service is https://tabqa.openutx.cn. A custom endpoint receives data if configured. Requests use JSON and the default endpoint uses HTTPS. Automatic redaction cannot cover every business field; log text and UI properties can contain sensitive data.

AI processing and offline fallback

The default diagnostic service processes requests without saving them as application records. Website access logs are described below. Confirm retention and usage policies with any custom endpoint or inference provider. After an AI request fails or times out, log triage, credential detection, UI assertions, and jank analysis fall back to local rules. Rule coverage can differ from cloud results. Initial activation needs internet access; offline Pro use still requires a valid license.

Payment and Pro licensing

Purchases use an external checkout; the extension does not receive card numbers, CVVs, or payment passwords. Activation sends an Order ID or License Key and a browser-generated client identifier to the license API. The server stores license, expiry, and binding information. The browser stores the license credential, token, and expiry. Deactivation clears local license data without releasing server bindings.

Local storage and deletion

Capture evidence is retained for seven days by default and can be deleted from history at any time. The ADB RSA key stays in the browser. Uninstalling the extension removes extension data and requires device authorization again.

Local text recognition (OCR)

Screenshot text recognition runs locally in the browser. Simplified Chinese and English recognition models are included in the extension package and stored in the browser's local cache on first use. Screenshots, selected regions, and recognized text are not sent to TabQA servers or any third party.

Historical waitlist data

For users who joined before launch, we still store email, role, page language, source path, and submission time to send essential launch notices. You can ask us to delete these records at any time. The website no longer accepts new waitlist submissions.

Anonymous analytics and server logs

The website uses a self-hosted Umami instance for pageviews, sources, device categories, and extension store button clicks. We do not send personal information to Umami and do not use advertising cookies. Server access logs are kept for up to 14 days solely for network security and troubleshooting.

No-Sale and No-Ad Commitment

We never sell, rent, or monetize your personal or testing data. Test evidence is never used for profiling or advertising.

Your rights and data requests

To request access, correction, or deletion of license or historical contact records, email [email protected]. We will respond within a reasonable time.