Privacy, by feature.
Last updated: August 17, 2026. This policy explains what Pairling processes, stores, transmits, deletes, and retains.
Scope
Pairling connects an iPhone to coding sessions on a selected Mac. Most product data stays on the iPhone or that Mac.
Pairling has no user account system, advertising tracker, or Pairling analytics service in the reviewed source.
Optional network services process limited data when you enable the related feature. The sections below identify those services.
Pairing and Mac profiles
- Process
- Device identifiers, Mac names, routes, scopes, tokens, signed challenges, App Attest data, and pairing proof.
- Store
- The iPhone stores credentials in Keychain. The Mac stores token hashes, device records, and a short-lived invitation record.
- Transmit
- The QR code transfers a short-lived secret to the iPhone. Modern pairing does not send that secret in its network claim.
- Delete
- A successful claim removes the invitation record. Forget Mac always removes iPhone secrets. Mac revocation succeeds only when the revoke request reaches the Mac.
Modern pairing combines a pre-shared secret with P-256 ECDH. It uses HKDF-SHA256, HMAC-SHA256 key confirmation, and AES-256-GCM token encryption.
The default runtime rejects legacy plaintext claims. An explicit Mac break-glass setting can enable that path.
Public Funnel pairing requires Apple App Attest. Local network pairing can use App Attest when the Mac requires it.
Coding sessions
- Process
- Session identifiers, provider names, project paths, transcript text, terminal output, approvals, input requests, and command results.
- Store
- The iPhone stores a recent session snapshot. Coding CLIs store their session and transcript files on the Mac.
- Transmit
- The Mac sends session data to the iPhone. The iPhone sends text and control actions to the exact Mac session.
- Delete
- Clear history clears the iPhone snapshot and hides rows. It does not delete provider transcript files on the Mac.
Search and synthesis
- Process
- Search terms, transcript blocks, project names, short snippets, dates, provider names, and local embedding vectors.
- Store
- The iPhone stores the semantic index and generated synthesis files in Application Support.
- Transmit
- Exact search goes to the Mac. Synthesis can use Apple Intelligence or the coding provider for the selected session.
- Delete
- Clear index and Clear synthesis remove the matching iPhone files. Original Mac transcripts remain.
Voice capture and transcription
- Process
- Recorded or imported audio, transcripts, word timings, extracted key points, and prompt drafts.
- Store
- The iPhone stores each Compose item in Application Support with its audio and metadata. Audio uses file protection that remains available while an already-open file is in use.
- Transmit
- Recording transcription and word timing run on the iPhone. Short dictation can send audio to Apple when on-device recognition is unavailable. A user-requested Mac sync sends the saved audio and its metadata through PairDrop and Pairling Connect.
- Delete
- Deleting a Compose item removes its iPhone item directory. A copy already synced to the Mac remains in PairDrop until its Mac data is removed separately.
Apple explains the Speech framework boundary in its speech recognition documentation.
Prompt Helper and model tools
- Process
- Draft text, posture instructions, selected context, transcript snippets, and text requested by a model-assisted feature.
- Store
- The iPhone stores the last posture choice. The Mac stores user posture files and optional personal context.
- Transmit
- Prompt Helper uses Apple Foundation Models on the iPhone. Other assists can use the selected Mac coding provider as a fallback.
- Delete
- Delete a posture to remove its Mac file. Provider retention applies after a fallback sends text to that provider.
Attachments and handoffs
- Process
- Selected photo, video, or file content, file metadata, destination paths, and opened OneStream handoff text.
- Store
- The Mac stores attachments under
~/Pairling/uploads. Handoff JSON can remain under~/.claude/companion/handoffs. - Transmit
- The iPhone sends attachment bytes to the Mac. The selected coding CLI can read the inserted Mac path.
- Delete
- Pairling has no automatic cleanup for regular attachments or handoff files. Remove those files on the Mac.
The iOS Share Extension copies accepted text, links, images, videos, and files into a protected app-group inbox. Pairling transfers queued items to PairDrop in the background or the next time the app enters the foreground. The extension does not directly start or modify a coding session.
PairDrop
- Process
- File content, names, MIME types, sizes, hashes, tags, session hints, source device data, and upload state.
- Store
- The Mac stores PairDrop under
~/PairDrop. The iPhone stores resumable upload state and a bounded preview cache. - Transmit
- PairDrop sends file bytes through Pairling Connect. A session receives the exact Mac path only after you attach the file.
- Delete
- Delete hides the item and records a deletion time. It does not erase the object bytes from the Mac.
Partial upload cleanup removes old partial files and expired upload sessions. It does not remove completed PairDrop objects.
Orchestrations
- Process
- Objectives, project paths, providers, modes, worker roles, limits, prompts, run events, output, errors, and result files.
- Store
- The Mac stores run files under
~/.claude/companion/orchestrations. Coding providers can also store their native transcripts. - Transmit
- Pairling sends each role prompt to its selected coding CLI. That provider controls its model connection and retention.
- Delete
- Stop ends active run processes. It does not delete run files, handoffs, or provider transcripts.
The selected permission profile is part of the role instructions. It is not proof of an operating-system sandbox.
Notifications and Live Activities
- Process
- APNs tokens, Live Activity tokens, session state, project basename, provider, progress, result, risk, and required action.
- Store
- The iPhone stores the APNs token in Keychain. The Mac stores registration, secret, event, outbox, and delivery records.
- Transmit
- The Mac or optional relay sends a token and bounded payload to APNs. APNs delivers the update to the iPhone.
- Delete
- Disable notifications stops future delivery work. It does not erase all Mac or relay registration records.
Push events exclude raw prompts, transcripts, command output, credentials, and full file paths.
Apple explains device token delivery in its APNs documentation.
Pairling Connect
- Process
- Tailnet node identity, public keys, IP addresses, route health, connection metadata, request paths, and encrypted Pairling traffic.
- Store
- The iPhone and Mac store embedded tailnet state in their Pairling application data.
- Transmit
- The default Tailscale control server receives required device and network metadata. Pairling content uses the encrypted data path.
- Delete
- Remove the embedded node to stop that route. Tailscale account controls apply to metadata held by Tailscale.
Tailscale states that it cannot read the end-to-end encrypted traffic content. Its privacy policy lists the metadata that it processes.
A DERP server can relay encrypted packets when a direct path fails. Tailscale states that the DERP server cannot decrypt those packets.
You can configure another compatible control server. That server applies its own privacy and retention terms.
Other connection routes
- Process
- Local network addresses, SSH host keys, route state, request paths, and encrypted session traffic.
- Store
- The iPhone profile stores route settings. The Mac gateway logs method, path, status, and result.
- Transmit
- Local and SSH routes send Pairling traffic to the selected Mac. The optional Funnel route handles bootstrap only.
- Delete
- Remove a route to stop its later use. Route removal does not delete coding session files.
The gateway does not log request bodies, prompts, transcripts, authorization values, proof values, or provider keys.
Coding CLI configuration
- Process
- Provider state, slash command metadata, permissions, effort, hooks, memory files, and MCP server status.
- Store
- The Mac stores provider visibility. Permission and hook changes update
~/.claude/settings.json. - Transmit
- The iPhone sends picker requests and approved changes to the Mac. MCP restart requests run through the Claude CLI.
- Delete
- Memory delete removes the selected file and index entry. Catalog browsing does not delete command, skill, or plugin files.
Phone Tools
- Process
- Bounded text for a second opinion, vibe check, preference check, or local corpus recall.
- Store
- The Mac holds requests and results in memory. The iPhone stores the enabled setting and port.
- Transmit
- Apple Intelligence can process text on the iPhone. A fallback can send text to the selected Mac coding provider.
- Delete
- Disable Phone Tools to stop new requests. Provider retention applies when a request uses the provider fallback.
Siri, Shortcuts, and Apple Watch
- Process
- Shortcut text, selected sessions, requested actions, Mac state, session counts, top session data, and deep links.
- Store
- The iPhone stores Shortcut settings. The Watch stores its last Pairling snapshot in UserDefaults.
- Transmit
- Apple system services can process Shortcut input. WatchConnectivity sends a bounded snapshot between the iPhone and Watch.
- Delete
- Disable direct send to stop that action. Pairling has no separate control for the Watch snapshot cache.
Optional Pairling relay
- Process
- Attested device identity, token hashes, raw push tokens, pairing claims, bounded events, deliveries, and revocation state.
- Store
- The relay stores public state and a restricted secret file. The secret file contains raw APNs and Live Activity tokens.
- Transmit
- The relay verifies App Attest claims and sends bounded notifications through APNs.
- Delete
- Revocation blocks later access. It does not erase all token, event, delivery, or secret records.
The optional Pairling relay is not the normal data path for coding session content.
This website and support email
- Process
- A site request includes normal web request metadata. Public pages send an aggregate page-view token and allowlisted action tokens. A support email includes information that you choose to send.
- Store
- The site sets no cookies or persistent identifiers. Cloudflare Analytics Engine stores page, action, source, and target tokens. Pairling does not store raw IPs, user agents, referrers, or query strings in that dataset.
- Transmit
- Aggregate events use a same-origin endpoint. No event goes to a third-party analytics service. Email passes through your email provider and the Pairling mailbox provider.
- Delete
- Cloudflare applies its service retention terms to hosting and aggregate analytics data. You can ask Pairling to delete a support message where applicable.
Cloudflare describes its handling of request information in the Cloudflare Privacy Policy.
The endpoint suppresses writes when Global Privacy Control or Do Not Track is enabled. Pairling does not collect events on /pair.
Tracking and the iOS privacy manifest
The reviewed app has no advertising tracker or Pairling analytics SDK. Its privacy manifest declares no tracking.
The manifest declares a device identifier for app functionality. It marks that identifier as not linked to you and not used for tracking.
The manifest also declares UserDefaults access for app functionality.
Data removal summary
Use Forget Mac before uninstalling Pairling when you want to remove the saved iPhone pairing credentials.
Remove provider transcripts through the matching coding CLI. Remove uploads, handoffs, and orchestration files directly on the Mac.
PairDrop Delete does not erase object bytes. Notification disable and device revocation do not erase all registration records.
Email support@pairling.dev when you need help locating Pairling data.
Contact and policy changes
For a privacy question, email support@pairling.dev.
Pairling will update the date and this page when product data handling changes.