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.
Security & trustBrowser QA touches sensitive apps.
Browser QA touches sensitive apps.
Treat it like production access.
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 policy →Cookies and login reuse are encrypted.
Saved browser state, environment cookies, database credentials, and integration tokens are encrypted before they hit storage.
Private hosts are blocked.
Browser requests to loopback, RFC1918, link-local, and metadata hosts are blocked so QA runs cannot be turned into an internal network scanner.
Project data is organization-scoped.
Projects, procedures, runs, fixtures, environments, and reports are scoped through the organization boundary.
Quick answers
Is my test data used to train AI models?
No. Test instructions, screenshots, artifacts, reports, and run data are not used to train AI models.
Do you store login/session context?
Only when a feature needs it, such as saved login reuse. Sensitive browser state and cookies are encrypted at rest.
Can Testorim reach private/internal network targets?
No. Testorim blocks private, loopback, link-local, and cloud metadata hosts at URL and browser request boundaries.