What H Company Receives
| Mode | What can be sent to H Company | What HoloDesktop CLI does not upload |
|---|---|---|
| Hosted models | Task text, rendered instructions, user-provided context, action history, and visual observations needed by H Company’s hosted model service. | Your local run artifact directory, local runtime logs, and local files that are not part of the task context. |
| Local model endpoint | Nothing for model inference, if the endpoint is running on your own machine. | Task text, screenshots, model inputs, local run artifacts, and local runtime logs. |
| Remote model endpoint you control | The remote endpoint receives the model inputs instead of H Company. | H Company still does not receive the model inference payload from that run. |
The privacy boundary follows the model endpoint. Hosted mode sends task-relevant inference inputs to H Company. Local mode sends them to the endpoint you configure.
What HoloDesktop CLI Can See
During a run, HoloDesktop CLI observes the visible desktop so it can decide what to do next. Observations can include anything visible on screen:- apps and browser tabs;
- local documents;
- chat or email content;
- account names and workspace names;
- file paths;
- permission dialogs;
- secrets or personal information visible in the foreground.
Anything visible on screen can become task context. Close unrelated tabs, documents, chats, password managers, and admin consoles before a sensitive run.
What H Retains
HoloDesktop CLI itself does not upload a recording of your desktop, your local run artifacts, or your local runtime logs to H Company storage. When you use hosted models, H Company’s hosted model service receives the task-relevant inference payload for the run. That payload can include text instructions, contextual files or memories included by HoloDesktop CLI, tool and event history, and visual observations of the desktop. Retention for hosted model requests is governed by the Models API terms and the agreement for your H Company organization. When you use a local model endpoint running on your own machine, H Company does not receive the task text, screenshots, or model inputs for that run.Local Artifacts
HoloDesktop CLI keeps diagnostic artifacts on your machine so you can inspect and debug runs. Those artifacts can include task text, event history, screenshots, model outputs, tool results, local paths, and app state that appeared during the run. These files are local diagnostics, not an analytics upload. Review and redact them before sharing with H Company, posting in an issue, or attaching them to support threads. For exact paths, see Paths and files. For event structure, see Debug a failed run.Host Integrations
When HoloDesktop CLI runs through MCP, ACP, or a skill, the host decides when to call it and what task text to pass into the run. Before enabling a host integration, check:- whether the host asks before tool calls or can invoke tools automatically;
- whether the configuration is project-local or global;
- whether the prompt gives the CLI permission to operate unrelated apps;
- whether the visible desktop contains information outside the task.
Practical Checklist
Before a sensitive run:- Close unrelated windows and tabs.
- Use local model mode if task context should not go to H Company’s hosted model service.
- Use a dedicated browser profile for sensitive web-app testing.
- Keep prompts narrow and task-specific.
- Review local artifacts before sharing them.
- Rotate credentials if you accidentally publish logs, screenshots, or run artifacts.