Codex Watch privacy policy
Effective November 16, 2026
Effective November 16, 2026
Codex Watch is made by Blue Matters Studio. It connects your Apple Watch to Codex running on your Mac. You do not need a separate Codex Watch or Cloudflare account. Your Codex account remains with OpenAI.
Your conversations and recordings
The app exchanges conversation text, project and chat names, visible work activity, question responses, queued messages and image previews between your Watch and Mac. Your Mac stores paired-device records, delivery receipts and cached conversations. Your Watch stores connection credentials in Keychain and keeps drafts, an outbox and recent conversations locally.
Bluetooth discovers nearby devices and verifies pairing. It is not used to determine your location. Microphone access is used when you record a message. Audio is saved on the Watch and sent to your Mac for transcription using Apple’s SpeechAnalyzer. Apple may download a language model. Codex Watch does not send raw microphone audio to an OpenAI transcription API.
You review the transcript before sending it to Codex. Submitted messages are then processed by Codex under your existing account terms and data settings. See OpenAI’s privacy policy. When available, pull-request status uses the Mac’s existing GitHub CLI authentication; the Watch does not request your GitHub password.
The connection service
New relay pairings use end-to-end encryption between your Watch and Mac. Conversation content, audio, images and the bridge authentication token are encrypted before reaching the Blue Matters relay hosted on Cloudflare. The relay forwards this ciphertext and does not persist chats, recordings or content-encryption keys. The keys remain on your paired devices.
The relay stores persistent, randomly generated Mac/device routing identifiers, channel authentication-token hashes, temporary-channel expiration times and connection-generation identifiers. These records are linked to the paired installation or device and are used to connect, authenticate and revoke devices. They are not used for advertising or tracking. The relay receives a channel access token over HTTPS to authenticate a request; its stored authorization record contains a hash of that token.
Cloudflare processes connection IP addresses, routing information, traffic sizes/timing and service diagnostics to deliver and protect the service. Encryption does not conceal that connection information. Cloudflare’s operational records are subject to its privacy policy; this policy does not promise a deletion deadline for those records. The relay’s application logging is disabled.
An existing direct HTTPS pairing from an earlier version remains a different connection mode. Its content is protected by HTTPS, but it does not have the new relay’s end-to-end encryption; a provider terminating HTTPS can process the traffic. Pair your Watch again with the current Mac companion to use the encrypted relay.
The first release does not provide background push notifications. The Watch refreshes while open, and watchOS controls complication refresh timing. Codex Watch has no advertising or behavioral analytics service and does not sell conversation or audio data or use it for targeted advertising.
Retention and deletion
Persistent relay authorization records have no automatic deletion period. Removing a paired device on your Mac removes its local authorization and updates the relay when the Mac is connected. If it is offline, the relay update waits until reconnection. The Mac routing identity and connection-generation record remain. Temporary pairing access expires after five minutes or less; expired authorization metadata can remain until the next update.
Recorded-audio uploads use temporary files on your Mac. They are removed after successful transfer into the Mac’s transcription storage, cancellation, device revocation or an orderly shutdown. Idle staging uploads become eligible for cleanup after 15 minutes; files left by a crash are cleaned on the next companion startup. This cleanup does not delete the saved recording or transcription.
Local conversation caches, delivery records and saved recordings remain in app storage. Saved audio and Mac transcription jobs have no automatic retention expiry. Delete all draft clears the active composer and offers Undo for 60 seconds; it does not erase all underlying archived audio, discarded text or Mac copies. Sending a draft archives its recording. Canceling an active recording removes that Watch recording, but cannot promise to remove audio already streamed to the Mac.
Revoking a device stops its future access; it does not erase existing caches, recordings or Codex history. Removing the Watch app removes its application container, while Keychain credentials and backups may have a separate lifecycle. To clear Mac companion data, quit the companion and remove its application-support folder after saving anything you need. See support for the storage paths. Codex history is separate and must be managed through Codex/OpenAI. Provider records and device backups follow the relevant provider and device settings.
Your controls and contact
You can stop remote access, remove a paired Watch, and change microphone or Bluetooth permissions in system settings. Stopping access does not erase stored data or cancel work already delivered to Codex. The relay does not queue actions while your Mac is offline; a failed outgoing message stays on your Watch for review and retry.
Contact support@bluematters.studio for support or privacy requests. If you email us, we receive your address, message and any attachments you choose to send so we can respond. Blue Matters Studio cannot directly erase recordings held only on your devices, but can help you locate them. Do not send authentication tokens, pairing codes or encryption keys.
We will update this policy and the App Store disclosures when data handling materially changes.