Support
Setup help, pairing/revocation, privacy requests, and security reports.
Common checks
Device offline: confirm the user-level device service is running and can reach the relay over HTTPS; no inbound port is required.
Request denied: unapproved workspaces, unsafe paths, unsupported commands, foreign devices, expired credentials, and policy violations intentionally fail closed.
Durable task pending: preserve the original operation/task identity and use status/result recovery rather than starting duplicate work.
Contact process
Farah Relay is published and developed by Abdelhamid Farah. Use the public farahdigital.com contact form and begin the subject with Farah Relay. Include the affected feature, approximate time, device label (never its credential), and a short description. Do not send access tokens, device credentials, OAuth codes, passwords, private keys, or unredacted secret-bearing logs.
Security reports
Use the same contact process with subject Farah Relay security and provide non-destructive reproduction steps. Do not exploit systems you do not own.
Privacy/deletion
Use subject Farah Relay privacy. We may need to verify the GitHub identity associated with the relay account before acting on account-data requests.
Service level
Farah Relay is provided on a best-effort basis. There is no guaranteed support-response or uptime SLA.