Privacy policy
How Cowork handles your information, and how desktop Cowork and this website fit in.
Effective October 7, 2026
Scope and contact
This policy covers the Cowork iPhone and iPad app, maintained by the Cowork project. Desktop and website processing is described separately below. For privacy questions or requests, use our support page.
Your computer runs the work
Cowork connects to a computer you pair, either on a trusted local network or through a relay you configure. Messages, selected attachments, commands and approval answers are sent to that computer. The computer sends authorized conversations, task status, files and results back to the app. The connection uses HTTPS with trust limited to the paired computer. A configured relay forwards encrypted traffic; its operator can process connection metadata such as IP addresses, timing and traffic volume under its own policies. Cowork does not provide an official hosted session relay or cloud conversation storage. You choose and operate the computer, model services and any relay.
Model services and other tools
Your computer may send prompts, conversation context, selected images, files and tool results to the AI service configured there. A local model can process requests locally; a hosted provider receives the data needed for its requests. Tools and integrations may also contact services as part of the task. These providers apply their own privacy and retention policies and may process data in other countries. Review the selected service and the information you send. The mobile app does not include a Cowork-hosted AI account or model quota. Before sending new task content, the app asks you to review data sharing with the paired computer and its reported model connections. These displayed names do not identify every tool or destination; review the actual configuration and policies on your computer. Starting with build 37, your choice is stored securely on the device for that paired computer and remains effective across app restarts. Earlier builds keep permission for the current app process. Ordinary reconnections and switching between the computer's configured local and relay routes do not require another agreement. Changes to pairing, the configured relay or reported AI services require another review. You can withdraw permission in Settings. Withdrawal stops further new-task and attachment sending from the app; it does not cancel tasks already running or erase data already sent.
Information stored on your device
The app keeps pairing credentials, computer trust information and records needed to reconcile pending actions in device-only secure storage. Earlier builds also keep drafts there. Starting with build 39, complete drafts are encrypted in the app’s private document files, with their key and file pointers in device-only secure storage. Existing drafts are migrated only after the encrypted copy is saved. Drafts are not subject to the shared cache’s expiry or eviction policy. Language preferences are also saved locally. Before build 38, received session content is held in memory for display. Starting with build 38, the app also caches loaded conversation text, images, attachments and workspace file previews on this device. The shared cache is encrypted with a key held in device-only secure storage, limited to 2 GiB (2,147,483,648 bytes), and expires 60 days after each entry is written. Expired entries are removed when the app next reads or maintains the cache; cleanup cannot run while the app is inactive. Capacity limits can remove older entries sooner; iOS can also purge this cache. Only content already loaded is cached, within the app’s existing file-size and preview limits. Reopening a conversation first displays eligible cached history and then synchronizes current content. Cached data remains scoped to its paired computer and current access; opening attachments and workspace files checks current authorization and file metadata. Files you explicitly preview, export or share can create local temporary copies. Before build 39, the app keeps at most three shared temporary files. Starting with build 39, there is no cumulative file-count ceiling, and identical exports reuse an existing file. Each file remains limited to 10 MiB; use the app’s clear control to remove temporary exports. Copies saved to another app or Files are controlled by you and that destination.
Permissions you control
Local network access connects to your computer. Camera access scans pairing codes or takes a photo when you use those features. The photo and document pickers let you select attachments. You can decline or change permissions in iOS Settings; the related feature may then be unavailable. The app does not need your contacts, precise location or an advertising identifier.
Optional task notifications
When you enable notifications for a paired computer and allow them in iOS, the app sends its native Apple push token, language and push environment to that computer. The computer stores the registration using system-protected encryption. Delivery uses the relay you configured and Apple Push Notification service. The relay and Apple receive the token, generic event type, language and opaque routing identifiers needed to open the relevant conversation; notification payloads contain no conversation text or files. Cowork does not use Expo Push Service.
Registrations are limited to the current device access grant and expire after seven days unless renewed while connected. You can turn notifications off for a computer while connected, or revoke the mobile device from desktop Cowork. Removing a pairing only on the phone does not revoke a registration already held by the computer. You can also disable alerts in iOS Settings. Delivery is best effort and subject to Apple and device settings.
Analytics, diagnostics and support
The iOS app has no first-party advertising or usage analytics SDK and does not send the desktop update-activity report described below. Apple may process purchase, distribution, diagnostics and TestFlight feedback data under your Apple settings and its policies; diagnostics or feedback you choose to share may reach us. If you contact us, we receive the details you provide and use them to investigate and reply. Do not include passwords, API keys, pairing invitations or private work in public issues. Support correspondence is kept while needed to resolve the request and meet applicable obligations; you can request deletion.
Desktop updates and website visits
Desktop releases configured for activity reporting send a randomly generated installation ID and the installed version when checking for updates. This is not a hardware identifier. The service stores a date-specific hash and the last reported version for daily deduplication, not the raw ID, and deletes daily records older than 35 days. It does not include chat or file contents. Our static website stores your language choice in your browser and does not embed advertising trackers. GitHub and Cloudflare provide website, download and update delivery; they process IP addresses and other connection metadata needed to serve and protect these services under their own policies.
Remove data and revoke access
Starting with build 38, Settings shows local cache usage and lets you clear cached conversations, images and files without removing pairings or drafts. Removing a paired computer also clears the shared content cache. Use Computers & connections to clear temporary shared files or remove a paired computer and its associated local state. Also revoke the mobile device in desktop Cowork to invalidate its access there. Temporary exports are cleared on app initialization and when a computer is removed. Device-only Keychain records can survive an app uninstall, so remove pairings in the app before uninstalling. Removing a pairing does not delete conversations or files on the computer, or copies already sent to a model provider or another app; manage those at the destination.
Your requests and policy updates
You may contact us about access, correction or deletion of information you supplied to us, or about applicable privacy rights. We can only act on information within our control. We do not sell your information or use it for targeted advertising. We will update this page when our practices change and show the effective date above.