Direct beta · Privacy
Your Mac.
Your connection.
This policy explains the Farhand Direct beta for iPhone, iPad and Mac, and farhand.app. The beta uses your local network or a private VPN you configure. Farhand’s cloud remote-session relay is disabled.
Updated 13 October 2026. Spørsmål på norsk er velkomne på [email protected].
Who is responsible?
Farhand is provided by Magnus Aadlandsvik Skaflestad, Norway. For privacy questions, support or requests about data we hold, contact [email protected].
Remote sessions and pairing
Screen content, pointer and keyboard input, clipboard content and commands travel between your paired devices through Farhand’s authenticated, encrypted connection. Farhand does not operate a server that stores or views your Direct remote session. The person controlling a paired device can access the Mac within the permissions you grant.
Pairing identities, access credentials and saved connection addresses are held on your devices. Pairing secrets and saved API keys use the system Keychain. Device names, permissions and connection history are used to identify and manage your paired devices. Local Mac logs can contain device names, IP addresses and operational events. They are not automatically uploaded to Farhand.
Face ID and Touch ID are handled by Apple’s system authentication. Farhand receives the authentication result, not your face or fingerprint data. Any saved Mac-unlock credential stays in protected storage on your devices.
Your VPN and network providers
Tailscale is a separate service with its own account, network metadata and privacy practices. Other VPN providers have their own policies. Farhand does not receive your VPN account password. Both devices must have an authorized network route and a valid Farhand pairing. Network providers can process connection metadata even though the Farhand session content is encrypted.
See Tailscale’s privacy policy. Farhand is an independent app, not a Tailscale product.
Optional speech recognition
Dictation is optional. You select a provider, grant microphone access and accept the app’s disclosure before using an external provider. The selected service receives the audio needed to transcribe it. A personal API key links requests to your account with that provider; using your own key does not make the processing anonymous.
- Apple: recognition runs on the device where supported; otherwise audio may be sent to Apple. Apple’s system permissions, settings and speech privacy information apply.
- Soniox: audio is sent directly to its real-time service in the selected region. Its published policy says real-time audio and transcripts are processed transiently, unless storage is requested or otherwise agreed. Account, usage and security metadata are separate. See Soniox’s policy.
- OpenAI: audio is sent directly to its Realtime transcription API. Standard API abuse-monitoring retention can be up to 30 days; approved account-specific controls can differ. See OpenAI’s API data controls.
Farhand does not receive a copy of your audio on a developer-operated speech server. Transcribed text and dictation history can remain on your device and be sent to the paired Mac when you use it. Stop dictation, change provider, remove the stored API key or revoke microphone permission to stop further use. Provider-side account data must be managed with that provider.
Wake requests and notifications
Configured wake requests and notifications use the selected ntfy server, which may be ntfy.sh. This is separate from the encrypted remote-screen session and can remain enabled in Direct beta. The server receives topic identifiers, timing, network metadata and the message sent to it. Wake requests contain signed control data; notification text may contain app or task information. Do not put sensitive content in notification messages.
The public ntfy.sh service documents a default message cache of 12 hours; self-hosted settings and other server operators can differ. See ntfy’s privacy information. Disabling these features or using your own server changes future processing, but does not instantly remove a provider’s existing records.
Apple, TestFlight and purchases
Apple handles TestFlight distribution and in-app purchases. Farhand uses purchase entitlement information to unlock the corresponding features. Farhand does not receive your card number. Apple’s privacy information applies to its services.
During the beta, Apple can make crash diagnostics, test usage and feedback available to the developer. Feedback you submit may include your contact information, comments and screenshots. Review screenshots before sending them: they may show private content from your Mac. These reports are used to investigate problems and improve Farhand, not for advertising.
Website, downloads and support
Cloudflare hosts farhand.app and update downloads. Requests expose ordinary network information such as IP address, requested resource and time to the hosting provider for delivery and security. App update checks and optional voice-model catalog requests also contact Farhand’s hosting. They do not upload screen content or pairing secrets. See Cloudflare’s privacy policy.
If you join the website’s interest list, we store your email address, language, signup time and consent record in Cloudflare D1 to follow up your request. A daily IP-derived value limits abuse; expired rate-limit records are cleaned up as new signups are processed. The list is not linked to your paired devices. Contact us to withdraw consent or remove a signup.
If you contact support, we receive your email address and what you choose to send. We use it to answer your request and keep necessary correspondence while the issue is followed up. Please do not send passwords, API keys or pairing QR codes. We do not sell personal data or use Farhand session data for advertising.
Storage, choices and your rights
Local app history, settings, recordings and exported images remain under your control. Use the app’s deletion controls for items you want to remove. Revoke a paired device on the Mac to remove its remote access; use “Forget pairing” only when you intend to remove that pairing. Uninstalling an app does not necessarily remove Keychain records, exported files or data held by another service.
We use data needed to provide the features you request and respond to support; optional signup and speech choices rely on your affirmative choices. Security and diagnostic processing supports reliable operation and prevention of abuse. We keep developer-held information only for those purposes and applicable legal requirements. Retention at Apple, Cloudflare, your VPN and speech or notification providers follows their respective services and account settings; processing may occur outside Norway or the EEA.
You can ask about access, correction, deletion, restriction, objection or portability of personal information we hold, as applicable, and withdraw consent for optional processing. Contact [email protected]. We cannot delete data directly from your own devices or another provider’s independent account. You can also contact the Norwegian Data Protection Authority.
Changes to this policy will be posted here with an updated date. A change to the beta’s data handling will be reflected in its disclosures.