This Privacy Policy explains how Claude Code Notifier (the macOS application) and Claude Code Notifier Companion (the iOS and Android companion applications), collectively referred to as "the Apps", handle your data. We are committed to transparency about what data is collected, how it is used, and who it may be shared with.
summary
Claude Code Notifier processes information about your Claude Code sessions to deliver notifications. When you enable mobile notifications, session data is transmitted through our cloud relay service to your paired mobile device. We do not sell your data or use it for advertising purposes.
01Overview of the Apps
Claude Code Notifier is a notification system consisting of:
macOSClaude Code NotifierA menu bar application that monitors Claude Code sessions and delivers system notifications when Claude is waiting for input or requires permission approval.
iOS/AndroidClaude Code Notifier CompanionMobile companion apps that receive notifications from your Mac and allow you to respond remotely.
02Data We Collect
2.1macOS Application
The macOS application collects and stores the following data locally on your device:
Data TypeDescriptionPurpose
Session RecordsClaude Code session IDs, start/end times, duration, and session statusTrack session history and statistics
Project InformationProject names and file system pathsIdentify which project a notification relates to
Terminal ContextTerminal application name, session identifiers, process IDs, working directoryEnable future remote response capability
Session EventsNotification timestamps, event types, messages, and user promptsSession history and analytics
Tool ContextTool names and summarised tool inputs when Claude requests permissionProvide context in permission notifications
User PreferencesNotification settings, quiet hours, reminder intervals, terminal app preferencesCustomise application behaviour
Webhook ConfigurationsURLs, authentication tokens, and payload templates for optional webhook integrationsForward notifications to external services
2.2iOS and Android Companion Applications
The companion applications collect and store:
Data TypeDescriptionPurpose
Device IdentifierA randomly generated UUID, created on first launchIdentify your device for pairing and notifications
Push TokenApple Push Notification Service (APNs) token or Firebase Cloud Messaging (FCM) tokenDeliver push notifications to your device
Notification CacheHistory of received notifications including titles, messages, project names, and responsesDisplay notification history and allow offline access
Pairing InformationList of paired Mac computers and pairing statusManage device pairings
Subscription StatusWhether you have an active subscription or lifetime purchase, and response usage countManage mobile response quota and entitlements
2.3Cloud Relay Service
When mobile notifications are enabled, our cloud relay service processes:
Data TypeDescriptionRetention
Notification PayloadsNotification type, title, message, prompt text, project name, project path, tool context24 hours maximum
Session IdentifiersSession IDs linking notifications to Claude Code sessions24 hours maximum
Terminal ContextTerminal application type and session identifiers24 hours maximum
Device RecordsDevice IDs, push tokens, platform type, device namesUntil pairing revoked
Pairing RecordsAssociations between Mac clients and mobile devicesUntil pairing revoked
User ResponsesText responses sent from mobile devices to Claude Code24 hours maximum
03How We Use Your Data
Your data is used exclusively to provide the functionality of the Apps:
- Notification Delivery: To alert you when Claude Code requires attention
- Remote Response: To relay your responses from mobile devices back to Claude Code on your Mac
- Session Tracking: To display session history and usage statistics
- Webhook Forwarding: To send notifications to your configured external services (Slack, Discord, or custom endpoints)
- License Verification: To validate your free license key (macOS app)
- In-App Purchase Verification: To validate subscription and lifetime purchases (companion apps)
We do not use your data for:
Advertising or marketing purposes
Selling or renting to third parties
Profiling or behavioural analysis
Training machine learning models
04Data Storage and Security
4.1Local Storage (macOS)
- Session Data: Stored using Apple's SwiftData framework in an encrypted database on your Mac
- Preferences: Stored in UserDefaults (standard macOS preferences storage)
- Cloud Credentials: Stored securely in the macOS Keychain
- Data Retention: Session history is automatically deleted after a configurable period (default: 30 days)
4.2Local Storage (iOS/Android)
- Notification Cache: Stored locally on your device in the app's private storage
- Preferences: Stored in UserDefaults (iOS) or DataStore (Android)
- Data Retention: Notification cache persists until you manually clear it or uninstall the app
4.3Cloud Storage
- Infrastructure: Our cloud relay service runs on Cloudflare Workers with data stored in Cloudflare D1 (SQLite)
- Encryption: All communications use TLS encryption (HTTPS/WSS)
- Geographic Location: Data may be processed in Cloudflare data centres worldwide
- Notification Expiry: Pending notifications are automatically deleted after 24 hours
05Third-Party Services
The Apps integrate with the following third-party services:
5.1Gumroad (License Verification)
- Used by
- macOS application
- Purpose
- Verify free license keys for the macOS application
- Data Shared
- License key (entered by you), Product identifier
- Data Received
- License validity, usage count
5.2Sparkle (Auto-Updates)
- Used by
- macOS application
- Purpose
- Check for and deliver application updates
- Data Shared
- Standard HTTP request headers (IP address, user agent)
- Note
- Sparkle retrieves update information from our servers; no personal data is collected by the Sparkle framework
5.3Apple App Store (In-App Purchases)
- Used by
- iOS companion application
- Purpose
- Process subscription and one-time purchase transactions for unlimited mobile responses
- Data Shared with Apple
- Transaction identifiers, purchase receipts
- Data Received
- Purchase verification, subscription status, expiry dates
- Note
- Payment information is handled entirely by Apple. We do not receive or store your payment details.
5.4Google Play (In-App Purchases)
- Used by
- Android companion application
- Purpose
- Process subscription and one-time purchase transactions for unlimited mobile responses
- Data Shared with Google
- Transaction identifiers, purchase tokens
- Data Received
- Purchase verification, subscription status, expiry dates
- Note
- Payment information is handled entirely by Google. We do not receive or store your payment details.
5.5Apple Push Notification Service (APNs)
- Used by
- iOS companion application, Cloud relay service
- Purpose
- Deliver push notifications to iOS devices
- Data Shared with Apple
- Device push token, Notification content (title, message, project name), Notification metadata
5.6Firebase Cloud Messaging (FCM)
- Used by
- Android companion application, Cloud relay service
- Purpose
- Deliver push notifications to Android devices
- Data Shared with Google
- Device push token, Notification content (title, message, project name), Notification metadata
5.7Cloudflare (Cloud Infrastructure)
- Used by
- Cloud relay service
- Purpose
- Host the cloud relay service and store pairing/notification data
- Data Processed
- All data transmitted through the cloud relay service
5.8Optional Webhook Services
- Used by
- macOS application (user-configured)
- Purpose
- Forward notifications to external services
- Supported Services
- Slack, Discord, or any custom HTTP endpoint
- Data Shared
- Notification content including project names, paths, messages, and timestamps
- Note
- Webhooks are entirely optional and configured by you. Data is only sent to services you explicitly configure.
06Data Sharing
We share your data only in the following circumstances:
- With Your Paired Devices: Notification data is shared between your Mac and paired mobile devices via our cloud relay service
- With Push Notification Providers: Apple (APNs) and Google (FCM) receive notification content to deliver push notifications
- With App Stores for Purchases: Apple App Store and Google Play process subscription and one-time purchase transactions; they receive transaction data but we do not receive your payment information
- With Your Configured Webhooks: If you configure webhook integrations, notification data is sent to those endpoints
- For License Verification: Free license keys are verified with Gumroad's API (macOS app)
- For Purchase Verification: Subscription and lifetime purchases are verified with Apple App Store and Google Play (companion apps)
- Legal Requirements: We may disclose data if required by law or to protect our legal rights
We do not sell, rent, or trade your personal data to third parties.
07Your Rights and Choices
7.1Data Access and Deletion
- View Your Data: Session history is viewable within the macOS application
- Delete Local Data: Uninstalling the Apps removes all locally stored data
- Delete Cloud Data: Revoking a device pairing removes associated data from our cloud service
- Data Retention Settings: Configure how long session history is retained in the macOS app settings
7.2Opt-Out Options
- Mobile Notifications: Disable mobile notifications to prevent data transmission to the cloud relay service
- Webhooks: Remove webhook configurations to stop data forwarding to external services
- Auto-Updates: Disable automatic update checks in the macOS app settings
7.3Data Portability
Currently, the Apps do not offer a data export feature. All locally stored data can be accessed through the application interface.
08Information About Project Paths and Commands
! important
When Claude Code Notifier sends notifications, it may include:
- Full file system paths to your projects (e.g.,
/Users/yourname/Projects/secret-project) - Tool names and summarised inputs (e.g., file paths being read or commands being executed)
- Working directory paths
This information is transmitted to our cloud relay service and to push notification providers (Apple/Google) when mobile notifications are enabled. If you work with sensitive or confidential projects, consider whether mobile notifications are appropriate for your use case.
09Children's Privacy
The Apps are not directed at children under 13 years of age. We do not knowingly collect personal information from children. If you believe we have inadvertently collected data from a child, please contact us to have it removed.
10International Data Transfers
Our cloud relay service operates on Cloudflare's global infrastructure. Your data may be processed in data centres located outside your country of residence. By using the mobile notification features, you consent to this transfer of data.
11Changes to This Privacy Policy
We may update this Privacy Policy as the Apps evolve. Material changes will be communicated through the application or on this page. The "Last updated" date at the top indicates when the policy was last revised.
12Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or your data, please contact us:
TouchTap Ltd
[email protected]