Draft for owner and legal review. This page describes how Taken currently works; it has not been reviewed by a lawyer or a regulator.
Access control
Every task, browser session, order intent and approval is tied to your account and checked on the server. Database row-level security limits reads to your own records.
Browser control
The live view uses short-lived, single-use tickets. Viewing never sends input; manual input works only after you take control. Pause, stop and take-over are enforced on the browser worker before any further AI action.
Orders
Orders require your approval of an exact, hashed snapshot that expires quickly. A separate rule-based check (not the AI) must pass before any submission, and live execution is currently switched off for every platform.
Known limits
Network protections for the cloud browser are best-effort and documented in the project's technical reports. Taken has no security certifications.
Reporting
A vulnerability reporting contact will be published by the owner.