Privacy Policy.

The extension handles messages you type, conversation and task identifiers, ordered task events, connection status, and protected-action approval records. An approval view displays the exact raw action content — including an exact URL, command, payload, or recipient when applicable — so you can see precisely what you are authorizing.

When you click Capture, Chrome asks you to select a screen, window, or tab. The resulting recording may contain website or other visible content, remains a transient local Blob, is not persisted by the extension, and is not uploaded or transferred by the extension.

Alpha One can act in your browser on your behalf. When you direct it to work in a tab, the extension can, for that tab: read the page — its URL, title, visible text, and HTML; act on the page — navigate to a URL, click an element, or type into a field; take a screenshot of the visible area of the tab it is operating; and list your open tabs — their URLs and titles — so it can choose which tab a task refers to.

To act with real mouse and keyboard input, Alpha One uses Chrome's debugging interface; while it does, Chrome shows its own banner reading that Alpha One is debugging the browser. A blue border and an "Alpha One — in control" badge appear on any tab it is driving, and the tab is grouped under a blue "Alpha One" label, so it is always visible when Alpha One has the wheel.

It never acts on its own. Every browser action is carried out only in response to a command that comes from your own Alpha One companion on your machine over the local Native Messaging connection; the extension originates nothing itself. Alpha One does not read or operate browser-internal pages such as chrome:// pages or the Chrome Web Store, which Chrome blocks. Page text that Alpha One reads is treated as untrusted input: it cannot by itself create or approve a protected action.

Data is used only to continue your Alpha One conversation and browser task across the Chrome side panel and the locally installed Alpha One companion, to recover ordered state after a reconnect, present or record your explicit approval decisions, and prepare a user-initiated workflow recording for local processing.

Alpha One keeps a single conversation so you can continue it wherever you are. Messages you send from your other Alpha One surfaces — the desktop application, the mobile app, or the command line — appear in the Chrome side panel, and messages you send here appear on those. This synchronization is performed by the Alpha One companion on your own computer, which holds the conversation. It does not pass through Precise Technology.

If you choose to use the Alpha One mobile app, it reaches that same companion over your own local network using a bearer token you configure. The browser extension itself never uses the network: its only channel is the local Native Messaging connection described below.

The extension communicates only with the locally installed Alpha One Native Messaging host on your computer. That host relays a fixed set of allowlisted operations to the Alpha One Gateway running on the same machine over an authenticated local IPC channel (a Windows named pipe or a Unix domain socket, depending on your operating system). Capture recordings do not enter that channel. The extension does not sell data, does not use data for advertising, and does not transmit data to unrelated third parties.

Page content that Alpha One reads from a tab — text, HTML, a title, a URL, or a screenshot — is relayed to your Alpha One companion over that same local channel so it can carry out the task you asked for. If the Alpha One agent you configure locally uses a remote AI provider, that content may be sent by the companion to the provider as part of the task, and the Alpha One desktop/Gateway application discloses that provider and the data sent to it. This browser extension makes no independent claim about your provider configuration; it does not itself send page content anywhere except to your local companion.

Chrome local extension storage retains your consent record, the current conversation and task identifiers, the last received event sequence number, and your side-panel display preference. The local Gateway retains the authoritative event history, approval records and your approval-settings preference according to its configured retention and compaction policy — all on your machine.

Because all data stays on your computer, you control deletion:

• Remove extension-local data by uninstalling the extension, or by clearing its data from chrome://extensions.
• Delete the conversation and approval history held by the local Gateway by clearing the Alpha One application data on your machine — on Windows this lives under %LOCALAPPDATA%\PreciseTechnology\AlphaOne — or by uninstalling the Alpha One desktop application.

The extension uses a single Native Messaging channel. The native host validates the exact extension origin before responding. Messages between the host and the Gateway use authenticated envelopes over a local channel. Tokens and credentials are not stored in the extension or its source repository and are not logged.

You must consent before synchronization begins. Protected actions pause for your approval and show the exact raw action content. Capture requires you to click Capture and approve a source in Chrome's picker. Approval requests expire and are cryptographically bound to the action shown.

Approval settings. By default, Alpha One stops and asks you before it carries out a protected action — sending, paying, posting, deleting, or using a credential. In Settings you may give Alpha One a standing instruction to proceed without asking. When you do, the action is still checked against the limits in your local configuration, an approval record is still created, and it is still shown to you — the record states that it was decided by your standing policy rather than by you at that moment. This preference is stored by the Alpha One companion on your computer. You can change it at any time, and turning it off takes effect immediately.

Material changes to what data is collected or how it is used will be reflected in an updated policy and, where required, renewed disclosure and consent.

Questions about this policy or your data: lafayettewright83@gmail.com.