Security at Docked

Updated October 15, 2026

Access begins with the browser owner

The owner reviews the task, access mode, website scope, and screenshot notice before Start. They can pause or end access. A session controls one active browser tab; it does not grant remote access to the operating system.

Chrome permissions and Docked’s session permissions serve different purposes. A broad Chrome grant needed for screenshots does not by itself expand the session’s authorized actions or websites.

Bounded browser commands

The extension executes a defined set of browser commands rather than arbitrary scripts supplied by an agent. Commands are tied to the session, current page, and execution lease. Pauses, document changes, and uncertain results are checked to reduce stale or repeated actions.

These controls reduce risk; they do not make arbitrary agent instructions safe. Review the access you grant and verify sensitive results.

Approve sensitive relies on the agent marking a change as sensitive; navigation also requires review. It does not independently detect risk. Full access permits actions within the scope reviewed at Start without repeated approvals.

Accounts and agent connections

Passwords are stored as hashes. Login sessions and workspace access determine who can read or manage records. Remote MCP uses OAuth authorization to a selected workspace; applications can be revoked from Settings → Connections. Keep advanced API keys private.

Workspace invitations are single-use bearer links: any signed-in account with the link can accept. They are not bound to a recipient’s email address. An unverified account email is a claimed address, not proof of inbox ownership. Send invitations through a trusted channel and verify the person who joined when identity matters.

Email verification and password-reset links, when delivery is available, are time-limited account capabilities. Do not forward them.

Session data and screenshots

Records are private by default and include information the agent observes, messages, tool results, and available screenshots. The extension attempts to mask sensitive or editable fields before capture, but other visible content can be included. Do not treat masking as guaranteed secret removal.

Authorized sharing is a separate action. Public links can expose the included record to anyone with the link; disable them when they are no longer needed. Recoverable deletion is not immediate physical erasure.

Infrastructure and payments

Docked uses HTTPS and access-controlled service and storage providers. Stripe handles card entry through embedded payment fields. Docked is not end-to-end encrypted: its service and the chosen agent provider process information needed to perform the task.

We do not claim SOC 2 certification or a compliance guarantee for your particular use case.

See our Chrome Web Store Limited Use disclosure for the restrictions on extension data use and transfer.

Report a concern

Email team@docked.ai with a description, relevant URLs, and steps to reproduce. Please avoid sending passwords, access tokens, or other people’s private data. We will review reports and coordinate next steps.