What this policy covers
This policy covers Commitment Desk — Open Tab Capture, version 0.1.0, its separate desktop companion, the optional private cloud coordinator, and the native Android companion. The extension's single purpose remains capturing supported, rendered conversation text from tabs you explicitly enable and sending it to the companion on your PC.
The desktop companion is required for local capture, planning, and desktop execution. Installing the extension alone does not install or start it. Cloud synchronization, Android pairing, AI processing, and approved execution are companion features; the extension itself does not perform them.
Data we handle
After you pair the extension and enable a supported Gmail, WhatsApp Web, or Google Meet tab, the extension can read:
- Supported rendered message text, including displayed meeting captions or chat.
- The page title, source URL, service name, and time of capture.
- Rendered sender details and message dates when available. These may include names and email addresses.
Conversation text may contain health, financial, location, or other sensitive information. The current reader does not automatically redact those details. Enable capture only for conversations you intend to include, and obtain any necessary permission from the people involved.
The extension also handles the pairing token you enter, enabled-tab identifiers, and capture status or errors. The pairing token is a credential for the local companion app.
The extension does not read the browser's history database, cookies, stored website passwords, compose drafts, or input fields. It does retain the URLs of conversations it captures. It does not log keystrokes, mouse movements, clicks, or scrolling; navigate through your inbox; send replies; or record microphone/system audio. Coverage is limited to supported content rendered in the tabs you enable.
Where the data goes
Extension to local companion
The extension sends captured text and service status to http://127.0.0.1:3217 on the same PC, using the pairing token to authenticate requests. It does not directly send captures to a cloud service, the publisher's server, or this website. Chrome's optional localhost permission cannot specify a port; this extension's code uses port 3217.
Configured AI processing
The desktop companion stores sources, tasks, client context, action plans, drafts, and execution history locally. Depending on your settings, extraction can place proposed tasks in review or create tracked tasks automatically. Automatic extraction does not grant permission to send messages or perform external actions. Model output may be incomplete or incorrect.
A local Ollama endpoint is available. If you select a remote model endpoint or a signed-in Codex or Claude runtime, relevant source text and work context are sent to that provider. Requests can include conversation timestamps, project facts, source references, names, tasks, instructions, draft content, and connected-tool results. The selected provider handles these under its own terms and retention practices. The extension itself makes no remote AI requests.
Optional private cloud and Android companion
When you enable and configure the cloud companion, the desktop sends selected client/project profiles and follow-up notes, action plans, prepared drafts and artifacts, exact tool and communication previews, schedules, approval information, execution results, and heartbeat timestamps to the configured private coordinator over HTTPS. These records may contain personal information from the underlying sources. Cloudflare hosts the coordinator and persistent storage. Authentication is required for client data; the public installation page and APK contain no client snapshot or pairing credential.
A phone paired with a one-use, time-limited code receives a separate device token. The coordinator stores a hash of that token, device identification supplied by the app, pairing/revocation timestamps, and approval or change-request records. The Android app encrypts its token with Android Keystore and keeps downloaded snapshots in its private application storage. It periodically checks availability and action status when Android permits; notification delivery is not instant or guaranteed.
The configured cloud account owner controls access to this cloud copy. Enabling cloud synchronization means those selected records are no longer stored only on your PC. Phone approval can queue an exact action for desktop receipt; a separately connected cloud email account can perform an explicitly approved scheduled email while the PC is offline. The current cloud sender supports one exact plain-text email and does not support attachments or WhatsApp sending.
Separate audio recording
The companion app records microphone or system audio only when you start recording and grant the necessary permissions. Audio is saved locally and transcribed by the installed local Whisper runtime. Transcripts become sources and may be included in configured AI processing or subsequent selected project context. The extension does not record audio.
Your controls
Pairing the extension enables no tabs. Enable each intended tab from its popup. Pause it, close the tab, revoke optional site access, or uninstall the extension to stop future capture. Pausing cannot retract a source already submitted to the companion app.
Enabled tabs reset when the browser restarts. The local extension pairing token remains in extension storage. Capture checks occur approximately once per minute while the browser runs, but suspension, unsupported layouts, errors, or a stopped companion may interrupt them.
In the desktop app you can choose automatic task creation or review, inspect dates and source evidence, manage context, and configure AI and cloud access. Archiving is not deletion. Opening messages yourself may trigger the source service's read receipts.
Cloud synchronization can be disabled in the companion. You can unpair the Android app or revoke a device token through the cloud companion's authenticated device-management controls. Successful unpairing clears the phone's saved token and snapshot. Revocation stops that token's future access; it does not erase previously downloaded copies or approval history.
Sending and external execution require approval of the exact draft/action, recipients and account where applicable, and scheduled time. A changed preview or time requires a new approval. Proposed fallback actions, timeline changes, and reassignments are not themselves approved actions. Cloud cancellation is effective only when acknowledged; a send that already started cannot be promised cancelled or recalled. Disabling synchronization or shutting down the PC does not cancel an approved cloud schedule.
Storage, retention, and deletion
The extension token is stored locally, not in Chrome Sync. Enabled-tab identifiers and status last for the browser session. The desktop stores sources, tasks, client profiles, follow-up history, plans, drafts, approvals, receipts, recordings, transcripts, and settings in its local data directory. Supplied credentials are handled by the companion's local credential storage or configured runtime.
Captured sources, recordings, and retained cloud records have no automatic expiry in this release. There is no complete per-record deletion interface. Some newer cloud snapshots replace earlier snapshot fields, while run, decision, device, and receipt history remains retained. Uninstalling the extension or deleting local data does not delete a cloud copy, phone cache, provider copy, or backup.
To remove local companion data, first preserve anything you need, stop the app and its service, and intentionally remove its data directory. Clear the Android app's storage or uninstall it to remove that device's private cache. Cloud data must be removed separately by the configured cloud account owner using the hosting account or maintenance tools; revoking a device token only removes access. Also remove unwanted exports and backups. Copies sent to AI or communication providers are subject to those providers' retention/deletion processes.
Protect devices, the private cloud account, credentials, and backups. Support cannot retrieve an otherwise inaccessible local database. The configured cloud account's owner or administrator can access and manage its stored cloud data; do not assume that an enabled cloud copy is accessible only from your PC.
This website
This privacy-policy website is hosted on Cloudflare Pages. It does not connect to your local companion app or receive your captured conversations. We do not add analytics scripts, advertising, contact forms, or tracking cookies to this page.
Cloudflare may process technical connection data, such as IP addresses and request details, to deliver and protect the website. See Cloudflare's privacy policy. The website asks search engines not to index its pages, but it remains publicly accessible to anyone with the URL.
Contact and policy changes
For questions about Commitment Desk, privacy requests, or help with local data, contact the publisher at help.thefirstranker@gmail.com.
If the product's data practices change, this page and the extension's store disclosures will be updated. The effective date at the top identifies this policy version.