Your runs are not training data.
Test instructions, screenshots, traces, reports, console logs, and network context are used to execute and explain your run, not to train a model.
Testorim runs real browsers against real web apps. That means the security baseline matters: no AI training on your runs, encrypted sensitive context, organization-scoped data, and network guardrails for browser sessions.
Trust posture
Test data stays your data. Artifacts exist to explain a run, not to feed a training set or create a resale dataset.
Read privacy policyTest instructions, screenshots, traces, reports, console logs, and network context are used to execute and explain your run, not to train a model.
Saved browser state, environment cookies, database credentials, and integration tokens are encrypted before they hit storage.
Browser requests to loopback, RFC1918, link-local, and metadata hosts are blocked so QA runs cannot be turned into an internal network scanner.
Each run's browser opens in a separate container that holds no application secret, runs on a read-only filesystem with Chromium's sandbox on, and has no network route except a proxy that refuses private addresses.
Projects, procedures, runs, fixtures, environments, and reports are scoped through the organization boundary.
No. Test instructions, screenshots, artifacts, reports, and run data are not used to train AI models.
Only when a feature needs it, such as saved login reuse. Sensitive browser state and cookies are encrypted at rest.
No. Testorim blocks private, loopback, link-local, and cloud metadata hosts at URL and browser request boundaries, and the browser's only network path is a proxy that enforces the same rule on every connection, redirects included.
Your workspaces, runs, screenshots, videos, traces, fixtures and baselines are deleted, and any live subscription is cancelled. Deleting your account in the app triggers it; a request by email is completed within 30 days.
See where AI is used in planning, execution support, and reports.
Learn how teams create browser coverage without writing scripts.
Runs, history and team seats scale with your plan.
This page describes how we build and operate the service today. It is a description, not a warranty, and it is not a certification, audit report or compliance attestation. No method of transmission over the internet and no method of electronic storage is completely secure, so we cannot guarantee absolute security and do not warrant that the service will be free from unauthorised access. Practices described here may change as the product changes.
A passing test is not a security assessment of your application. Testorim runs the steps you describe; it does not certify that your software is secure or fit to release. Your own responsibilities, including your authority to test a target and the data you put into test inputs, are set out in the terms and the privacy policy.