Session setup
Open the host on the computer, approve required operating-system permissions, then scan or open the controller link from the second device.
Support - Last updated May 20, 2026
Support for setup, billing, privacy, and security.
Use this page as the public Support URL for marketplace review and customer help. It covers remote session setup, subscription questions, account deletion, privacy requests, security reports, and troubleshooting.
Contact
support@remotecomp.appInclude device type, app version, purchase platform, approximate time, and screenshots only when safe to share.
Billing
Apple subscriptions are managed in Apple account settings. Web subscriptions may be handled through Stripe or the web billing flow.
Account access
For sign-in issues, lost devices, suspicious sessions, or entitlement problems, include the account email and platform used for purchase.
Privacy requests
Use the privacy choices page for access, correction, export, deletion, opt-out, and consent-withdrawal requests.
Account deletion
If an account exists, start deletion from the signed-in account page. Privacy Choices and support remain available alternatives. Apple subscriptions must be canceled separately through Apple.
Security reports
If a device or session looks unfamiliar, stop the host, revoke permissions, rotate credentials, and contact support with timestamps.
Before contacting support
Quick checks
- Confirm the host computer is awake, online, and not blocked by a firewall, VPN, browser permission, or OS privacy prompt.
- Confirm screen recording, accessibility, local network, camera, microphone, and input permissions match the feature you are trying to use.
- Try the direct route first, then check same-network access, private mesh access, firewall rules, or VPN settings if peer-to-peer traffic is blocked.
- Check that both host and controller are on supported app versions and that the browser allows WebRTC.
- If billing access is missing, restore purchases in the app or include the Apple receipt, Stripe receipt, or transaction ID in your request.
- For privacy requests or support-assisted deletion, include the account email and country or state where you live so the request can be routed correctly.
Response targets
- Security issue
- Priority review
- Billing issue
- 1-2 business days
- Privacy request
- Legal deadline
- General support
- 2-3 business days
Response targets are operational goals, not guaranteed resolution times. Security and privacy requests may require verification.
Mac account fixes
Known Mac sign-in and controller checks
Browser sign-in finishes but Mac stays signed out
Sign in from the Mac account row, then use the signed-in Open Remote Comp handoff. Current Mac builds use remotecomp://account because existing Mac installs already claim that callback scheme.
RC_LOCAL_ACCOUNT_ROUTE_FORBIDDEN
inactive-entitlement or missing account owner diagnostics, not proof gates
Same-account Local Network authorization requires valid sessions for the same account on both devices; it does not require active paid entitlement or a pre-existing owner record. Confirm both devices use the same account, then retry. If a session is rejected, sign in again; if the account API is unavailable, retry after service is restored. A successful Host proof redemption caches the local owner id, even when diagnostics show accountOwnerPresent=false or entitlement.active=false. Manual local pairing remains the fallback while sign-in or the proof exchange is repaired.
RC_LOCAL_ACCOUNT_ROUTE_MISSING or 404
If a peer returns HTTP 404 for /v1/local/account-direct-access or does not advertise localAccountDirectAccess, install the current Mac agent on that host, quit stale RemoteCompMacAgent processes, and confirm macOS is running ~/Applications/RemoteCompMacAgent.app. The empty compatibility probe should return HTTP 400, 401, or 403, not 404.
RC_LOCAL_HOST_NOT_LISTENING
Mac pings, but Remote Comp is not listening
If the host Mac is awake and responds to ping but /v1/local/device times out or returns HTTP 000, open Remote Comp from ~/Applications/RemoteCompMacAgent.app on that Mac, confirm incoming connections are allowed, confirm macOS Firewall's Block all incoming connections setting is off and RemoteCompMacAgent is allowed, quit stale RemoteCompMacAgent processes after updates, then rerun diagnostics from both Macs.
Local Network peer is on an older Mac agent
agentVersion older than latest manifest
If diagnostics say a peer is reachable but older than the public Mac update manifest, update that host first. Install from /api/download/mac, quit any stale RemoteCompMacAgent process, reopen ~/Applications/RemoteCompMacAgent.app, then rerun diagnostics on host and controller Macs. This is not a Wi-Fi, Screen Recording, or Accessibility failure.
Mac-to-Mac controller opens too small
The route, account, and settings menu should stay compact. Only the live desktop control surface should expand to a near-full-window Mac controller.
On Mac, run scripts/diagnose-mac-agent-state.sh. Share the warning name, not private tokens or screen contents.
Contact support
Send a support request
Legal and account controls