Legal

Terms of service

These terms cover the PRCHD Mac host, the phone and tablet applications, and the Slack and webhook surfaces the host can be connected to.

Last updated August 31, 2026

Agreement

These terms are between you and Velzosoft (“we”, “us”). They cover the PRCHD Mac host, the PRCHD phone and tablet applications, and the PRCHD service that carries host identity, push notifications, and sealed webhook deliveries — together, “the software”. By installing or using the software, you agree to these terms. If you do not agree, do not use it.

What PRCHD provides

The software runs coding agent CLIs on a Mac you control and gives that machine two remote controls: a phone app over your own private network, and a Slack bot in a Slack workspace you control. It can also start stored recipes on a schedule or from a webhook. It does not provide an agent model, a private network, or a Slack workspace. You supply and operate any Claude Code, Codex, Grok, Tailscale, GitHub, Slack, or other third-party service you choose to connect.

Your responsibility for agent and terminal actions

The software lets an agent read, write, execute, and commit on your Mac, and lets a paired phone run arbitrary commands there. You are responsible for the instructions you give, the Plan, Act, or Work mode you select, the changes you merge, the commands you run, and the devices you pair.

  • Review changes before they reach a base branch or external repository
  • Keep backups and version-control history appropriate for your work
  • Secure paired devices and revoke any device you no longer control
  • Protect credentials and confidential material on the Mac
  • Confirm that your use follows employer, client, and repository policies

Agents can make incorrect changes and produce confident but wrong explanations. Diffs, commands, and explicit close actions help you review the result; they do not replace your judgment.

Operating a shared host

A host may be installed on a machine several people reach through Slack. Whoever installs and administers it is the operator, and the operator’s decisions are the access model: there are no PRCHD accounts, roles, or per-person permissions. Membership of a bound channel is the entire grant, and every member of it has the same reach.

  • Bind a channel only when everyone who can post in it may see code from that project — an answer may quote it
  • Enable runs only on a private channel you intend to be able to start work
  • Keep channel membership current; removing someone from the channel removes their access
  • Confirm that binding a channel is permitted by your employer, client, and repository policies

The Slack app is your own custom app, installed into your Slack workspace from a published manifest with tokens you hold. You are responsible for installing it, for the tokens, and for what is posted into your Slack workspace.

Webhook triggers

A trigger accepts deliveries from a service you point at it and starts a stored recipe you wrote. The verifier that decides whether a delivery is authentic is your own code, running in its own short-lived process with the obvious globals removed. That isolation is a contract to catch accidents, not a security boundary against code you did not write. You are responsible for the verifier you write, for the recipe a trigger fires, and for the data a third party sends to a URL you gave them.

Acceptable use

You agree not to use the software to:

  • Access a machine, network, repository, or account without authorization
  • Break applicable law or the terms of a connected service
  • Distribute malware or attack, disrupt, or abuse a system
  • Interfere with the software’s security, pairing, or update mechanisms

Third-party services

The software interoperates with services we do not control, including Anthropic’s Claude Code, OpenAI’s Codex, xAI’s Grok, Tailscale, GitHub, Slack, any tool server you configure for an agent, Apple notification services, Google notification services, and the processors named in the privacy policy. Their terms govern your relationship with them. We are not responsible for their behavior or availability.

Your content and local work

You retain responsibility for repositories, prompts, attachments, worktrees, branches, command output, and other content on your devices. PRCHD does not claim ownership of that content. Removing the software does not remove your responsibility to preserve or clean up local worktrees and processes.

Updates and changes

The Mac host can check for and install signed updates. Updates may add, change, or remove functionality. Compatibility with agent CLIs, operating systems, and third-party services can change when those systems change.

No warranty

To the extent allowed by law, the software is provided “as is” and “as available”, without express or implied warranties, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant uninterrupted or error-free operation or preservation of a particular piece of work.

Limitation of liability

To the maximum extent allowed by law, we are not liable for indirect, incidental, special, consequential, or punitive damages, or for loss of data, code, revenue, or business arising from use of the software, including actions taken by an agent or paired device. Nothing here excludes liability that cannot legally be excluded.

Ending use

You may stop using the software at any time by uninstalling it and revoking paired devices. Before uninstalling, review local worktrees, branches, running processes, and any work you want to preserve.

Changes to these terms

The updated date at the top changes when these terms change. Continued use after an update means you accept the revised terms.

Contact

Questions about these terms: hello@prchd.app.

Continue

Download PRCHD →