Privacy Policy
This policy explains what information Jiro processes and how it is used to operate coding-agent sessions, integrations, and related dashboard features.
Last updated: July 14, 2026
Information Jiro Processes
Jiro processes information needed to authenticate users, connect repositories and integrations, run coding-agent sessions, and display session state in the dashboard.
- Account profile details from authentication providers, such as GitHub identity.
- Workspace, repository, installation, and integration configuration metadata.
- Prompts, session messages, tool output, generated artifacts, and runtime logs.
- Secrets and tokens that users or workspace admins configure for connected services.
How Information Is Used
Jiro uses this information to provide access control, create and restore sandboxed development environments, stream session progress, route notifications, troubleshoot failures, protect the service, and maintain product reliability.
Service Providers and Integrations
Jiro may send relevant information to configured infrastructure and integration providers such as GitHub, Slack, Linear, OpenAI, Cloudflare, Modal, Daytona, and other services selected by the workspace operator. Jiro does not sell personal information.
Retention and Control
Jiro retains operational records for as long as needed to provide the service, satisfy security and audit needs, and support the workspace. Users can contact the workspace admin or Jiro operator to request access, correction, export, or deletion of their information.
Contact
For privacy questions or data requests, contact thezachzhao@gmail.com.