DATA & WORKSPACE BOUNDARIES

Your workspace. Your test data.

This notice describes the current single-owner pilot, whether run locally or on the hosted server.

What is stored?

The workspace databases store your owner identifier, password hash, workspace details, test briefs, synthetic profiles, campaign results and research notes. Browser traces may contain screenshots and visible page text from the sites you test. Saved account states and proxy credentials are held in the local private directory.

What leaves the server?

The local model plans browser actions through Ollama. Browser sessions contact your target website and its resources. An explicit network check contacts a public IP measurement service. If you configure a remote worker, it receives the task, allowed domains and assigned account state needed for that session.

Account protection

This release supports one workspace owner with a hashed password, expiring session cookies and CSRF checks. Cookies are marked Secure when served over HTTPS. Plain HTTP on localhost is a local development transport. There is no configured OAuth provider, email service or team access system.

Reports and public demos

Workspace reports require sign-in. A downloaded report is a file you control; it may contain page text and task details. Public demo recordings contain fictional sample data from our own isolated test apps.

Use appropriate test data

Prefer staging sites and dedicated test accounts. Page screenshots and agent observations can retain what is visible during a test. Review them before sharing. Keep workspace database and private-directory backups protected.

Recovery and retention

Owner recovery is an interactive local administrator command documented in the setup guide. It changes the owner password and revokes existing sessions without deleting test history. This build does not provide a data-deletion UI or automated retention policy.