Support

Poor Devs OÜ · farcrew

Write to support@farcrew.app. It reaches a human, and one usually answers within two working days. There is no phone line and no chat widget — this is a small operation, and email is the whole of it.

What to put in the mail

Anything that lets the problem be found without a round trip:

• the machine's name or id (Settings shows both, e.g. m-1a2b…);
• what you did, what happened, and what you expected instead;
• the exact wording of any message the app showed;
• where you were — the app on iOS, the web console, or a paired box;
• for a daemon problem, the output of farcrewd status.

Never send a password, a recovery code or a daemon token. We will never ask for one, and no support question needs it.

Things you can settle yourself

• A machine reads offline. The daemon is not connected. On the box: systemctl status farcrewd (or farcrewd status), and check it can reach api.farcrew.app over TLS.
• Pairing a new box. curl -fsSL https://get.farcrew.app/install.sh | sudo sh, then farcrewd pair CODE with the code the console gives you.
• Lost the passkey. Sign in with a recovery code — that is what they are for. Lost those too, and the account cannot be recovered by anyone, including us: the keys are yours alone.
• Subscription, card, invoices. Manage them in the web console at my.farcrew.app, which opens Stripe's own billing portal.
• Deleting the account. Settings → Danger zone. It removes the account, its machines, passkeys, sessions and saved workspaces, and cannot be undone.
• A warning about a changed machine fingerprint. Take it seriously: the app pins each machine's key the first time it sees it, and a change means either the daemon's identity was rebuilt or someone is in the middle. Write to us before dismissing it.

Reporting something security-related

Mail support@farcrew.app with "security" in the subject and we will come back to you quickly. Please give us a reasonable window to fix an issue before publishing it. The terminal stream is end-to-end encrypted and the relay holds no key for it — if you have found otherwise, we very much want to know.

The rest

The documentation covers installing the daemon, pairing, port previews and the agent hooks. The privacy policy says what we hold and what we cannot read; the terms are the agreement itself.