Last updated: May 25, 2026
Reach ("the App") — comprising Reach Remote and Reach Host — is developed by Minjae Cho ("we", "us"). This policy explains how the App handles your data.
Reach has no backend account system, no telemetry, and no analytics. We do not run any backend account system, analytics service, advertising system, or tracking service. Reach-operated rendezvous infrastructure may process temporary connection metadata, such as attempt identifiers and network endpoints, only to establish or secure a session. However, when you opt into CloudKit-based pairing, a small set of pairing metadata is stored in Apple's iCloud (see "CloudKit pairing metadata" below). We treat this as data that leaves your device, even though Apple operates the storage.
The App operates as a peer-to-peer remote desktop. Video, audio, and input data flows directly between Reach Remote and Reach Host over an authenticated, encrypted connection and never touches Reach-operated infrastructure.
When you choose to pair using CloudKit (so the viewer can find your host on the public internet without typing a 6-digit code each time), the host publishes a small CKRecord into the public CloudKit database of your Reach iCloud container. The record is keyed by your 6-digit pairing code, so it is not user-discoverable without that code, but the database scope itself is public — not your private container.
The record contains:
This data is used only to set up a connection between your devices. It is not used for advertising, profiling, or analytics, and it is never shared with parties other than Apple's CloudKit infrastructure.
Reach Remote requests camera access only for QR-code scanning during first-time pairing (to fill in the pairing code). QR-code processing is done locally by iOS Vision frameworks. The camera feed is never recorded, stored, or transmitted.
Reach Remote uses local network access to discover hosts running Reach Host via Bonjour/mDNS. Required for LAN connectivity. Without it, only a manually configured direct WAN path can work.
Reach Host requests macOS Screen Recording permission to capture the selected display for streaming to your paired viewer. Optionally, it requests Microphone permission, which macOS uses to gate system audio capture on macOS 14+ via ScreenCaptureKit — no microphone input is actually recorded. Capture happens locally and is transmitted only to authenticated viewers.
To power the cursor-handle UI in the viewer's Direct Touch mode, Reach Host can send the position of your Mac's cursor (a normalized coordinate, the display it belongs to, and a timestamp) to the connected, authenticated viewer. The data is end-to-end encrypted over the same QUIC session as video and input; only the paired viewer can read it. It is never logged, stored, or sent to any third party.
This feature is on by default. You can turn it off any time in Reach Host → Advanced → Cursor Telemetry → "Share cursor position with viewer". When turned off, the host stops sending cursor position and explicitly tells supported viewers to clear any cursor handle that may be on screen.
Reach Host checks for new versions on launch and periodically while running, using the Sparkle update framework. Update checks make a standard HTTPS request to our update feed; your IP address and a User-Agent header are visible to that endpoint as with any HTTPS request, but no Reach account, telemetry, or identifying payload is sent. The viewer (Reach Remote) updates through the App Store and is governed by Apple's standard App Store policies.
The App does not include any analytics, tracking, advertising identifiers (IDFA), fingerprinting, cookies, or third-party SDKs that profile you. We do not use Crashlytics, Sentry, Google Analytics, or similar services.
Reach stores the following locally on your devices:
All local data is removed when you uninstall the respective app.
Reach does not share data with any third-party services for advertising, analytics, or profiling. The third-party services touched by Reach are limited and scoped:
Reach-operated infrastructure does not collect, store, or relay screen, audio, or input session content.
Reach is not directed at children under 13 and does not knowingly collect data from children. Pairing metadata is used only for connection setup and is not used for advertising, profiling, or tracking.
Direct path: All traffic between Reach Remote and Reach Host on the direct LAN or WAN path is end-to-end encrypted with TLS 1.3 over QUIC and protected by certificate pinning established during pairing. A viewer can only connect to a host whose certificate fingerprint it has previously trusted (or which has been explicitly re-paired). We cannot decrypt this traffic.
Last updated: the date at the top of this page reflects the most recent change to this policy. We will update it whenever the trust model or data flow changes.
We may update this policy from time to time. Changes will be posted on this page with an updated date at the top.
If you have questions about this privacy policy, contact: [email protected].