Security & data handling
WebSureQTool is a desktop application that runs on your Windows machine. Your test content lives in a local workspace and stays there. This page explains, plainly, what stays local and the few things that connect to the internet — so you can review it before you adopt the tool.
What stays on your machine
WebSureQTool does not upload your test content. These artifacts are written to your local workspace and remain under your control:
Test suites
Your suite.yaml files and reusable page metadata.
Datasets
Your CSV / JSON data files used for data-driven runs.
Run histories
Past executions and their status, stored locally.
Evidence & reports
report.html, junit.xml, run.json, logs, and screenshots.
Exported code
Java / C# code you generate is written to your disk.
Your workspace
Projects and configuration live in your local workspace folder.
What connects to the internet — and why
WebSureQTool is hybrid SaaS: the app and everything you create run and stay on your PC, and it goes online mainly to confirm your subscription. It sends no telemetry and uploads none of your test content. Here is the complete list of what reaches the internet.
Sign-in & subscription
WebSureQTool signs you in with Microsoft or Google through our sign-in service (Microsoft Entra) to verify which plan you are on; subscriptions are billed through Stripe. This checks entitlements only — it does not send your test suites, datasets, or results. On the free plan, the app also reads the current free-plan limits from websureqtool.com once a day. The app can run within an offline grace period between checks.
Update checks
Direct installs ask GitHub Releases about once a day whether a newer version exists (only the version number is read; nothing about you is sent). Nothing downloads or installs without your explicit consent, your current version is backed up first so you can revert, and you can skip a version. Microsoft Store installs update through the Store instead.
Browser drivers
You download the browser driver (msedgedriver or chromedriver) yourself from Microsoft or Google and add it with Tools > Import Driver — step-by-step video. WebSureQTool then uses only that driver (or one you put on PATH) and never downloads a driver on its own; with none set up, it stops and shows where to get one.
The websites you test
When you run a suite, WebSureQTool drives a local browser (Chrome or Edge via Selenium WebDriver) against the URLs in your suite — the same sites you would open yourself. That traffic goes directly from your machine to those sites.
This website
websureqtool.com uses Vercel Analytics (aggregate, cookieless), Google Analytics, and Google Ads conversion measurement, with a consent banner where required. This applies to the marketing website only — not to the desktop application or your test data. Details in the Privacy Policy.
Security reviews & compliance
Evaluating WebSureQTool for a regulated or enterprise environment? If you need a data-flow summary, a data-processing agreement, or documentation for a security review, get in touch and we will work through your requirements.