What this policy covers
This policy covers Commitment Desk — Open Tab Capture, version 0.1.0, and its handoff to the separate local Commitment Desk companion app. The extension's single purpose is to capture supported, rendered conversation text from tabs you explicitly enable and send it to your local task-review workspace.
The companion app is required. Installing the extension alone does not install or start the companion app. Features described as belonging to the companion app are not performed by the extension itself.
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 send captures to the publisher's server or this website. Chrome's optional localhost permission cannot specify a port; this extension's code uses port 3217.
Local AI by default
The companion app stores sources and processes them into proposed tasks and work-context suggestions. Its default model configuration uses a local Ollama endpoint. Tasks and learned context require your review before acceptance; model output can be incomplete or incorrect.
Optional remote AI
If you configure a remote model endpoint in the companion app, that app sends source text and relevant context to your chosen provider. For task extraction this can include conversation timestamps, the workspace time zone, names of known team members, and approved work context. Your configured provider receives these requests and handles them according to its own policies. The extension itself does not call a remote AI service.
Separate audio recording
The companion app can record 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. Resulting transcripts are treated as sources; they may be sent to a remote model if you configured one. The extension does not record audio.
Your controls
Pairing alone enables no tabs. You enable each intended tab from the extension popup. Pause it in the popup, 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 pairing token remains in local extension storage. Capture checks occur approximately once per minute while the browser runs, but browser suspension, unsupported page layouts, errors, or a stopped companion can interrupt them. Check the popup for status.
You can review proposed tasks and dates, approve or reject proposed work context, and edit or archive accepted memory in the companion app. Archiving is not deletion. Opening messages yourself may trigger the source service's read receipts.
Storage, retention, and deletion
The pairing token is stored in local extension storage, not Chrome Sync. Enabled-tab identifiers and status are stored for the browser session. The companion app saves sources, tasks, history, work context, recordings, transcripts, and settings in its local data directory. Provider credentials, if supplied, are stored locally by the companion app.
Version 0.1.0 has no automatic expiry for captured sources or recordings and no complete per-source deletion interface. Closing a tab, pausing capture, or uninstalling the extension does not delete data already received by the companion.
To remove all companion data, first export or back up anything you need, stop the companion app and its background service, and remove its local data directory. This also removes tasks, settings, and history. Separately remove copies you created in exports or backups. Uninstalling the extension removes its local settings; copies previously sent to a remote provider are subject to that provider's retention and deletion process.
Protect your PC and backups using appropriate operating-system and browser access controls. The publisher does not receive a copy of your local database and cannot remotely retrieve or erase it. Contact us for help locating the relevant local files.
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.