PRIVACY

DeskPet privacy notes

Last updated: May 2026

1. Core principle

DeskPet is a local-first desktop AI workflow companion. The goal is not to push your working life into the cloud, but to make AI tools, task rhythm, wait states, and intervention points visible on your own desktop.

The default rule is simple: core workflow signals should stay local first, and users should be able to understand what DeskPet sees, what it does not see, and when explicit human confirmation is required.

2. What DeskPet may sense

• Local activity signals from AI tools such as Cursor, Claude Code, Codex, OpenCode, and Trae.
• Task state, wait state, risk prompts, and suggested next actions.
• Themes, character forms, skins, language, and workspace preferences that you explicitly configure.
• Minimal LAN-sharing information only when you intentionally enable LAN features.

3. What DeskPet should not do by default

• It should not upload your core workflow data to remote servers by default.
• It should not silently send your code, private docs, or task context to unknown third parties.
• It should not pretend to complete high-risk external actions without visible confirmation semantics.
• It should not behave like a cute black box that secretly acts on everything for you.

4. Storage model

The current product direction stores primary state locally, including but not limited to:

• App configuration and user preferences
• Local history and workflow state restoration data
• Custom companion skins and local visual assets

DeskPet should make its boundaries understandable instead of hiding critical state in invisible remote systems.

5. Permissions and boundaries

• File access: for local resources, skins, and configuration management.
• Network access: only when needed for clearly defined release sources, update sources, or LAN capabilities.
• Auto-start: optional capability and should never be forced silently.

6. Open source and auditability

DeskPet is publicly hosted on GitHub . Users should be able to inspect the release chain, site copy, and app behavior instead of relying on vague trust statements.

7. Future changes

If monitoring boundaries, release behavior, or data-handling policy changes materially, this page should change with it rather than hiding the shift in a release note.

8. Contact

Questions about DeskPet privacy boundaries, release provenance, or behavior policy can be raised through GitHub Issues .