Privacy Policy

Jiranimo Privacy Policy

Jiranimo is a developer tool made of a Chrome extension and a local server. It is designed to work primarily on your machine and inside your own Jira, GitHub, and Claude workflows. This page explains what data Jiranimo handles, where that data goes, and what you control.

Last updated: April 7, 2026 Project: Jiranimo Source: github.com/Niryo/Jiranimo

Summary

Jiranimo does not run a central cloud backend for the extension itself. The Chrome extension runs in your browser and connects to a local server that you run yourself. Jiranimo reads Jira issue data needed to perform the actions you request, stores local configuration and task state on your device, and may send task content to third-party services only when those services are part of your chosen workflow.

In practical terms: the extension talks to Jira pages you visit and to your own local Jiranimo server. The local server may then interact with Claude, GitHub, or screenshot hosting if you choose to use those features.

Data We Handle

Depending on the feature you use, Jiranimo may handle:

  • Jira issue metadata such as issue key, summary, description, labels, comments, status, subtasks, linked issues, attachments, assignee, reporter, and issue URL.
  • Per-board extension settings, such as the configured workflow columns and the local server URL.
  • Local task state, including queued or completed runs, progress updates, local log files, PR links, and related metadata.
  • GitHub pull request information if you use PR creation, PR updates, or review-comment handling features.
  • Screenshots and screenshot instructions if you use the optional screenshot workflow.

How Data Is Used

Jiranimo uses this data to:

  • Show AI controls directly inside supported Jira board pages.
  • Read the Jira issue you select so the local server can prepare implementation context.
  • Track task progress and update the board state or comments when a run completes.
  • Remember your local settings so you do not need to reconfigure each board every time.
  • Optionally continue work on an existing PR, read GitHub review comments, or attach screenshots when you use those features.

Where Data Is Stored

The extension stores configuration locally in Chrome storage. The local Jiranimo server stores task state and logs on your machine, by default under your user home directory in a .jiranimo folder. The exact location can be changed through local server configuration.

  • Extension settings are stored locally in your browser.
  • Server task state is stored locally on disk.
  • Server log files are stored locally on disk.

Jiranimo does not use its own hosted database for this extension workflow.

Third-Party Services

Jiranimo can work with third-party services that you already use. Data is sent to those services only as part of the features you trigger.

  • Atlassian Jira: the extension runs on Jira board pages and reads issue data through Jira APIs using your existing Jira session.
  • Anthropic / Claude Code: if you run implementation tasks, your local server may send task context and repository-related prompts to Claude Code according to your local setup.
  • GitHub: if you use PR creation, PR updates, or GitHub review comment features, the local server may use your local GitHub tooling and send relevant PR data to GitHub.
  • ImgBB: if you use the optional screenshot upload tool, screenshot images may be uploaded to ImgBB.

Each third-party service has its own terms and privacy practices. Your use of those services through Jiranimo is also subject to their policies.

Sharing

Jiranimo is not designed to sell personal data or share data with advertising networks. Data is shared only when needed to carry out the workflow you initiate, such as sending task context to Claude Code, posting updates to Jira, reading or updating a GitHub pull request, or uploading a screenshot when you explicitly use that feature.

Your Controls

  • You can remove the extension at any time.
  • You can clear extension settings from Chrome and remove board configurations from the options page.
  • You can delete local Jiranimo state and logs from your machine.
  • You control whether the local server is running and whether you use GitHub, Claude, or screenshot-related features.
This policy describes the current open-source implementation of Jiranimo. If you distribute a modified version or run Jiranimo with additional services, review this policy and update it to match your actual deployment.

Contact

For questions about this policy or the project, open an issue in the Jiranimo GitHub repository.