Reach the right RemoteHands channel.

Email [email protected] for questions about venue onboarding, worker or entertainer profiles, public gig listings, account access, privacy requests, or RemoteHands developer resources. You can also contact the official RemoteHands LINE account. Include the account role and the public URL or reference identifier involved, but do not send passwords, authentication tokens, payment credentials, identity documents, or other sensitive material in an initial message.

For an API or MCP question, first review the RemoteHands developer index. A useful support report names the endpoint or MCP tool, operation ID, request time, HTTP or JSON-RPC status, and a redacted example response. Remove bearer tokens, cookies, private venue notes, worker contact details, and personal data before sending diagnostics. Public API errors include machine-readable codes and hints intended to make this triage easier.

Requests involving private account information may require a signed-in workflow or other reasonable verification before RemoteHands can act. This protects venue, worker, and entertainer data from unauthorized disclosure or changes. Read the privacy notice for the categories of information processed and the available request channels.