Privacy Policy - Claude Code Notifier

This Privacy Policy explains how Claude Code Notifier handles your data. Claude Code Notifier is made up of the phone apps for iOS and Android, ccn (a command line tool for macOS, Linux and Windows), the optional Mac menu bar app, our relay server, and this website. Together we call them "the Apps". They are provided by TouchTap Ltd ("we", "us", "our"). We want to be clear about what data is collected, how it is used, and who it may be shared with.

summary There are no accounts. When Claude Code finishes or needs you, the computer side (ccn or the Mac app) sends a notification through our relay server to the phones you have paired. A notification can include the project's name and folder path, Claude's message or the question it is asking, and, for a permission prompt, the command or file involved. The server deletes notifications within 48 hours. We do not sell your data or use it for advertising.

01Overview of the Apps

Claude Code Notifier consists of:

iOS / AndroidClaude Code Notifier phone appsReceive notifications from your computers and let you answer Claude Code from your phone. Listed on the App Store as Claude Code Notifier Companion.

macOS / Linux / Windowsccn, the command line toolA small program that Claude Code runs through its hooks. It sends notifications to your phone and waits for your answers. Windows support is in beta.

macOS, optionalClaude Code Notifier for MacA menu bar app that does the same job as ccn on a Mac, and can also show Mac notifications and send webhooks.

cloudRelay serverPasses notifications and your answers between your computers and your phones, and keeps each computer's settings so you can change them from the phone.

02Data We Collect

2.1ccn (Command Line Tool)

Claude Code runs ccn at seven points in a session (session start, each prompt you submit, before each tool use, permission requests, permission notifications, when Claude stops, and session end) and hands it details of that moment: the session ID, the working folder, the tool Claude wants to use and its input, the prompt you typed, Claude's last message, and any question Claude is asking. ccn keeps the following on your computer, in ~/.config/ccn/ (%APPDATA%\ccn\ on Windows):

Data TypeDescriptionPurpose

ConfigurationServer address, this computer's ID, its name, a copy of its settings, whether desktop notifications, automatic updates and pairing suggestions are on (config.toml), and when it last checked for an updateRemember the pairing and your preferences

CredentialsA random token that identifies this computer to our server, in a file only your user account can read (credentials), or in the system keychain if you choose itAuthenticate with the relay server

Session FilesOne small file per Claude Code session: the working folder, your latest prompt (up to 4,000 characters), the latest tool call, terminal identifiers (such as the terminal program and tmux pane), and the last notification sent. Deleted when the session ends, or after 7 days without useBuild notifications and spot repeats

LogErrors and timings, without prompts, commands or messages (ccn.log, kept under 1 MB)Troubleshooting

Claude Code SettingsSeven hook entries added to ~/.claude/settings.json, plus a one-time backup of that fileLet Claude Code run ccn

ccn sends our relay server: when it registers, this computer's random ID, its token, its name (by default the computer's hostname; you can choose another name), its operating system, the ccn version and the features it supports; and, for each notification, the data listed in 2.4. Every request to our server also carries the ccn version and the computer's language (one of the 17 languages the Apps support, taken from the operating system or from CCN_LANG), so that the server can answer in your language. To decide whether to wait for your phone, ccn checks how long the keyboard and mouse have been idle. That check happens on your computer and the result is never sent. ccn pair sends the anonymous setup events described in 2.5; its hooks send no analytics.

ccn's hooks are installed when you install it, before any phone is paired. Until you pair a phone, ccn shows notifications on the computer itself and sends nothing about your sessions to our server; if the computer has already been registered, it asks our server whether a phone has paired each time a Claude Code session starts. After about ten notifications on the computer it may suggest pairing a phone, in a single line in the terminal; ccn config set pair_nudges off turns that off.

Once a day, when a Claude Code session starts, ccn checks for a new version in the background. It asks our server for the number of the newest release, sending only its own version and the computer's language, and no identifier. If there is a newer version and ccn was installed with the install script from this website or with npx, it downloads the release and its checksum file from GitHub, verifies the checksum and replaces its own program file; GitHub sees that download like any other (see 5.6). A copy installed with Homebrew, npm, Scoop or winget is never replaced; ccn only prints the command to run. Turn the check off with ccn config set auto_update off or by setting CCN_NO_AUTO_UPDATE=1. Whether an update succeeded or failed is reported as an anonymous setup event (2.5).

