cohandry.
Menu

Development preview · Updated November 6, 2026

Privacy for the website and desktop app

Your project data deserves a clear explanation.

This notice describes the current Cohandry development preview. It separates the installed desktop application from the website’s signup, download and reporting services.

On your computer

The desktop app stores coordinator project records, conversations, task history, received artifacts, command logs and settings locally. API keys entered for a session are memory-only. Starting with 0.1.14, the installed desktop app encrypts saved ChatGPT account profiles and Slack credentials using OS-backed secure storage. Other host/tool configuration and worker credentials have separate storage limits; project records are not encrypted by this feature. Older backups or unsuccessful migrations may retain plaintext credential files. GitHub CLI uses its own credential store and can fall back to a plaintext host file. Exported templates and workspace exports exclude configured credentials, but text you include can itself contain private information.

Optional PR evidence publication

In 0.1.14, you can choose to send a revision-bound report and selected logs/text/images to your connected GitHub repository. Preview and explicit confirmation are required. Everyone with repository access can read the published package; a public repository makes it public. Repository owners can edit/delete its evidence branch and PR comment, and GitHub retains CI under its own rules. Known-pattern scanning cannot detect every secret, including private text inside screenshots. Inspect every selection before sharing. No complete coordinator database or all-log export is automatic.

Model providers and connected tools

When you run an agent, its instructions and selected project content, messages and evidence may be sent to your selected model provider. That provider processes the request under its own settings and terms. Configured MCP servers, commands and remote workers may also process data as part of authorized work. Local storage does not mean that inference or all tools stay local.

When you enable GitHub delivery or Slack, repository content, task information, messages and approval-related data are sent as required by those features. Review the destination, scopes and content before enabling an integration or publishing work.

Update checks and reports

The app checks public release metadata on cohandry.com by default. You can disable automatic update checks in app settings. The preview does not automatically attach your project files, conversations, logs or credentials to a report. Manual reports transmit the fields and files you choose. Review them for private information before sending. Website hosting and network services may process request metadata, including IP addresses, under their service settings.

Website signup and downloads

Email verification is required for download access. Project type and project description are optional. Signup, optional answers, email preferences and relevant timestamps are stored in Cloudflare D1. Private release files and report attachments use Cloudflare R2. The configured transactional email service delivers verification codes and report notifications. Product-update emails are a separate, unchecked choice.

The website uses an essential short-lived verified-session cookie, Cloudflare Turnstile and short-lived hashed rate-limit records to help prevent abuse. Verification codes, sessions and download links expire. The site does not use advertising trackers or third-party fonts.

Private support reports

A report does not subscribe you to updates. A reply address is used to follow up on that report. Reports and attachments are private to the Cohandry owner/support process; they are not posted automatically to GitHub. An unsent report draft remains in its window and is discarded when that window closes.

Optional pack accounts

When activated, pack accounts use your verified website email identity. The service stores connected computer names, hashed device tokens, pending connection requests, pack entitlements, license history and security audit events. Signing keys remain on the service; device credentials are not returned in the account page. The desktop can optionally remember its token using protected storage. It caches signed pack licenses for seven days of offline access. This account is separate from your AI provider connections; signing in does not opt you into product updates. Pack purchasing is not open.

Control, retention and deletion

Sign in to the download flow to change your update preference or delete your website signup. Deleting your website account also removes its pack entitlements, license history, connected devices and pack audit rows, and revokes its sessions and download tickets. Previously issued offline licenses can remain valid until expiry; existing local projects are preserved. It it does not delete separately submitted reports. Contact support@cohandry.com with your report reference to request report or attachment removal. Reports and signup records remain until removed; no fixed automatic retention period is promised in this preview.

For desktop data, export what you want to keep, disconnect accounts and remove the app’s data directory using the operations and backup guidance. Uninstalling the application can preserve that directory. Separately manage repository copies, external assets and backups; removing local app data does not remove data already sent to a provider or integration.

Questions: support@cohandry.com. Read the security model before enabling command execution.