Prompts, code, transcripts, and tool details sent between a paired client and daemon are end-to-end encrypted. The relay processes routing and connection metadata. App telemetry and push services are separate third-party data paths.
Session content
Claude Code or Codex and your project files run on your computer. When CC Pocket sends session content between the daemon and a paired client, the content is encrypted at the endpoints using the protocol described in the security model. The hosted relay forwards encrypted frames and is not designed to receive plaintext prompts, code, transcripts, private keys, or session keys.
Relay data and metadata
To authenticate devices and route traffic, the relay stores an account identifier derived from a daemon public key, daemon and device public keys, hashes of credentials and pairing tickets, timestamps, and revocation state. It can also observe source IP addresses, online timing, ciphertext size and timing, byte counts, and the account-to-device routing relationship. Operational logs include connection lifecycle, authentication results, and rate-limit events.
Data stored on your devices
The client and daemon store pairing credentials, public and private key material, preferences, and local session references needed to operate the product. Project content and coding-agent credentials remain under the control of the computer that runs the agent. Unpair or revoke a device when it is lost or no longer trusted.
Analytics and crash reporting
The distributed mobile apps integrate Firebase Analytics and Crashlytics. The app code emits enumerated usage and diagnostic events such as app launch, connection state, session opened, prompt sent, and approval decision. It is designed not to include prompt text, directory paths, tool inputs, account identifiers, code, or transcript content. Crash reports can include technical diagnostic information. These requests go directly to Google services and do not pass through the CC Pocket relay. Desktop analytics is enabled only when a build is configured with the relevant GA4 credentials.
Push notifications
On supported platforms, APNs or Firebase Cloud Messaging may process a device push token and notification-delivery metadata. Push payloads are designed to avoid prompt or code content. Opening the app retrieves session details through the encrypted CC Pocket channel.
Website requests
This static website is hosted by GitHub Pages and loads font files from Google Fonts. Its homepage also loads a QR-code utility from jsDelivr. Those providers receive ordinary web-request information such as IP address, browser headers, and requested resource. The site itself does not provide a CC Pocket account or advertising profile.
Optional AI customer support
If you message an official CC Pocket support bot, the message text and ordinary channel metadata are processed by the selected messaging provider, the project-operated OpenClaw server, and the model provider configured for that bot. The support server keeps conversation records under its session-maintenance policy. It may store a concise, paraphrased, code-evidence-backed answer as a private knowledge candidate; a candidate becomes part of the public manual only after separate model review and maintainer approval. Do not send API keys, access tokens, private source code, private keys, full configuration files, or complete private logs. The support bot is designed to reject requests for credentials and to inspect only the public CC Pocket repository.
Self-hosting
If you build or self-host CC Pocket components, the operator of that deployment determines the relevant logging, retention, analytics configuration, and infrastructure access. Review and modify the source and deployment files to match your requirements.
Changes and questions
This notice may change as the product changes. The effective date above identifies the current version. For implementation questions, open a GitHub issue. Report security vulnerabilities privately through GitHub Security Advisories.