2.2Mac Application (Optional)

The Mac menu bar app collects and stores the following data locally on your Mac:

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 directorySend your answers from the phone to the right terminal

Session EventsNotification timestamps, event types, messages, and user promptsSession history and statistics

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

When paired with a phone, the Mac app sends our relay server its random ID, a token, the Mac's name, and the notification data listed in 2.4.

2.3iOS and Android Apps

The phone apps collect and store:

Data TypeDescriptionPurpose

Device IdentifierA random ID created on first launch. On iOS it is kept in the Keychain; on Android, in the app's encrypted storageIdentify your phone for pairing, notifications and purchases

Push TokenAn Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM) token. The app requests it when it opens, before asking for notification permission, so the server can send silent updates (for example, that pairing has finished) even if you have not allowed notificationsDeliver notifications and updates to your phone

Device DetailsThe device name your phone gives apps (on Android, the model name), model, operating system version, app version, App Store or region country, preferred language, whether notifications are allowed, and your access state (trial, subscribed, lifetime or none)Show your phone by name on your computers, send visible notifications only where they are allowed, and support

Notification HistoryNotifications you have received, including titles, messages, project names and your answers, kept on the phoneShow notification history and allow offline access

Pairings and Computer SettingsThe computers you have paired, their names and kinds, and the settings you change for each oneManage your computers

Pairing CodeA 6-digit code the phone shows so that a computer can pair with itPair a computer running ccn

Subscription StatusWhether you have an active subscription or a lifetime purchase, and how many answers you have sentManage access to the apps

Reminders and CountsReminders the app sets on the phone itself (a trial ending, connecting a computer, or one you ask for when you say you do not use Claude Code yet), and a few counts kept on the phone, such as when you answered requests. None of this is sent to usHelp you finish setup and decide which plan to suggest

Install Link (Android)When you install the Android app from a link that a computer showed, Google Play gives the app a single-use pairing token. The app reads it once, on first launch, and ignores it after 30 minutesConnect your computer without typing a code

Lock-Screen Cards (iOS)If you use lock-screen cards (Live Activities): the token Apple gives the app to start and update them, whether they are on, and whether details are hidden while the phone is lockedShow requests and progress on the lock screen

The phone apps can use the camera to scan the QR code that a computer shows (from ccn pair or the Mac app). The image is processed on the phone and is neither stored nor sent.

2.4Relay Server

Our relay server stores:

Data TypeDescriptionRetention

NotificationsNotification type, title, message, prompt text (which can be Claude's last message, up to 1,500 characters; the start of your prompt, up to 300 characters; a plan; or a question and its options), project name, project folder path, tool name, a summary of the tool's input (such as the shell command or file path, up to 200 characters), session ID, and terminal context (terminal type, session identifiers and working folder)Deleted within 48 hours

Your AnswersWhat you send from the phone (an approval, a choice, or a follow-up instruction for Claude), when, and whether it came from the phone or the computerDeleted with the notification, within 48 hours

Computer RecordsEach computer's random ID and token, name, operating system, kind (ccn or Mac app), version, the features it supports, and when it was registered and last seenDeleted, with the computer's settings and pairings, when the computer has not connected for 60 days

Computer SettingsSettings you choose for a computer, from the phone or with ccn config set: which notifications to send, quiet hours, sound, and how long to wait for the phoneUntil changed, with the computer record

Phone RecordsThe device identifier, push token, platform, and the device details listed in 2.3Deleted, with the phone's pairings, when the phone has not used the app for 60 days and is not paired with a computer that has connected in that time; also deleted when Apple or Google report the push token is no longer valid, for example after the app is deleted

Pairing RecordsWhich phones are paired with which computers (up to three phones per computer), and whether each pairing is active or revokedMarked revoked when you unpair, then deleted 60 days later

Pairing Codes6-digit codes shown by a phone or by the Mac appA code the Mac app shows expires after 5 minutes; a code or QR code that ccn shows, and a code the phone showed, can be used for 24 hours. Cleared when used

Product AnalyticsAnonymous events from the phone apps, and setup events from ccn and the install scripts, described in 2.560 days

Crash and Hang ReportsAnonymous reports of crashes and hangs in the iOS app, described in 2.560 days

FeedbackWhat you send in the feedback form, or when you say what held you back as you leave the purchase sheet: the reason you chose, any words you add (up to 1,000 characters), platform, app version and language, linked to the device identifier60 days

Usage CountsFor each phone and day, how many requests reached it from a paired computer and how many it answeredWithin 60 days

Billing and Trial NoticesOnce your phone has held a store subscription: its push token, platform, language and time zone, so we can tell you if a payment fails, linked to the device identifier. Also which notices a subscription has had (a payment reminder, up to three; an apology after a cancelled trial; a summary of the usage counts) and the numbers a summary quoted. The app also asks our server whether a payment is failingThe push token: 60 days after the app last refreshed it. All of it: when you use Delete my data

Pairing FailuresWhen a pairing code is rejected: the reason, platform, app version, country, how many digits differ from the closest live code, whether it matches an older code, and a salted one-way hash of the device identifier, never the identifier itself60 days

Lock-Screen CardsFor iOS lock-screen cards: the phone's start and update tokens, whether cards are on, and each card's content (project name and a short summary of the request or of what Claude is doing, which can include a command or file name unless the phone hides details while locked). For a computer's working and finished sessions: project name, a short title and summary, and counts of steps, files, approvals and timeCards: a week after they end. Sessions: with the computer's record

Purchase RecordsNotices about your purchase from Apple and Google: product, transaction IDs or purchase token, dates, price, currency, storefront country, and renewal, cancellation and refund status, linked to the device identifierKept as financial records for 6 years from the date of each purchase, renewal or notice, then deleted. They are kept for those 6 years even if the phone's record is deleted

Web LicencesFor a licence bought on our website: the email address you gave Lemon Squeezy, the plan, its status and renewal date, Lemon Squeezy's customer, order and subscription IDs, the website page and campaign tags (such as utm_source) the checkout started from, the last four characters of the key and a one-way hash of it (never the key itself), and which computers hold it (their ID, name, operating system and the dates each was added and removed)Kept as a purchase record while the licence is valid and for 6 years after it ends, then deleted. The email is used only to send your key and replacement links. A computer's name is removed from the licence when the computer's own record is deleted

Licence PurchasesLemon Squeezy's notices about each licence order, renewal and refund: amounts, currency, tax, dates and statusKept as financial records for 6 years from their date, then deleted

Team Plan EnquiriesWhat you type into the team plan form on our website (your name, email address, company, number of seats, billing preference and message), the page and any campaign tags that brought you to it, the page's language, the country your connection comes from, and a one-way hash of your IP address used only to limit repeated sending. Each enquiry is also emailed to us so we can replyUsed only to reply about team plans. Deleted after 12 months, or sooner if you ask

Licence Checkouts and LinksA random ID linking a checkout to the terminal or web page waiting for it, which holds a new key until it is shown once; and the one-way hash of each emailed link for replacing a lost keyA new key is removed when it is first shown, or after 24 hours. Checkouts are deleted after 60 days; replacement links work for 30 minutes and are deleted a day later

Pricing TestsWhich version of a pricing test your install saw when it started a purchase, linked to the device identifierDeleted with the phone's record, or 60 days after the purchase started if the phone was never paired

Refund ConsentWhether you turned on “Help with refund requests” in the iOS app, linked to the device identifierDeleted 60 days after you last changed it, once no purchase record is linked to it

If a phone or computer is not used for 60 days, the server deletes its records and its pairings. To use it again, you will need to pair it again.

The relay server does not store your IP address. Our hosting provider, Cloudflare, processes it to deliver each request and tells us which country a request comes from. We record that country when a pairing code is rejected, to spot misuse, and with analytics events and crash reports (see 2.5), including the setup events from ccn, and delete those records after 60 days.

2.5Analytics

The phone apps send anonymous product events to our own server. Events carry no device identifier, and the server does not store IP addresses with them. Each batch includes only the platform, app version and build, operating system version, device model, country, language, access state, and build type. Events describe how the app is used: for example, that the app was opened, the paywall was viewed or a plan was chosen, the outcome of a purchase, onboarding steps, whether notification permission was granted, which kind of computer you chose to set up (macOS, Linux or Windows), that a pairing code was shown or an install command was copied, that pairing finished (with the kind of computer and its operating system), and that you answered a notification (with the kind of prompt only). Events never contain project names, commands, prompts, or Claude's messages.

The iOS app sends anonymous crash and hang reports to our own server, so we can find and fix crashes. Apple’s MetricKit framework supplies them. A report holds the app version and build, the operating system version, the device model, the country, and technical details of the fault: the error type and signal, and the stack as code module names and offsets. It holds no name, account, device identifier, IP address or notification content, and the server does not store the IP address. Reports are deleted after 60 days. The phone apps use no third-party analytics or crash-reporting service, and the Android app does not send crash reports to our server.

ccn pair and the install scripts on this website send a few anonymous setup events to our own server, so we can see where installing or pairing fails: that an install started, finished or failed (and at which step), that pairing started, finished or failed (with a short reason, such as an expired code), how ccn was installed (install script, Homebrew or npm), the ccn version, and the operating system and processor type. ccn also reports whether an automatic update succeeded or failed, with the version before and after. They carry no identifier, no computer name and nothing from your Claude Code sessions. The server adds the country the request came from and the computer's language, as it does for the phone apps' events, and does not store the IP address. Set CCN_NO_ANALYTICS=1 or DO_NOT_TRACK=1 to turn them off.

This website uses Umami, a privacy-focused analytics service that does not use cookies. It counts page views and clicks on download and install buttons, including which operating system's install command was shown or copied. On the licence page it counts clicks on Buy (with the plan), that a key was looked up or a replacement link asked for, and that a new key was shown; never the key, your email or the checkout's ID.

ccn unlock, ccn activate and ccn deactivate send the same kind of anonymous setup events as ccn pair: that a purchase was started (with the plan) and whether the browser opened, that the computer was licensed (by checkout or by key) or why activation failed, and that a licence was removed. Once a day, a Claude Code session start asks our server whether this computer has a licence; nothing about the session is sent.

03How We Use Your Data

Your data is used only to provide and improve the Apps:

Notification Delivery: To alert you when Claude Code finishes or needs your attention
Remote Response: To pass your answers from the phone back to Claude Code on your computer
Pairing: To connect your computers and phones with a short-lived code
Computer Settings: To let you change a computer's settings from your phone
Session Tracking: To show session history and statistics (Mac app)
Webhook Forwarding: To send notifications to external services you configure, such as Slack or Discord (Mac app)
In-App Purchase Verification: To confirm subscriptions and lifetime purchases (phone apps), and to keep financial records
Product Improvement: To count, in aggregate, how the apps are used and how pricing tests perform
Security: To detect misuse of pairing codes and the relay server
Crash Fixing: To find and fix crashes and hangs in the iOS app
Reminders and Notices: To remind you to finish setup, to tell you if a payment fails or a trial is cancelled, and to show lock-screen cards
Updates: To tell ccn and the Mac app whether a newer version exists
Feedback: To read what you tell us and improve the apps

We do not use your data for:

Advertising or marketing purposes Selling or renting to third parties Profiling individual users Training machine learning models

04Data Storage and Security

4.1Local Storage (ccn)

Files: Kept in ~/.config/ccn/ (%APPDATA%\ccn\ on Windows). On macOS and Linux the configuration and credentials files can be read only by your user account
Credentials: Stored in a private file by default, or in the macOS Keychain, Windows Credential Manager or Linux Secret Service if you set credential_store to keychain
Data Retention: Session files are deleted when a session ends, or after 7 days without use. ccn uninstall deletes everything ccn keeps

4.2Local Storage (Mac App)

Session Data: Stored in a local 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.3Local Storage (iOS/Android)

Notification History: Stored in the app's private storage on your phone
Device Identifier: Stored in the iOS Keychain, or in encrypted storage on Android. iOS can keep Keychain items after an app is deleted, so reinstalling may reuse the same identifier
Preferences: Stored in UserDefaults (iOS) or DataStore (Android)
Data Retention: Notification history stays until you clear it or delete the app

4.4Cloud Storage

Infrastructure: The relay server runs on Cloudflare Workers, with data stored in Cloudflare D1 (SQLite) and Durable Objects
Encryption: All communication with the server uses TLS encryption (HTTPS/WSS)
Geographic Location: Data may be processed in Cloudflare data centres worldwide
Notification Expiry: A cleanup job runs every day and deletes notifications, with your answers to them, that are more than 24 hours old, so none is kept longer than 48 hours. While a computer is waiting for your answer, a copy of the answer is also held for up to 1 hour
Inactive Records: The same daily job deletes phones and computers that have not been used for 60 days, with their pairings and settings, and revoked pairings 60 days after they were revoked. Purchase records are deleted 6 years after their date

05Third-Party Services

The Apps use the following third-party services:

5.1Apple App Store (In-App Purchases)

Used by: iOS app, relay server
Purpose: Process subscriptions and one-time purchases, and send us notices about them
Data Shared with Apple: The purchase, with the device identifier as its account token. If you turn on “Help with refund requests” in the app and then ask Apple for a refund, we also tell Apple that the purchase was delivered, whether you set up the app and used it (a computer paired with your phone since the purchase), and whether we think the refund should be granted. We do this only with your consent, which you can withdraw in Settings at any time, and keep a copy of each answer for 60 days
Data Received: Purchase verification, subscription status, dates, price, currency and storefront country
Note: Payment information is handled entirely by Apple. We do not receive or store your payment details.

5.2Google Play (In-App Purchases)

Used by: Android app, relay server
Purpose: Process subscriptions and one-time purchases, and send us notices about them
Data Shared with Google: The purchase, with the device identifier as its obfuscated account ID. For a link that a computer showed, the single-use pairing token passes through Google Play as the install referrer
Data Received: Purchase verification, purchase tokens, subscription status and dates
Note: Payment information is handled entirely by Google. We do not receive or store your payment details.

5.3Apple Push Notification Service (APNs)

Used by: iOS app, relay server
Purpose: Deliver notifications and silent updates to iPhones and iPads
Data Shared with Apple: Push token; notification title and text (up to 200 characters); project name; prompt text (up to 500 characters); tool name and input summary; answer options; notification IDs. Project folder paths are not sent. For lock-screen cards: the card’s content (project name and a short summary)

5.4Firebase (Google)

Used by: Android app, relay server
Purpose: Deliver notifications and silent updates to Android phones with Firebase Cloud Messaging (FCM)
Data Shared with Google: Push token and the same notification data as for APNs; Firebase installation ID

Privacy and Security ↗

5.5Cloudflare (Cloud Infrastructure)

Used by: Relay server, this website
Purpose: Host the relay server and this website, and store the server data described in 2.4
Data Processed: All data sent to the relay server, and standard request data such as IP addresses. Cloudflare Email Service also sends the licence emails: your key, and links to replace it

5.6GitHub, Homebrew and npm (Downloads)

Used by: ccn and the Mac app
Purpose: Release files are hosted on GitHub. The install scripts on this website download ccn from GitHub and check its checksum, and ccn downloads its own updates from GitHub in the same way (see 2.1). You can also install with Homebrew or npm
Data Shared: Standard request data (IP address, user agent) with the service you download from. Homebrew and npm have their own analytics and policies

GitHub Privacy Statement ↗

5.7Sparkle (Mac App Updates)

Used by: Mac app
Purpose: Check for and deliver Mac app updates
Data Shared: Standard HTTP request data (IP address, user agent) when the app reads this website's update feed and downloads from GitHub
Note: Sparkle is open-source software built into the app, not a service; it sends nothing to its developers

More Information ↗

5.8Umami (Website Analytics)

Used by: This website
Purpose: Count page views and button clicks, without cookies
Data Processed: Page address, referrer, browser, device type and country

5.9Optional Webhook Services

Used by: Mac app (set up by you)
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. ccn does not send webhooks.

5.10Lemon Squeezy (Licence Payments)

Used by: Licences bought on this website or with ccn unlock
Purpose: Sell licences as merchant of record: take the payment, charge tax, send receipts and handle renewals, cancellations and refunds
Data Shared with Lemon Squeezy: What you enter at checkout goes to Lemon Squeezy, not to us: your name, email, billing address and payment details. We send it only a random checkout ID, so the purchase can find the page or terminal waiting for it
Data Received: Your email address and name (we keep only the email), the plan, order, subscription and refund status, amounts, currency and tax. We never receive your card details

06Data Sharing

We share your data only in the following circumstances:

Between Your Devices: Notifications pass between your computers and the phones paired with them through our relay server. A paired phone can see each computer's name, kind, operating system and settings
With Push Notification Providers: Apple (APNs) and Google (FCM) receive notification content to deliver it to your phone
With App Stores for Purchases: Apple and Google process subscriptions and one-time purchases; they receive transaction data, and we do not receive your payment information
With Lemon Squeezy for Licences: Lemon Squeezy sells licences bought on our website; you give your payment details to it directly, and we receive the order and your email address
With Our Service Providers: Cloudflare hosts the relay server and this website, and Umami counts website visits
With Your Configured Webhooks: If you set up webhooks in the Mac app, notification data is sent to those endpoints
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: Notification history is shown in the phone apps; ccn config show shows a computer's settings; session history is shown in the Mac app
Unpair: Revoke a pairing from the phone, with ccn devices, or in the Mac app. The phone stops receiving that computer's notifications straight away. The server marks the pairing as revoked, deletes its notifications on the usual schedule, within 48 hours, and deletes the pairing 60 days later
Remove ccn: ccn uninstall removes its hooks from Claude Code's settings, revokes every pairing, and deletes its credentials and local files
Delete Local Data: Deleting a phone app or the Mac app removes the data it stored on that device (except, on iOS, the device identifier in the Keychain; see 4.3)
Delete Server Data: Do it yourself whenever you like. In a phone app, open Settings and choose Delete my data; on a computer, run ccn forget. Each removes that phone or computer, its pairings and its queued notifications from our server straight away. Anything you leave is deleted automatically once it has not been used for 60 days. This also removes its feedback, usage counts, billing-notice records, lock-screen cards and pairing-failure records
Erase a Licence: On claudecodenotifier.com/licence, enter your key and choose Erase my licence. This ends the licence for good, stops an annual plan renewing, and removes your email address, the key and the computer names from our records. If you have lost the key, get a replacement through the link we email you first. Purchase records (amounts, tax, dates and Lemon Squeezy order IDs) are kept for 6 years because the law requires it, and Lemon Squeezy keeps its own records as merchant of record, so ask it to erase what it holds
Data Retention Settings: Choose how long the Mac app keeps session history in its settings

7.2Opt-Out Options

Choose What Is Sent: For each computer, turn off notifications for finished turns, permission requests or questions, or set quiet hours, from the phone or with ccn config set
Notification Permission: If you turn off notifications for the app on your phone, the server records that and stops sending it visible notifications. Silent updates, such as pairing confirmation, still arrive
Stop Using the Relay: Unpair every phone to stop sending data to the relay server. The Mac app can still show Mac notifications without it
Webhooks: Remove webhook configurations in the Mac app to stop forwarding data to external services
Auto-Updates: Turn off automatic update checks in the Mac app's settings, or for ccn with ccn config set auto_update off or CCN_NO_AUTO_UPDATE=1
Pairing Suggestions: ccn config set pair_nudges off stops ccn suggesting that you pair a phone

7.3Your Legal Rights

TouchTap Ltd is the controller of the personal data described in this policy. Depending on where you live, including in the UK and the European Union, you may have the right to access, correct or delete your personal data, to object to or restrict how we use it, and to receive a copy of it. You can use most of these rights yourself, without asking us, as described in 7.1. To use them another way, email [email protected]. Because there are no accounts, we may ask for details, such as the names of your computers and phones, to find your records. You also have the right to complain to a data protection authority; in the UK this is the Information Commissioner's Office (ico.org.uk).

7.4Data Portability

The Apps do not currently offer a data export feature. Data stored on your devices can be seen in the Apps, and ccn's files are plain text.

08Information About Project Paths and Commands

! important Notifications from ccn and the Mac app 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 shell commands being run)
Claude's last message, plans and questions, and the start of your prompt
Your computer's name, which is its hostname unless you choose another

This information is sent to our relay server, and a shorter version to Apple or Google to deliver the notification. If you work with sensitive or confidential projects, consider whether phone notifications are appropriate, and which kinds of notification to turn on for each computer.

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 relay server runs on Cloudflare's global network, and Apple and Google deliver notifications from their own infrastructure. Your data may be processed in data centres outside your country of residence. Where the law requires safeguards for these transfers, we rely on the ones those providers put in place, such as the EU–US Data Privacy Framework and standard contractual clauses.

11Changes to This Privacy Policy

We may update this Privacy Policy as the Apps evolve. Material changes will be communicated through the Apps or on this page. The "Last updated" date at the top indicates when the policy was last revised. Translations are provided for convenience; if a translation differs from the English version, the English version prevails.

12Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or your data, please contact us:

TouchTap Ltd [email protected]